brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hadrian Zbarcea <>
Subject Re: No 0.7.0-rc1 release today :(
Date Sat, 27 Jun 2015 03:58:05 GMT
First thing, the <parent> for the brooklyn-downstream-parent should not be:

but the apache parent ultimately. I think this should completely resolve 
the problem. It's a bit late here to test, I'll do it tomorrow.


On 06/26/2015 11:35 PM, Hadrian Zbarcea wrote:
> I did try a dryRun myself and did encounter a problem with the
> brooklyn-downstream-parent, but of a different nature
> "'parent.relativePath' points at wrong local POM", but I suspect there
> more issues there. From my experience releasing other projects, I try to
> first remove relevant branches from my local maven repo before preparing
> a release.
> I will look at it during the weekend. Somebody should revert the version
> back from 0.8.0-SNAPSHOT though.
> Cheers,
> Hadrian
> On 06/26/2015 04:53 PM, Richard Downer wrote:
>> So we got all the source code lined up today, and the release branch
>> made.
>> Everything was going very promisingly until I tried to close the Nexus
>> repository to publish the artifacts and got a rule violation error.
>> I'll have a look at fixing the problem and re-starting the release on
>> Monday (unfortunately I won't have any availability to look at this over
>> the weekend).
>> In the meantime if anyone is looking for something to do over the
>> weekend,
>> the exact failure Nexus reported was:
>> Missing Signature:
>> '/org/apache/brooklyn/brooklyn-downstream-parent/0.7.0-incubating/brooklyn-downstream-parent-0.7.0-incubating.pom.asc'
>> does not exist for 'brooklyn-downstream-parent-0.7.0-incubating.pom'.
>> Everything else has a .pom.asc except downstream-parent so it seems
>> there's
>> something special about this project.
>> Richard.

View raw message