dependencies/JAR

[Brant Gurganus <br...@cherokeescouting.org>]

How do other projects deal with moving dependencies to the build 
directory and adding them to the classpath entry of the generated JAR?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: dependencies/JAR

[Felipe Leme <ma...@felipeal.net>]

On Tue, 2004-08-31 at 01:13, Dion Gillard wrote: 
> In which case, placing a pre-goal on the dist goal would help.

I'm not sure if I understood correctly the issue, but the dist goal
already offers such hook, which is the dist:prepare-bin-filesystem goal.

Felipe



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: dependencies/JAR

[Dion Gillard <di...@gmail.com>]

Isn't this only valid for a distribution?

In which case, placing a pre-goal on the dist goal would help.

On Sun, 22 Aug 2004 07:27:19 -0500, Brant Gurganus
<br...@cherokeescouting.org> wrote:
> Stefan Kleineikenscheidt wrote:
> 
> >i think i don't fully understand.  If you want to bundle your
> >application JAR with its dependencies you can use the uberjar plugin
> >(part of the standard maven distro) or the javaapp plugin
> >(http://maven-plugins.sourceforge.net/maven-javaapp-plugin/index.html).
> >I've found the javaapp plugin working better (although uberjar is
> >certainly more sexy ;).
> >
> >Using the classpath-entry of the manifest-file for this is usually more
> >tricky, as the entry is dependent on the location of the dependencies.
> >So far I've only used it for EJB-JARs in EARs.
> >
> >Another way of doing this is shipping the dependencies in a lib/ dir and
> >providing a start-script.
> >
> >-Stefan
> >
> >
> >
> >
> >>-----Original Message-----
> >>From: Brant Gurganus [mailto:brantgurganus2001@cherokeescouting.org]
> >>Sent: Sunday, August 22, 2004 3:18 AM
> >>To: users@maven.apache.org
> >>Subject: dependencies/JAR
> >>
> >>
> >>How do other projects deal with moving dependencies to the build
> >>directory and adding them to the classpath entry of the generated JAR?
> >>
> >>
> The problem with uberjar and javaapp is that they pack the dependencies
> into a single JAR.  That prevents a user from updating a dependency
> provided the dependency is compatible.  I would prefer the ability for
> the JAR plugin to include relative entries for the dependencies and to
> copy the dependencies to a lib/ or author-specified subdirectory of the
> build directory.
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 


-- 
http://www.multitask.com.au/people/dion/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: dependencies/JAR

[Brant Gurganus <br...@cherokeescouting.org>]

Stefan Kleineikenscheidt wrote:

>i think i don't fully understand.  If you want to bundle your
>application JAR with its dependencies you can use the uberjar plugin
>(part of the standard maven distro) or the javaapp plugin
>(http://maven-plugins.sourceforge.net/maven-javaapp-plugin/index.html).
>I've found the javaapp plugin working better (although uberjar is
>certainly more sexy ;).
>
>Using the classpath-entry of the manifest-file for this is usually more
>tricky, as the entry is dependent on the location of the dependencies.
>So far I've only used it for EJB-JARs in EARs.
>
>Another way of doing this is shipping the dependencies in a lib/ dir and
>providing a start-script.
>
>-Stefan
>
>
>  
>
>>-----Original Message-----
>>From: Brant Gurganus [mailto:brantgurganus2001@cherokeescouting.org] 
>>Sent: Sunday, August 22, 2004 3:18 AM
>>To: users@maven.apache.org
>>Subject: dependencies/JAR
>>
>>
>>How do other projects deal with moving dependencies to the build 
>>directory and adding them to the classpath entry of the generated JAR?
>>    
>>
The problem with uberjar and javaapp is that they pack the dependencies 
into a single JAR.  That prevents a user from updating a dependency 
provided the dependency is compatible.  I would prefer the ability for 
the JAR plugin to include relative entries for the dependencies and to 
copy the dependencies to a lib/ or author-specified subdirectory of the 
build directory.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

RE: dependencies/JAR

[Stefan Kleineikenscheidt <st...@kleineikenscheidt.de>]

Hi Brant,

i think i don't fully understand.  If you want to bundle your
application JAR with its dependencies you can use the uberjar plugin
(part of the standard maven distro) or the javaapp plugin
(http://maven-plugins.sourceforge.net/maven-javaapp-plugin/index.html).
I've found the javaapp plugin working better (although uberjar is
certainly more sexy ;).

Using the classpath-entry of the manifest-file for this is usually more
tricky, as the entry is dependent on the location of the dependencies.
So far I've only used it for EJB-JARs in EARs.

Another way of doing this is shipping the dependencies in a lib/ dir and
providing a start-script.

-Stefan


> -----Original Message-----
> From: Brant Gurganus [mailto:brantgurganus2001@cherokeescouting.org] 
> Sent: Sunday, August 22, 2004 3:18 AM
> To: users@maven.apache.org
> Subject: dependencies/JAR
> 
> 
> How do other projects deal with moving dependencies to the build 
> directory and adding them to the classpath entry of the generated JAR?
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org