Re: Extra dependency added to eclipse projects
Barrie Treloar wrote: > On Sat, Mar 12, 2011 at 5:26 AM, John Lussmyer > wrote: > >> We have a large project hierarchy, and use "mvn eclipse:eclipse" to >> generate Eclipse projects for it. >> In 3 of the projects, maven adds a dependency to "spring-2.0.3.jar" - >> which we don't use, and don't have. >> This .jar does not appear in ANY of our pom.xml files. >> "mvn dependency:tree" doesn't find any references to this jar either. >> >> Any ideas on how to get rid of these added, annoying, unwanted, >> dependencies? >> > > eclipse:eclipse doesn't make up dependencies, it must be in there > somewhere. > > try using -X and wading though the console output, that should list spring > and maybe you can see how it is included. > > It's odd that mvn dependency:tree doesn't find your dependency. If he uses M3 then the output may be different to the real deps. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
can I use Maven repository manager outside of Maven?
I'm trying to create an application that will download and use Maven
artifacts outside of Maven. I think that in this case the smartest way would
be to use Maven already existing classes. Can anyone help me with a hint
where to look for?
Would be nice to make it working this way:
Repository rep = new Repository("~/.m2");
Artifact artifact = new Artifact("com.example", "foo", "1.0");
String path = rep.resolve(artifact);
assert path.equals("~/.m2/repository/com/example/foo/1.0/foo.jar");
Thanks!
—
Yegor Bugayenko
NullPointerException in maven assembly plugin
Hi, I am upgrading my projects from maven 2 to maven 3 and most of them are fine. However, there is one project that gives a NullPointerException during the assembly: maven builder waiting mavenExecutionResult exceptions not empty org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.2:single (make zipfile) on project plugin-sdk-assembly: Execution make zipfile of goal org.apache.maven.plugins:maven-assembly-plugin:2.2:single failed. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) 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:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:145) at hudson.maven.Maven3Builder.call(Maven3Builder.java:124) at hudson.maven.Maven3Builder.call(Maven3Builder.java:71) at hudson.remoting.UserRequest.perform(UserRequest.java:114) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:270) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.maven.plugin.PluginExecutionException: Execution make zipfile of goal org.apache.maven.plugins:maven-assembly-plugin:2.2:single failed. at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 27 more Caused by: java.lang.NullPointerException at org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.getLocalFilename(AbstractRepositoryMetadata.java:61) at org.apache.maven.artifact.repository.layout.DefaultRepositoryLayout.pathOfLocalRepositoryMetadata(DefaultRepositoryLayout.java:72) at org.apache.maven.artifact.repository.DefaultArtifactRepository.pathOfLocalRepositoryMetadata(DefaultArtifactRepository.java:129) at org.apache.maven.shared.repository.DefaultRepositoryAssembler.assembleRepositoryMetadata(DefaultRepositoryAssembler.java:487) at org.apache.maven.shared.repository.DefaultRepositoryAssembler.buildRemoteRepository(DefaultRepositoryAssembler.java:231) at org.apache.maven.plugin.assembly.archive.phase.RepositoryAssemblyPhase.execute(RepositoryAssemblyPhase.java:100) at org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:189) at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:409) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) Any idea what might be wrong ? I am using Maven 3.0.3: > mvn --version Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: /home/wdb/Programs/apache-maven-3.0.3 Java version: 1.6.0_24, vendor: Sun Microsystems Inc. Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "2.6.35-27-generic", arch: "i386", family: "unix" regards, Wim
Re: Skin customization error
2011/3/13 Simone Tripodi : > Hi all guys, > I'm developing a new site skin, imported, without altering, the > default-site.vm[1], then installed the artifact locally; when using it > to render the site, the error belowa occurs: > > [ERROR] org.apache.velocity.runtime.parser.ParseException: Encountered > "org" at line 268, column 11. The strangest thing is that there is no "org" character sequence at 268,11, neither in trunk nor in 1.0.x branch. Antonio - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: NullPointerException in maven assembly plugin
Hello, Do you have same exception outside Jenkins ? Thanks -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy 2011/3/14 Wim Deblauwe : > Hi, > > I am upgrading my projects from maven 2 to maven 3 and most of them are > fine. However, there is one project that gives a NullPointerException during > the assembly: > > maven builder waiting > mavenExecutionResult exceptions not empty > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-assembly-plugin:2.2:single (make > zipfile) on project plugin-sdk-assembly: Execution make zipfile of goal > org.apache.maven.plugins:maven-assembly-plugin:2.2:single failed. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > at > org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) > 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:597) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) > at > org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:145) > at hudson.maven.Maven3Builder.call(Maven3Builder.java:124) > at hudson.maven.Maven3Builder.call(Maven3Builder.java:71) > at hudson.remoting.UserRequest.perform(UserRequest.java:114) > at hudson.remoting.UserRequest.perform(UserRequest.java:48) > at hudson.remoting.Request$2.run(Request.java:270) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:619) > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution make > zipfile of goal org.apache.maven.plugins:maven-assembly-plugin:2.2:single > failed. > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > ... 27 more > Caused by: java.lang.NullPointerException > at > org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.getLocalFilename(AbstractRepositoryMetadata.java:61) > at > org.apache.maven.artifact.repository.layout.DefaultRepositoryLayout.pathOfLocalRepositoryMetadata(DefaultRepositoryLayout.java:72) > at > org.apache.maven.artifact.repository.DefaultArtifactRepository.pathOfLocalRepositoryMetadata(DefaultArtifactRepository.java:129) > at > org.apache.maven.shared.repository.DefaultRepositoryAssembler.assembleRepositoryMetadata(DefaultRepositoryAssembler.java:487) > at > org.apache.maven.shared.repository.DefaultRepositoryAssembler.buildRemoteRepository(DefaultRepositoryAssembler.java:231) > at > org.apache.maven.plugin.assembly.archive.phase.RepositoryAssemblyPhase.execute(RepositoryAssemblyPhase.java:100) > at > org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:189) > at > org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:409) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > > > Any idea what might be wrong ? > > I am using Maven 3.0.3: >> mvn --version > Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) > Maven home: /home/wdb/Programs/apache-maven-3.0.3 > Java version: 1.6.0_24, vendor: Sun Microsystems Inc. > Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre > Defa
Re: maven subversion issue
but sir i will have to use file:/// such type of url because my repository is local type -- View this message in context: http://maven.40175.n5.nabble.com/maven-subversion-issue-tp3555224p363.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: can I use Maven repository manager outside of Maven?
I think you should have a look at Aether, which is the repository API which
Maven 3 uses for artifact handling.
[1] is probably a good place to start.
/Anders
[1] http://aether.sonatype.org/
On Mon, Mar 14, 2011 at 09:21, Yegor Bugayenko wrote:
> I'm trying to create an application that will download and use Maven
> artifacts outside of Maven. I think that in this case the smartest way
> would
> be to use Maven already existing classes. Can anyone help me with a hint
> where to look for?
>
> Would be nice to make it working this way:
>
> Repository rep = new Repository("~/.m2");
> Artifact artifact = new Artifact("com.example", "foo", "1.0");
> String path = rep.resolve(artifact);
> assert path.equals("~/.m2/repository/com/example/foo/1.0/foo.jar");
>
> Thanks!
>
> —
> Yegor Bugayenko
>
Re: Using the new maven assembly goals
Hi Rui, I guess You were formally using the 'assembly:assembly' (or 'assembly:directory') goal, right? Those goals where "not inherited by default in multi-project builds" [1], but they "forced Maven to build all included POMs up to the package phase before the assembly is processed" [1]. This is discouraged now, You should assemble Your release artifacts using an additional submodule instead - like discribed in [2]. About Your POM and command invocation: In contrast to using 'assembly:assembly', the 'assembly:single' goal is inherited to the sub modules. The results are: - With inherited=false, the 'assembly:single' execution is missing the assembly descriptor configuration. - With inherited=true, the 'assembly:single' execution cannot find Your assembly descriptor, because it expects a 'release.xml' file in the base directory of each sub module. - You could call 'mvn help:effective-pom -N' to not recurse into the sub modules, but how would You get their artifacts then? One last point: With all my questions I wanted to tell You that You should tend to provide all the information that might be needed to answer Your question. Even in Your last mail I didn't find enough information so that I had to guess what You really want to achieve and how Your assembly descriptor might look like. (And I guess that this lack of information is the main reason why no one else took care of Your question so far) Kind regards Marc [1] http://maven.apache.org/plugins/maven-assembly-plugin/assembly-mojo.html [2] http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Sharing data between archetypes
Hi all, I am currently creating several archetypes and was wondering what the best way is to share data. Some of my archetypes are up to 90% the same and I don't want to copy around all the files they share. Wouldn't be a problem the first time, but of course all updates should then be copied around multiple times as well! So, I was thinking of creating several small projects that contain those files and then have them extracted into the archetype before it is packaged. The only thing I am not sure about (haven't tested my archetypes yet) is whether I can add these JARs as dependencies. What I mean by that is, that I don't want the JAR to be downloaded when someone wants to setup the archetype, because the data would already be inside the created project... Does someone have some experience with this? Am I going in the right direction or is there perhaps another (easier? better?) way to do this? Would the packaging JAR be a good idea or would it be a better idea to make something else, perhaps a ZIP? Any input is welcome! Thanks, -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien M +43 664 88657566 E roland.asm...@adesso.at W www.adesso.at - >>> business. people. technology. <<< - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven subversion issue
Then you don't use svn+ssh. On Sun, Mar 13, 2011 at 1:50 PM, anjana wrote: > but sir i will have to use file:/// such type of url because my repository is > local type > > -- > View this message in context: > http://maven.40175.n5.nabble.com/maven-subversion-issue-tp3555224p363.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using the new maven assembly goals
Hi, Thanks for the reply. -- Rui On Mon, Mar 14, 2011 at 10:01 AM, Marc Rohlfs wrote: > Hi Rui, > > I guess You were formally using the 'assembly:assembly' (or > 'assembly:directory') goal, right? Those goals where "not inherited by > default in multi-project builds" [1], but they "forced Maven to build all > included POMs up to the package phase before the assembly is processed" [1]. > This is discouraged now, You should assemble Your release artifacts using > an additional submodule instead - like discribed in [2]. > > About Your POM and command invocation: > In contrast to using 'assembly:assembly', the 'assembly:single' goal is > inherited to the sub modules. The results are: > - With inherited=false, the 'assembly:single' execution is missing the > assembly descriptor configuration. > - With inherited=true, the 'assembly:single' execution cannot find Your > assembly descriptor, because it expects a 'release.xml' file in the base > directory of each sub module. > - You could call 'mvn help:effective-pom -N' to not recurse into the sub > modules, but how would You get their artifacts then? > > One last point: With all my questions I wanted to tell You that You should > tend to provide all the information that might be needed to answer Your > question. Even in Your last mail I didn't find enough information so that I > had to guess what You really want to achieve and how Your assembly > descriptor might look like. (And I guess that this lack of information is > the main reason why no one else took care of Your question so far) > > Kind regards > > Marc > > > [1] > http://maven.apache.org/plugins/maven-assembly-plugin/assembly-mojo.html > [2] > http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: can I use Maven repository manager outside of Maven?
Thanks Anders, that's exactly what I was looking for!
—
Yegor Bugayenko
On Mon, Mar 14, 2011 at 10:36 AM, Anders Hammar wrote:
> I think you should have a look at Aether, which is the repository API which
> Maven 3 uses for artifact handling.
> [1] is probably a good place to start.
>
> /Anders
>
> [1] http://aether.sonatype.org/
>
> On Mon, Mar 14, 2011 at 09:21, Yegor Bugayenko wrote:
>
>> I'm trying to create an application that will download and use Maven
>> artifacts outside of Maven. I think that in this case the smartest way
>> would
>> be to use Maven already existing classes. Can anyone help me with a hint
>> where to look for?
>>
>> Would be nice to make it working this way:
>>
>> Repository rep = new Repository("~/.m2");
>> Artifact artifact = new Artifact("com.example", "foo", "1.0");
>> String path = rep.resolve(artifact);
>> assert path.equals("~/.m2/repository/com/example/foo/1.0/foo.jar");
>>
>> Thanks!
>>
>> —
>> Yegor Bugayenko
>>
>
>
RE: Extra dependency added to eclipse projects
So, I ran: mvn -X eclipse:eclipse And sorted through the output. There are NO occurrences of "spring-2.0.3". There are NO occurrences of "2.0.3" We are using Spring 3.0.2 - Which is spread through a dozen jars, and doesn't have a spring.jar. -Original Message- From: Jörg Schaible [mailto:joerg.schai...@scalaris.com] Sent: Monday, March 14, 2011 12:39 AM To: users@maven.apache.org Subject: Re: Extra dependency added to eclipse projects Barrie Treloar wrote: > On Sat, Mar 12, 2011 at 5:26 AM, John Lussmyer > wrote: > >> We have a large project hierarchy, and use "mvn eclipse:eclipse" to >> generate Eclipse projects for it. >> In 3 of the projects, maven adds a dependency to "spring-2.0.3.jar" - >> which we don't use, and don't have. >> This .jar does not appear in ANY of our pom.xml files. >> "mvn dependency:tree" doesn't find any references to this jar either. >> >> Any ideas on how to get rid of these added, annoying, unwanted, >> dependencies? >> > > eclipse:eclipse doesn't make up dependencies, it must be in there > somewhere. > > try using -X and wading though the console output, that should list spring > and maybe you can see how it is included. > > It's odd that mvn dependency:tree doesn't find your dependency. If he uses M3 then the output may be different to the real deps. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp
How to get between overlay processing and webapp assembly
Hello Everyone,
I have a scenario where I need to make tweaks to a war and repackage
it. Initially, I thought that creating a maven war project would be
perfect for this as I would be able to use overlays to replace/add
files as I wish. And I still think this is a good idea. But in
addition to that, I have realized that for some files ... like
localized properties files ... I really do not want to replace them
via an overlay because I do not have the knowledge to prepare all the
translations ahead of time. Rather I want to edit just a few well
known key=value pairs in the localized properties files.
I have written a properties-editor-maven-plugin to do this but the
problem is that the extraction of the war-dependency is not part of
any maven phase, so I can't get a hook between the
dependency-war-extraction and the webapp build processes.
It all seems to happen atomically in the maven war plugin:
[INFO] [war:war {execution: default-war}]
[INFO] Packaging webapp
[INFO] Assembling webapp[customWebapp] in [C:\dev\target\customWebapp]
[INFO] Processing war project
[INFO] Copying webapp resources[C:\dev\src\main\webapp]
[INFO] Processing overlay[ id just.some.package:mywar]
[INFO] Webapp assembled in[X msecs]
[INFO] Building war: C:\dev\target\customWebapp.war
I am guessing that the mywar.war file gets expanded onto the
file-system and then the overlay processed in the following step:
[INFO] Processing overlay[ id just.some.package:mywar]
How do I get between that step and the step indicated by the following log?
[INFO] Webapp assembled in[X msecs]
Thanks!
- Pulkit
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Extra dependency added to eclipse projects
On Tue, Mar 15, 2011 at 1:34 AM, John Lussmyer wrote: > So, I ran: mvn -X eclipse:eclipse > And sorted through the output. > There are NO occurrences of "spring-2.0.3". There are NO occurrences of > "2.0.3" > > We are using Spring 3.0.2 - Which is spread through a dozen jars, and > doesn't have a spring.jar. > I'm sorry, I can't offer much more help. This is the first I've heard of this type of issue. I recommend that you grab the source of the plugin (details here http://maven.apache.org/plugins/maven-eclipse-plugin/source-repository.html) and compile up your own version. Splatter some debug statements in around the dependency resolution and see if you can catch it that way. Check out org.apache.maven.plugin.ide.AbstractIdeSupportMojo.doDependencyResolution() Alternatively you can attempt to use another eclipse / maven integration like m2eclipse or sts. If you are able to reproduce the problem then we can look into getting it fixed.
Re: Extra dependency added to eclipse projects
I mean the following suggestion in all seriousness (because I think it might work to help find your problem). 1. Download IntelliJ Idea 10, ultimate edition. You'll get a free 30 day trial. 2. Copy your workspace to a new directory or (better yet) check it out from version control. 3. Start idea and New Project -> Import From External Model -> Maven -> point it at your top level pom (do NOT import from the eclipse model) 4. Open the maven widget on the top right. Select the top-level module (pom) or rinse-repeat through the following steps for each jar module: a. Open up the dependencies section b. If there are red squiggly lines anywhere, do the following: c. Right-click -> jump to source (or F4) d. Mouse to the bottom of the page, where there are two itty bitty tabs: text and [dependencies] (can't remember exactly). Click [dependencies]. Your first job is to remove all of the red lines from the graph. e. Re-run dependency:list on your project or module frequently. The reason for this advice is that, oftentimes, conflicting "transitive dependencies" slip in through other libraries you're using. The apache commons projects frequently reference different versions of commons-logging, for example. I have found that attempting such fix without great tool support is of the needle/haystack variety. Removing undesired conflicts involves the following two-part algorithm: 1. Add an directive to all or all-but-one-of the dependencies that are importing the unexpected spring deps. 2. Include the version you wish explicitly (with appropriate scope). When you're finished, either uninstall-delete Idea or see if there are other features worth fiddling with. My other favorite is NeverCrashesAndSeldomNeedsARestart. I'm guessing that one of the dependencies you are using hasn't bern tended to in a while and depends upon the ancient Spring. You'll probably see that as a red line in the dependency graph pretty quickly. I don't think it's Eclipse's fault (per se). -- JPN -- Sent from my iPhone On Mar 14, 2011, at 9:01 PM, Barrie Treloar wrote: > On Tue, Mar 15, 2011 at 1:34 AM, John Lussmyer > wrote: > >> So, I ran: mvn -X eclipse:eclipse >> And sorted through the output. >> There are NO occurrences of "spring-2.0.3". There are NO occurrences of >> "2.0.3" >> >> We are using Spring 3.0.2 - Which is spread through a dozen jars, and >> doesn't have a spring.jar. >> > > I'm sorry, I can't offer much more help. > > This is the first I've heard of this type of issue. > > I recommend that you grab the source of the plugin (details here > http://maven.apache.org/plugins/maven-eclipse-plugin/source-repository.html) > and compile up your own version. > > Splatter some debug statements in around the dependency resolution and see > if you can catch it that way. > Check out > org.apache.maven.plugin.ide.AbstractIdeSupportMojo.doDependencyResolution() > > Alternatively you can attempt to use another eclipse / maven integration > like m2eclipse or sts. > > If you are able to reproduce the problem then we can look into getting it > fixed. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
