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 <exclude> 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 <[email protected]> wrote: > On Tue, Mar 15, 2011 at 1:34 AM, John Lussmyer > <[email protected]>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: [email protected] For additional commands, e-mail: [email protected]
