OK, so it seems that it's not possible to manage the build of a
stand-alone, desktop application entirely in Maven without resorting to
one or more hacks or manual processes.  I find it rather odd that the
most basic of all use-cases usually fulfilled by software build systems
is not yet supported by Maven.  But I'm willing to try my hand at
writing a plugin or goal to fulfill this need and give something back to
the Maven community.

Just to recap my earlier inquiry, what I'm looking for is a goal whose
resulting artifact is an executable jar file along with all the
dependencies it needs in order to run.  The goal would automatically
make the appropriate entries into the artifact jar's manifest.mf for the
main class and the jar file dependencies.  Then, it would copy the
dependency jar files themselves from the repository to the locations
specified in the manifest.mf.

Would anybody else here have a need for such a goal, or am I the only
one using Maven to build stand-alone Java apps?  If other people would
find such a goal useful, should I try to write it as a goal of the
assembly plugin, with the idea that I could submit it to a committer and
have it become a goal called, for example, assembly:stand-alone-app?

Any feedback or tips would be great--especially from someone who has
written a Maven goal before.

Thanks,
--Erik

***********************************************************************************
The information in this email (including any attachments) is confidential and 
may be legally privileged.  Access to this e-mail by anyone other than the 
intended addressee is unauthorized.  If you are not the intended recipient of 
this message, any review, disclosure, copying, distribution, retention, or any 
action taken or omitted to be taken in reliance on it (including any 
attachments) is prohibited and may be unlawful.  If you are not the intended 
recipient, please reply to or forward a copy of this message to the sender and 
delete the message, all attachments, and any copies thereof from your system 
and destroy any printout thereof.

______________________________________________________________________
The information in this email (including any attachments) is confidential and 
may be legally privileged. Access to this e-mail by anyone other than the 
intended addressee is unauthorized. If you are not the intended recipient of 
this message, any review, disclosure, copying, distribution, retention, or any 
action taken or omitted to be taken in reliance on it (including any 
attachments) is prohibited and may be unlawful. If you are not the intended 
recipient, please reply to or forward a copy of this message to the sender and 
delete the message, all attachments, and any copies thereof from your system 
and destroy any printout thereof.

Reply via email to