Forgot to mention the problem happens with Eclipse 3.4.2, retrieved
originally using Yoxos, but after hitting a showstopper bug, decided to
start over with manual installation for plugins, then make a copy before
I add m2eclipse so I can rollback easily.
I saw this post in the archives:
http://archive.hausfoundation.org/lists/org.codehaus.m2eclipse.user/msg/[email protected]
If there is an existing bug I can create a sample project to reproduce
the problem. Or should I create a new issue in jira?
Paul Sundling
Paul Sundling (Webdaddy) wrote:
I checked both http://m2eclipse.sonatype.org/update/ and
http://m2eclipse.sonatype.org/update-dev/ and I only saw the same
recent version (0.97.200902090947) which I already encountered a
showstopper bug in.
Version 0.0.12 has been rock solid and some other guys have 0.96.xxxx
and it has no problems with our codebase. So ideally I'd like to use
an older version until it's fixed.
The problem I have is with a multi-project module. When not using
workspace resolution it finds the jars from the repository just fine.
With workspace resolution some projects are not found. I remember
seeing a bug filed about projects with dependencies that have
classifiers when using workspace resolution. That sounds like this
problem.
Projects
simple-lib (no dependencies of any kind)
service-lib (depends on simple-lib and lots of external libs including
classifiers and property usage)
web-project (depends on simple-lib, service-lib and lots of external
libs)
Maven dependencies for web-project with workspace resolution OFF
simple-lib jar
service-lib jar
dependencies of service-lib jars
dependencies of web-project jars
Maven dependencies for web-project with workspace resolution ON
simple-lib project
SERVICE-LIB PROJECT IS MISSING (causing lots of missing classes)
dependencies of service-lib jars
dependencies of web-project jars
What I find amusing is that the transitive dependencies of service-lib
are detected, but not the service-lib project itself! Sure it's
possible to workaround by turning workspace resolution off and doing
an mvn install after each code change. That's such a GIGANTIC step
backward, that it's definitely preferable to just use an older version
without the issue.
Paul Sundling
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
