[
http://jira.codehaus.org/browse/MNG-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108302
]
Michael Lee commented on MNG-3086:
----------------------------------
We have also hit this problem in our environment. All of our projects have a
mix of internal and external dependencies
Running: "mvn clean install" on Project A caused the problem. Running "mvn
dependency:resolve" also causes the problment
In our case we isolated our problem to a change in the version dependencies of
our internal project
WORKING CASE:
Project A depends directly on exact version 1.2.4 of Project B
Project A depends directly on exact version 1.1.2 of Project C
Project C depends directly on exact version 1.2.4 of Project B
i.e. Project A, and it's dedendency C, both agree on the specific version of B
required.
FAILING CASE 1:
We build a new version of Project B to make it vesion 1.2.5
We change the Project A dependency to depend on version 1.2.5 of Project B
Project A depends directly on exact version 1.1.2 of Project C
Project C continues to depend directly on exact version 1.2.4 of Project B
The difference in version now triggers the getTrail error
FAILING CASE 2:
We change the Project A dependency to depend on version 1.2.5 of Project B
We update Project C to depend on range of Project B i.e. [1.2.5,) and we
rebuild Project C to create version 1.1.3 (i.e. new build just to change the
dependency)
We update Project A to depent directly on exact version 1.1.3 of Project C
I was expecting this to work, but it still triggers the getTrail exception
TEMPORARY RESOLUTION
Building on failing case 2, I:
Updated Project A to depend on a range of Project B i.e. [1.2.5,) instead of
1.2.5
Updated Project A to depend on a range of Project C i.e. [1.1.3,) instead of
1.1.3
This now works correctly.
Whoever gets assigned to this bug - keep up the great work.
> NullPointerException in ResolutionNode.getTrail(ResolutionNode.java:136)
> ------------------------------------------------------------------------
>
> Key: MNG-3086
> URL: http://jira.codehaus.org/browse/MNG-3086
> Project: Maven 2
> Issue Type: Bug
> Components: Errors
> Affects Versions: 2.0.7
> Reporter: Thomas Leonard
>
> After upgrading from 2.0.6 to 2.0.7, our build fails with:
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] null
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.artifact.resolver.ResolutionNode.getTrail(ResolutionNode.java:136)
> at
> org.apache.maven.artifact.resolver.ResolutionNode.filterTrail(ResolutionNode.java:211)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:89)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:284)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
> at
> org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Thanks,
--
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
