maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ron Wheeler <>
Subject Re: Overriding artifact to be installed/deployed
Date Wed, 11 Dec 2013 18:32:44 GMT
I think that your suggestion has a lot of merit.
It is easier to optimize something that works than to try to make 
something new without a set of working components.


On 11/12/2013 11:50 AM, Bruce Albrecht wrote:
> One of my teams is trying to build a bundled application that first
> builds a jar file using the jar plugin and then uses maven-exec plugin
> to run something that bundles the jar file into a specialized osgi
> bundle.  When we run the mvn install or deploy, it will deploy the jar
> file created by the jar plugin. Is there some way to override the
> artifact location so that it will upload the bundled jar?  Currently
> this is all done in a single project, and I'm beginning to wonder if the
> way to go is to change it to a multi-module project, with one module to
> create the jar file, and a second module to create the bundled jar, and
> use build-helper:attach-artifact to attach the bundled jar. They don't
> need the unbundled jar to be uploaded to the repository.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Ron Wheeler
Artifact Software Inc
skype: ronaldmwheeler
phone: 866-970-2435, ext 102

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message