[ 
http://jira.codehaus.org/browse/MSHADE-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Bentmann updated MSHADE-66:
------------------------------------

    Description: When running the Shade Plugin with Maven 3, the plugin will 
fail to create the dependency reduced POM if the POM inherits from a parent 
that is not installed to the local repo but only available from the project 
checkout via {{<relativePath>}} and that parent is not part of the reactor 
build. The problem being that the plugin creates the dependency reduced POM in 
the {{target}} directory, thereby changing the base directory when it calls the 
project builder. This only works in Maven 2.x because of internal project 
caches which are not present in this form in 3.x  (was: When running the Shade 
Plugin with Maven 3, the plugin will fail to create the dependency reduced POM 
if the POM inherits from a parent that is not installed to the local repo but 
only available from the project checkout via {{<relativePath>}}. The problem 
being that the plugin creates the dependency reduced POM in the {{target}} 
directory, thereby changing the base directory when it calls the project 
builder. This only works in Maven 2.x because of internal project caches which 
are not present in this form in 3.x)

> Creation of dependency reduced POM fails for project with uninstalled local 
> parent using Maven 3
> ------------------------------------------------------------------------------------------------
>
>                 Key: MSHADE-66
>                 URL: http://jira.codehaus.org/browse/MSHADE-66
>             Project: Maven 2.x Shade Plugin
>          Issue Type: Bug
>    Affects Versions: 1.2.1
>            Reporter: Benjamin Bentmann
>            Assignee: Benjamin Bentmann
>             Fix For: 1.2.2
>
>
> When running the Shade Plugin with Maven 3, the plugin will fail to create 
> the dependency reduced POM if the POM inherits from a parent that is not 
> installed to the local repo but only available from the project checkout via 
> {{<relativePath>}} and that parent is not part of the reactor build. The 
> problem being that the plugin creates the dependency reduced POM in the 
> {{target}} directory, thereby changing the base directory when it calls the 
> project builder. This only works in Maven 2.x because of internal project 
> caches which are not present in this form in 3.x

-- 
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


Reply via email to