On 10/30/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
You set up your workspace to look like a deployed WAR to a point.
You should not have a ...workspace/.../WEB-INF/lib
What happens is that the JARs end up on the classpath twice: Once because
they are on Eclipse's project classpath, then
You set up your workspace to look like a deployed WAR to a point.
You should not have a ...workspace/.../WEB-INF/lib
What happens is that the JARs end up on the classpath twice: Once because
they are on Eclipse's project classpath, then a second time when Jetty
creates a class loader for the WAR
On 10/30/06, nard man <[EMAIL PROTECTED]> wrote:
That plugin appears to work best if jars are *not* located in WEB-INF/lib.
My preference is just manually remove the jars /WEB-INF/lib at
classpath config dialog box at eclipse.
--
That plugin appears to work best if jars are *not* located in WEB-INF/lib.
Just put them somewhere else in the project and add them to the
project build path and the plugin will work ok.
When you build a war file for production deployment, use ant to ensure
the jars are in WEB-INF/lib.
On 10/2
I encounter this problem before because of the way the eclipse-jetty
plugin load same jar twice.
However, I am not sure why this is a problem of hivemind Just pick
either isn't ok? Probably worth to show a warning to user but I don't
see there is a point to forbid user from running the applic
Check the classpath settings that jetty-launcher uses...
Your hivemind-1.1.1.jar is getting included twice
Bill Holloway wrote:
> Apologies if this is already covered. Probabaly is, but when I run
> the jetty launcher in eclipse, I get
>
> Unable to initialize application servlet: Error: Module
Sounds like you have the jar on your classpath twice.
Tapestry uses jetty to run all of the internal/sample applications from
eclipse, so you should find plenty of working examples in the repo.
On 10/29/06, Bill Holloway <[EMAIL PROTECTED]> wrote:
Apologies if this is already covered. Probaba
