I was concerned myself, then I checked the Aries release instructions
and one option listed was to make sure the ("dev") profile gets updated
which is what I did. However I only updated dev properties in the
released module poms - let me check the whole trunk
Sergey
On 30/06/15 20:15, Thomas Watson wrote:
Is the intent to leave trunk broken for building while the votes are going
on? Right now I can no longer build trunk because it complains about not
finding the these soon to be released artifacts.
Tom
From: David Bosschaert <[email protected]>
To: "[email protected]" <[email protected]>
Date: 06/30/2015 01:31 PM
Subject: Re: [VOTE] blueprint-parser-1.3.1, blueprint-noosgi-1.1.1,
blueprint-web-1.1.1 releases
+1
David
On 29 June 2015 at 16:56, Sergey Beryozkin <[email protected]> wrote:
Hi All
This is a vote to support the release of blueprint-parser-1.3.1,
blueprint-noosgi-1.1.1, blueprint-web 1.1.1.
The staging repository for blueprint-parser-1.3.1 is at
https://repository.apache.org/content/repositories/orgapachearies-1027
The staging repository for blueprint-noosgi-1.1.1 and
blueprint-web-1.1.1 is
at
https://repository.apache.org/content/repositories/orgapachearies-1028
The following issues have been addressed:
https://issues.apache.org/jira/browse/ARIES-1322
https://issues.apache.org/jira/browse/ARIES-1323
https://issues.apache.org/jira/browse/ARIES-1334
A servlet-based deployment of Blueprint contexts with custom namespace
handlers will work better in non OSGI environments after the release.
The vote is open for the next 72 hours, here is my +1,
Thanks, Sergey
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
