[ http://jira.codehaus.org/browse/MNGECLIPSE-157?page=all ]

Tuomas Kiviaho updated MNGECLIPSE-157:
--------------------------------------

    Attachment: NullPointerException.jpg

Eclipse Webtools Editor cranking up.

1.8.2006 11:15:47 EEST: [DEBUG] test:test:jar:0.0.1 (selected for null)
1.8.2006 11:15:47 EEST: [DEBUG]   jaxen:jaxen:jar:1.1-beta-9:compile (selected 
for compile)
1.8.2006 11:15:47 EEST: [DEBUG]     jaxen:jaxen:jar:1.1-beta-6:compile (removed 
- causes a cycle in the graph)
1.8.2006 11:15:47 EEST: [DEBUG]     dom4j:dom4j:jar:1.6.1:compile (selected for 
compile)
1.8.2006 11:15:47 EEST: [DEBUG]     jaxen:jaxen:jar:1.0-FCS:compile (removed - 
causes a cycle in the graph)
1.8.2006 11:15:47 EEST: [DEBUG]     jdom:jdom:jar:1.0:compile (selected for 
compile)
1.8.2006 11:15:47 EEST: [DEBUG]     xom:xom:jar:1.0b3:compile (selected for 
compile)
1.8.2006 11:15:47 EEST: [DEBUG]       xerces:xercesImpl:jar:2.2.1:compile 
(applying version: 2.7.1;applying scope: system)
1.8.2006 11:15:47 EEST: [DEBUG]       xerces:xercesImpl:jar:2.7.1:system 
(selected for system)
1.8.2006 11:15:47 EEST: [DEBUG]       xalan:xalan:jar:2.6.0:compile (selected 
for compile)
1.8.2006 11:15:47 EEST: [DEBUG] While downloading xml-apis:xml-apis:2.0.2
  This artifact has been relocated to xml-apis:xml-apis:1.0.b2.


> Runtime exceptions in embedder should be caught and logged by the plugin.
> -------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-157
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-157
>             Project: Maven 2.x Extension for Eclipse
>          Issue Type: Wish
>          Components: Dependency Resolver
>    Affects Versions: 0.0.9
>            Reporter: Tuomas Kiviaho
>         Assigned To: Eugene Kuleshov
>         Attachments: child.pom, NullPointerException.jpg, parent.pom
>
>
> When inserting a dependency (in my case jaxen) which has a dependency of it's 
> own (xercesImpl) to a project that has a parent which has the same dependency 
> (xercesImpl) already declared (scope was system) a NullPointerException 
> emerges to the WTP xml editors topmost row and classpath container doesn't 
> show anymore any of the dependencies. Workspace log file and console did not 
> show any anomalities. 
> With standalone maven everything work just fine, but with embedder I managed 
> to pull out a following stacktrace
> java.lang.NullPointerException
>       at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:82)
>       at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63)
>       at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:233)
>       at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:211)
>       at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:192)
>       at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildWithDependencies(DefaultMavenProjectBuilder.java:342)
>       at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildWithDependencies(DefaultMavenProjectBuilder.java:289)
>       at 
> org.apache.maven.embedder.MavenEmbedder.readProjectWithDependencies(MavenEmbedder.java:277)
>       at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:53)
> This seemed very familiar and here's a link 
> <http://jira.codehaus.org/browse/MPIR-2> to another project. This issue has 
> been around for quite a while and despite the status FIXED, I don't think 
> this actually is fixed but at least it has been patched couple of times. 
> Workaround: Add an exclusion clause to the new dependency if you have it's 
> dependencies already declared in parent.
> What is left for this project could be a more informative way to express 
> runtime exceptions/errors when embedder fails to do so. NullPointerException 
> in the xml editor gives a wrong expression where the problem actually 
> resides. I'd prefer m2 console over eclipse workspace log. 

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