Open GoogleCodeExporter opened 8 years ago
I have similar issue with the same configuration (Eclipse 3.7 SR1)
To be more specific, if I have a web project A, java project B
A has a maven dependency on B, B has several maven dependencies on other Maven
artifacts which has "provided" scope.
As a result, the artifacts having "provided" scope are mistakenly added to web
app classpath only if I open project B in Eclipse workspace. If I close project
B in Eclipse workspace, the classpath becomes correct.
Please take a look.
Original comment by olive...@gmail.com
on 19 May 2012 at 4:49
I have an issue maybe related to this one (Eclipse Juno 4.2 , m2e 1.1.0).
All the jar with scope "provided" and "test" are included in the classpath even
if the plugin WebClasspath tab doesn't contain them. Moreover, I have a version
of asm which is omitted by Maven in version 1.5.3 because of an earlier version
3.1 that's still in the classloader printed at startup in the console.
I must go back to maven-jetty-plugin while I find this plugin very usefull...
Original comment by guillaum...@gmail.com
on 25 Sep 2012 at 4:44
The workaround indicated by tonylove resolved by problem too. Waiting for a
more elegant solution in a future version ;)
Original comment by guillaum...@gmail.com
on 26 Sep 2012 at 7:43
I also have this issue using Eclipse Juno SR1 and m2e 1.2.0
The workaround is working fine, but cannot applicable due to a lot of
dependency to exclude.
I have to go back to maven-jetty-plugin.
Original comment by tphuoct...@gmail.com
on 21 Nov 2012 at 3:22
I have the same problem... I have a lot of test dependencies being included on
the jetty classpath, and using maven exlcusions doesn't fix the problem.
I have Eclipse Indigo 3.7.2, with m2eclipse 1.2.
I love run-jetty-run, but it's a show stopper for me.. I'll need to fall back
to tomcat until it's fixed :(
Original comment by bruno...@gmail.com
on 14 Mar 2014 at 5:21
I fixed this issue here -
https://code.google.com/p/run-jetty-run/issues/detail?id=187
Original comment by jumperc...@gmail.com
on 11 Nov 2014 at 4:07
Original issue reported on code.google.com by
tonylovejava
on 23 Mar 2012 at 7:39