Stuart James Penrose wrote:
You might find something useful in Eugene's comments on
http://jira.codehaus.org/browse/MNGECLIPSE-369 - in a nutshell the
runtime classpath can differ from the compile classpath when workspace
dependency resolution is turned on. I haven't updated to 0.9.0 yet
but if the behavior is the same in this regard it could be that your
new checkout is using the workspace dependency resolution whereas it
didn't before. Try turning off workspace dependency resolution for
the project and see if that helps.
Actually, starting from 0.9.0 release runtime classpath for JUnit and
Java app launch configurations will be always different from the compile
classpath if you have maven dependecy management enabled for the
project. We have tried to make it as close as possible to the
corresponding Maven scopes.
I would recommend to run "Update Sources" action on all your projects
after updating to the new version, so there won't be any legacy
configuration.
Stuard, it would be great if you could check if MNGECLIPSE-369 is
resolved in the new version and comment on the bug report.
Thanks
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
