You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Steve Cohen <sc...@javactivity.org> on 2012/01/10 23:22:25 UTC
howto simply export dependent jars someplace
I have the following task, which should be simple. I'm having a brain
cramp but I can't figure out how to do it.
I am building a straight java application with dependencies. Under
"normal" circumstances, I can get what I need painlessly by using the
maven assembly plugin and building a jar-with-dependencies.
However, the end goal here is that this application runs on a number of
workstations, to which new versions would be pushed if available by an
outside legacy process (not maven).
In this scenario we simply wish to have the dependent jars (which will
change rarely, if ever) in a lib directory on each machine, and an
executable jar with a manifest putting all the jars on the classpath.
I simply want to extract all the dependent jars from the repository into
a directory. This collection can then be copied out to the production
servers.
What, if any, maven goal/lifecycle phase allows me to gather all the
dependent jars someplace without manually picking each one out of my
local repo?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: howto simply export dependent jars someplace
Posted by Jesse Farinacci <ji...@gmail.com>.
Greetings,
Try dependency:copy-dependencies
-Jesse
On Jan 10, 2012 5:23 PM, "Steve Cohen" <sc...@javactivity.org> wrote:
> I have the following task, which should be simple. I'm having a brain
> cramp but I can't figure out how to do it.
>
> I am building a straight java application with dependencies. Under
> "normal" circumstances, I can get what I need painlessly by using the maven
> assembly plugin and building a jar-with-dependencies.
>
> However, the end goal here is that this application runs on a number of
> workstations, to which new versions would be pushed if available by an
> outside legacy process (not maven).
>
> In this scenario we simply wish to have the dependent jars (which will
> change rarely, if ever) in a lib directory on each machine, and an
> executable jar with a manifest putting all the jars on the classpath.
>
> I simply want to extract all the dependent jars from the repository into a
> directory. This collection can then be copied out to the production
> servers.
>
> What, if any, maven goal/lifecycle phase allows me to gather all the
> dependent jars someplace without manually picking each one out of my local
> repo?
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<us...@maven.apache.org>
> For additional commands, e-mail: users-help@maven.apache.org
>
>