You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Thomas Watson <tj...@us.ibm.com> on 2015/07/01 14:25:05 UTC
Re: [VOTE] blueprint-parser-1.3.1, blueprint-noosgi-1.1.1, blueprint-web-1.1.1
releases
I must confess that I did not know about this -Pdev option. Is that only
needed when we are in this release limbo period?
Tom
From: Sergey Beryozkin <sb...@gmail.com>
To: dev@aries.apache.org
Date: 06/30/2015 04:24 PM
Subject: Re: [VOTE] blueprint-parser-1.3.1, blueprint-noosgi-1.1.1,
blueprint-web-1.1.1 releases
Building with -Pdev is OK now, sorry I did not update all the properties
immediately. As a side note a number of other dev properties have been
out of sync...
Thanks, Sergey
On 30/06/15 21:41, Sergey Beryozkin wrote:
> 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 <da...@gmail.com>
>> To: "dev@aries.apache.org" <de...@aries.apache.org>
>> 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 <sb...@gmail.com>
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
Re: [VOTE] blueprint-parser-1.3.1, blueprint-noosgi-1.1.1, blueprint-web-1.1.1
releases
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi Christian
Indeed, I had a profile in my .m2/settings.xml with those repositories
activated by default. Updating the relevant poms and reverting
immediately after the artifacts have become available in central can be
reasonable too
Sergey
On 01/07/15 15:48, Christian Schneider wrote:
> Hi Sergey,
>
> we might also look into trying to include the staging repository into
> the poms when doing releases for several bundles.
> I am not sure what downsides there may be but it could help
>
> Christian
>
>
> On 01.07.2015 15:15, Sergey Beryozkin wrote:
>> Hi Tom
>>
>> I think it is onlt the 2nd time I'm doing an Aries release, may be
>> 3rd, the last time it was a new module, so only this time, when I
>> looked at release few blueprint modules did I find myself about -Pdev,
>> I saw the dev profile properties before but never thouyght about why
>> one would use them until I checked the Aries Blueprint section.
>>
>> I think it is reasonable to use -Pdev for a short period of time,
>> though it s obviously the responsibility of the current release
>> manager to ensure -Pdev works :-). I guess it's been relied upon in
>> few cases before.
>>
>> Perhaps it makes sense to have a dedicated dev discussion about
>> various release strategies, the parent pom one, vs -Pdev, etc
>>
>> Thanks, Sergey
>
Re: [VOTE] blueprint-parser-1.3.1, blueprint-noosgi-1.1.1, blueprint-web-1.1.1
releases
Posted by Christian Schneider <ch...@die-schneider.net>.
Hi Sergey,
we might also look into trying to include the staging repository into
the poms when doing releases for several bundles.
I am not sure what downsides there may be but it could help
Christian
On 01.07.2015 15:15, Sergey Beryozkin wrote:
> Hi Tom
>
> I think it is onlt the 2nd time I'm doing an Aries release, may be
> 3rd, the last time it was a new module, so only this time, when I
> looked at release few blueprint modules did I find myself about -Pdev,
> I saw the dev profile properties before but never thouyght about why
> one would use them until I checked the Aries Blueprint section.
>
> I think it is reasonable to use -Pdev for a short period of time,
> though it s obviously the responsibility of the current release
> manager to ensure -Pdev works :-). I guess it's been relied upon in
> few cases before.
>
> Perhaps it makes sense to have a dedicated dev discussion about
> various release strategies, the parent pom one, vs -Pdev, etc
>
> Thanks, Sergey
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: [VOTE] blueprint-parser-1.3.1, blueprint-noosgi-1.1.1, blueprint-web-1.1.1
releases
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi Tom
I think it is onlt the 2nd time I'm doing an Aries release, may be 3rd,
the last time it was a new module, so only this time, when I looked at
release few blueprint modules did I find myself about -Pdev, I saw the
dev profile properties before but never thouyght about why one would use
them until I checked the Aries Blueprint section.
I think it is reasonable to use -Pdev for a short period of time, though
it s obviously the responsibility of the current release manager to
ensure -Pdev works :-). I guess it's been relied upon in few cases before.
Perhaps it makes sense to have a dedicated dev discussion about various
release strategies, the parent pom one, vs -Pdev, etc
Thanks, Sergey
On 01/07/15 13:25, Thomas Watson wrote:
> I must confess that I did not know about this -Pdev option. Is that only
> needed when we are in this release limbo period?
>
> Tom
>
>
>
>
>
> From: Sergey Beryozkin <sb...@gmail.com>
> To: dev@aries.apache.org
> Date: 06/30/2015 04:24 PM
> Subject: Re: [VOTE] blueprint-parser-1.3.1, blueprint-noosgi-1.1.1,
> blueprint-web-1.1.1 releases
>
>
>
> Building with -Pdev is OK now, sorry I did not update all the properties
> immediately. As a side note a number of other dev properties have been
> out of sync...
>
> Thanks, Sergey
> On 30/06/15 21:41, Sergey Beryozkin wrote:
>> 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 <da...@gmail.com>
>>> To: "dev@aries.apache.org" <de...@aries.apache.org>
>>> 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 <sb...@gmail.com>
> 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
>>>>
>>>
>>>
>>>
>>
>>
>
>