[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [virgo-dev] Publishing snapshot maven artifacts
- From: Dmitry Sklyut <dmitry@xxxxxxxxxxx>
- Date: Tue, 18 Jan 2011 15:18:26 -0500
- Delivered-to: firstname.lastname@example.org
The change was made by Chris in ab971b72256cf56c96b197798d2cd505ebb6d37f
with comment "Removing maven publish to get the ripple through".
This corresponds to virgo-build version 2.01
On Tue, Jan 18, 2011 at 3:01 PM, Glyn Normington <gnormington@xxxxxxxxxx>
Chris should comment, but meanwhile you could check back in the git history of the file to see if maven was deliberately taken out at some stage and by whom.
My opinion is we should suck it and see, but we'd better keep it at the front of our minds the first time we do a ripple and the first time we do a release after the change.
On 18 Jan 2011, at 19:10, Dmitry Sklyut wrote:
> I noticed that virgo-build/common/publish.xml publish target does not call into maven-publish only ivy-publish.
> Description calls for maven publishing.
> <target name="publish" depends="publish-ivy" description="Publishes all artifacts to remote eclipse ivy and maven repositories"/>
> Can we enable maven publishing? Are there limitations/issues with maven publish?
> virgo-dev mailing list
virgo-dev mailing list