Deploy or app based on target structure

[mark_in_gr <mc...@xrite.com>]

I am trying to find out the best practice regarding how I can deploy an
executable jar application, which has dependencies found in a lib directory.
I am attempting to accomplish this using both the maven-jar-plugin and the
maven-assembly-plugin, but I am a bit confused on a few things.

Namely, is it possible to use the "deploy" goal to transfer an application,
say via straight file copy(file>// . . .) and use the format found in the
target directory. I assume that the "deploy" goal transfers artifacts from
your local repository, however, this local respository ONLY contains the jar
dependency specified in the pom. After added the maven-assembly-plugin to
the pom, I get xxx-jar-with-dependencies directory with all of the jar
dependencies exploded, but the goal which produced this(the assembly plugin
is tied to the package phase in my pom) does NOT affect the local
repository, ONLY the target directory.

Simply put . . . how does one set up a project so one may use the deploy
phase to transfer an application similar to how it the build structure is
produced in the target directory?
-- 
View this message in context: http://www.nabble.com/Deploy-or-app-based-on-target-structure-tf3329333s177.html#a9257401
Sent from the Maven - Users mailing list archive at Nabble.com.


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