Closed GoogleCodeExporter closed 9 years ago
Did you try including slf4j? I just looked at possible missing dependencies,
but I can't find anything obvious. And
I'm not crazy about the idea of just randomly including jars that are not even
packaged with Jetty.
If you can figure out what misses, I'd be happy to apply a patch.
Original comment by eelco.hi...@gmail.com
on 3 Feb 2008 at 6:21
Another issue with T5.
If you include T5 in your workspace and Maven plugin resolves it as a
dependency, you
will have another org.mortbay.jetty.Server in your classpath (from selenium).
This
version is not compatible with runjettyrun Bootstrap.
So, in debug dialog, be sure to set your workspace source folder after
runjettyrun
jars on classpath tab.
Original comment by gabriel.landais@gmail.com
on 5 Mar 2008 at 2:59
In the VM argsuments of the lauch config add:
-Dorg.mortbay.jetty.webapp.parentLoaderPriority=true
Seemed to work for me.
Original comment by goo...@azudio.co.uk
on 20 Mar 2008 at 7:20
>So, in debug dialog, be sure to set your workspace source folder after
runjettyrun
That sounds like it fixes the problem for you, but I just do not understand
what to
do. I think the debug dialog means the debug/run configuration of rjr, but how
can
you influence the order of dependency resolving there? Would not the two
versions
conflict anyway? I tried the argument below as well, apparently did not change
anything. Thanks for helping.
Original comment by mich...@googlemail.com
on 2 Apr 2008 at 8:24
Under classpath tab (plugin run/debug options) you can select the order in which
"User entries" are added to the classpath.
Original comment by mluse...@gmail.com
on 2 May 2008 at 9:14
This may be because of:
http://jira.codehaus.org/browse/JETTY-574
Fix version is 6.1.7 and current version in run-jetty-run is 6.1.6 .
Original comment by simonhar...@hotmail.com
on 14 Nov 2008 at 3:27
I think it's a old issue and still need more info to verify this.
Original comment by tonylovejava
on 11 Mar 2011 at 8:45
Original comment by tonylovejava
on 1 Jul 2011 at 8:34
Original issue reported on code.google.com by
standa.k...@gmail.com
on 23 Jan 2008 at 7:26