Hi,
The build was hanging during the Maven publish stage and I couldn't
figure out why. I know I raised a bug but I can't find it. I don't
think this was before Bugzilla, was a while ago though. I would
suggest taking this bug
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=329824) and
repurposing it to find out why Maven publish is failing
intermittently. Once that target is working and publish is calling
in to it again we will get everything publishing to a Maven format
again.
Chris.
On 18/01/2011 20:18, Dmitry Sklyut wrote:
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
Regards,
Dmitry
On Tue, Jan 18, 2011 at 3:01 PM, Glyn
Normington <gnormington@xxxxxxxxxx>
wrote:
Hi Dmitry
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.
Chris?
Regards,
Glyn
On 18 Jan 2011, at 19:10, Dmitry Sklyut wrote:
> Hi,
>
> 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?
>
> Regards,
> Dmitry
> _______________________________________________
> virgo-dev mailing list
> virgo-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/virgo-dev
_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev
|
