Thanks both. I think that could work.
There a few other problems with pipelines and Maven. I will probably open
another thread for this.
Regards.
On Wed, Mar 14, 2012 at 10:25 PM, Pete peteha...@gmail.com wrote:
We do this but do not rely on the repository manager to pull down the
artifact.
If archiving allows referencing an artifact with a url, why not use the
Maven repository URL for the artifact?
And as to JAR naming (reponding to a previous post ), maven builds jars
with the version and optional SNAPSHOT tag, which is the way it should be
in my opinion...because I really dislike
Actually, even though grabbing the artifact from the Maven repository seems
like a good idea, I think it's more coherent that you use the artifact from
the upstream job in order to guarantee that the artifact is the one being
processed at the current pipeline. Another build might be run in the
