Hi Jack,
Please elaborate as to how this does not work "as advertised", these are
after all *separate build processes*; how is this information mean to be
guessed if the only connections between these builds are a Bamboo build
configuration (which Maven doesn't recognize either) and your intention?
Should I clarify in the documentation that the plugin lives, participates
and dies* *with the native Maven process and can't acknowledge the
existence of other Maven processes which might or might not have occurred
sooner or later?
Do Nexus or Archive provide a solution for this case? Perhaps we can
implement this too.
-Noam
On Wed, Feb 15, 2012 at 10:17 PM, Jack Godau <[email protected]>wrote:
>
> Noam Y. Tenne wrote
> >
> > The meaning of "Deploy all artifacts to the selected target repository in
> > one go (as opposed to the deploy at the end of each module build, used by
> > Maven/Ivy)" is that it deploys all the artifacts at the end of the
> reactor
> > build, as opposed to Maven deploy which publishes at the end of each
> > reactor
> > module.
> > Although you conceive the different parts of the build you've split up as
> > "Modules", they are now separate Maven runs, not Maven reactor modules.
> > The Artifactory Maven 3 plugin is integrated into Maven's lifecycle and
> > thus
> > "lives" as long as each reactor build lives.
> >
> > If you're looking for the Maven consistency and layout, the Generic
> > deployment won't be of too much help.
> > Other than that, I can only suggest that you configure each separate
> build
> > to archive it's produced artifacts and write a small script to analyze
> the
> > pom files and deploy them to the correct locations.
> >
>
> That response is severely disappointing! I've just spent a couple of days
> switching to Artifactory (as it can integrate with Bamboo to provide this
> added functionality) and now find out that the main reason we wanted it -
> "Deploy all artifacts to the selected target repository in one go" doesn't
> work "as advertised".
>
> Huge disappointment guys! :((((
>
> I think we'll drop Artifactory and go back to Nexus or Archiva - if I need
> to write me own scripts to do this, then I can do that with any tool.
> *sigh*
>
> Jack...
>
>
> --
> View this message in context:
> http://forums.jfrog.org/Question-on-Bamboo-Artifactory-Plug-in-and-multiple-jobs-tp6605402p7288848.html
> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
