Closed GoogleCodeExporter closed 8 years ago
Suggestion, or plugin could just attach the artifacts to the build... so people
can
decide if they wanna to install or deploy...
if they do mvn install, it would just install... if they do mvn deploy it would
be
deployed.
VELO
Original comment by velo...@gmail.com
on 8 Feb 2010 at 11:35
Hi Velo,
I did separate each task: resolve (download), install, and deploy to individual
discrete goals. I thought
for a while on attaching the artifacts to the build so that they would
automatically be included on
standard install and deploy workflows. I was concerned about the plugin
dictating the processing of its
goals by being tied to predetermined phases. I ended up just creating the
separate goals and then
assigning them via the <executions> node in the POM file. This way users can
be in control over if and
when each goal may be run. For example, in my use case for this plugin, I want
to install any external
dependencies into my local repository if they are not already there before my
project gets compiled. If I
were bound to the project's install phase, this would not occur until after
compile and I will get compile
errors since the compilation is dependent on the dependencies existing first.
Please take a look at the <executions> in this most recent POM file and let me
know what you think about
this plan.
http://code.google.com/p/maven-external-dependency-plugin/source/browse/trunk/ma
ven-external-dependency-
plugin-test/pom.xml
I am new to this and learning as I go, so I certainly welcome any input and
feedback.
Thank You, Robert
Original comment by savage7....@gmail.com
on 9 Feb 2010 at 4:09
Deployment is now implemented.
However I would still like to optimize this to be a little more intelligent
about only
deploying files that it needs to. The current implementation will deploy all
external
defined artifacts when the deploy-external goal is invoked.
Original comment by savage7....@gmail.com
on 11 Feb 2010 at 2:58
Original comment by savage7....@gmail.com
on 11 Feb 2010 at 3:04
Original issue reported on code.google.com by
savage7....@gmail.com
on 8 Feb 2010 at 6:46