Well using the Jboss jars is indeed the solution. The only thing I
would do is install it in my local repository using
install:install-file. But you have to know it won't work on other
desktop so usually you should have an internal corporation repository
and deploy them there. This each developper won't have to install them
manually. After that, you can work with those jar like they were
normal dependencies.

On 4/25/06, Anshuman Srivastava <[EMAIL PROTECTED]> wrote:
> If we do not use the "system" dependecies then how can we resolve the
> dependency on ejb3.0 which is not available on
> http://www.ibiblio.org/maven2/. This was my problem so i used ejb3 jars
> distributed by jboss.Is there any other way?
>
> pom.xml---
>
>  <groupId>jboss.ejb3</groupId>
>      <artifactId>ejb3-persistence</artifactId>
>         <version>3.0</version>
>         <scope>system</scope>
>         <systemPath>C:/boss-4.0.4/server/default/deploy/ejb3.deployer/ejb3-
> persistence.jar</systemPath>
>      </dependency>
>      <dependency>
>         <groupId>jboss.ejb3</groupId>
>      <artifactId>ejb3-management</artifactId>
>         <version>3.0</version>
>         <scope>system</scope>
>         <systemPath>C:/boss-4.0.4/docs/examples/jmx/ejb-management.jar
> </systemPath>
>      </dependency>
>      <dependency>
>         <groupId>jboss-ejb3x</groupId>
>      <artifactId>ejb3x</artifactId>
>         <version>3.0</version>
>         <scope>system</scope>
>         <systemPath>C:/boss-4.0.4/server/default/deploy/ejb3.deployer/jboss-
> ejb3x.jar</systemPath>
>      </dependency>
>      <dependency>
>         <groupId>jboss-annotations-ejb3</groupId>
>      <artifactId>annotations-ejb3</artifactId>
>         <version>3.0</version>
>         <scope>system</scope>
>      <systemPath>C:/boss-4.0.4/server/default/deploy/ejb3.deployer/jboss-
> annotations-ejb3.jar</systemPath>
>      </dependency>
>
>
> On 4/25/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
> >
> > Well you can use *system* dependencies but you loose tons of
> > advantages. Instead, maybe you should just populate your local
> > repository using the install plugin and -o to run mvn offline.
> >
> > On 4/24/06, Brandon Goodin <[EMAIL PROTECTED]> wrote:
> > > Is it a requirement that i use the remote repository for jars? Is
> > > there a way to reference jars that are distributed with the code when
> > > checked out from the code repository?
> > >
> > > Brandon
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to