You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Vonnahme (JIRA)" <ji...@apache.org> on 2015/04/24 21:34:39 UTC

[jira] [Commented] (MENFORCER-156) Upgrading maven-enforcer-plugin from 1.2 to 1.3 breaks maven-assembly-plugin

    [ https://issues.apache.org/jira/browse/MENFORCER-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511599#comment-14511599 ] 

Paul Vonnahme commented on MENFORCER-156:
-----------------------------------------

https://svn.apache.org/viewvc/maven/enforcer/trunk/maven-enforcer-plugin/src/main/java/org/apache/maven/plugins/enforcer/EnforceMojo.java?r1=1493565&r2=1499852&pathrev=1499852&diff_format=h

Did this fix inadvertently break any plugin to the enforcer that used mavenProject.getArtifacts() or analyzed transitive dependencies?  Some internal plugins of ours don't work the same, and neither do things like BanDuplicateClasses from the extra-enforcer-rules since this was put in.  Right now we're sticking to the 1.2 version of the enforcer.

This could also be the cause of MENFORCER-194?

Is there some way for enforcer plugins to override this?  Or is there another way to fix this issue, and you could add 
{code:java}
requiresDependencyCollection = ResolutionScope.TEST 
{code}
back to the enforcer mojo?  Or is 'DependecyGraphBuilder' now the only way to get transitive dependencies?



> Upgrading maven-enforcer-plugin from 1.2 to 1.3 breaks maven-assembly-plugin
> ----------------------------------------------------------------------------
>
>                 Key: MENFORCER-156
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-156
>             Project: Maven 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
>            Priority: Blocker
>             Fix For: 1.3.1
>
>         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 was sent by Atlassian JIRA
(v6.3.4#6332)