1 Reply Latest reply on Sep 28, 2006 11:03 AM by rob.stryker

Jboss IDE deploy vs. run.bat Classpath error

nic.botha Sep 27, 2006 1:53 AM

Hi, deploying my ear when starting JBoss in Eclipse IDE it works but when starting up JBoss with run.bat a certain jar is not in the classpath. In Eclipse in server view I add the jars (sitting in ) to classpath. Same jars are in environment setttings PATH and CLASSPATH. These are security providers and are not included in my war. I have tried using the -c option in run.bat but can't getting it to work. What is the difference between starting in Eclipse and starting JBoss from command line?

Thanks.
Nic

1. Re: Jboss IDE deploy vs. run.bat Classpath error

rob.stryker Sep 28, 2006 11:03 AM (in response to nic.botha)

The -c option says which configuration you plan on using, (default, minimal, all etc). When using run.bat directly you should probably add elements to the classpath.

If you run run.bat -h you should probably see common flags to set.

There it says you need -C (capital letter, not lowercase) or --classpath= to add elements to the classpath.

So the only difference between run.bat and eclpse is that elcipse gives you a nice graphical way to edit the classpath, whereas via command line that responsibility is yours.
Actions