You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "David Smiley (JIRA)" <ji...@codehaus.org> on 2006/05/19 16:25:40 UTC

[jira] Created: (MWAR-42) relative path of webResources in parent pom not anchored correctly when run from parent

relative path of webResources in parent pom not anchored correctly when run from parent
---------------------------------------------------------------------------------------

         Key: MWAR-42
         URL: http://jira.codehaus.org/browse/MWAR-42
     Project: Maven 2.x War Plugin
        Type: Bug

    Versions: 2.0    
    Reporter: David Smiley
    Priority: Minor


In my parent POM, in pluginManagement, I have:
{quote}
          <plugin>
               <artifactId>maven-war-plugin</artifactId>
               <configuration>
                  <webResources>
                     <resource>
                        <directory>src/webapp</directory>
                     </resource>
                  </webResources>
               </configuration>
            </plugin>
{quote}
If I run {{mvn package}} when at the child module with war packaging, this works fine.  But when I run that at the parent module, the {{src/webapp}} path is not interpreted as relative to the child module being built, as it should (I think).  By comparison, when I configure my source directory, test source directory, or resources in the parent pom using a relative path, they are correctly interpreted as relative to the module being built, regardless of wether I run it from the parent or child module.

As a work-around, I am forced to prefix the relative path with ${basedir}, which should not be necessary.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (MNG-2382) relative path of webResources in parent pom not anchored correctly when run from parent

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-2382?page=all ]

John Casey updated MNG-2382:
----------------------------

    Fix Version: 2.0.5

> relative path of webResources in parent pom not anchored correctly when run from parent
> ---------------------------------------------------------------------------------------
>
>          Key: MNG-2382
>          URL: http://jira.codehaus.org/browse/MNG-2382
>      Project: Maven 2
>         Type: Improvement

>     Versions: 2.0.4
>     Reporter: David Smiley
>     Priority: Minor
>      Fix For: 2.0.5

>
>
> In my parent POM, in pluginManagement, I have:
> {quote}
>           <plugin>
>                <artifactId>maven-war-plugin</artifactId>
>                <configuration>
>                   <webResources>
>                      <resource>
>                         <directory>src/webapp</directory>
>                      </resource>
>                   </webResources>
>                </configuration>
>             </plugin>
> {quote}
> If I run {{mvn package}} when at the child module with war packaging, this works fine.  But when I run that at the parent module, the {{src/webapp}} path is not interpreted as relative to the child module being built, as it should (I think).  By comparison, when I configure my source directory, test source directory, or resources in the parent pom using a relative path, they are correctly interpreted as relative to the module being built, regardless of wether I run it from the parent or child module.
> As a work-around, I am forced to prefix the relative path with ${basedir}, which should not be necessary.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (MNG-2382) relative path of webResources in parent pom not anchored correctly when run from parent

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MNG-2382:
------------------------------

    Component/s: Inheritance and Interpolation

> relative path of webResources in parent pom not anchored correctly when run from parent
> ---------------------------------------------------------------------------------------
>
>                 Key: MNG-2382
>                 URL: http://jira.codehaus.org/browse/MNG-2382
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Inheritance and Interpolation
>    Affects Versions: 2.0.4
>            Reporter: David Smiley
>            Priority: Minor
>             Fix For: 2.0.x
>
>
> In my parent POM, in pluginManagement, I have:
> {quote}
>           <plugin>
>                <artifactId>maven-war-plugin</artifactId>
>                <configuration>
>                   <webResources>
>                      <resource>
>                         <directory>src/webapp</directory>
>                      </resource>
>                   </webResources>
>                </configuration>
>             </plugin>
> {quote}
> If I run {{mvn package}} when at the child module with war packaging, this works fine.  But when I run that at the parent module, the {{src/webapp}} path is not interpreted as relative to the child module being built, as it should (I think).  By comparison, when I configure my source directory, test source directory, or resources in the parent pom using a relative path, they are correctly interpreted as relative to the module being built, regardless of wether I run it from the parent or child module.
> As a work-around, I am forced to prefix the relative path with ${basedir}, which should not be necessary.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MNG-2382) relative path of webResources in parent pom not anchored correctly when run from parent

Posted by "Kenney Westerhof (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-2382?page=all ]

Kenney Westerhof updated MNG-2382:
----------------------------------

    Fix Version/s:     (was: 2.0.5)
                   2.0.6

> relative path of webResources in parent pom not anchored correctly when run from parent
> ---------------------------------------------------------------------------------------
>
>                 Key: MNG-2382
>                 URL: http://jira.codehaus.org/browse/MNG-2382
>             Project: Maven 2
>          Issue Type: Improvement
>    Affects Versions: 2.0.4
>            Reporter: David Smiley
>            Priority: Minor
>             Fix For: 2.0.6
>
>
> In my parent POM, in pluginManagement, I have:
> {quote}
>           <plugin>
>                <artifactId>maven-war-plugin</artifactId>
>                <configuration>
>                   <webResources>
>                      <resource>
>                         <directory>src/webapp</directory>
>                      </resource>
>                   </webResources>
>                </configuration>
>             </plugin>
> {quote}
> If I run {{mvn package}} when at the child module with war packaging, this works fine.  But when I run that at the parent module, the {{src/webapp}} path is not interpreted as relative to the child module being built, as it should (I think).  By comparison, when I configure my source directory, test source directory, or resources in the parent pom using a relative path, they are correctly interpreted as relative to the module being built, regardless of wether I run it from the parent or child module.
> As a work-around, I am forced to prefix the relative path with ${basedir}, which should not be necessary.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Closed: (MNG-2382) relative path of webResources in parent pom not anchored correctly when run from parent

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter closed MNG-2382.
-----------------------------

       Resolution: Duplicate
    Fix Version/s:     (was: 2.2.x (to be reviewed))
         Assignee: Brett Porter

> relative path of webResources in parent pom not anchored correctly when run from parent
> ---------------------------------------------------------------------------------------
>
>                 Key: MNG-2382
>                 URL: http://jira.codehaus.org/browse/MNG-2382
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>          Components: Inheritance and Interpolation
>    Affects Versions: 2.0.4
>            Reporter: David Smiley
>            Assignee: Brett Porter
>            Priority: Minor
>
> In my parent POM, in pluginManagement, I have:
> {quote}
>           <plugin>
>                <artifactId>maven-war-plugin</artifactId>
>                <configuration>
>                   <webResources>
>                      <resource>
>                         <directory>src/webapp</directory>
>                      </resource>
>                   </webResources>
>                </configuration>
>             </plugin>
> {quote}
> If I run {{mvn package}} when at the child module with war packaging, this works fine.  But when I run that at the parent module, the {{src/webapp}} path is not interpreted as relative to the child module being built, as it should (I think).  By comparison, when I configure my source directory, test source directory, or resources in the parent pom using a relative path, they are correctly interpreted as relative to the module being built, regardless of wether I run it from the parent or child module.
> As a work-around, I am forced to prefix the relative path with ${basedir}, which should not be necessary.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MNG-2382) relative path of webResources in parent pom not anchored correctly when run from parent

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-2382?page=comments#action_67558 ] 

Brett Porter commented on MNG-2382:
-----------------------------------

I've moved this from MWAR to MNG, as it's a general issue for Maven. We can only align top level plugin configuration, not elements of subclasses (and besides that, I'm not sure if the alignment would be to the pluginManagement or where it is instantiated - that's also worth checking).

> relative path of webResources in parent pom not anchored correctly when run from parent
> ---------------------------------------------------------------------------------------
>
>          Key: MNG-2382
>          URL: http://jira.codehaus.org/browse/MNG-2382
>      Project: Maven 2
>         Type: Improvement

>     Versions: 2.0.4
>     Reporter: David Smiley
>     Priority: Minor

>
>
> In my parent POM, in pluginManagement, I have:
> {quote}
>           <plugin>
>                <artifactId>maven-war-plugin</artifactId>
>                <configuration>
>                   <webResources>
>                      <resource>
>                         <directory>src/webapp</directory>
>                      </resource>
>                   </webResources>
>                </configuration>
>             </plugin>
> {quote}
> If I run {{mvn package}} when at the child module with war packaging, this works fine.  But when I run that at the parent module, the {{src/webapp}} path is not interpreted as relative to the child module being built, as it should (I think).  By comparison, when I configure my source directory, test source directory, or resources in the parent pom using a relative path, they are correctly interpreted as relative to the module being built, regardless of wether I run it from the parent or child module.
> As a work-around, I am forced to prefix the relative path with ${basedir}, which should not be necessary.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (MNG-2382) relative path of webResources in parent pom not anchored correctly when run from parent

Posted by "Mark Jeffery (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96557 ] 

Mark Jeffery commented on MNG-2382:
-----------------------------------

Isn't this a duplicate of MWAR-79 which has been resolved ?

> relative path of webResources in parent pom not anchored correctly when run from parent
> ---------------------------------------------------------------------------------------
>
>                 Key: MNG-2382
>                 URL: http://jira.codehaus.org/browse/MNG-2382
>             Project: Maven 2
>          Issue Type: Improvement
>    Affects Versions: 2.0.4
>            Reporter: David Smiley
>            Priority: Minor
>             Fix For: 2.0.x
>
>
> In my parent POM, in pluginManagement, I have:
> {quote}
>           <plugin>
>                <artifactId>maven-war-plugin</artifactId>
>                <configuration>
>                   <webResources>
>                      <resource>
>                         <directory>src/webapp</directory>
>                      </resource>
>                   </webResources>
>                </configuration>
>             </plugin>
> {quote}
> If I run {{mvn package}} when at the child module with war packaging, this works fine.  But when I run that at the parent module, the {{src/webapp}} path is not interpreted as relative to the child module being built, as it should (I think).  By comparison, when I configure my source directory, test source directory, or resources in the parent pom using a relative path, they are correctly interpreted as relative to the module being built, regardless of wether I run it from the parent or child module.
> As a work-around, I am forced to prefix the relative path with ${basedir}, which should not be necessary.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira