You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by rs...@imolinfo.it on 2006/10/02 11:13:44 UTC
better way to include tools.jar
Hi,
I'm developing a binding component. My binding component needs to do some
compilation at deploy time so it needs tool.jar.
I've declared this dependency as suggested by maven documentation:
<dependency>
<groupId>com.sun</groupId>
<artifactId>tools</artifactId>
<version>1.5.0_06</version>
<scope>system</scope>
<systemPath>${java.home}/../lib/tools.jar</systemPath>
</dependency>
This way tools.jar doesn't get bundled in the install package. So I get a
ClassNotFoundException at deploy time.
Considering that this kind of library depends on the jvm version what is the
better way to have it available.
Is it possible to configure servicemix to have it loaded at boot time?
thanks
Raffaele
Re: better way to include tools.jar
Posted by Guillaume Nodet <gn...@gmail.com>.
If you use the jdk to launch ServiceMix, the tools.jar
should be in the classpath. You need to properly
configure your system or hack the scripts to make
sure that the java command launched uses the jdk.
On 10/2/06, rspazzoli@imolinfo.it <rs...@imolinfo.it> wrote:
> Hi,
> I'm developing a binding component. My binding component needs to do some
> compilation at deploy time so it needs tool.jar.
> I've declared this dependency as suggested by maven documentation:
> <dependency>
> <groupId>com.sun</groupId>
> <artifactId>tools</artifactId>
> <version>1.5.0_06</version>
> <scope>system</scope>
> <systemPath>${java.home}/../lib/tools.jar</systemPath>
> </dependency>
>
> This way tools.jar doesn't get bundled in the install package. So I get a
> ClassNotFoundException at deploy time.
> Considering that this kind of library depends on the jvm version what is the
> better way to have it available.
> Is it possible to configure servicemix to have it loaded at boot time?
>
> thanks
> Raffaele
>
>
--
Cheers,
Guillaume Nodet