Submitted by Nicolas (not verified) on Fri, 2011-01-14 15:54.
I never deploy neither. And I think I have a better solution than yours because you are messing up with the classloaders! The container and the webapp have the same classloader. And in your Eclipse project you may have some jars required for units tests which get loaded whereas they should not be there in production-like deployment.
What I wrote is an Eclipse plugin which is extending the usual java launcher. In the usual java launch configuration you can configure the classpath. With my plugin, the I use this configured classpath to be the jetty's extra classpath: http://docs.codehaus.org/display/JETTY/Classloading#Classloading-Usingth...
And this works very nicely with IvyDE, contrary to the other launch frameworks like WTP.
I never deploy neither. And I think I have a better solution than yours because you are messing up with the classloaders! The container and the webapp have the same classloader. And in your Eclipse project you may have some jars required for units tests which get loaded whereas they should not be there in production-like deployment.
What I wrote is an Eclipse plugin which is extending the usual java launcher. In the usual java launch configuration you can configure the classpath. With my plugin, the I use this configured classpath to be the jetty's extra classpath: http://docs.codehaus.org/display/JETTY/Classloading#Classloading-Usingth...
And this works very nicely with IvyDE, contrary to the other launch frameworks like WTP.
I should probably get it open source :p