[
https://jira.codehaus.org/browse/MENFORCER-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=327935#comment-327935
]
Robert Scholte commented on MENFORCER-156:
------------------------------------------
MENFORCER-42 is an important improvement, it seems to have a side-effect: even
though dependencies are now calculated instead of gathered, the artifact is
still marked as {{resolved}} afterwards. The assembly-plugin checks if the
artifacts is resolved, otherwise i'll search the local and remote repositories
for the files. ( The NPE is caused by the {{artifact.getFile()}} ).
I think the assumption of the assembly-plugin is correct, so I have to figure
out why the new [Maven Dependency
Tree|http://maven.apache.org/shared/maven-dependency-tree/] marks those
artifacts as resolved.
> Upgrading maven-enforcer-plugin from 1.2 to 1.3 breaks maven-assembly-plugin
> ----------------------------------------------------------------------------
>
> Key: MENFORCER-156
> URL: https://jira.codehaus.org/browse/MENFORCER-156
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: Ubuntu 12.04 fully patched / Maven 3.0.5 / Oracle Java
> 1.7.0_25
> Reporter: Wolf Geldmacher
> Assignee: Robert Scholte
> Attachments: extjars.xml, pom.xml
>
>
> After upgrading m-e-p from 1.2 to 1.3 the maven-assembly-plugin generates the
> following error:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.4:single (assemble) on
> project extjars: Execution assemble of goal
> org.apache.maven.plugins:maven-assembly-plugin:2.4:single failed.
> NullPointerException -> [Help 1]
> Downgrading to m-e-p 1.2 makes the assembly work again.
> Sample pom & assembly that expose the error attached.
> When called via:
> mvn -Dplugins.maven-enforcer-plugin.version=1.2
> a zip file is generated as expected, when called via
> mvn -Dplugins.maven-enforcer-plugin.version=1.3
> (or without argument) you will get the NPE.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
