Clay,
Can you please open a bug report in JIRA [1] with sample project and
content of your user settints.xml file? This seems like a bug in maven,
but I need to be able to reproduce the problem to be certain.
[1] http://jira.codehaus.org/browse/MNGECLIPSE
Clay Graham wrote:
Maven Integration for Eclipse 0.9.3-20080421-2352
are you saying I should update to 0.9.4 using
http://m2eclipse.sonatype.org/update-dev/
>Do you see any exceptions in maven console or in eclipse .log file?
!ENTRY org.maven.ide.eclipse 4 0 2008-05-24 10:45:05.812
!MESSAGE
!STACK 0
java.lang.NullPointerException
at
org.apache.maven.artifact.manager.DefaultWagonManager.matchPattern(DefaultWagonManager.java:875)
at
org.apache.maven.artifact.manager.DefaultWagonManager.getMirror(DefaultWagonManager.java:846)
at
org.apache.maven.artifact.manager.DefaultWagonManager.getMirrorRepository(DefaultWagonManager.java:681)
at
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:431)
at
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:348)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:192)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:82)
at
org.maven.ide.eclipse.internal.project.EclipseArtifactResolver.resolve(EclipseArtifactResolver.java:31)
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:543)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:234)
at
org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:131)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:514)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:138)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:88)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:540)
>What happens if you run Maven->Update Project Dependencies (or
Maven->Update Source Folders if you're on older version of m2e).
nothing changes
>Also, if you just want to create a project, then New->Maven Project
wizard
tried that too behaves the same way.
Thanks!
Clay
Igor Fedorenko wrote:
I just tried this scenario with latest 0.9.4 from SVN and everything
works as expected, i.e. I see Maven Dependencies classpath container
with proper entries.
What m2eclipse version do you have? Do you see any exceptions in maven
console or in eclipse .log file? What happens if you run Maven->Update
Project Dependencies (or Maven->Update Source Folders if you're on
older version of m2e).
Also, if you just want to create a project, then New->Maven Project
wizard is probably an easier way. It is also more used, so it is more
tested and likely to work ;-)
Clay Graham wrote:
Hello All,
Got the indexing working fine thanks.
So when I create a Java project and enable Managed dependencies I
cant see the Maven Managed Dependencies Library under the Package
Explorer Tree, this is kindof a problem because I cant see what is
included in the build path for Eclipse. I try to add it manually but
it tells me I need to set the Maven Project Settings for the project,
doing this does not help.
Secondly when I add a dependency Eclipse doesnt recognize it, so I
have errors all over the place. The dependency is clearly in the POM
though.
Any Ideas?
Clay
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
