You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-dev@axis.apache.org by Selvaratnam Uthaiyashankar <ut...@gmail.com> on 2010/12/23 05:37:18 UTC

[VOTE] Apache Rampart 1.5.1 release

Devs,

This is the vote for Apache Rampart 1.5.1 release.

Please review the signed artifacts:

http://people.apache.org/~shankar/rampart/1.5.1/dist/

The m2 repository is available at:
http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/

The site is temporarily hosted at:
http://people.apache.org/~shankar/rampart/1.5.1/site/

SVN Info:
https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1

It was tested against Axis2 release candidates hosted in:
http://people.apache.org/~veithen/1.5.4/

Here's my +1 (binding) to declare the above dist as Apache Rampart 1.5.1

thanks,
Shankar

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Senaka Fernando <se...@apache.org>.

+1 (Binding)

Thanks,
Senaka.

On Thu, Dec 23, 2010 at 10:07 AM, Selvaratnam Uthaiyashankar <
uthaiyashankar@gmail.com> wrote:

> Devs,
>
> This is the vote for Apache Rampart 1.5.1 release.
>
> Please review the signed artifacts:
>
> http://people.apache.org/~shankar/rampart/1.5.1/dist/<http://people.apache.org/%7Eshankar/rampart/1.5.1/dist/>
>
> The m2 repository is available at:
> http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/<http://people.apache.org/%7Eshankar/rampart/1.5.1/m2_repo/>
>
> The site is temporarily hosted at:
> http://people.apache.org/~shankar/rampart/1.5.1/site/<http://people.apache.org/%7Eshankar/rampart/1.5.1/site/>
>
> SVN Info:
> https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>
> It was tested against Axis2 release candidates hosted in:
> http://people.apache.org/~veithen/1.5.4/<http://people.apache.org/%7Eveithen/1.5.4/>
>
> Here's my +1 (binding) to declare the above dist as Apache Rampart 1.5.1
>
> thanks,
> Shankar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>


-- 
*Senaka Fernando*
Member; Apache Software Foundation; http://apache.org
*
Associate Technical Lead & Product Manager - WSO2 G-Reg;
WSO2, Inc.; http://wso2.com** <http://apache.org/>

E-mail: senaka AT apache.org
**P: +94 11 223 2481*; *M: +94 77 322 1818
Linked-In: http://www.linkedin.com/in/senakafernando
Blog: http://senakafdo.blogspot.com
*

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Dimuthu Leelarathne <di...@wso2.com>.

+1 for the release.

Thanks,
Dimuthu

On Thu, Dec 23, 2010 at 11:13 AM, Ruwan Linton <ru...@gmail.com>wrote:

> Tested with Synapse-2.0 proposed release and seems to work just fine :-)
>
> +1 for the release (Binding)
>
> Thanks,
> Ruwan
>
>
> On Thu, Dec 23, 2010 at 11:09 AM, Prabath Siriwardana <pr...@wso2.com>wrote:
>
>> +1 (Binding)
>>
>> Thanks & regards,
>> -Prabath
>>
>>
>> On Thu, Dec 23, 2010 at 11:01 AM, Samisa Abeysinghe <
>> samisa.abeysinghe@gmail.com> wrote:
>>
>>> I tested and all seems fine!
>>>
>>> Here is my vote: +1 (Binding)
>>>
>>> Samisa...
>>>
>>>
>>> On Thu, Dec 23, 2010 at 10:07 AM, Selvaratnam Uthaiyashankar <
>>> uthaiyashankar@gmail.com> wrote:
>>>
>>>> Devs,
>>>>
>>>> This is the vote for Apache Rampart 1.5.1 release.
>>>>
>>>> Please review the signed artifacts:
>>>>
>>>> http://people.apache.org/~shankar/rampart/1.5.1/dist/<http://people.apache.org/%7Eshankar/rampart/1.5.1/dist/>
>>>>
>>>> The m2 repository is available at:
>>>> http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/<http://people.apache.org/%7Eshankar/rampart/1.5.1/m2_repo/>
>>>>
>>>> The site is temporarily hosted at:
>>>> http://people.apache.org/~shankar/rampart/1.5.1/site/<http://people.apache.org/%7Eshankar/rampart/1.5.1/site/>
>>>>
>>>> SVN Info:
>>>> https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>>>>
>>>> It was tested against Axis2 release candidates hosted in:
>>>> http://people.apache.org/~veithen/1.5.4/<http://people.apache.org/%7Eveithen/1.5.4/>
>>>>
>>>> Here's my +1 (binding) to declare the above dist as Apache Rampart 1.5.1
>>>>
>>>> thanks,
>>>> Shankar
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>>
>>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>> Prabath
>>
>> http://blog.facilelogin.com
>> http://RampartFAQ.com
>>
>
>
>
> --
> Ruwan Linton
> Software Architect & Product Manager
>
> WSO2 Inc.; http://wso2.org
>
> Lean . Enterprise . Middleware
>
> phone: +1 408 754 7388 ext 51789
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> google: http://www.google.com/profiles/ruwan.linton
> tweet: http://twitter.com/ruwanlinton
>

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Ruwan Linton <ru...@gmail.com>.

Tested with Synapse-2.0 proposed release and seems to work just fine :-)

+1 for the release (Binding)

Thanks,
Ruwan

On Thu, Dec 23, 2010 at 11:09 AM, Prabath Siriwardana <pr...@wso2.com>wrote:

> +1 (Binding)
>
> Thanks & regards,
> -Prabath
>
>
> On Thu, Dec 23, 2010 at 11:01 AM, Samisa Abeysinghe <
> samisa.abeysinghe@gmail.com> wrote:
>
>> I tested and all seems fine!
>>
>> Here is my vote: +1 (Binding)
>>
>> Samisa...
>>
>>
>> On Thu, Dec 23, 2010 at 10:07 AM, Selvaratnam Uthaiyashankar <
>> uthaiyashankar@gmail.com> wrote:
>>
>>> Devs,
>>>
>>> This is the vote for Apache Rampart 1.5.1 release.
>>>
>>> Please review the signed artifacts:
>>>
>>> http://people.apache.org/~shankar/rampart/1.5.1/dist/<http://people.apache.org/%7Eshankar/rampart/1.5.1/dist/>
>>>
>>> The m2 repository is available at:
>>> http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/<http://people.apache.org/%7Eshankar/rampart/1.5.1/m2_repo/>
>>>
>>> The site is temporarily hosted at:
>>> http://people.apache.org/~shankar/rampart/1.5.1/site/<http://people.apache.org/%7Eshankar/rampart/1.5.1/site/>
>>>
>>> SVN Info:
>>> https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>>>
>>> It was tested against Axis2 release candidates hosted in:
>>> http://people.apache.org/~veithen/1.5.4/<http://people.apache.org/%7Eveithen/1.5.4/>
>>>
>>> Here's my +1 (binding) to declare the above dist as Apache Rampart 1.5.1
>>>
>>> thanks,
>>> Shankar
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>>
>
>
> --
> Thanks & Regards,
> Prabath
>
> http://blog.facilelogin.com
> http://RampartFAQ.com
>



-- 
Ruwan Linton
Software Architect & Product Manager
WSO2 Inc.; http://wso2.org

Lean . Enterprise . Middleware

phone: +1 408 754 7388 ext 51789
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Prabath Siriwardana <pr...@wso2.com>.

+1 (Binding)

Thanks & regards,
-Prabath

On Thu, Dec 23, 2010 at 11:01 AM, Samisa Abeysinghe <
samisa.abeysinghe@gmail.com> wrote:

> I tested and all seems fine!
>
> Here is my vote: +1 (Binding)
>
> Samisa...
>
>
> On Thu, Dec 23, 2010 at 10:07 AM, Selvaratnam Uthaiyashankar <
> uthaiyashankar@gmail.com> wrote:
>
>> Devs,
>>
>> This is the vote for Apache Rampart 1.5.1 release.
>>
>> Please review the signed artifacts:
>>
>> http://people.apache.org/~shankar/rampart/1.5.1/dist/<http://people.apache.org/%7Eshankar/rampart/1.5.1/dist/>
>>
>> The m2 repository is available at:
>> http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/<http://people.apache.org/%7Eshankar/rampart/1.5.1/m2_repo/>
>>
>> The site is temporarily hosted at:
>> http://people.apache.org/~shankar/rampart/1.5.1/site/<http://people.apache.org/%7Eshankar/rampart/1.5.1/site/>
>>
>> SVN Info:
>> https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>>
>> It was tested against Axis2 release candidates hosted in:
>> http://people.apache.org/~veithen/1.5.4/<http://people.apache.org/%7Eveithen/1.5.4/>
>>
>> Here's my +1 (binding) to declare the above dist as Apache Rampart 1.5.1
>>
>> thanks,
>> Shankar
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>


-- 
Thanks & Regards,
Prabath

http://blog.facilelogin.com
http://RampartFAQ.com

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Samisa Abeysinghe <sa...@gmail.com>.

I tested and all seems fine!

Here is my vote: +1 (Binding)

Samisa...

On Thu, Dec 23, 2010 at 10:07 AM, Selvaratnam Uthaiyashankar <
uthaiyashankar@gmail.com> wrote:

> Devs,
>
> This is the vote for Apache Rampart 1.5.1 release.
>
> Please review the signed artifacts:
>
> http://people.apache.org/~shankar/rampart/1.5.1/dist/<http://people.apache.org/%7Eshankar/rampart/1.5.1/dist/>
>
> The m2 repository is available at:
> http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/<http://people.apache.org/%7Eshankar/rampart/1.5.1/m2_repo/>
>
> The site is temporarily hosted at:
> http://people.apache.org/~shankar/rampart/1.5.1/site/<http://people.apache.org/%7Eshankar/rampart/1.5.1/site/>
>
> SVN Info:
> https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>
> It was tested against Axis2 release candidates hosted in:
> http://people.apache.org/~veithen/1.5.4/<http://people.apache.org/%7Eveithen/1.5.4/>
>
> Here's my +1 (binding) to declare the above dist as Apache Rampart 1.5.1
>
> thanks,
> Shankar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Selvaratnam Uthaiyashankar <ut...@gmail.com>.

On Tue, Dec 28, 2010 at 3:30 AM, Andreas Veithen
<an...@gmail.com> wrote:
> It's actually not difficult at all to set this up correctly. Here is
> what needs to be done:
>
> 1. Make sure that the project uses a recent version of the
> org.apache:apache super-POM (which contains the relevant default
> configurations for the standard Apache release process).
> 2. Ask infra to add org.apache.rampart to the Axis2 staging profile
> (see INFRA-3271 for corresponding the request for Sandesha2).


It is already done[1] and I am waiting for the response.

Regards,
Shankar

[1] https://issues.apache.org/jira/browse/INFRA-3320


> 3. Eliminate stuff from the Rampart POMs that conflicts with the
> configurations in org.apache:apache.
> 4. [For the RM and other people who want to test the release process]
> Set up the credentials in settings.xml as described in [1].
> 5. Test the release process, check the produced artifacts and do
> whatever fixes are necessary.
>
> It should only take a couple of hours to do the necessary changes. The
> only uncertainty is item 2, because this requires somebody from the
> infra team to pick up and execute the task.
>
> Andreas
>
> [1] http://axis.apache.org/axis2/java/core/release-process.html#Pre-requisites
>
> On Sat, Dec 25, 2010 at 10:18, Senaka Fernando <se...@apache.org> wrote:
>> Hi all,
>>
>> Andreas is correct. I discussed the issue on legal@, and the conclusions
>> were to stage a Maven Repository. Also, we might need to work with infra@ to
>> get the permissions etc sorted out, and we will have to use the Maven
>> release plugin to sign the Maven artifacts.
>>
>> Now, Rampart and Sandesha2, should be having a nearly similar structure, and
>> we should be able to follow the same approach here.
>>
>> Thanks,
>> Senaka.
>>
>> On Sat, Dec 25, 2010 at 2:14 AM, Andreas Veithen <an...@gmail.com>
>> wrote:
>>>
>>> On Fri, Dec 24, 2010 at 16:07, Senaka Fernando <se...@apache.org> wrote:
>>> > Hi Andreas,
>>> >
>>> > On Fri, Dec 24, 2010 at 2:04 PM, Andreas Veithen
>>> > <an...@gmail.com>
>>> > wrote:
>>> >>
>>> >> On Fri, Dec 24, 2010 at 07:33, Senaka Fernando <se...@apache.org>
>>> >> wrote:
>>> >> > Hi Andreas,
>>> >> >
>>> >> > Many thanks for reminding.
>>> >> >
>>> >> > On Fri, Dec 24, 2010 at 4:54 AM, Andreas Veithen
>>> >> > <an...@gmail.com>
>>> >> > wrote:
>>> >> >>
>>> >> >> Unfortunately, the release candidate doesn't yet meet the (new) ASF
>>> >> >> requirements for a valid release :-(. See [1]:
>>> >> >>
>>> >> >> "Every artifact distributed by the Apache Software Foundation should
>>> >> >> and every new one must be accompanied by one file containing an
>>> >> >> OpenPGP compatible ASCII armored detached signature and another file
>>> >> >> containing an MD5 checksum."
>>> >> >>
>>> >> >> Although the document doesn't mention Maven artifacts explicitly,
>>> >> >> the
>>> >> >> common interpretation [2] of this requirement is that every
>>> >> >> individual
>>> >> >> Maven artifact must be signed.
>>> >> >
>>> >> > I will get this clarified, to how this should be done. Signing Maven
>>> >> > artifacts should not be done manually, it should be done
>>> >> > automatically
>>> >> > through Maven itself. And, I don't see many apache projects doing the
>>> >> > same
>>> >> > as of now.
>>> >> >>
>>> >> >> Also, I think that the key used to sign the distributions doesn't
>>> >> >> meet
>>> >> >> the new requirements in terms of key type and length.
>>> >> >
>>> >> > Yes, that's a concern, the required key-lengths were revised, and
>>> >> > mentioned
>>> >> > at the very top of [1]. There were some instructions to how you could
>>> >> > upgrade, if you already have a weak key.
>>> >> >>
>>> >> >> These requirements are part of the reasons why I migrated Axiom,
>>> >> >> Axis2
>>> >> >> and Sandesha2 to the (new) standard ASF release process based on
>>> >> >> maven-release-plugin and Nexus. It automates most of the stuff and
>>> >> >> Nexus does some validation of the artifacts already when staging
>>> >> >> them.
>>> >> >> I think we should migrate Rampart as well, at least for the next
>>> >> >> release.
>>> >> >
>>> >> > So, have you got the Maven Release plugin to sign artifacts as
>>> >> > mentioned,
>>> >> > plus upload them to ASF's Maven repositories in a single go?
>>> >>
>>> >> Yes. Here are the documents that explain how this is executed for
>>> >> Axiom and Axis2:
>>> >>
>>> >> http://ws.apache.org/axiom/devguide/ch02.html#d0e326
>>> >> http://axis.apache.org/axis2/java/core/release-process.html
>>> >>
>>> >> Sandesha2 pretty much sticks to the standard procedure:
>>> >>
>>> >> http://www.apache.org/dev/publishing-maven-artifacts.html
>>> >>
>>> >> As mentioned earlier, before this could be applied to Rampart, you
>>> >> would have to request inclusion of org.apache.rampart in the staging
>>> >> profile for Axis2.
>>> >
>>> > Thanks for the information. For the benefit of someone who's reading
>>> > this
>>> > mail thread, the documents that Andreas linked also explains how you
>>> > could
>>> > publish the artifacts on the staging repo etc.
>>> >
>>> > Having said that, I am yet to figure out the legitimacy (hard to find
>>> > the
>>> > people during the holiday season, :-).. ) of a release without having
>>> > the
>>> > Maven artifacts signed, for projects that are not under the Maven PMC (I
>>> > found out that they do need something as such).
>>> >
>>> > But, as you have mentioned in your first reply to this thread, I'm +1
>>> > for
>>> > introducing the same concepts for Rampart. My concern is that, if these
>>> > requirements are not mandatory, we could go ahead with this release,
>>> > instead
>>> > of delaying it (some other releases, Synapse is also waiting for this
>>> > AFAIK), and fix these inconsistencies for the next release.
>>>
>>> I think these requirements are mandatory for all projects. What is
>>> sure is that if the Maven artifacts are not signed, you will get a
>>> friendly reminder about that:
>>>
>>> http://markmail.org/search/?q=%22your+MAVEN+repo+artifacts%22
>>>
>>> We can't simply ignore this.
>>>
>>> > However, in general, everything under [1] are mandatory, and enforced by
>>> > the
>>> > ASF.
>>> >
>>> > [1] http://www.apache.org/dev/release-signing.html
>>> >
>>> > Thanks,
>>> > Senaka.
>>> >>
>>> >> > [1] http://www.apache.org/dev/release-signing.html
>>> >> >
>>> >> > Thanks,
>>> >> > Senaka.
>>> >> >>
>>> >> >> Andreas
>>> >> >>
>>> >> >> [1] http://www.apache.org/dev/release-signing.html
>>> >> >> [2] http://people.apache.org/~henkp/repo/faq.html
>>> >> >>
>>> >> >> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
>>> >> >> <ut...@gmail.com> wrote:
>>> >> >> > Devs,
>>> >> >> >
>>> >> >> > This is the vote for Apache Rampart 1.5.1 release.
>>> >> >> >
>>> >> >> > Please review the signed artifacts:
>>> >> >> >
>>> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/dist/
>>> >> >> >
>>> >> >> > The m2 repository is available at:
>>> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/
>>> >> >> >
>>> >> >> > The site is temporarily hosted at:
>>> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/site/
>>> >> >> >
>>> >> >> > SVN Info:
>>> >> >> >
>>> >> >> > https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>>> >> >> >
>>> >> >> > It was tested against Axis2 release candidates hosted in:
>>> >> >> > http://people.apache.org/~veithen/1.5.4/
>>> >> >> >
>>> >> >> > Here's my +1 (binding) to declare the above dist as Apache Rampart
>>> >> >> > 1.5.1
>>> >> >> >
>>> >> >> > thanks,
>>> >> >> > Shankar
>>> >> >> >
>>> >> >> >
>>> >> >> > ---------------------------------------------------------------------
>>> >> >> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> >> >> > For additional commands, e-mail: java-dev-help@axis.apache.org
>>> >> >> >
>>> >> >> >
>>> >> >>
>>> >> >>
>>> >> >> ---------------------------------------------------------------------
>>> >> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> >> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>>> >> >>
>>> >> >
>>> >> >
>>> >> >
>>> >> > --
>>> >> > Senaka Fernando
>>> >> > Member; Apache Software Foundation; http://apache.org
>>> >> >
>>> >> > Associate Technical Lead & Product Manager - WSO2 G-Reg;
>>> >> > WSO2, Inc.; http://wso2.com
>>> >> >
>>> >> > E-mail: senaka AT apache.org
>>> >> > P: +94 11 223 2481; M: +94 77 322 1818
>>> >> > Linked-In: http://www.linkedin.com/in/senakafernando
>>> >> > Blog: http://senakafdo.blogspot.com
>>> >> >
>>> >> >
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>>> >>
>>> >> --
>>> >> Senaka Fernando
>>> >> Member; Apache Software Foundation; http://apache.org
>>> >>
>>> >> Associate Technical Lead & Product Manager - WSO2 G-Reg;
>>> >> WSO2, Inc.; http://wso2.com
>>> >>
>>> >> E-mail: senaka AT apache.org
>>> >> P: +94 11 223 2481; M: +94 77 322 1818
>>> >> Linked-In: http://www.linkedin.com/in/senakafernando
>>> >> Blog: http://senakafdo.blogspot.com
>>> >>
>>> >>
>>> >>
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>
>>
>>
>> --
>> Senaka Fernando
>> Member; Apache Software Foundation; http://apache.org
>>
>> Associate Technical Lead & Product Manager - WSO2 G-Reg;
>> WSO2, Inc.; http://wso2.com
>>
>> E-mail: senaka AT apache.org
>> P: +94 11 223 2481; M: +94 77 322 1818
>> Linked-In: http://www.linkedin.com/in/senakafernando
>> Blog: http://senakafdo.blogspot.com
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>



-- 
S.Uthaiyashankar
Senior Architect & Senior Manager
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Andreas Veithen <an...@gmail.com>.

It's actually not difficult at all to set this up correctly. Here is
what needs to be done:

1. Make sure that the project uses a recent version of the
org.apache:apache super-POM (which contains the relevant default
configurations for the standard Apache release process).
2. Ask infra to add org.apache.rampart to the Axis2 staging profile
(see INFRA-3271 for corresponding the request for Sandesha2).
3. Eliminate stuff from the Rampart POMs that conflicts with the
configurations in org.apache:apache.
4. [For the RM and other people who want to test the release process]
Set up the credentials in settings.xml as described in [1].
5. Test the release process, check the produced artifacts and do
whatever fixes are necessary.

It should only take a couple of hours to do the necessary changes. The
only uncertainty is item 2, because this requires somebody from the
infra team to pick up and execute the task.

Andreas

[1] http://axis.apache.org/axis2/java/core/release-process.html#Pre-requisites

On Sat, Dec 25, 2010 at 10:18, Senaka Fernando <se...@apache.org> wrote:
> Hi all,
>
> Andreas is correct. I discussed the issue on legal@, and the conclusions
> were to stage a Maven Repository. Also, we might need to work with infra@ to
> get the permissions etc sorted out, and we will have to use the Maven
> release plugin to sign the Maven artifacts.
>
> Now, Rampart and Sandesha2, should be having a nearly similar structure, and
> we should be able to follow the same approach here.
>
> Thanks,
> Senaka.
>
> On Sat, Dec 25, 2010 at 2:14 AM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> On Fri, Dec 24, 2010 at 16:07, Senaka Fernando <se...@apache.org> wrote:
>> > Hi Andreas,
>> >
>> > On Fri, Dec 24, 2010 at 2:04 PM, Andreas Veithen
>> > <an...@gmail.com>
>> > wrote:
>> >>
>> >> On Fri, Dec 24, 2010 at 07:33, Senaka Fernando <se...@apache.org>
>> >> wrote:
>> >> > Hi Andreas,
>> >> >
>> >> > Many thanks for reminding.
>> >> >
>> >> > On Fri, Dec 24, 2010 at 4:54 AM, Andreas Veithen
>> >> > <an...@gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> Unfortunately, the release candidate doesn't yet meet the (new) ASF
>> >> >> requirements for a valid release :-(. See [1]:
>> >> >>
>> >> >> "Every artifact distributed by the Apache Software Foundation should
>> >> >> and every new one must be accompanied by one file containing an
>> >> >> OpenPGP compatible ASCII armored detached signature and another file
>> >> >> containing an MD5 checksum."
>> >> >>
>> >> >> Although the document doesn't mention Maven artifacts explicitly,
>> >> >> the
>> >> >> common interpretation [2] of this requirement is that every
>> >> >> individual
>> >> >> Maven artifact must be signed.
>> >> >
>> >> > I will get this clarified, to how this should be done. Signing Maven
>> >> > artifacts should not be done manually, it should be done
>> >> > automatically
>> >> > through Maven itself. And, I don't see many apache projects doing the
>> >> > same
>> >> > as of now.
>> >> >>
>> >> >> Also, I think that the key used to sign the distributions doesn't
>> >> >> meet
>> >> >> the new requirements in terms of key type and length.
>> >> >
>> >> > Yes, that's a concern, the required key-lengths were revised, and
>> >> > mentioned
>> >> > at the very top of [1]. There were some instructions to how you could
>> >> > upgrade, if you already have a weak key.
>> >> >>
>> >> >> These requirements are part of the reasons why I migrated Axiom,
>> >> >> Axis2
>> >> >> and Sandesha2 to the (new) standard ASF release process based on
>> >> >> maven-release-plugin and Nexus. It automates most of the stuff and
>> >> >> Nexus does some validation of the artifacts already when staging
>> >> >> them.
>> >> >> I think we should migrate Rampart as well, at least for the next
>> >> >> release.
>> >> >
>> >> > So, have you got the Maven Release plugin to sign artifacts as
>> >> > mentioned,
>> >> > plus upload them to ASF's Maven repositories in a single go?
>> >>
>> >> Yes. Here are the documents that explain how this is executed for
>> >> Axiom and Axis2:
>> >>
>> >> http://ws.apache.org/axiom/devguide/ch02.html#d0e326
>> >> http://axis.apache.org/axis2/java/core/release-process.html
>> >>
>> >> Sandesha2 pretty much sticks to the standard procedure:
>> >>
>> >> http://www.apache.org/dev/publishing-maven-artifacts.html
>> >>
>> >> As mentioned earlier, before this could be applied to Rampart, you
>> >> would have to request inclusion of org.apache.rampart in the staging
>> >> profile for Axis2.
>> >
>> > Thanks for the information. For the benefit of someone who's reading
>> > this
>> > mail thread, the documents that Andreas linked also explains how you
>> > could
>> > publish the artifacts on the staging repo etc.
>> >
>> > Having said that, I am yet to figure out the legitimacy (hard to find
>> > the
>> > people during the holiday season, :-).. ) of a release without having
>> > the
>> > Maven artifacts signed, for projects that are not under the Maven PMC (I
>> > found out that they do need something as such).
>> >
>> > But, as you have mentioned in your first reply to this thread, I'm +1
>> > for
>> > introducing the same concepts for Rampart. My concern is that, if these
>> > requirements are not mandatory, we could go ahead with this release,
>> > instead
>> > of delaying it (some other releases, Synapse is also waiting for this
>> > AFAIK), and fix these inconsistencies for the next release.
>>
>> I think these requirements are mandatory for all projects. What is
>> sure is that if the Maven artifacts are not signed, you will get a
>> friendly reminder about that:
>>
>> http://markmail.org/search/?q=%22your+MAVEN+repo+artifacts%22
>>
>> We can't simply ignore this.
>>
>> > However, in general, everything under [1] are mandatory, and enforced by
>> > the
>> > ASF.
>> >
>> > [1] http://www.apache.org/dev/release-signing.html
>> >
>> > Thanks,
>> > Senaka.
>> >>
>> >> > [1] http://www.apache.org/dev/release-signing.html
>> >> >
>> >> > Thanks,
>> >> > Senaka.
>> >> >>
>> >> >> Andreas
>> >> >>
>> >> >> [1] http://www.apache.org/dev/release-signing.html
>> >> >> [2] http://people.apache.org/~henkp/repo/faq.html
>> >> >>
>> >> >> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
>> >> >> <ut...@gmail.com> wrote:
>> >> >> > Devs,
>> >> >> >
>> >> >> > This is the vote for Apache Rampart 1.5.1 release.
>> >> >> >
>> >> >> > Please review the signed artifacts:
>> >> >> >
>> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/dist/
>> >> >> >
>> >> >> > The m2 repository is available at:
>> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/
>> >> >> >
>> >> >> > The site is temporarily hosted at:
>> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/site/
>> >> >> >
>> >> >> > SVN Info:
>> >> >> >
>> >> >> > https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>> >> >> >
>> >> >> > It was tested against Axis2 release candidates hosted in:
>> >> >> > http://people.apache.org/~veithen/1.5.4/
>> >> >> >
>> >> >> > Here's my +1 (binding) to declare the above dist as Apache Rampart
>> >> >> > 1.5.1
>> >> >> >
>> >> >> > thanks,
>> >> >> > Shankar
>> >> >> >
>> >> >> >
>> >> >> > ---------------------------------------------------------------------
>> >> >> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >> >> > For additional commands, e-mail: java-dev-help@axis.apache.org
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Senaka Fernando
>> >> > Member; Apache Software Foundation; http://apache.org
>> >> >
>> >> > Associate Technical Lead & Product Manager - WSO2 G-Reg;
>> >> > WSO2, Inc.; http://wso2.com
>> >> >
>> >> > E-mail: senaka AT apache.org
>> >> > P: +94 11 223 2481; M: +94 77 322 1818
>> >> > Linked-In: http://www.linkedin.com/in/senakafernando
>> >> > Blog: http://senakafdo.blogspot.com
>> >> >
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>> >>
>> >> --
>> >> Senaka Fernando
>> >> Member; Apache Software Foundation; http://apache.org
>> >>
>> >> Associate Technical Lead & Product Manager - WSO2 G-Reg;
>> >> WSO2, Inc.; http://wso2.com
>> >>
>> >> E-mail: senaka AT apache.org
>> >> P: +94 11 223 2481; M: +94 77 322 1818
>> >> Linked-In: http://www.linkedin.com/in/senakafernando
>> >> Blog: http://senakafdo.blogspot.com
>> >>
>> >>
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>
>
>
> --
> Senaka Fernando
> Member; Apache Software Foundation; http://apache.org
>
> Associate Technical Lead & Product Manager - WSO2 G-Reg;
> WSO2, Inc.; http://wso2.com
>
> E-mail: senaka AT apache.org
> P: +94 11 223 2481; M: +94 77 322 1818
> Linked-In: http://www.linkedin.com/in/senakafernando
> Blog: http://senakafdo.blogspot.com
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Ruwan Linton <ru...@gmail.com>.

Folks so, what is the conclusion, are we going to re-pack, if so the synapse
release has to be restarted with the new Rampart packs :-) for the 5th time.

Ruwan

On Sat, Dec 25, 2010 at 6:43 PM, Senaka Fernando <se...@apache.org> wrote:

>
>
> On Sat, Dec 25, 2010 at 3:08 PM, Selvaratnam Uthaiyashankar <
> uthaiyashankar@gmail.com> wrote:
>
>> On Sat, Dec 25, 2010 at 2:56 PM, Senaka Fernando <se...@apache.org>
>> wrote:
>> > Hi again,
>> >
>> > So, let's work on these changes and get the release out soon, so that
>> other
>> > downstream releases (Synapse etc), can get going.
>>
>> +1. I'll update the pom.xml and host the maven repo again.
>>
>
> +1. FYI, I got these two links from legal@, which were two articles done
> by Donald Woods, for Apache BVAL. These extend the write-up by Henk.
>
> [1] http://incubator.apache.org/bval/cwiki/release-setup.html
> [2] http://incubator.apache.org/bval/cwiki/release-process.html
>
> Thanks,
> Senaka.
>
>>
>> Regards,
>> Shankar
>>
>>
>> >
>> > Wish you all a Merry Christmas!
>> >
>> > Thanks,
>> > Senaka.
>> >
>> > On Sat, Dec 25, 2010 at 2:48 PM, Senaka Fernando <se...@apache.org>
>> wrote:
>> >>
>> >> Hi all,
>> >>
>> >> Andreas is correct. I discussed the issue on legal@, and the
>> conclusions
>> >> were to stage a Maven Repository. Also, we might need to work with
>> infra@ to
>> >> get the permissions etc sorted out, and we will have to use the Maven
>> >> release plugin to sign the Maven artifacts.
>> >>
>> >> Now, Rampart and Sandesha2, should be having a nearly similar
>> structure,
>> >> and we should be able to follow the same approach here.
>> >>
>> >> Thanks,
>> >> Senaka.
>> >>
>> >> On Sat, Dec 25, 2010 at 2:14 AM, Andreas Veithen
>> >> <an...@gmail.com> wrote:
>> >>>
>> >>> On Fri, Dec 24, 2010 at 16:07, Senaka Fernando <se...@apache.org>
>> wrote:
>> >>> > Hi Andreas,
>> >>> >
>> >>> > On Fri, Dec 24, 2010 at 2:04 PM, Andreas Veithen
>> >>> > <an...@gmail.com>
>> >>> > wrote:
>> >>> >>
>> >>> >> On Fri, Dec 24, 2010 at 07:33, Senaka Fernando <se...@apache.org>
>> >>> >> wrote:
>> >>> >> > Hi Andreas,
>> >>> >> >
>> >>> >> > Many thanks for reminding.
>> >>> >> >
>> >>> >> > On Fri, Dec 24, 2010 at 4:54 AM, Andreas Veithen
>> >>> >> > <an...@gmail.com>
>> >>> >> > wrote:
>> >>> >> >>
>> >>> >> >> Unfortunately, the release candidate doesn't yet meet the (new)
>> ASF
>> >>> >> >> requirements for a valid release :-(. See [1]:
>> >>> >> >>
>> >>> >> >> "Every artifact distributed by the Apache Software Foundation
>> >>> >> >> should
>> >>> >> >> and every new one must be accompanied by one file containing an
>> >>> >> >> OpenPGP compatible ASCII armored detached signature and another
>> >>> >> >> file
>> >>> >> >> containing an MD5 checksum."
>> >>> >> >>
>> >>> >> >> Although the document doesn't mention Maven artifacts
>> explicitly,
>> >>> >> >> the
>> >>> >> >> common interpretation [2] of this requirement is that every
>> >>> >> >> individual
>> >>> >> >> Maven artifact must be signed.
>> >>> >> >
>> >>> >> > I will get this clarified, to how this should be done. Signing
>> Maven
>> >>> >> > artifacts should not be done manually, it should be done
>> >>> >> > automatically
>> >>> >> > through Maven itself. And, I don't see many apache projects doing
>> >>> >> > the
>> >>> >> > same
>> >>> >> > as of now.
>> >>> >> >>
>> >>> >> >> Also, I think that the key used to sign the distributions
>> doesn't
>> >>> >> >> meet
>> >>> >> >> the new requirements in terms of key type and length.
>> >>> >> >
>> >>> >> > Yes, that's a concern, the required key-lengths were revised, and
>> >>> >> > mentioned
>> >>> >> > at the very top of [1]. There were some instructions to how you
>> >>> >> > could
>> >>> >> > upgrade, if you already have a weak key.
>> >>> >> >>
>> >>> >> >> These requirements are part of the reasons why I migrated Axiom,
>> >>> >> >> Axis2
>> >>> >> >> and Sandesha2 to the (new) standard ASF release process based on
>> >>> >> >> maven-release-plugin and Nexus. It automates most of the stuff
>> and
>> >>> >> >> Nexus does some validation of the artifacts already when staging
>> >>> >> >> them.
>> >>> >> >> I think we should migrate Rampart as well, at least for the next
>> >>> >> >> release.
>> >>> >> >
>> >>> >> > So, have you got the Maven Release plugin to sign artifacts as
>> >>> >> > mentioned,
>> >>> >> > plus upload them to ASF's Maven repositories in a single go?
>> >>> >>
>> >>> >> Yes. Here are the documents that explain how this is executed for
>> >>> >> Axiom and Axis2:
>> >>> >>
>> >>> >> http://ws.apache.org/axiom/devguide/ch02.html#d0e326
>> >>> >> http://axis.apache.org/axis2/java/core/release-process.html
>> >>> >>
>> >>> >> Sandesha2 pretty much sticks to the standard procedure:
>> >>> >>
>> >>> >> http://www.apache.org/dev/publishing-maven-artifacts.html
>> >>> >>
>> >>> >> As mentioned earlier, before this could be applied to Rampart, you
>> >>> >> would have to request inclusion of org.apache.rampart in the
>> staging
>> >>> >> profile for Axis2.
>> >>> >
>> >>> > Thanks for the information. For the benefit of someone who's reading
>> >>> > this
>> >>> > mail thread, the documents that Andreas linked also explains how you
>> >>> > could
>> >>> > publish the artifacts on the staging repo etc.
>> >>> >
>> >>> > Having said that, I am yet to figure out the legitimacy (hard to
>> find
>> >>> > the
>> >>> > people during the holiday season, :-).. ) of a release without
>> having
>> >>> > the
>> >>> > Maven artifacts signed, for projects that are not under the Maven
>> PMC
>> >>> > (I
>> >>> > found out that they do need something as such).
>> >>> >
>> >>> > But, as you have mentioned in your first reply to this thread, I'm
>> +1
>> >>> > for
>> >>> > introducing the same concepts for Rampart. My concern is that, if
>> these
>> >>> > requirements are not mandatory, we could go ahead with this release,
>> >>> > instead
>> >>> > of delaying it (some other releases, Synapse is also waiting for
>> this
>> >>> > AFAIK), and fix these inconsistencies for the next release.
>> >>>
>> >>> I think these requirements are mandatory for all projects. What is
>> >>> sure is that if the Maven artifacts are not signed, you will get a
>> >>> friendly reminder about that:
>> >>>
>> >>> http://markmail.org/search/?q=%22your+MAVEN+repo+artifacts%22
>> >>>
>> >>> We can't simply ignore this.
>> >>>
>> >>> > However, in general, everything under [1] are mandatory, and
>> enforced
>> >>> > by the
>> >>> > ASF.
>> >>> >
>> >>> > [1] http://www.apache.org/dev/release-signing.html
>> >>> >
>> >>> > Thanks,
>> >>> > Senaka.
>> >>> >>
>> >>> >> > [1] http://www.apache.org/dev/release-signing.html
>> >>> >> >
>> >>> >> > Thanks,
>> >>> >> > Senaka.
>> >>> >> >>
>> >>> >> >> Andreas
>> >>> >> >>
>> >>> >> >> [1] http://www.apache.org/dev/release-signing.html
>> >>> >> >> [2] http://people.apache.org/~henkp/repo/faq.html<http://people.apache.org/%7Ehenkp/repo/faq.html>
>> >>> >> >>
>> >>> >> >> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
>> >>> >> >> <ut...@gmail.com> wrote:
>> >>> >> >> > Devs,
>> >>> >> >> >
>> >>> >> >> > This is the vote for Apache Rampart 1.5.1 release.
>> >>> >> >> >
>> >>> >> >> > Please review the signed artifacts:
>> >>> >> >> >
>> >>> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/dist/<http://people.apache.org/%7Eshankar/rampart/1.5.1/dist/>
>> >>> >> >> >
>> >>> >> >> > The m2 repository is available at:
>> >>> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/<http://people.apache.org/%7Eshankar/rampart/1.5.1/m2_repo/>
>> >>> >> >> >
>> >>> >> >> > The site is temporarily hosted at:
>> >>> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/site/<http://people.apache.org/%7Eshankar/rampart/1.5.1/site/>
>> >>> >> >> >
>> >>> >> >> > SVN Info:
>> >>> >> >> >
>> >>> >> >> >
>> https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>> >>> >> >> >
>> >>> >> >> > It was tested against Axis2 release candidates hosted in:
>> >>> >> >> > http://people.apache.org/~veithen/1.5.4/<http://people.apache.org/%7Eveithen/1.5.4/>
>> >>> >> >> >
>> >>> >> >> > Here's my +1 (binding) to declare the above dist as Apache
>> >>> >> >> > Rampart
>> >>> >> >> > 1.5.1
>> >>> >> >> >
>> >>> >> >> > thanks,
>> >>> >> >> > Shankar
>> >>> >> >> >
>> >>> >> >> >
>> >>> >> >> >
>> ---------------------------------------------------------------------
>> >>> >> >> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >>> >> >> > For additional commands, e-mail:
>> java-dev-help@axis.apache.org
>> >>> >> >> >
>> >>> >> >> >
>> >>> >> >>
>> >>> >> >>
>> >>> >> >>
>> ---------------------------------------------------------------------
>> >>> >> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >>> >> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>> >>> >> >>
>> >>> >> >
>> >>> >> >
>> >>> >> >
>> >>> >> > --
>> >>> >> > Senaka Fernando
>> >>> >> > Member; Apache Software Foundation; http://apache.org
>> >>> >> >
>> >>> >> > Associate Technical Lead & Product Manager - WSO2 G-Reg;
>> >>> >> > WSO2, Inc.; http://wso2.com
>> >>> >> >
>> >>> >> > E-mail: senaka AT apache.org
>> >>> >> > P: +94 11 223 2481; M: +94 77 322 1818
>> >>> >> > Linked-In: http://www.linkedin.com/in/senakafernando
>> >>> >> > Blog: http://senakafdo.blogspot.com
>> >>> >> >
>> >>> >> >
>> >>> >>
>> >>> >>
>> ---------------------------------------------------------------------
>> >>> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >>> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>> >>> >>
>> >>> >> --
>> >>> >> Senaka Fernando
>> >>> >> Member; Apache Software Foundation; http://apache.org
>> >>> >>
>> >>> >> Associate Technical Lead & Product Manager - WSO2 G-Reg;
>> >>> >> WSO2, Inc.; http://wso2.com
>> >>> >>
>> >>> >> E-mail: senaka AT apache.org
>> >>> >> P: +94 11 223 2481; M: +94 77 322 1818
>> >>> >> Linked-In: http://www.linkedin.com/in/senakafernando
>> >>> >> Blog: http://senakafdo.blogspot.com
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >>> For additional commands, e-mail: java-dev-help@axis.apache.org
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Senaka Fernando
>> >> Member; Apache Software Foundation; http://apache.org
>> >>
>> >> Associate Technical Lead & Product Manager - WSO2 G-Reg;
>> >> WSO2, Inc.; http://wso2.com
>> >>
>> >> E-mail: senaka AT apache.org
>> >> P: +94 11 223 2481;
>> >> M: +94 77 322 1818
>> >> Linked-In: http://www.linkedin.com/in/senakafernando
>> >> Blog:
>> >> http://senakafdo.blogspot.com
>> >>
>> >> --
>> >> Senaka Fernando
>> >> Member; Apache Software Foundation;
>> >> http://apache.org
>> >>
>> >> Associate Technical Lead & Product Manager - WSO2 G-Reg;
>> >> WSO2, Inc.; http://wso2.com
>> >>
>> >> E-mail: senaka AT apache.org
>> >> P: +94 11 223 2481; M: +94 77 322 1818
>> >> Linked-In: http://www.linkedin.com/in/senakafernando
>> >> Blog: http://senakafdo.blogspot.com
>> >>
>> >>
>> >>
>> >
>>
>>
>>
>> --
>> S.Uthaiyashankar
>> Senior Architect & Senior Manager
>> WSO2 Inc.
>> http://wso2.com/ - "lean . enterprise . middleware"
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>
>
> --
> *Senaka Fernando*
> Member; Apache Software Foundation; http://apache.org
> *
> Associate Technical Lead & Product Manager - WSO2 G-Reg;
> WSO2, Inc.; http://wso2.com** <http://apache.org/>
>
> E-mail: senaka AT apache.org
> **P: +94 11 223 2481*; *M: +94 77 322 1818
> Linked-In: http://www.linkedin.com/in/senakafernando
> Blog: http://senakafdo.blogspot.com
> *
>



-- 
Ruwan Linton
Software Architect & Product Manager
WSO2 Inc.; http://wso2.org

Lean . Enterprise . Middleware

phone: +1 408 754 7388 ext 51789
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Senaka Fernando <se...@apache.org>.

On Sat, Dec 25, 2010 at 3:08 PM, Selvaratnam Uthaiyashankar <
uthaiyashankar@gmail.com> wrote:

> On Sat, Dec 25, 2010 at 2:56 PM, Senaka Fernando <se...@apache.org>
> wrote:
> > Hi again,
> >
> > So, let's work on these changes and get the release out soon, so that
> other
> > downstream releases (Synapse etc), can get going.
>
> +1. I'll update the pom.xml and host the maven repo again.
>

+1. FYI, I got these two links from legal@, which were two articles done by
Donald Woods, for Apache BVAL. These extend the write-up by Henk.

[1] http://incubator.apache.org/bval/cwiki/release-setup.html
[2] http://incubator.apache.org/bval/cwiki/release-process.html

Thanks,
Senaka.

>
> Regards,
> Shankar
>
>
> >
> > Wish you all a Merry Christmas!
> >
> > Thanks,
> > Senaka.
> >
> > On Sat, Dec 25, 2010 at 2:48 PM, Senaka Fernando <se...@apache.org>
> wrote:
> >>
> >> Hi all,
> >>
> >> Andreas is correct. I discussed the issue on legal@, and the
> conclusions
> >> were to stage a Maven Repository. Also, we might need to work with
> infra@ to
> >> get the permissions etc sorted out, and we will have to use the Maven
> >> release plugin to sign the Maven artifacts.
> >>
> >> Now, Rampart and Sandesha2, should be having a nearly similar structure,
> >> and we should be able to follow the same approach here.
> >>
> >> Thanks,
> >> Senaka.
> >>
> >> On Sat, Dec 25, 2010 at 2:14 AM, Andreas Veithen
> >> <an...@gmail.com> wrote:
> >>>
> >>> On Fri, Dec 24, 2010 at 16:07, Senaka Fernando <se...@apache.org>
> wrote:
> >>> > Hi Andreas,
> >>> >
> >>> > On Fri, Dec 24, 2010 at 2:04 PM, Andreas Veithen
> >>> > <an...@gmail.com>
> >>> > wrote:
> >>> >>
> >>> >> On Fri, Dec 24, 2010 at 07:33, Senaka Fernando <se...@apache.org>
> >>> >> wrote:
> >>> >> > Hi Andreas,
> >>> >> >
> >>> >> > Many thanks for reminding.
> >>> >> >
> >>> >> > On Fri, Dec 24, 2010 at 4:54 AM, Andreas Veithen
> >>> >> > <an...@gmail.com>
> >>> >> > wrote:
> >>> >> >>
> >>> >> >> Unfortunately, the release candidate doesn't yet meet the (new)
> ASF
> >>> >> >> requirements for a valid release :-(. See [1]:
> >>> >> >>
> >>> >> >> "Every artifact distributed by the Apache Software Foundation
> >>> >> >> should
> >>> >> >> and every new one must be accompanied by one file containing an
> >>> >> >> OpenPGP compatible ASCII armored detached signature and another
> >>> >> >> file
> >>> >> >> containing an MD5 checksum."
> >>> >> >>
> >>> >> >> Although the document doesn't mention Maven artifacts explicitly,
> >>> >> >> the
> >>> >> >> common interpretation [2] of this requirement is that every
> >>> >> >> individual
> >>> >> >> Maven artifact must be signed.
> >>> >> >
> >>> >> > I will get this clarified, to how this should be done. Signing
> Maven
> >>> >> > artifacts should not be done manually, it should be done
> >>> >> > automatically
> >>> >> > through Maven itself. And, I don't see many apache projects doing
> >>> >> > the
> >>> >> > same
> >>> >> > as of now.
> >>> >> >>
> >>> >> >> Also, I think that the key used to sign the distributions doesn't
> >>> >> >> meet
> >>> >> >> the new requirements in terms of key type and length.
> >>> >> >
> >>> >> > Yes, that's a concern, the required key-lengths were revised, and
> >>> >> > mentioned
> >>> >> > at the very top of [1]. There were some instructions to how you
> >>> >> > could
> >>> >> > upgrade, if you already have a weak key.
> >>> >> >>
> >>> >> >> These requirements are part of the reasons why I migrated Axiom,
> >>> >> >> Axis2
> >>> >> >> and Sandesha2 to the (new) standard ASF release process based on
> >>> >> >> maven-release-plugin and Nexus. It automates most of the stuff
> and
> >>> >> >> Nexus does some validation of the artifacts already when staging
> >>> >> >> them.
> >>> >> >> I think we should migrate Rampart as well, at least for the next
> >>> >> >> release.
> >>> >> >
> >>> >> > So, have you got the Maven Release plugin to sign artifacts as
> >>> >> > mentioned,
> >>> >> > plus upload them to ASF's Maven repositories in a single go?
> >>> >>
> >>> >> Yes. Here are the documents that explain how this is executed for
> >>> >> Axiom and Axis2:
> >>> >>
> >>> >> http://ws.apache.org/axiom/devguide/ch02.html#d0e326
> >>> >> http://axis.apache.org/axis2/java/core/release-process.html
> >>> >>
> >>> >> Sandesha2 pretty much sticks to the standard procedure:
> >>> >>
> >>> >> http://www.apache.org/dev/publishing-maven-artifacts.html
> >>> >>
> >>> >> As mentioned earlier, before this could be applied to Rampart, you
> >>> >> would have to request inclusion of org.apache.rampart in the staging
> >>> >> profile for Axis2.
> >>> >
> >>> > Thanks for the information. For the benefit of someone who's reading
> >>> > this
> >>> > mail thread, the documents that Andreas linked also explains how you
> >>> > could
> >>> > publish the artifacts on the staging repo etc.
> >>> >
> >>> > Having said that, I am yet to figure out the legitimacy (hard to find
> >>> > the
> >>> > people during the holiday season, :-).. ) of a release without having
> >>> > the
> >>> > Maven artifacts signed, for projects that are not under the Maven PMC
> >>> > (I
> >>> > found out that they do need something as such).
> >>> >
> >>> > But, as you have mentioned in your first reply to this thread, I'm +1
> >>> > for
> >>> > introducing the same concepts for Rampart. My concern is that, if
> these
> >>> > requirements are not mandatory, we could go ahead with this release,
> >>> > instead
> >>> > of delaying it (some other releases, Synapse is also waiting for this
> >>> > AFAIK), and fix these inconsistencies for the next release.
> >>>
> >>> I think these requirements are mandatory for all projects. What is
> >>> sure is that if the Maven artifacts are not signed, you will get a
> >>> friendly reminder about that:
> >>>
> >>> http://markmail.org/search/?q=%22your+MAVEN+repo+artifacts%22
> >>>
> >>> We can't simply ignore this.
> >>>
> >>> > However, in general, everything under [1] are mandatory, and enforced
> >>> > by the
> >>> > ASF.
> >>> >
> >>> > [1] http://www.apache.org/dev/release-signing.html
> >>> >
> >>> > Thanks,
> >>> > Senaka.
> >>> >>
> >>> >> > [1] http://www.apache.org/dev/release-signing.html
> >>> >> >
> >>> >> > Thanks,
> >>> >> > Senaka.
> >>> >> >>
> >>> >> >> Andreas
> >>> >> >>
> >>> >> >> [1] http://www.apache.org/dev/release-signing.html
> >>> >> >> [2] http://people.apache.org/~henkp/repo/faq.html<http://people.apache.org/%7Ehenkp/repo/faq.html>
> >>> >> >>
> >>> >> >> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
> >>> >> >> <ut...@gmail.com> wrote:
> >>> >> >> > Devs,
> >>> >> >> >
> >>> >> >> > This is the vote for Apache Rampart 1.5.1 release.
> >>> >> >> >
> >>> >> >> > Please review the signed artifacts:
> >>> >> >> >
> >>> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/dist/<http://people.apache.org/%7Eshankar/rampart/1.5.1/dist/>
> >>> >> >> >
> >>> >> >> > The m2 repository is available at:
> >>> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/<http://people.apache.org/%7Eshankar/rampart/1.5.1/m2_repo/>
> >>> >> >> >
> >>> >> >> > The site is temporarily hosted at:
> >>> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/site/<http://people.apache.org/%7Eshankar/rampart/1.5.1/site/>
> >>> >> >> >
> >>> >> >> > SVN Info:
> >>> >> >> >
> >>> >> >> >
> https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
> >>> >> >> >
> >>> >> >> > It was tested against Axis2 release candidates hosted in:
> >>> >> >> > http://people.apache.org/~veithen/1.5.4/<http://people.apache.org/%7Eveithen/1.5.4/>
> >>> >> >> >
> >>> >> >> > Here's my +1 (binding) to declare the above dist as Apache
> >>> >> >> > Rampart
> >>> >> >> > 1.5.1
> >>> >> >> >
> >>> >> >> > thanks,
> >>> >> >> > Shankar
> >>> >> >> >
> >>> >> >> >
> >>> >> >> >
> ---------------------------------------------------------------------
> >>> >> >> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >>> >> >> > For additional commands, e-mail: java-dev-help@axis.apache.org
> >>> >> >> >
> >>> >> >> >
> >>> >> >>
> >>> >> >>
> >>> >> >>
> ---------------------------------------------------------------------
> >>> >> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >>> >> >> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>> >> >>
> >>> >> >
> >>> >> >
> >>> >> >
> >>> >> > --
> >>> >> > Senaka Fernando
> >>> >> > Member; Apache Software Foundation; http://apache.org
> >>> >> >
> >>> >> > Associate Technical Lead & Product Manager - WSO2 G-Reg;
> >>> >> > WSO2, Inc.; http://wso2.com
> >>> >> >
> >>> >> > E-mail: senaka AT apache.org
> >>> >> > P: +94 11 223 2481; M: +94 77 322 1818
> >>> >> > Linked-In: http://www.linkedin.com/in/senakafernando
> >>> >> > Blog: http://senakafdo.blogspot.com
> >>> >> >
> >>> >> >
> >>> >>
> >>> >>
> ---------------------------------------------------------------------
> >>> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >>> >> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>> >>
> >>> >> --
> >>> >> Senaka Fernando
> >>> >> Member; Apache Software Foundation; http://apache.org
> >>> >>
> >>> >> Associate Technical Lead & Product Manager - WSO2 G-Reg;
> >>> >> WSO2, Inc.; http://wso2.com
> >>> >>
> >>> >> E-mail: senaka AT apache.org
> >>> >> P: +94 11 223 2481; M: +94 77 322 1818
> >>> >> Linked-In: http://www.linkedin.com/in/senakafernando
> >>> >> Blog: http://senakafdo.blogspot.com
> >>> >>
> >>> >>
> >>> >>
> >>> >
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >>> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>>
> >>
> >>
> >>
> >> --
> >> Senaka Fernando
> >> Member; Apache Software Foundation; http://apache.org
> >>
> >> Associate Technical Lead & Product Manager - WSO2 G-Reg;
> >> WSO2, Inc.; http://wso2.com
> >>
> >> E-mail: senaka AT apache.org
> >> P: +94 11 223 2481;
> >> M: +94 77 322 1818
> >> Linked-In: http://www.linkedin.com/in/senakafernando
> >> Blog:
> >> http://senakafdo.blogspot.com
> >>
> >> --
> >> Senaka Fernando
> >> Member; Apache Software Foundation;
> >> http://apache.org
> >>
> >> Associate Technical Lead & Product Manager - WSO2 G-Reg;
> >> WSO2, Inc.; http://wso2.com
> >>
> >> E-mail: senaka AT apache.org
> >> P: +94 11 223 2481; M: +94 77 322 1818
> >> Linked-In: http://www.linkedin.com/in/senakafernando
> >> Blog: http://senakafdo.blogspot.com
> >>
> >>
> >>
> >
>
>
>
> --
> S.Uthaiyashankar
> Senior Architect & Senior Manager
> WSO2 Inc.
> http://wso2.com/ - "lean . enterprise . middleware"
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>


-- 
*Senaka Fernando*
Member; Apache Software Foundation; http://apache.org
*
Associate Technical Lead & Product Manager - WSO2 G-Reg;
WSO2, Inc.; http://wso2.com** <http://apache.org/>

E-mail: senaka AT apache.org
**P: +94 11 223 2481*; *M: +94 77 322 1818
Linked-In: http://www.linkedin.com/in/senakafernando
Blog: http://senakafdo.blogspot.com
*

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Selvaratnam Uthaiyashankar <ut...@gmail.com>.

On Sat, Dec 25, 2010 at 2:56 PM, Senaka Fernando <se...@apache.org> wrote:
> Hi again,
>
> So, let's work on these changes and get the release out soon, so that other
> downstream releases (Synapse etc), can get going.

+1. I'll update the pom.xml and host the maven repo again.

Regards,
Shankar


>
> Wish you all a Merry Christmas!
>
> Thanks,
> Senaka.
>
> On Sat, Dec 25, 2010 at 2:48 PM, Senaka Fernando <se...@apache.org> wrote:
>>
>> Hi all,
>>
>> Andreas is correct. I discussed the issue on legal@, and the conclusions
>> were to stage a Maven Repository. Also, we might need to work with infra@ to
>> get the permissions etc sorted out, and we will have to use the Maven
>> release plugin to sign the Maven artifacts.
>>
>> Now, Rampart and Sandesha2, should be having a nearly similar structure,
>> and we should be able to follow the same approach here.
>>
>> Thanks,
>> Senaka.
>>
>> On Sat, Dec 25, 2010 at 2:14 AM, Andreas Veithen
>> <an...@gmail.com> wrote:
>>>
>>> On Fri, Dec 24, 2010 at 16:07, Senaka Fernando <se...@apache.org> wrote:
>>> > Hi Andreas,
>>> >
>>> > On Fri, Dec 24, 2010 at 2:04 PM, Andreas Veithen
>>> > <an...@gmail.com>
>>> > wrote:
>>> >>
>>> >> On Fri, Dec 24, 2010 at 07:33, Senaka Fernando <se...@apache.org>
>>> >> wrote:
>>> >> > Hi Andreas,
>>> >> >
>>> >> > Many thanks for reminding.
>>> >> >
>>> >> > On Fri, Dec 24, 2010 at 4:54 AM, Andreas Veithen
>>> >> > <an...@gmail.com>
>>> >> > wrote:
>>> >> >>
>>> >> >> Unfortunately, the release candidate doesn't yet meet the (new) ASF
>>> >> >> requirements for a valid release :-(. See [1]:
>>> >> >>
>>> >> >> "Every artifact distributed by the Apache Software Foundation
>>> >> >> should
>>> >> >> and every new one must be accompanied by one file containing an
>>> >> >> OpenPGP compatible ASCII armored detached signature and another
>>> >> >> file
>>> >> >> containing an MD5 checksum."
>>> >> >>
>>> >> >> Although the document doesn't mention Maven artifacts explicitly,
>>> >> >> the
>>> >> >> common interpretation [2] of this requirement is that every
>>> >> >> individual
>>> >> >> Maven artifact must be signed.
>>> >> >
>>> >> > I will get this clarified, to how this should be done. Signing Maven
>>> >> > artifacts should not be done manually, it should be done
>>> >> > automatically
>>> >> > through Maven itself. And, I don't see many apache projects doing
>>> >> > the
>>> >> > same
>>> >> > as of now.
>>> >> >>
>>> >> >> Also, I think that the key used to sign the distributions doesn't
>>> >> >> meet
>>> >> >> the new requirements in terms of key type and length.
>>> >> >
>>> >> > Yes, that's a concern, the required key-lengths were revised, and
>>> >> > mentioned
>>> >> > at the very top of [1]. There were some instructions to how you
>>> >> > could
>>> >> > upgrade, if you already have a weak key.
>>> >> >>
>>> >> >> These requirements are part of the reasons why I migrated Axiom,
>>> >> >> Axis2
>>> >> >> and Sandesha2 to the (new) standard ASF release process based on
>>> >> >> maven-release-plugin and Nexus. It automates most of the stuff and
>>> >> >> Nexus does some validation of the artifacts already when staging
>>> >> >> them.
>>> >> >> I think we should migrate Rampart as well, at least for the next
>>> >> >> release.
>>> >> >
>>> >> > So, have you got the Maven Release plugin to sign artifacts as
>>> >> > mentioned,
>>> >> > plus upload them to ASF's Maven repositories in a single go?
>>> >>
>>> >> Yes. Here are the documents that explain how this is executed for
>>> >> Axiom and Axis2:
>>> >>
>>> >> http://ws.apache.org/axiom/devguide/ch02.html#d0e326
>>> >> http://axis.apache.org/axis2/java/core/release-process.html
>>> >>
>>> >> Sandesha2 pretty much sticks to the standard procedure:
>>> >>
>>> >> http://www.apache.org/dev/publishing-maven-artifacts.html
>>> >>
>>> >> As mentioned earlier, before this could be applied to Rampart, you
>>> >> would have to request inclusion of org.apache.rampart in the staging
>>> >> profile for Axis2.
>>> >
>>> > Thanks for the information. For the benefit of someone who's reading
>>> > this
>>> > mail thread, the documents that Andreas linked also explains how you
>>> > could
>>> > publish the artifacts on the staging repo etc.
>>> >
>>> > Having said that, I am yet to figure out the legitimacy (hard to find
>>> > the
>>> > people during the holiday season, :-).. ) of a release without having
>>> > the
>>> > Maven artifacts signed, for projects that are not under the Maven PMC
>>> > (I
>>> > found out that they do need something as such).
>>> >
>>> > But, as you have mentioned in your first reply to this thread, I'm +1
>>> > for
>>> > introducing the same concepts for Rampart. My concern is that, if these
>>> > requirements are not mandatory, we could go ahead with this release,
>>> > instead
>>> > of delaying it (some other releases, Synapse is also waiting for this
>>> > AFAIK), and fix these inconsistencies for the next release.
>>>
>>> I think these requirements are mandatory for all projects. What is
>>> sure is that if the Maven artifacts are not signed, you will get a
>>> friendly reminder about that:
>>>
>>> http://markmail.org/search/?q=%22your+MAVEN+repo+artifacts%22
>>>
>>> We can't simply ignore this.
>>>
>>> > However, in general, everything under [1] are mandatory, and enforced
>>> > by the
>>> > ASF.
>>> >
>>> > [1] http://www.apache.org/dev/release-signing.html
>>> >
>>> > Thanks,
>>> > Senaka.
>>> >>
>>> >> > [1] http://www.apache.org/dev/release-signing.html
>>> >> >
>>> >> > Thanks,
>>> >> > Senaka.
>>> >> >>
>>> >> >> Andreas
>>> >> >>
>>> >> >> [1] http://www.apache.org/dev/release-signing.html
>>> >> >> [2] http://people.apache.org/~henkp/repo/faq.html
>>> >> >>
>>> >> >> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
>>> >> >> <ut...@gmail.com> wrote:
>>> >> >> > Devs,
>>> >> >> >
>>> >> >> > This is the vote for Apache Rampart 1.5.1 release.
>>> >> >> >
>>> >> >> > Please review the signed artifacts:
>>> >> >> >
>>> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/dist/
>>> >> >> >
>>> >> >> > The m2 repository is available at:
>>> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/
>>> >> >> >
>>> >> >> > The site is temporarily hosted at:
>>> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/site/
>>> >> >> >
>>> >> >> > SVN Info:
>>> >> >> >
>>> >> >> > https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>>> >> >> >
>>> >> >> > It was tested against Axis2 release candidates hosted in:
>>> >> >> > http://people.apache.org/~veithen/1.5.4/
>>> >> >> >
>>> >> >> > Here's my +1 (binding) to declare the above dist as Apache
>>> >> >> > Rampart
>>> >> >> > 1.5.1
>>> >> >> >
>>> >> >> > thanks,
>>> >> >> > Shankar
>>> >> >> >
>>> >> >> >
>>> >> >> > ---------------------------------------------------------------------
>>> >> >> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> >> >> > For additional commands, e-mail: java-dev-help@axis.apache.org
>>> >> >> >
>>> >> >> >
>>> >> >>
>>> >> >>
>>> >> >> ---------------------------------------------------------------------
>>> >> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> >> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>>> >> >>
>>> >> >
>>> >> >
>>> >> >
>>> >> > --
>>> >> > Senaka Fernando
>>> >> > Member; Apache Software Foundation; http://apache.org
>>> >> >
>>> >> > Associate Technical Lead & Product Manager - WSO2 G-Reg;
>>> >> > WSO2, Inc.; http://wso2.com
>>> >> >
>>> >> > E-mail: senaka AT apache.org
>>> >> > P: +94 11 223 2481; M: +94 77 322 1818
>>> >> > Linked-In: http://www.linkedin.com/in/senakafernando
>>> >> > Blog: http://senakafdo.blogspot.com
>>> >> >
>>> >> >
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>>> >>
>>> >> --
>>> >> Senaka Fernando
>>> >> Member; Apache Software Foundation; http://apache.org
>>> >>
>>> >> Associate Technical Lead & Product Manager - WSO2 G-Reg;
>>> >> WSO2, Inc.; http://wso2.com
>>> >>
>>> >> E-mail: senaka AT apache.org
>>> >> P: +94 11 223 2481; M: +94 77 322 1818
>>> >> Linked-In: http://www.linkedin.com/in/senakafernando
>>> >> Blog: http://senakafdo.blogspot.com
>>> >>
>>> >>
>>> >>
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>
>>
>>
>> --
>> Senaka Fernando
>> Member; Apache Software Foundation; http://apache.org
>>
>> Associate Technical Lead & Product Manager - WSO2 G-Reg;
>> WSO2, Inc.; http://wso2.com
>>
>> E-mail: senaka AT apache.org
>> P: +94 11 223 2481;
>> M: +94 77 322 1818
>> Linked-In: http://www.linkedin.com/in/senakafernando
>> Blog:
>> http://senakafdo.blogspot.com
>>
>> --
>> Senaka Fernando
>> Member; Apache Software Foundation;
>> http://apache.org
>>
>> Associate Technical Lead & Product Manager - WSO2 G-Reg;
>> WSO2, Inc.; http://wso2.com
>>
>> E-mail: senaka AT apache.org
>> P: +94 11 223 2481; M: +94 77 322 1818
>> Linked-In: http://www.linkedin.com/in/senakafernando
>> Blog: http://senakafdo.blogspot.com
>>
>>
>>
>



-- 
S.Uthaiyashankar
Senior Architect & Senior Manager
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Senaka Fernando <se...@apache.org>.

Hi again,

So, let's work on these changes and get the release out soon, so that other
downstream releases (Synapse etc), can get going.

Wish you all a Merry Christmas!

Thanks,
Senaka.

On Sat, Dec 25, 2010 at 2:48 PM, Senaka Fernando <se...@apache.org> wrote:

> Hi all,
>
> Andreas is correct. I discussed the issue on legal@, and the conclusions
> were to stage a Maven Repository. Also, we might need to work with infra@to get the permissions etc sorted out, and we will have to use the Maven
> release plugin to sign the Maven artifacts.
>
> Now, Rampart and Sandesha2, should be having a nearly similar structure,
> and we should be able to follow the same approach here.
>
> Thanks,
> Senaka.
>
>
> On Sat, Dec 25, 2010 at 2:14 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Fri, Dec 24, 2010 at 16:07, Senaka Fernando <se...@apache.org> wrote:
>> > Hi Andreas,
>> >
>> > On Fri, Dec 24, 2010 at 2:04 PM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> On Fri, Dec 24, 2010 at 07:33, Senaka Fernando <se...@apache.org>
>> wrote:
>> >> > Hi Andreas,
>> >> >
>> >> > Many thanks for reminding.
>> >> >
>> >> > On Fri, Dec 24, 2010 at 4:54 AM, Andreas Veithen
>> >> > <an...@gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> Unfortunately, the release candidate doesn't yet meet the (new) ASF
>> >> >> requirements for a valid release :-(. See [1]:
>> >> >>
>> >> >> "Every artifact distributed by the Apache Software Foundation should
>> >> >> and every new one must be accompanied by one file containing an
>> >> >> OpenPGP compatible ASCII armored detached signature and another file
>> >> >> containing an MD5 checksum."
>> >> >>
>> >> >> Although the document doesn't mention Maven artifacts explicitly,
>> the
>> >> >> common interpretation [2] of this requirement is that every
>> individual
>> >> >> Maven artifact must be signed.
>> >> >
>> >> > I will get this clarified, to how this should be done. Signing Maven
>> >> > artifacts should not be done manually, it should be done
>> automatically
>> >> > through Maven itself. And, I don't see many apache projects doing the
>> >> > same
>> >> > as of now.
>> >> >>
>> >> >> Also, I think that the key used to sign the distributions doesn't
>> meet
>> >> >> the new requirements in terms of key type and length.
>> >> >
>> >> > Yes, that's a concern, the required key-lengths were revised, and
>> >> > mentioned
>> >> > at the very top of [1]. There were some instructions to how you could
>> >> > upgrade, if you already have a weak key.
>> >> >>
>> >> >> These requirements are part of the reasons why I migrated Axiom,
>> Axis2
>> >> >> and Sandesha2 to the (new) standard ASF release process based on
>> >> >> maven-release-plugin and Nexus. It automates most of the stuff and
>> >> >> Nexus does some validation of the artifacts already when staging
>> them.
>> >> >> I think we should migrate Rampart as well, at least for the next
>> >> >> release.
>> >> >
>> >> > So, have you got the Maven Release plugin to sign artifacts as
>> >> > mentioned,
>> >> > plus upload them to ASF's Maven repositories in a single go?
>> >>
>> >> Yes. Here are the documents that explain how this is executed for
>> >> Axiom and Axis2:
>> >>
>> >> http://ws.apache.org/axiom/devguide/ch02.html#d0e326
>> >> http://axis.apache.org/axis2/java/core/release-process.html
>> >>
>> >> Sandesha2 pretty much sticks to the standard procedure:
>> >>
>> >> http://www.apache.org/dev/publishing-maven-artifacts.html
>> >>
>> >> As mentioned earlier, before this could be applied to Rampart, you
>> >> would have to request inclusion of org.apache.rampart in the staging
>> >> profile for Axis2.
>> >
>> > Thanks for the information. For the benefit of someone who's reading
>> this
>> > mail thread, the documents that Andreas linked also explains how you
>> could
>> > publish the artifacts on the staging repo etc.
>> >
>> > Having said that, I am yet to figure out the legitimacy (hard to find
>> the
>> > people during the holiday season, :-).. ) of a release without having
>> the
>> > Maven artifacts signed, for projects that are not under the Maven PMC (I
>> > found out that they do need something as such).
>> >
>> > But, as you have mentioned in your first reply to this thread, I'm +1
>> for
>> > introducing the same concepts for Rampart. My concern is that, if these
>> > requirements are not mandatory, we could go ahead with this release,
>> instead
>> > of delaying it (some other releases, Synapse is also waiting for this
>> > AFAIK), and fix these inconsistencies for the next release.
>>
>> I think these requirements are mandatory for all projects. What is
>> sure is that if the Maven artifacts are not signed, you will get a
>> friendly reminder about that:
>>
>> http://markmail.org/search/?q=%22your+MAVEN+repo+artifacts%22
>>
>> We can't simply ignore this.
>>
>> > However, in general, everything under [1] are mandatory, and enforced by
>> the
>> > ASF.
>> >
>> > [1] http://www.apache.org/dev/release-signing.html
>> >
>> > Thanks,
>> > Senaka.
>> >>
>> >> > [1] http://www.apache.org/dev/release-signing.html
>> >> >
>> >> > Thanks,
>> >> > Senaka.
>> >> >>
>> >> >> Andreas
>> >> >>
>> >> >> [1] http://www.apache.org/dev/release-signing.html
>> >> >> [2] http://people.apache.org/~henkp/repo/faq.html<http://people.apache.org/%7Ehenkp/repo/faq.html>
>> >> >>
>> >> >> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
>> >> >> <ut...@gmail.com> wrote:
>> >> >> > Devs,
>> >> >> >
>> >> >> > This is the vote for Apache Rampart 1.5.1 release.
>> >> >> >
>> >> >> > Please review the signed artifacts:
>> >> >> >
>> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/dist/<http://people.apache.org/%7Eshankar/rampart/1.5.1/dist/>
>> >> >> >
>> >> >> > The m2 repository is available at:
>> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/<http://people.apache.org/%7Eshankar/rampart/1.5.1/m2_repo/>
>> >> >> >
>> >> >> > The site is temporarily hosted at:
>> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/site/<http://people.apache.org/%7Eshankar/rampart/1.5.1/site/>
>> >> >> >
>> >> >> > SVN Info:
>> >> >> >
>> https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>> >> >> >
>> >> >> > It was tested against Axis2 release candidates hosted in:
>> >> >> > http://people.apache.org/~veithen/1.5.4/<http://people.apache.org/%7Eveithen/1.5.4/>
>> >> >> >
>> >> >> > Here's my +1 (binding) to declare the above dist as Apache Rampart
>> >> >> > 1.5.1
>> >> >> >
>> >> >> > thanks,
>> >> >> > Shankar
>> >> >> >
>> >> >> >
>> ---------------------------------------------------------------------
>> >> >> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >> >> > For additional commands, e-mail: java-dev-help@axis.apache.org
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Senaka Fernando
>> >> > Member; Apache Software Foundation; http://apache.org
>> >> >
>> >> > Associate Technical Lead & Product Manager - WSO2 G-Reg;
>> >> > WSO2, Inc.; http://wso2.com
>> >> >
>> >> > E-mail: senaka AT apache.org
>> >> > P: +94 11 223 2481; M: +94 77 322 1818
>> >> > Linked-In: http://www.linkedin.com/in/senakafernando
>> >> > Blog: http://senakafdo.blogspot.com
>> >> >
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>> >>
>> >> --
>> >> Senaka Fernando
>> >> Member; Apache Software Foundation; http://apache.org
>> >>
>> >> Associate Technical Lead & Product Manager - WSO2 G-Reg;
>> >> WSO2, Inc.; http://wso2.com
>> >>
>> >> E-mail: senaka AT apache.org
>> >> P: +94 11 223 2481; M: +94 77 322 1818
>> >> Linked-In: http://www.linkedin.com/in/senakafernando
>> >> Blog: http://senakafdo.blogspot.com
>> >>
>> >>
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>
>
> --
> *Senaka Fernando*
> Member; Apache Software Foundation; http://apache.org
> *
> Associate Technical Lead & Product Manager - WSO2 G-Reg;
> WSO2, Inc.; http://wso2.com** <http://apache.org/>
>
> E-mail: senaka AT apache.org
> **P: +94 11 223 2481*; *M: +94 77 322 1818
> Linked-In: http://www.linkedin.com/in/senakafernando
> Blog: http://senakafdo.blogspot.com
>
> --
> Senaka Fernando
> Member; Apache Software Foundation; <http://senakafdo.blogspot.com>
> http://apache.org
>
> Associate Technical Lead & Product Manager - WSO2 G-Reg;
> WSO2, Inc.; http://wso2.com <http://apache.org/>
>
> E-mail: senaka AT apache.org
> P: +94 11 223 2481; M: +94 77 322 1818
> Linked-In: http://www.linkedin.com/in/senakafernando
> Blog: http://senakafdo.blogspot.com
>
>
>
> *
>

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Senaka Fernando <se...@apache.org>.

Hi all,

Andreas is correct. I discussed the issue on legal@, and the conclusions
were to stage a Maven Repository. Also, we might need to work with infra@ to
get the permissions etc sorted out, and we will have to use the Maven
release plugin to sign the Maven artifacts.

Now, Rampart and Sandesha2, should be having a nearly similar structure, and
we should be able to follow the same approach here.

Thanks,
Senaka.

On Sat, Dec 25, 2010 at 2:14 AM, Andreas Veithen
<an...@gmail.com>wrote:

> On Fri, Dec 24, 2010 at 16:07, Senaka Fernando <se...@apache.org> wrote:
> > Hi Andreas,
> >
> > On Fri, Dec 24, 2010 at 2:04 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> On Fri, Dec 24, 2010 at 07:33, Senaka Fernando <se...@apache.org>
> wrote:
> >> > Hi Andreas,
> >> >
> >> > Many thanks for reminding.
> >> >
> >> > On Fri, Dec 24, 2010 at 4:54 AM, Andreas Veithen
> >> > <an...@gmail.com>
> >> > wrote:
> >> >>
> >> >> Unfortunately, the release candidate doesn't yet meet the (new) ASF
> >> >> requirements for a valid release :-(. See [1]:
> >> >>
> >> >> "Every artifact distributed by the Apache Software Foundation should
> >> >> and every new one must be accompanied by one file containing an
> >> >> OpenPGP compatible ASCII armored detached signature and another file
> >> >> containing an MD5 checksum."
> >> >>
> >> >> Although the document doesn't mention Maven artifacts explicitly, the
> >> >> common interpretation [2] of this requirement is that every
> individual
> >> >> Maven artifact must be signed.
> >> >
> >> > I will get this clarified, to how this should be done. Signing Maven
> >> > artifacts should not be done manually, it should be done automatically
> >> > through Maven itself. And, I don't see many apache projects doing the
> >> > same
> >> > as of now.
> >> >>
> >> >> Also, I think that the key used to sign the distributions doesn't
> meet
> >> >> the new requirements in terms of key type and length.
> >> >
> >> > Yes, that's a concern, the required key-lengths were revised, and
> >> > mentioned
> >> > at the very top of [1]. There were some instructions to how you could
> >> > upgrade, if you already have a weak key.
> >> >>
> >> >> These requirements are part of the reasons why I migrated Axiom,
> Axis2
> >> >> and Sandesha2 to the (new) standard ASF release process based on
> >> >> maven-release-plugin and Nexus. It automates most of the stuff and
> >> >> Nexus does some validation of the artifacts already when staging
> them.
> >> >> I think we should migrate Rampart as well, at least for the next
> >> >> release.
> >> >
> >> > So, have you got the Maven Release plugin to sign artifacts as
> >> > mentioned,
> >> > plus upload them to ASF's Maven repositories in a single go?
> >>
> >> Yes. Here are the documents that explain how this is executed for
> >> Axiom and Axis2:
> >>
> >> http://ws.apache.org/axiom/devguide/ch02.html#d0e326
> >> http://axis.apache.org/axis2/java/core/release-process.html
> >>
> >> Sandesha2 pretty much sticks to the standard procedure:
> >>
> >> http://www.apache.org/dev/publishing-maven-artifacts.html
> >>
> >> As mentioned earlier, before this could be applied to Rampart, you
> >> would have to request inclusion of org.apache.rampart in the staging
> >> profile for Axis2.
> >
> > Thanks for the information. For the benefit of someone who's reading this
> > mail thread, the documents that Andreas linked also explains how you
> could
> > publish the artifacts on the staging repo etc.
> >
> > Having said that, I am yet to figure out the legitimacy (hard to find the
> > people during the holiday season, :-).. ) of a release without having the
> > Maven artifacts signed, for projects that are not under the Maven PMC (I
> > found out that they do need something as such).
> >
> > But, as you have mentioned in your first reply to this thread, I'm +1 for
> > introducing the same concepts for Rampart. My concern is that, if these
> > requirements are not mandatory, we could go ahead with this release,
> instead
> > of delaying it (some other releases, Synapse is also waiting for this
> > AFAIK), and fix these inconsistencies for the next release.
>
> I think these requirements are mandatory for all projects. What is
> sure is that if the Maven artifacts are not signed, you will get a
> friendly reminder about that:
>
> http://markmail.org/search/?q=%22your+MAVEN+repo+artifacts%22
>
> We can't simply ignore this.
>
> > However, in general, everything under [1] are mandatory, and enforced by
> the
> > ASF.
> >
> > [1] http://www.apache.org/dev/release-signing.html
> >
> > Thanks,
> > Senaka.
> >>
> >> > [1] http://www.apache.org/dev/release-signing.html
> >> >
> >> > Thanks,
> >> > Senaka.
> >> >>
> >> >> Andreas
> >> >>
> >> >> [1] http://www.apache.org/dev/release-signing.html
> >> >> [2] http://people.apache.org/~henkp/repo/faq.html<http://people.apache.org/%7Ehenkp/repo/faq.html>
> >> >>
> >> >> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
> >> >> <ut...@gmail.com> wrote:
> >> >> > Devs,
> >> >> >
> >> >> > This is the vote for Apache Rampart 1.5.1 release.
> >> >> >
> >> >> > Please review the signed artifacts:
> >> >> >
> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/dist/<http://people.apache.org/%7Eshankar/rampart/1.5.1/dist/>
> >> >> >
> >> >> > The m2 repository is available at:
> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/<http://people.apache.org/%7Eshankar/rampart/1.5.1/m2_repo/>
> >> >> >
> >> >> > The site is temporarily hosted at:
> >> >> > http://people.apache.org/~shankar/rampart/1.5.1/site/<http://people.apache.org/%7Eshankar/rampart/1.5.1/site/>
> >> >> >
> >> >> > SVN Info:
> >> >> >
> https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
> >> >> >
> >> >> > It was tested against Axis2 release candidates hosted in:
> >> >> > http://people.apache.org/~veithen/1.5.4/<http://people.apache.org/%7Eveithen/1.5.4/>
> >> >> >
> >> >> > Here's my +1 (binding) to declare the above dist as Apache Rampart
> >> >> > 1.5.1
> >> >> >
> >> >> > thanks,
> >> >> > Shankar
> >> >> >
> >> >> >
> ---------------------------------------------------------------------
> >> >> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >> >> > For additional commands, e-mail: java-dev-help@axis.apache.org
> >> >> >
> >> >> >
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >> >> For additional commands, e-mail: java-dev-help@axis.apache.org
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Senaka Fernando
> >> > Member; Apache Software Foundation; http://apache.org
> >> >
> >> > Associate Technical Lead & Product Manager - WSO2 G-Reg;
> >> > WSO2, Inc.; http://wso2.com
> >> >
> >> > E-mail: senaka AT apache.org
> >> > P: +94 11 223 2481; M: +94 77 322 1818
> >> > Linked-In: http://www.linkedin.com/in/senakafernando
> >> > Blog: http://senakafdo.blogspot.com
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>
> >> --
> >> Senaka Fernando
> >> Member; Apache Software Foundation; http://apache.org
> >>
> >> Associate Technical Lead & Product Manager - WSO2 G-Reg;
> >> WSO2, Inc.; http://wso2.com
> >>
> >> E-mail: senaka AT apache.org
> >> P: +94 11 223 2481; M: +94 77 322 1818
> >> Linked-In: http://www.linkedin.com/in/senakafernando
> >> Blog: http://senakafdo.blogspot.com
> >>
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>


-- 
*Senaka Fernando*
Member; Apache Software Foundation; http://apache.org
*
Associate Technical Lead & Product Manager - WSO2 G-Reg;
WSO2, Inc.; http://wso2.com** <http://apache.org/>

E-mail: senaka AT apache.org
**P: +94 11 223 2481*; *M: +94 77 322 1818
Linked-In: http://www.linkedin.com/in/senakafernando
Blog: http://senakafdo.blogspot.com
*

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Andreas Veithen <an...@gmail.com>.

On Fri, Dec 24, 2010 at 16:07, Senaka Fernando <se...@apache.org> wrote:
> Hi Andreas,
>
> On Fri, Dec 24, 2010 at 2:04 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> On Fri, Dec 24, 2010 at 07:33, Senaka Fernando <se...@apache.org> wrote:
>> > Hi Andreas,
>> >
>> > Many thanks for reminding.
>> >
>> > On Fri, Dec 24, 2010 at 4:54 AM, Andreas Veithen
>> > <an...@gmail.com>
>> > wrote:
>> >>
>> >> Unfortunately, the release candidate doesn't yet meet the (new) ASF
>> >> requirements for a valid release :-(. See [1]:
>> >>
>> >> "Every artifact distributed by the Apache Software Foundation should
>> >> and every new one must be accompanied by one file containing an
>> >> OpenPGP compatible ASCII armored detached signature and another file
>> >> containing an MD5 checksum."
>> >>
>> >> Although the document doesn't mention Maven artifacts explicitly, the
>> >> common interpretation [2] of this requirement is that every individual
>> >> Maven artifact must be signed.
>> >
>> > I will get this clarified, to how this should be done. Signing Maven
>> > artifacts should not be done manually, it should be done automatically
>> > through Maven itself. And, I don't see many apache projects doing the
>> > same
>> > as of now.
>> >>
>> >> Also, I think that the key used to sign the distributions doesn't meet
>> >> the new requirements in terms of key type and length.
>> >
>> > Yes, that's a concern, the required key-lengths were revised, and
>> > mentioned
>> > at the very top of [1]. There were some instructions to how you could
>> > upgrade, if you already have a weak key.
>> >>
>> >> These requirements are part of the reasons why I migrated Axiom, Axis2
>> >> and Sandesha2 to the (new) standard ASF release process based on
>> >> maven-release-plugin and Nexus. It automates most of the stuff and
>> >> Nexus does some validation of the artifacts already when staging them.
>> >> I think we should migrate Rampart as well, at least for the next
>> >> release.
>> >
>> > So, have you got the Maven Release plugin to sign artifacts as
>> > mentioned,
>> > plus upload them to ASF's Maven repositories in a single go?
>>
>> Yes. Here are the documents that explain how this is executed for
>> Axiom and Axis2:
>>
>> http://ws.apache.org/axiom/devguide/ch02.html#d0e326
>> http://axis.apache.org/axis2/java/core/release-process.html
>>
>> Sandesha2 pretty much sticks to the standard procedure:
>>
>> http://www.apache.org/dev/publishing-maven-artifacts.html
>>
>> As mentioned earlier, before this could be applied to Rampart, you
>> would have to request inclusion of org.apache.rampart in the staging
>> profile for Axis2.
>
> Thanks for the information. For the benefit of someone who's reading this
> mail thread, the documents that Andreas linked also explains how you could
> publish the artifacts on the staging repo etc.
>
> Having said that, I am yet to figure out the legitimacy (hard to find the
> people during the holiday season, :-).. ) of a release without having the
> Maven artifacts signed, for projects that are not under the Maven PMC (I
> found out that they do need something as such).
>
> But, as you have mentioned in your first reply to this thread, I'm +1 for
> introducing the same concepts for Rampart. My concern is that, if these
> requirements are not mandatory, we could go ahead with this release, instead
> of delaying it (some other releases, Synapse is also waiting for this
> AFAIK), and fix these inconsistencies for the next release.

I think these requirements are mandatory for all projects. What is
sure is that if the Maven artifacts are not signed, you will get a
friendly reminder about that:

http://markmail.org/search/?q=%22your+MAVEN+repo+artifacts%22

We can't simply ignore this.

> However, in general, everything under [1] are mandatory, and enforced by the
> ASF.
>
> [1] http://www.apache.org/dev/release-signing.html
>
> Thanks,
> Senaka.
>>
>> > [1] http://www.apache.org/dev/release-signing.html
>> >
>> > Thanks,
>> > Senaka.
>> >>
>> >> Andreas
>> >>
>> >> [1] http://www.apache.org/dev/release-signing.html
>> >> [2] http://people.apache.org/~henkp/repo/faq.html
>> >>
>> >> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
>> >> <ut...@gmail.com> wrote:
>> >> > Devs,
>> >> >
>> >> > This is the vote for Apache Rampart 1.5.1 release.
>> >> >
>> >> > Please review the signed artifacts:
>> >> >
>> >> > http://people.apache.org/~shankar/rampart/1.5.1/dist/
>> >> >
>> >> > The m2 repository is available at:
>> >> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/
>> >> >
>> >> > The site is temporarily hosted at:
>> >> > http://people.apache.org/~shankar/rampart/1.5.1/site/
>> >> >
>> >> > SVN Info:
>> >> > https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>> >> >
>> >> > It was tested against Axis2 release candidates hosted in:
>> >> > http://people.apache.org/~veithen/1.5.4/
>> >> >
>> >> > Here's my +1 (binding) to declare the above dist as Apache Rampart
>> >> > 1.5.1
>> >> >
>> >> > thanks,
>> >> > Shankar
>> >> >
>> >> > ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >> > For additional commands, e-mail: java-dev-help@axis.apache.org
>> >> >
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>> >>
>> >
>> >
>> >
>> > --
>> > Senaka Fernando
>> > Member; Apache Software Foundation; http://apache.org
>> >
>> > Associate Technical Lead & Product Manager - WSO2 G-Reg;
>> > WSO2, Inc.; http://wso2.com
>> >
>> > E-mail: senaka AT apache.org
>> > P: +94 11 223 2481; M: +94 77 322 1818
>> > Linked-In: http://www.linkedin.com/in/senakafernando
>> > Blog: http://senakafdo.blogspot.com
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>> --
>> Senaka Fernando
>> Member; Apache Software Foundation; http://apache.org
>>
>> Associate Technical Lead & Product Manager - WSO2 G-Reg;
>> WSO2, Inc.; http://wso2.com
>>
>> E-mail: senaka AT apache.org
>> P: +94 11 223 2481; M: +94 77 322 1818
>> Linked-In: http://www.linkedin.com/in/senakafernando
>> Blog: http://senakafdo.blogspot.com
>>
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Ruwan Linton <ru...@gmail.com>.

+1, lets do this release as it is.

Ruwan

On Fri, Dec 24, 2010 at 8:37 PM, Senaka Fernando <se...@apache.org> wrote:

> Hi Andreas,
>
> On Fri, Dec 24, 2010 at 2:04 PM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Fri, Dec 24, 2010 at 07:33, Senaka Fernando <se...@apache.org> wrote:
>> > Hi Andreas,
>> >
>> > Many thanks for reminding.
>> >
>> > On Fri, Dec 24, 2010 at 4:54 AM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> Unfortunately, the release candidate doesn't yet meet the (new) ASF
>> >> requirements for a valid release :-(. See [1]:
>> >>
>> >> "Every artifact distributed by the Apache Software Foundation should
>> >> and every new one must be accompanied by one file containing an
>> >> OpenPGP compatible ASCII armored detached signature and another file
>> >> containing an MD5 checksum."
>> >>
>> >> Although the document doesn't mention Maven artifacts explicitly, the
>> >> common interpretation [2] of this requirement is that every individual
>> >> Maven artifact must be signed.
>> >
>> > I will get this clarified, to how this should be done. Signing Maven
>> > artifacts should not be done manually, it should be done automatically
>> > through Maven itself. And, I don't see many apache projects doing the
>> same
>> > as of now.
>> >>
>> >> Also, I think that the key used to sign the distributions doesn't meet
>> >> the new requirements in terms of key type and length.
>> >
>> > Yes, that's a concern, the required key-lengths were revised, and
>> mentioned
>> > at the very top of [1]. There were some instructions to how you could
>> > upgrade, if you already have a weak key.
>> >>
>> >> These requirements are part of the reasons why I migrated Axiom, Axis2
>> >> and Sandesha2 to the (new) standard ASF release process based on
>> >> maven-release-plugin and Nexus. It automates most of the stuff and
>> >> Nexus does some validation of the artifacts already when staging them.
>> >> I think we should migrate Rampart as well, at least for the next
>> >> release.
>> >
>> > So, have you got the Maven Release plugin to sign artifacts as
>> mentioned,
>> > plus upload them to ASF's Maven repositories in a single go?
>>
>> Yes. Here are the documents that explain how this is executed for
>> Axiom and Axis2:
>>
>> http://ws.apache.org/axiom/devguide/ch02.html#d0e326
>> http://axis.apache.org/axis2/java/core/release-process.html
>>
>> Sandesha2 pretty much sticks to the standard procedure:
>>
>> http://www.apache.org/dev/publishing-maven-artifacts.html
>>
>> As mentioned earlier, before this could be applied to Rampart, you
>> would have to request inclusion of org.apache.rampart in the staging
>> profile for Axis2.
>>
>
> Thanks for the information. For the benefit of someone who's reading this
> mail thread, the documents that Andreas linked also explains how you could
> publish the artifacts on the staging repo etc.
>
> Having said that, I am yet to figure out the legitimacy (hard to find the
> people during the holiday season, :-).. ) of a release without having the
> Maven artifacts signed, for projects that are not under the Maven PMC (I
> found out that they do need something as such).
>
> But, as you have mentioned in your first reply to this thread, I'm +1 for
> introducing the same concepts for Rampart. My concern is that, if these
> requirements are not mandatory, we could go ahead with this release, instead
> of delaying it (some other releases, Synapse is also waiting for this
> AFAIK), and fix these inconsistencies for the next release.
>
> However, in general, everything under [1] are mandatory, and enforced by
> the ASF.
>
>
> [1] http://www.apache.org/dev/release-signing.html
>
> Thanks,
> Senaka.
>
>>
>> > [1] http://www.apache.org/dev/release-signing.html
>> >
>> > Thanks,
>> > Senaka.
>> >>
>> >> Andreas
>> >>
>> >> [1] http://www.apache.org/dev/release-signing.html
>> >> [2] http://people.apache.org/~henkp/repo/faq.html<http://people.apache.org/%7Ehenkp/repo/faq.html>
>> >>
>> >> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
>> >> <ut...@gmail.com> wrote:
>> >> > Devs,
>> >> >
>> >> > This is the vote for Apache Rampart 1.5.1 release.
>> >> >
>> >> > Please review the signed artifacts:
>> >> >
>> >> > http://people.apache.org/~shankar/rampart/1.5.1/dist/<http://people.apache.org/%7Eshankar/rampart/1.5.1/dist/>
>> >> >
>> >> > The m2 repository is available at:
>> >> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/<http://people.apache.org/%7Eshankar/rampart/1.5.1/m2_repo/>
>> >> >
>> >> > The site is temporarily hosted at:
>> >> > http://people.apache.org/~shankar/rampart/1.5.1/site/<http://people.apache.org/%7Eshankar/rampart/1.5.1/site/>
>> >> >
>> >> > SVN Info:
>> >> > https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>> >> >
>> >> > It was tested against Axis2 release candidates hosted in:
>> >> > http://people.apache.org/~veithen/1.5.4/<http://people.apache.org/%7Eveithen/1.5.4/>
>> >> >
>> >> > Here's my +1 (binding) to declare the above dist as Apache Rampart
>> 1.5.1
>> >> >
>> >> > thanks,
>> >> > Shankar
>> >> >
>> >> > ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >> > For additional commands, e-mail: java-dev-help@axis.apache.org
>> >> >
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>> >>
>> >
>> >
>> >
>> > --
>> > Senaka Fernando
>> > Member; Apache Software Foundation; http://apache.org
>> >
>> > Associate Technical Lead & Product Manager - WSO2 G-Reg;
>> > WSO2, Inc.; http://wso2.com
>> >
>> > E-mail: senaka AT apache.org
>> > P: +94 11 223 2481; M: +94 77 322 1818
>> > Linked-In: http://www.linkedin.com/in/senakafernando
>> > Blog: http://senakafdo.blogspot.com
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail:
>> java-dev-help@axis.apache.org
>>
>> --
>> *Senaka Fernando*
>> Member; Apache Software Foundation;
>> <ja...@axis.apache.org>http://apache.org
>>
>> *
>> Associate Technical Lead & Product Manager - WSO2 G-Reg;
>> WSO2, Inc.; http://wso2.com** <http://apache.org/>
>>
>> E-mail: senaka AT apache.org
>> **P: +94 11 223 2481*; *M: +94 77 322 1818
>> Linked-In: http://www.linkedin.com/in/senakafernando
>> Blog: http://senakafdo.blogspot.com
>> *
>>
>>
>>


-- 
Ruwan Linton
Software Architect & Product Manager
WSO2 Inc.; http://wso2.org

Lean . Enterprise . Middleware

phone: +1 408 754 7388 ext 51789
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Senaka Fernando <se...@apache.org>.

Hi Andreas,

On Fri, Dec 24, 2010 at 2:04 PM, Andreas Veithen
<an...@gmail.com>wrote:

> On Fri, Dec 24, 2010 at 07:33, Senaka Fernando <se...@apache.org> wrote:
> > Hi Andreas,
> >
> > Many thanks for reminding.
> >
> > On Fri, Dec 24, 2010 at 4:54 AM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> Unfortunately, the release candidate doesn't yet meet the (new) ASF
> >> requirements for a valid release :-(. See [1]:
> >>
> >> "Every artifact distributed by the Apache Software Foundation should
> >> and every new one must be accompanied by one file containing an
> >> OpenPGP compatible ASCII armored detached signature and another file
> >> containing an MD5 checksum."
> >>
> >> Although the document doesn't mention Maven artifacts explicitly, the
> >> common interpretation [2] of this requirement is that every individual
> >> Maven artifact must be signed.
> >
> > I will get this clarified, to how this should be done. Signing Maven
> > artifacts should not be done manually, it should be done automatically
> > through Maven itself. And, I don't see many apache projects doing the
> same
> > as of now.
> >>
> >> Also, I think that the key used to sign the distributions doesn't meet
> >> the new requirements in terms of key type and length.
> >
> > Yes, that's a concern, the required key-lengths were revised, and
> mentioned
> > at the very top of [1]. There were some instructions to how you could
> > upgrade, if you already have a weak key.
> >>
> >> These requirements are part of the reasons why I migrated Axiom, Axis2
> >> and Sandesha2 to the (new) standard ASF release process based on
> >> maven-release-plugin and Nexus. It automates most of the stuff and
> >> Nexus does some validation of the artifacts already when staging them.
> >> I think we should migrate Rampart as well, at least for the next
> >> release.
> >
> > So, have you got the Maven Release plugin to sign artifacts as mentioned,
> > plus upload them to ASF's Maven repositories in a single go?
>
> Yes. Here are the documents that explain how this is executed for
> Axiom and Axis2:
>
> http://ws.apache.org/axiom/devguide/ch02.html#d0e326
> http://axis.apache.org/axis2/java/core/release-process.html
>
> Sandesha2 pretty much sticks to the standard procedure:
>
> http://www.apache.org/dev/publishing-maven-artifacts.html
>
> As mentioned earlier, before this could be applied to Rampart, you
> would have to request inclusion of org.apache.rampart in the staging
> profile for Axis2.
>

Thanks for the information. For the benefit of someone who's reading this
mail thread, the documents that Andreas linked also explains how you could
publish the artifacts on the staging repo etc.

Having said that, I am yet to figure out the legitimacy (hard to find the
people during the holiday season, :-).. ) of a release without having the
Maven artifacts signed, for projects that are not under the Maven PMC (I
found out that they do need something as such).

But, as you have mentioned in your first reply to this thread, I'm +1 for
introducing the same concepts for Rampart. My concern is that, if these
requirements are not mandatory, we could go ahead with this release, instead
of delaying it (some other releases, Synapse is also waiting for this
AFAIK), and fix these inconsistencies for the next release.

However, in general, everything under [1] are mandatory, and enforced by the
ASF.

[1] http://www.apache.org/dev/release-signing.html

Thanks,
Senaka.

>
> > [1] http://www.apache.org/dev/release-signing.html
> >
> > Thanks,
> > Senaka.
> >>
> >> Andreas
> >>
> >> [1] http://www.apache.org/dev/release-signing.html
> >> [2] http://people.apache.org/~henkp/repo/faq.html<http://people.apache.org/%7Ehenkp/repo/faq.html>
> >>
> >> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
> >> <ut...@gmail.com> wrote:
> >> > Devs,
> >> >
> >> > This is the vote for Apache Rampart 1.5.1 release.
> >> >
> >> > Please review the signed artifacts:
> >> >
> >> > http://people.apache.org/~shankar/rampart/1.5.1/dist/<http://people.apache.org/%7Eshankar/rampart/1.5.1/dist/>
> >> >
> >> > The m2 repository is available at:
> >> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/<http://people.apache.org/%7Eshankar/rampart/1.5.1/m2_repo/>
> >> >
> >> > The site is temporarily hosted at:
> >> > http://people.apache.org/~shankar/rampart/1.5.1/site/<http://people.apache.org/%7Eshankar/rampart/1.5.1/site/>
> >> >
> >> > SVN Info:
> >> > https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
> >> >
> >> > It was tested against Axis2 release candidates hosted in:
> >> > http://people.apache.org/~veithen/1.5.4/<http://people.apache.org/%7Eveithen/1.5.4/>
> >> >
> >> > Here's my +1 (binding) to declare the above dist as Apache Rampart
> 1.5.1
> >> >
> >> > thanks,
> >> > Shankar
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >> > For additional commands, e-mail: java-dev-help@axis.apache.org
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>
> >
> >
> >
> > --
> > Senaka Fernando
> > Member; Apache Software Foundation; http://apache.org
> >
> > Associate Technical Lead & Product Manager - WSO2 G-Reg;
> > WSO2, Inc.; http://wso2.com
> >
> > E-mail: senaka AT apache.org
> > P: +94 11 223 2481; M: +94 77 322 1818
> > Linked-In: http://www.linkedin.com/in/senakafernando
> > Blog: http://senakafdo.blogspot.com
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
> --
> *Senaka Fernando*
> Member; Apache Software Foundation; <ja...@axis.apache.org>
> http://apache.org
> *
> Associate Technical Lead & Product Manager - WSO2 G-Reg;
> WSO2, Inc.; http://wso2.com** <http://apache.org/>
>
> E-mail: senaka AT apache.org
> **P: +94 11 223 2481*; *M: +94 77 322 1818
> Linked-In: http://www.linkedin.com/in/senakafernando
> Blog: http://senakafdo.blogspot.com
> *
>
>
>

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Andreas Veithen <an...@gmail.com>.

On Fri, Dec 24, 2010 at 07:33, Senaka Fernando <se...@apache.org> wrote:
> Hi Andreas,
>
> Many thanks for reminding.
>
> On Fri, Dec 24, 2010 at 4:54 AM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> Unfortunately, the release candidate doesn't yet meet the (new) ASF
>> requirements for a valid release :-(. See [1]:
>>
>> "Every artifact distributed by the Apache Software Foundation should
>> and every new one must be accompanied by one file containing an
>> OpenPGP compatible ASCII armored detached signature and another file
>> containing an MD5 checksum."
>>
>> Although the document doesn't mention Maven artifacts explicitly, the
>> common interpretation [2] of this requirement is that every individual
>> Maven artifact must be signed.
>
> I will get this clarified, to how this should be done. Signing Maven
> artifacts should not be done manually, it should be done automatically
> through Maven itself. And, I don't see many apache projects doing the same
> as of now.
>>
>> Also, I think that the key used to sign the distributions doesn't meet
>> the new requirements in terms of key type and length.
>
> Yes, that's a concern, the required key-lengths were revised, and mentioned
> at the very top of [1]. There were some instructions to how you could
> upgrade, if you already have a weak key.
>>
>> These requirements are part of the reasons why I migrated Axiom, Axis2
>> and Sandesha2 to the (new) standard ASF release process based on
>> maven-release-plugin and Nexus. It automates most of the stuff and
>> Nexus does some validation of the artifacts already when staging them.
>> I think we should migrate Rampart as well, at least for the next
>> release.
>
> So, have you got the Maven Release plugin to sign artifacts as mentioned,
> plus upload them to ASF's Maven repositories in a single go?

Yes. Here are the documents that explain how this is executed for
Axiom and Axis2:

http://ws.apache.org/axiom/devguide/ch02.html#d0e326
http://axis.apache.org/axis2/java/core/release-process.html

Sandesha2 pretty much sticks to the standard procedure:

http://www.apache.org/dev/publishing-maven-artifacts.html

As mentioned earlier, before this could be applied to Rampart, you
would have to request inclusion of org.apache.rampart in the staging
profile for Axis2.

> [1] http://www.apache.org/dev/release-signing.html
>
> Thanks,
> Senaka.
>>
>> Andreas
>>
>> [1] http://www.apache.org/dev/release-signing.html
>> [2] http://people.apache.org/~henkp/repo/faq.html
>>
>> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
>> <ut...@gmail.com> wrote:
>> > Devs,
>> >
>> > This is the vote for Apache Rampart 1.5.1 release.
>> >
>> > Please review the signed artifacts:
>> >
>> > http://people.apache.org/~shankar/rampart/1.5.1/dist/
>> >
>> > The m2 repository is available at:
>> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/
>> >
>> > The site is temporarily hosted at:
>> > http://people.apache.org/~shankar/rampart/1.5.1/site/
>> >
>> > SVN Info:
>> > https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>> >
>> > It was tested against Axis2 release candidates hosted in:
>> > http://people.apache.org/~veithen/1.5.4/
>> >
>> > Here's my +1 (binding) to declare the above dist as Apache Rampart 1.5.1
>> >
>> > thanks,
>> > Shankar
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> > For additional commands, e-mail: java-dev-help@axis.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>
>
>
> --
> Senaka Fernando
> Member; Apache Software Foundation; http://apache.org
>
> Associate Technical Lead & Product Manager - WSO2 G-Reg;
> WSO2, Inc.; http://wso2.com
>
> E-mail: senaka AT apache.org
> P: +94 11 223 2481; M: +94 77 322 1818
> Linked-In: http://www.linkedin.com/in/senakafernando
> Blog: http://senakafdo.blogspot.com
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Senaka Fernando <se...@apache.org>.

Hi Andreas,

Many thanks for reminding.

On Fri, Dec 24, 2010 at 4:54 AM, Andreas Veithen
<an...@gmail.com>wrote:

> Unfortunately, the release candidate doesn't yet meet the (new) ASF
> requirements for a valid release :-(. See [1]:
>
> "Every artifact distributed by the Apache Software Foundation should
> and every new one must be accompanied by one file containing an
> OpenPGP compatible ASCII armored detached signature and another file
> containing an MD5 checksum."
>
> Although the document doesn't mention Maven artifacts explicitly, the
> common interpretation [2] of this requirement is that every individual
> Maven artifact must be signed.
>

I will get this clarified, to how this should be done. Signing Maven
artifacts should not be done manually, it should be done automatically
through Maven itself. And, I don't see many apache projects doing the same
as of now.

>
> Also, I think that the key used to sign the distributions doesn't meet
> the new requirements in terms of key type and length.
>

Yes, that's a concern, the required key-lengths were revised, and mentioned
at the very top of [1]. There were some instructions to how you could
upgrade, if you already have a weak key.

>
> These requirements are part of the reasons why I migrated Axiom, Axis2
> and Sandesha2 to the (new) standard ASF release process based on
> maven-release-plugin and Nexus. It automates most of the stuff and
> Nexus does some validation of the artifacts already when staging them.
> I think we should migrate Rampart as well, at least for the next
> release.
>

So, have you got the Maven Release plugin to sign artifacts as mentioned,
plus upload them to ASF's Maven repositories in a single go?

[1] http://www.apache.org/dev/release-signing.html

Thanks,
Senaka.

>
> Andreas
>
> [1] http://www.apache.org/dev/release-signing.html
> [2] http://people.apache.org/~henkp/repo/faq.html<http://people.apache.org/%7Ehenkp/repo/faq.html>
>
> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
> <ut...@gmail.com> wrote:
> > Devs,
> >
> > This is the vote for Apache Rampart 1.5.1 release.
> >
> > Please review the signed artifacts:
> >
> > http://people.apache.org/~shankar/rampart/1.5.1/dist/<http://people.apache.org/%7Eshankar/rampart/1.5.1/dist/>
> >
> > The m2 repository is available at:
> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/<http://people.apache.org/%7Eshankar/rampart/1.5.1/m2_repo/>
> >
> > The site is temporarily hosted at:
> > http://people.apache.org/~shankar/rampart/1.5.1/site/<http://people.apache.org/%7Eshankar/rampart/1.5.1/site/>
> >
> > SVN Info:
> > https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
> >
> > It was tested against Axis2 release candidates hosted in:
> > http://people.apache.org/~veithen/1.5.4/<http://people.apache.org/%7Eveithen/1.5.4/>
> >
> > Here's my +1 (binding) to declare the above dist as Apache Rampart 1.5.1
> >
> > thanks,
> > Shankar
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> > For additional commands, e-mail: java-dev-help@axis.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>


-- 
*Senaka Fernando*
Member; Apache Software Foundation; http://apache.org
*
Associate Technical Lead & Product Manager - WSO2 G-Reg;
WSO2, Inc.; http://wso2.com** <http://apache.org/>

E-mail: senaka AT apache.org
**P: +94 11 223 2481*; *M: +94 77 322 1818
Linked-In: http://www.linkedin.com/in/senakafernando
Blog: http://senakafdo.blogspot.com
*

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Andreas Veithen <an...@gmail.com>.

Unfortunately, the release candidate doesn't yet meet the (new) ASF
requirements for a valid release :-(. See [1]:

"Every artifact distributed by the Apache Software Foundation should
and every new one must be accompanied by one file containing an
OpenPGP compatible ASCII armored detached signature and another file
containing an MD5 checksum."

Although the document doesn't mention Maven artifacts explicitly, the
common interpretation [2] of this requirement is that every individual
Maven artifact must be signed.

Also, I think that the key used to sign the distributions doesn't meet
the new requirements in terms of key type and length.

These requirements are part of the reasons why I migrated Axiom, Axis2
and Sandesha2 to the (new) standard ASF release process based on
maven-release-plugin and Nexus. It automates most of the stuff and
Nexus does some validation of the artifacts already when staging them.
I think we should migrate Rampart as well, at least for the next
release.

Andreas

[1] http://www.apache.org/dev/release-signing.html
[2] http://people.apache.org/~henkp/repo/faq.html

On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
<ut...@gmail.com> wrote:
> Devs,
>
> This is the vote for Apache Rampart 1.5.1 release.
>
> Please review the signed artifacts:
>
> http://people.apache.org/~shankar/rampart/1.5.1/dist/
>
> The m2 repository is available at:
> http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/
>
> The site is temporarily hosted at:
> http://people.apache.org/~shankar/rampart/1.5.1/site/
>
> SVN Info:
> https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>
> It was tested against Axis2 release candidates hosted in:
> http://people.apache.org/~veithen/1.5.4/
>
> Here's my +1 (binding) to declare the above dist as Apache Rampart 1.5.1
>
> thanks,
> Shankar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Isuru Suriarachchi <is...@gmail.com>.

+1

Thanks,
~Isuru

On Thu, Dec 23, 2010 at 10:07 AM, Selvaratnam Uthaiyashankar <
uthaiyashankar@gmail.com> wrote:

> Devs,
>
> This is the vote for Apache Rampart 1.5.1 release.
>
> Please review the signed artifacts:
>
> http://people.apache.org/~shankar/rampart/1.5.1/dist/<http://people.apache.org/%7Eshankar/rampart/1.5.1/dist/>
>
> The m2 repository is available at:
> http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/<http://people.apache.org/%7Eshankar/rampart/1.5.1/m2_repo/>
>
> The site is temporarily hosted at:
> http://people.apache.org/~shankar/rampart/1.5.1/site/<http://people.apache.org/%7Eshankar/rampart/1.5.1/site/>
>
> SVN Info:
> https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>
> It was tested against Axis2 release candidates hosted in:
> http://people.apache.org/~veithen/1.5.4/<http://people.apache.org/%7Eveithen/1.5.4/>
>
> Here's my +1 (binding) to declare the above dist as Apache Rampart 1.5.1
>
> thanks,
> Shankar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>


-- 
Technical Lead,
WSO2 Inc. http://wso2.org/
Blog : http://isurues.wordpress.com/

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Ruwan Linton <ru...@gmail.com>.

Thanks Shankar for the Update.

Ruwan

On Mon, Jan 3, 2011 at 12:39 PM, Selvaratnam Uthaiyashankar <
uthaiyashankar@gmail.com> wrote:

> On Mon, Jan 3, 2011 at 12:35 PM, Ruwan Linton <ru...@gmail.com>
> wrote:
> > Folks, any news about the next release candidate?
>
> Still no update from https://issues.apache.org/jira/browse/INFRA-3320
> :(.  Waiting for it.
>
> Hopefully, we can repack within this week.
>
> Regards,
> Shankar
>
>
> > Ruwan
> >
> > On Thu, Dec 30, 2010 at 3:19 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> On Wed, Dec 29, 2010 at 09:25, Afkham Azeez <af...@gmail.com> wrote:
> >> >
> >> >
> >> > On Tue, Dec 28, 2010 at 5:48 PM, Andreas Veithen
> >> > <an...@gmail.com>
> >> > wrote:
> >> >>
> >> >> There is another issue with that release caused by the change in
> >> >> r1051839, which adds http://dist.wso2.org/maven2 as a repository.
> The
> >> >> problem is that this repository is not properly managed. It contains
> >> >> artifacts with the same groupId, artifactId and version as Maven
> >> >> central, but with different content. Example:
> >> >>
> >> >>
> >> >>
> >> >>
> http://dist.wso2.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
> >> >>
> >> >>
> >> >>
> http://repo1.maven.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
> >> >
> >> > Can you please enlighten us on how you detected these discrepancies,
> and
> >> > also let us know what else seems to be out of order in
> >> > the  http://dist.wso2.org/maven2 repo?
> >>
> >> Here is another one, even more disturbing (also discovered by
> >> coincidence):
> >>
> >> http://dist.wso2.org/maven2/wsdl4j/wsdl4j/1.6.2/wsdl4j-1.6.2.pom
> >> http://repo1.maven.org/maven2/wsdl4j/wsdl4j/1.6.2/wsdl4j-1.6.2.pom
> >>
> >> Andreas
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>
> >
> >
> >
> > --
> > Ruwan Linton
> > Software Architect & Product Manager
> > WSO2 Inc.; http://wso2.org
> >
> > Lean . Enterprise . Middleware
> >
> > phone: +1 408 754 7388 ext 51789
> > email: ruwan@wso2.com; cell: +94 77 341 3097
> > blog: http://blog.ruwan.org
> > linkedin: http://www.linkedin.com/in/ruwanlinton
> > google: http://www.google.com/profiles/ruwan.linton
> > tweet: http://twitter.com/ruwanlinton
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>


-- 
Ruwan Linton
Software Architect & Product Manager
WSO2 Inc.; http://wso2.org

Lean . Enterprise . Middleware

phone: +1 408 754 7388 ext 51789
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Selvaratnam Uthaiyashankar <ut...@gmail.com>.

On Mon, Jan 3, 2011 at 12:35 PM, Ruwan Linton <ru...@gmail.com> wrote:
> Folks, any news about the next release candidate?

Still no update from https://issues.apache.org/jira/browse/INFRA-3320
:(.  Waiting for it.

Hopefully, we can repack within this week.

Regards,
Shankar


> Ruwan
>
> On Thu, Dec 30, 2010 at 3:19 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> On Wed, Dec 29, 2010 at 09:25, Afkham Azeez <af...@gmail.com> wrote:
>> >
>> >
>> > On Tue, Dec 28, 2010 at 5:48 PM, Andreas Veithen
>> > <an...@gmail.com>
>> > wrote:
>> >>
>> >> There is another issue with that release caused by the change in
>> >> r1051839, which adds http://dist.wso2.org/maven2 as a repository. The
>> >> problem is that this repository is not properly managed. It contains
>> >> artifacts with the same groupId, artifactId and version as Maven
>> >> central, but with different content. Example:
>> >>
>> >>
>> >>
>> >> http://dist.wso2.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
>> >>
>> >>
>> >> http://repo1.maven.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
>> >
>> > Can you please enlighten us on how you detected these discrepancies, and
>> > also let us know what else seems to be out of order in
>> > the  http://dist.wso2.org/maven2 repo?
>>
>> Here is another one, even more disturbing (also discovered by
>> coincidence):
>>
>> http://dist.wso2.org/maven2/wsdl4j/wsdl4j/1.6.2/wsdl4j-1.6.2.pom
>> http://repo1.maven.org/maven2/wsdl4j/wsdl4j/1.6.2/wsdl4j-1.6.2.pom
>>
>> Andreas
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>
>
>
> --
> Ruwan Linton
> Software Architect & Product Manager
> WSO2 Inc.; http://wso2.org
>
> Lean . Enterprise . Middleware
>
> phone: +1 408 754 7388 ext 51789
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> google: http://www.google.com/profiles/ruwan.linton
> tweet: http://twitter.com/ruwanlinton
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Ruwan Linton <ru...@gmail.com>.

Folks, any news about the next release candidate?

Ruwan

On Thu, Dec 30, 2010 at 3:19 PM, Andreas Veithen
<an...@gmail.com>wrote:

> On Wed, Dec 29, 2010 at 09:25, Afkham Azeez <af...@gmail.com> wrote:
> >
> >
> > On Tue, Dec 28, 2010 at 5:48 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> There is another issue with that release caused by the change in
> >> r1051839, which adds http://dist.wso2.org/maven2 as a repository. The
> >> problem is that this repository is not properly managed. It contains
> >> artifacts with the same groupId, artifactId and version as Maven
> >> central, but with different content. Example:
> >>
> >>
> >>
> http://dist.wso2.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
> >>
> >>
> http://repo1.maven.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
> >
> > Can you please enlighten us on how you detected these discrepancies, and
> > also let us know what else seems to be out of order in
> > the  http://dist.wso2.org/maven2 repo?
>
> Here is another one, even more disturbing (also discovered by coincidence):
>
> http://dist.wso2.org/maven2/wsdl4j/wsdl4j/1.6.2/wsdl4j-1.6.2.pom
> http://repo1.maven.org/maven2/wsdl4j/wsdl4j/1.6.2/wsdl4j-1.6.2.pom
>
> Andreas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>


-- 
Ruwan Linton
Software Architect & Product Manager
WSO2 Inc.; http://wso2.org

Lean . Enterprise . Middleware

phone: +1 408 754 7388 ext 51789
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Andreas Veithen <an...@gmail.com>.

On Wed, Dec 29, 2010 at 09:25, Afkham Azeez <af...@gmail.com> wrote:
>
>
> On Tue, Dec 28, 2010 at 5:48 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> There is another issue with that release caused by the change in
>> r1051839, which adds http://dist.wso2.org/maven2 as a repository. The
>> problem is that this repository is not properly managed. It contains
>> artifacts with the same groupId, artifactId and version as Maven
>> central, but with different content. Example:
>>
>>
>> http://dist.wso2.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
>>
>> http://repo1.maven.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
>
> Can you please enlighten us on how you detected these discrepancies, and
> also let us know what else seems to be out of order in
> the  http://dist.wso2.org/maven2 repo?

Here is another one, even more disturbing (also discovered by coincidence):

http://dist.wso2.org/maven2/wsdl4j/wsdl4j/1.6.2/wsdl4j-1.6.2.pom
http://repo1.maven.org/maven2/wsdl4j/wsdl4j/1.6.2/wsdl4j-1.6.2.pom

Andreas

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Andreas Veithen <an...@gmail.com>.

On Wed, Dec 29, 2010 at 09:25, Afkham Azeez <af...@gmail.com> wrote:
>
>
> On Tue, Dec 28, 2010 at 5:48 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> There is another issue with that release caused by the change in
>> r1051839, which adds http://dist.wso2.org/maven2 as a repository. The
>> problem is that this repository is not properly managed. It contains
>> artifacts with the same groupId, artifactId and version as Maven
>> central, but with different content. Example:
>>
>>
>> http://dist.wso2.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
>>
>> http://repo1.maven.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
>
> Can you please enlighten us on how you detected these discrepancies, and
> also let us know what else seems to be out of order in
> the  http://dist.wso2.org/maven2 repo?

That was by pure coincidence. I noticed that when building the
Sandesha2 1.4 branch with an empty local repository, at some point,
Maven started downloading things with -wso2vX in the version number.
I've been able to track this down to the discrepancy in
addressing-1.5.pom. Note that Sandesha2 1.4 doesn't use the WSO2
repository, but depends on Rampart 1.5 which uses it. I did some
changes (usage of dependencyManagement) to the Sandesha2 build to work
around this issue, but you can still reproduce it with the 1.4 tag.
You can also reproduce this with the last Synapse 2.0 release
candidate.

Andreas

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Afkham Azeez <af...@gmail.com>.

On Tue, Dec 28, 2010 at 5:48 PM, Andreas Veithen
<an...@gmail.com>wrote:

> There is another issue with that release caused by the change in
> r1051839, which adds http://dist.wso2.org/maven2 as a repository. The
> problem is that this repository is not properly managed. It contains
> artifacts with the same groupId, artifactId and version as Maven
> central, but with different content. Example:
>
>
> http://dist.wso2.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
>
> http://repo1.maven.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom

Can you please enlighten us on how you detected these discrepancies, and
also let us know what else seems to be out of order in the
http://dist.wso2.org/maven2 repo?

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Senaka Fernando <se...@apache.org>.

Hi Ruwan,

On Wed, Dec 29, 2010 at 1:19 PM, Senaka Fernando <se...@apache.org> wrote:

> Hi all,
>
> On Wed, Dec 29, 2010 at 12:20 PM, Ruwan Linton <ru...@gmail.com>wrote:
>
>> Hi Andreas,
>>
>> Please see my comments inline;
>>
>> On Tue, Dec 28, 2010 at 5:48 PM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> There is another issue with that release caused by the change in
>>> r1051839, which adds http://dist.wso2.org/maven2 as a repository. The
>>> problem is that this repository is not properly managed.
>>
>>
>> Well as of what you have found this statement seems to be correct, but it
>> is a mistake that we have done, and we are managing the WSO2 m2 repo
>> properly.
>>
>>
>>> It contains
>>> artifacts with the same groupId, artifactId and version as Maven
>>> central, but with different content. Example:
>>>
>>>
>>> http://dist.wso2.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
>>>
>>> http://repo1.maven.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
>>
>>
>>  Regarding this particular issue, if you carefully have a look, the pom on
>> the WSO2 m2 repo points to the 1.5-wso2v4 as it's parent, and the mistake
>> there was that the addressing version has not been updated and it is
>> deployed as a 1.5 version. I guess this happened because Axis2 fails to
>> resolve the module version with letters in the trailing part like wso2v4.
>>
>
> Ruwan, actually, this particular pom does not use the inherited version
> from the parent. It has its own version. If you check carefully, the parent
> version is 1.5-wso2v4, but for this particular module, it has been
> overridden and defined as 1.5.
>

Oops, sorry for the oversight, actually we are saying the same thing, :-).
But, one issue, IMO, Maven, and Axis2 should not have anything in common. In
other words, the version of an artifact defined in Maven should not be the
basis of versioning of an artifact on Axis2. So, the POM could have version
1.5-wso2v4, whereas the module could have been bundled as 1.5. Am I missing
something?

Thanks,
Senaka.

>
>>
>>>
>>>
>>> This threatens the stability of the build of the Rampart project as
>>> well as downstream projects. We had lots of issues with the java.net
>>> repository, which is also not managed properly, and Axis2 now no
>>> longer relies on this repository. We should not make the same mistake
>>> again.
>>>
>>
>> I am not quite sure why the WSO2 m2 repo is being added to rampart as I do
>> not see any specific WSO2 dependency being added to rampart.
>>
>
> Same here, I wonder what the intentions were? Do we use any library that's
> only available on the WSO2 Repo, and from 1.5.1 onwards?
>
>
>>  Being said that we are managing the repository properly and we are in the
>> process of getting Nexus or some infrastructure inplace for managing the
>> repo decently.
>>
>> Thanks,
>> Ruwan
>>
>>
>>>
>>> Therefore my vote is -1.
>>>
>>
> Andreas, I agree with you. Thanks for keeping a good eye on these changes.
>
> Thanks,
> Senaka.
>
>>
>>> Andreas
>>>
>>> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
>>> <ut...@gmail.com> wrote:
>>> > Devs,
>>> >
>>> > This is the vote for Apache Rampart 1.5.1 release.
>>> >
>>> > Please review the signed artifacts:
>>> >
>>> > http://people.apache.org/~shankar/rampart/1.5.1/dist/<http://people.apache.org/%7Eshankar/rampart/1.5.1/dist/>
>>> >
>>> > The m2 repository is available at:
>>> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/<http://people.apache.org/%7Eshankar/rampart/1.5.1/m2_repo/>
>>> >
>>> > The site is temporarily hosted at:
>>> > http://people.apache.org/~shankar/rampart/1.5.1/site/<http://people.apache.org/%7Eshankar/rampart/1.5.1/site/>
>>> >
>>> > SVN Info:
>>> > https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>>> >
>>> > It was tested against Axis2 release candidates hosted in:
>>> > http://people.apache.org/~veithen/1.5.4/<http://people.apache.org/%7Eveithen/1.5.4/>
>>> >
>>> > Here's my +1 (binding) to declare the above dist as Apache Rampart
>>> 1.5.1
>>> >
>>> > thanks,
>>> > Shankar
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> > For additional commands, e-mail: java-dev-help@axis.apache.org
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>>
>>
>> --
>> Ruwan Linton
>> Software Architect & Product Manager
>> WSO2 Inc.; http://wso2.org
>>
>> Lean . Enterprise . Middleware
>>
>> phone: +1 408 754 7388 ext 51789
>> email: ruwan@wso2.com; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>> linkedin: http://www.linkedin.com/in/ruwanlinton
>> google: http://www.google.com/profiles/ruwan.linton
>> tweet: http://twitter.com/ruwanlinton
>>
>
>
>
> --
> *Senaka Fernando*
> Member; Apache Software Foundation; http://apache.org
> *
> Associate Technical Lead & Product Manager - WSO2 G-Reg;
> WSO2, Inc.; http://wso2.com** <http://apache.org/>
>
> E-mail: senaka AT apache.org
> **P: +94 11 223 2481*; *M: +94 77 322 1818
> Linked-In: http://www.linkedin.com/in/senakafernando
> Blog: http://senakafdo.blogspot.com
> *
>



-- 
*Senaka Fernando*
Member; Apache Software Foundation; http://apache.org
*
Associate Technical Lead & Product Manager - WSO2 G-Reg;
WSO2, Inc.; http://wso2.com** <http://apache.org/>

E-mail: senaka AT apache.org
**P: +94 11 223 2481*; *M: +94 77 322 1818
Linked-In: http://www.linkedin.com/in/senakafernando
Blog: http://senakafdo.blogspot.com
*

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Senaka Fernando <se...@apache.org>.

Hi all,

On Wed, Dec 29, 2010 at 12:20 PM, Ruwan Linton <ru...@gmail.com>wrote:

> Hi Andreas,
>
> Please see my comments inline;
>
> On Tue, Dec 28, 2010 at 5:48 PM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> There is another issue with that release caused by the change in
>> r1051839, which adds http://dist.wso2.org/maven2 as a repository. The
>> problem is that this repository is not properly managed.
>
>
> Well as of what you have found this statement seems to be correct, but it
> is a mistake that we have done, and we are managing the WSO2 m2 repo
> properly.
>
>
>> It contains
>> artifacts with the same groupId, artifactId and version as Maven
>> central, but with different content. Example:
>>
>>
>> http://dist.wso2.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
>>
>> http://repo1.maven.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
>
>
>  Regarding this particular issue, if you carefully have a look, the pom on
> the WSO2 m2 repo points to the 1.5-wso2v4 as it's parent, and the mistake
> there was that the addressing version has not been updated and it is
> deployed as a 1.5 version. I guess this happened because Axis2 fails to
> resolve the module version with letters in the trailing part like wso2v4.
>

Ruwan, actually, this particular pom does not use the inherited version from
the parent. It has its own version. If you check carefully, the parent
version is 1.5-wso2v4, but for this particular module, it has been
overridden and defined as 1.5.

>
>
>>
>>
>> This threatens the stability of the build of the Rampart project as
>> well as downstream projects. We had lots of issues with the java.net
>> repository, which is also not managed properly, and Axis2 now no
>> longer relies on this repository. We should not make the same mistake
>> again.
>>
>
> I am not quite sure why the WSO2 m2 repo is being added to rampart as I do
> not see any specific WSO2 dependency being added to rampart.
>

Same here, I wonder what the intentions were? Do we use any library that's
only available on the WSO2 Repo, and from 1.5.1 onwards?


>  Being said that we are managing the repository properly and we are in the
> process of getting Nexus or some infrastructure inplace for managing the
> repo decently.
>
> Thanks,
> Ruwan
>
>
>>
>> Therefore my vote is -1.
>>
>
Andreas, I agree with you. Thanks for keeping a good eye on these changes.

Thanks,
Senaka.

>
>> Andreas
>>
>> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
>> <ut...@gmail.com> wrote:
>> > Devs,
>> >
>> > This is the vote for Apache Rampart 1.5.1 release.
>> >
>> > Please review the signed artifacts:
>> >
>> > http://people.apache.org/~shankar/rampart/1.5.1/dist/<http://people.apache.org/%7Eshankar/rampart/1.5.1/dist/>
>> >
>> > The m2 repository is available at:
>> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/<http://people.apache.org/%7Eshankar/rampart/1.5.1/m2_repo/>
>> >
>> > The site is temporarily hosted at:
>> > http://people.apache.org/~shankar/rampart/1.5.1/site/<http://people.apache.org/%7Eshankar/rampart/1.5.1/site/>
>> >
>> > SVN Info:
>> > https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>> >
>> > It was tested against Axis2 release candidates hosted in:
>> > http://people.apache.org/~veithen/1.5.4/<http://people.apache.org/%7Eveithen/1.5.4/>
>> >
>> > Here's my +1 (binding) to declare the above dist as Apache Rampart 1.5.1
>> >
>> > thanks,
>> > Shankar
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> > For additional commands, e-mail: java-dev-help@axis.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>
>
> --
> Ruwan Linton
> Software Architect & Product Manager
> WSO2 Inc.; http://wso2.org
>
> Lean . Enterprise . Middleware
>
> phone: +1 408 754 7388 ext 51789
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> google: http://www.google.com/profiles/ruwan.linton
> tweet: http://twitter.com/ruwanlinton
>



-- 
*Senaka Fernando*
Member; Apache Software Foundation; http://apache.org
*
Associate Technical Lead & Product Manager - WSO2 G-Reg;
WSO2, Inc.; http://wso2.com** <http://apache.org/>

E-mail: senaka AT apache.org
**P: +94 11 223 2481*; *M: +94 77 322 1818
Linked-In: http://www.linkedin.com/in/senakafernando
Blog: http://senakafdo.blogspot.com
*

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Thilina Mahesh Buddhika <th...@gmail.com>.

Sorry, missed the link of Rampart 1.5 root pom.xml file.

https://svn.apache.org/repos/asf/axis/axis2/java/rampart/branches/1_5/pom.xml

Thanks,
Thilina

Thilina Mahesh Buddhika
http://blog.thilinamb.com


On Wed, Dec 29, 2010 at 9:37 PM, Thilina Mahesh Buddhika <
thilinamb@gmail.com> wrote:

>
>
> On Wed, Dec 29, 2010 at 12:20 PM, Ruwan Linton <ru...@gmail.com>wrote:
>
>> Hi Andreas,
>>
>> Please see my comments inline;
>>
>> On Tue, Dec 28, 2010 at 5:48 PM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> There is another issue with that release caused by the change in
>>> r1051839, which adds http://dist.wso2.org/maven2 as a repository. The
>>> problem is that this repository is not properly managed.
>>
>>
>> Well as of what you have found this statement seems to be correct, but it
>> is a mistake that we have done, and we are managing the WSO2 m2 repo
>> properly.
>>
>>
>>> It contains
>>> artifacts with the same groupId, artifactId and version as Maven
>>> central, but with different content. Example:
>>>
>>>
>>> http://dist.wso2.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
>>>
>>> http://repo1.maven.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
>>
>>
>>  Regarding this particular issue, if you carefully have a look, the pom on
>> the WSO2 m2 repo points to the 1.5-wso2v4 as it's parent, and the mistake
>> there was that the addressing version has not been updated and it is
>> deployed as a 1.5 version. I guess this happened because Axis2 fails to
>> resolve the module version with letters in the trailing part like wso2v4.
>>
>>
>>>
>>>
>>> This threatens the stability of the build of the Rampart project as
>>> well as downstream projects. We had lots of issues with the java.net
>>> repository, which is also not managed properly, and Axis2 now no
>>> longer relies on this repository. We should not make the same mistake
>>> again.
>>>
>>
>> I am not quite sure why the WSO2 m2 repo is being added to rampart as I do
>> not see any specific WSO2 dependency being added to rampart.
>>
>
> Sorry for being late to reply. We had to add this repository in order to
> get opensaml-1.1.406 artifacts which contains a bug fix which is required
> for certain WS-Trust related scenarios to work out of the box.
>
> Rampart 1.5 [1] was also released with having WSO2 M2 repo listed as a
> repository due to some issues we had (I can't recall the exact reason). So
> we added WSO2 M2 repo, which contains this patched version of OpenSAML 1.1
> artifacts.
>
> If we can push these OpenSAML-1.1.406 related artifacts into an Apache
> repo, this we can remove the newly added repository entry.
>
> Thanks,
> Thilina
>
>
>
>> Being said that we are managing the repository properly and we are in the
>> process of getting Nexus or some infrastructure inplace for managing the
>> repo decently.
>>
>> Thanks,
>> Ruwan
>>
>>
>>>
>>> Therefore my vote is -1.
>>>
>>> Andreas
>>>
>>> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
>>> <ut...@gmail.com> wrote:
>>> > Devs,
>>> >
>>> > This is the vote for Apache Rampart 1.5.1 release.
>>> >
>>> > Please review the signed artifacts:
>>> >
>>> > http://people.apache.org/~shankar/rampart/1.5.1/dist/<http://people.apache.org/%7Eshankar/rampart/1.5.1/dist/>
>>> >
>>> > The m2 repository is available at:
>>> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/<http://people.apache.org/%7Eshankar/rampart/1.5.1/m2_repo/>
>>> >
>>> > The site is temporarily hosted at:
>>> > http://people.apache.org/~shankar/rampart/1.5.1/site/<http://people.apache.org/%7Eshankar/rampart/1.5.1/site/>
>>> >
>>> > SVN Info:
>>> > https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>>> >
>>> > It was tested against Axis2 release candidates hosted in:
>>> > http://people.apache.org/~veithen/1.5.4/<http://people.apache.org/%7Eveithen/1.5.4/>
>>> >
>>> > Here's my +1 (binding) to declare the above dist as Apache Rampart
>>> 1.5.1
>>> >
>>> > thanks,
>>> > Shankar
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> > For additional commands, e-mail: java-dev-help@axis.apache.org
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>>
>>
>> --
>> Ruwan Linton
>> Software Architect & Product Manager
>> WSO2 Inc.; http://wso2.org
>>
>> Lean . Enterprise . Middleware
>>
>> phone: +1 408 754 7388 ext 51789
>> email: ruwan@wso2.com; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>> linkedin: http://www.linkedin.com/in/ruwanlinton
>> google: http://www.google.com/profiles/ruwan.linton
>> tweet: http://twitter.com/ruwanlinton
>>
>
>

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Thilina Mahesh Buddhika <th...@gmail.com>.

On Thu, Dec 30, 2010 at 10:42 AM, Selvaratnam Uthaiyashankar <
uthaiyashankar@gmail.com> wrote:

> On Wed, Dec 29, 2010 at 9:37 PM, Thilina Mahesh Buddhika
> <th...@gmail.com> wrote:
> >
> >
> > On Wed, Dec 29, 2010 at 12:20 PM, Ruwan Linton <ru...@gmail.com>
> > wrote:
> >>
> >> Hi Andreas,
> >> Please see my comments inline;
> >>
> >> On Tue, Dec 28, 2010 at 5:48 PM, Andreas Veithen
> >> <an...@gmail.com> wrote:
> >>>
> >>> There is another issue with that release caused by the change in
> >>> r1051839, which adds http://dist.wso2.org/maven2 as a repository. The
> >>> problem is that this repository is not properly managed.
> >>
> >> Well as of what you have found this statement seems to be correct, but
> it
> >> is a mistake that we have done, and we are managing the WSO2 m2 repo
> >> properly.
> >>
> >>>
> >>> It contains
> >>> artifacts with the same groupId, artifactId and version as Maven
> >>> central, but with different content. Example:
> >>>
> >>>
> >>>
> http://dist.wso2.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
> >>>
> >>>
> http://repo1.maven.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
> >>
> >> Regarding this particular issue, if you carefully have a look, the pom
> on
> >> the WSO2 m2 repo points to the 1.5-wso2v4 as it's parent, and the
> mistake
> >> there was that the addressing version has not been updated and it is
> >> deployed as a 1.5 version. I guess this happened because Axis2 fails to
> >> resolve the module version with letters in the trailing part like
> wso2v4.
> >>
> >>>
> >>> This threatens the stability of the build of the Rampart project as
> >>> well as downstream projects. We had lots of issues with the java.net
> >>> repository, which is also not managed properly, and Axis2 now no
> >>> longer relies on this repository. We should not make the same mistake
> >>> again.
> >>
> >> I am not quite sure why the WSO2 m2 repo is being added to rampart as I
> do
> >> not see any specific WSO2 dependency being added to rampart.
> >
> > Sorry for being late to reply. We had to add this repository in order to
> get
> > opensaml-1.1.406 artifacts which contains a bug fix which is required for
> > certain WS-Trust related scenarios to work out of the box.
> >
> > Rampart 1.5 [1] was also released with having WSO2 M2 repo listed as a
> > repository due to some issues we had (I can't recall the exact reason).
> So
> > we added WSO2 M2 repo, which contains this patched version of OpenSAML
> 1.1
> > artifacts.
>
>
> Thilina, AFAIK this particular version (opensaml-1.1.40) is needed
> only for some features demonstrated in sample 5 right? How about if we
> ask users to download this version of opensaml as part of sample
> configuration procedure? I can see that the instructions are  already
> available in [1].  In that case, can we remove the repo and have the
> dependency to opensaml 1.1, which is available in [2]?
>

+1.

Thanks,
Thilina


>
> Regards,
> Shankar
>
> [1]
> https://svn.apache.org/repos/asf/axis/axis2/java/rampart/trunk/modules/rampart-samples/policy/sample05/README.txt
> [2] http://repo2.maven.org/maven2/org/opensaml/opensaml/
>
> >
> > If we can push these OpenSAML-1.1.406 related artifacts into an Apache
> repo,
> > this we can remove the newly added repository entry.
>
>
>
>
>
> >
> > Thanks,
> > Thilina
> >
> >
> >>
> >> Being said that we are managing the repository properly and we are in
> the
> >> process of getting Nexus or some infrastructure inplace for managing the
> >> repo decently.
> >> Thanks,
> >> Ruwan
> >>
> >>>
> >>> Therefore my vote is -1.
> >>>
> >>> Andreas
> >>>
> >>> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
> >>> <ut...@gmail.com> wrote:
> >>> > Devs,
> >>> >
> >>> > This is the vote for Apache Rampart 1.5.1 release.
> >>> >
> >>> > Please review the signed artifacts:
> >>> >
> >>> > http://people.apache.org/~shankar/rampart/1.5.1/dist/<http://people.apache.org/%7Eshankar/rampart/1.5.1/dist/>
> >>> >
> >>> > The m2 repository is available at:
> >>> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/<http://people.apache.org/%7Eshankar/rampart/1.5.1/m2_repo/>
> >>> >
> >>> > The site is temporarily hosted at:
> >>> > http://people.apache.org/~shankar/rampart/1.5.1/site/<http://people.apache.org/%7Eshankar/rampart/1.5.1/site/>
> >>> >
> >>> > SVN Info:
> >>> > https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
> >>> >
> >>> > It was tested against Axis2 release candidates hosted in:
> >>> > http://people.apache.org/~veithen/1.5.4/<http://people.apache.org/%7Eveithen/1.5.4/>
> >>> >
> >>> > Here's my +1 (binding) to declare the above dist as Apache Rampart
> >>> > 1.5.1
> >>> >
> >>> > thanks,
> >>> > Shankar
> >>> >
> >>> > ---------------------------------------------------------------------
> >>> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >>> > For additional commands, e-mail: java-dev-help@axis.apache.org
> >>> >
> >>> >
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >>> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>>
> >>
> >>
> >>
> >> --
> >> Ruwan Linton
> >> Software Architect & Product Manager
> >> WSO2 Inc.; http://wso2.org
> >>
> >> Lean . Enterprise . Middleware
> >>
> >> phone: +1 408 754 7388 ext 51789
> >> email: ruwan@wso2.com; cell: +94 77 341 3097
> >> blog: http://blog.ruwan.org
> >> linkedin: http://www.linkedin.com/in/ruwanlinton
> >> google: http://www.google.com/profiles/ruwan.linton
> >> tweet: http://twitter.com/ruwanlinton
> >
> >
>
>
>
> --
> S.Uthaiyashankar
> Senior Architect & Senior Manager
> WSO2 Inc.
> http://wso2.com/ - "lean . enterprise . middleware"
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Thilina Mahesh Buddhika <th...@gmail.com>.

And also following modification should be applied to the bin.xml, so that it
will copy the correct OpenSAML jar to the distribution.

Index: modules/distribution/bin.xml
===================================================================
--- modules/distribution/bin.xml (revision 1054533)
+++ modules/distribution/bin.xml (working copy)
@@ -22,7 +22,7 @@
                 <include>org.apache.rampart:rampart-core:jar</include>
                 <include>org.apache.rampart:rampart-policy:jar</include>
                 <include>org.apache.rampart:rampart-trust:jar</include>
-                <include>org.opensaml:opensaml:jar</include>
+                <include>org.opensaml:opensaml1:jar</include>
                 <include>org.opensaml:xmltooling:jar</include>
                 <include>joda-time:joda-time:jar</include>
                 <include>org.slf4j:slf4j-api:jar</include>


Thanks,
Thilina
Thilina Mahesh Buddhika
http://blog.thilinamb.com


On Mon, Jan 3, 2011 at 12:38 PM, Thilina Mahesh Buddhika <
thilinamb@gmail.com> wrote:

> Hi Shankar,
>
> We can replace the OpenSAML 1.1 dependency with the following entry and
> remove the WSO2 M2 repo from the root pom.xml.
>
>         <dependency>
>             <groupId>org.opensaml</groupId>
>             <artifactId>opensaml1</artifactId>
>             <version>1.1</version>
>         </dependency>
>
> Thanks,
> Thilina
>
> Thilina Mahesh Buddhika
> http://blog.thilinamb.com
>
>
> On Thu, Dec 30, 2010 at 10:42 AM, Selvaratnam Uthaiyashankar <
> uthaiyashankar@gmail.com> wrote:
>
>> On Wed, Dec 29, 2010 at 9:37 PM, Thilina Mahesh Buddhika
>> <th...@gmail.com> wrote:
>> >
>> >
>> > On Wed, Dec 29, 2010 at 12:20 PM, Ruwan Linton <ru...@gmail.com>
>> > wrote:
>> >>
>> >> Hi Andreas,
>> >> Please see my comments inline;
>> >>
>> >> On Tue, Dec 28, 2010 at 5:48 PM, Andreas Veithen
>> >> <an...@gmail.com> wrote:
>> >>>
>> >>> There is another issue with that release caused by the change in
>> >>> r1051839, which adds http://dist.wso2.org/maven2 as a repository. The
>> >>> problem is that this repository is not properly managed.
>> >>
>> >> Well as of what you have found this statement seems to be correct, but
>> it
>> >> is a mistake that we have done, and we are managing the WSO2 m2 repo
>> >> properly.
>> >>
>> >>>
>> >>> It contains
>> >>> artifacts with the same groupId, artifactId and version as Maven
>> >>> central, but with different content. Example:
>> >>>
>> >>>
>> >>>
>> http://dist.wso2.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
>> >>>
>> >>>
>> http://repo1.maven.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
>> >>
>> >> Regarding this particular issue, if you carefully have a look, the pom
>> on
>> >> the WSO2 m2 repo points to the 1.5-wso2v4 as it's parent, and the
>> mistake
>> >> there was that the addressing version has not been updated and it is
>> >> deployed as a 1.5 version. I guess this happened because Axis2 fails to
>> >> resolve the module version with letters in the trailing part like
>> wso2v4.
>> >>
>> >>>
>> >>> This threatens the stability of the build of the Rampart project as
>> >>> well as downstream projects. We had lots of issues with the java.net
>> >>> repository, which is also not managed properly, and Axis2 now no
>> >>> longer relies on this repository. We should not make the same mistake
>> >>> again.
>> >>
>> >> I am not quite sure why the WSO2 m2 repo is being added to rampart as I
>> do
>> >> not see any specific WSO2 dependency being added to rampart.
>> >
>> > Sorry for being late to reply. We had to add this repository in order to
>> get
>> > opensaml-1.1.406 artifacts which contains a bug fix which is required
>> for
>> > certain WS-Trust related scenarios to work out of the box.
>> >
>> > Rampart 1.5 [1] was also released with having WSO2 M2 repo listed as a
>> > repository due to some issues we had (I can't recall the exact reason).
>> So
>> > we added WSO2 M2 repo, which contains this patched version of OpenSAML
>> 1.1
>> > artifacts.
>>
>>
>> Thilina, AFAIK this particular version (opensaml-1.1.40) is needed
>> only for some features demonstrated in sample 5 right? How about if we
>> ask users to download this version of opensaml as part of sample
>> configuration procedure? I can see that the instructions are  already
>> available in [1].  In that case, can we remove the repo and have the
>> dependency to opensaml 1.1, which is available in [2]?
>>
>> Regards,
>> Shankar
>>
>> [1]
>> https://svn.apache.org/repos/asf/axis/axis2/java/rampart/trunk/modules/rampart-samples/policy/sample05/README.txt
>> [2] http://repo2.maven.org/maven2/org/opensaml/opensaml/
>>
>> >
>> > If we can push these OpenSAML-1.1.406 related artifacts into an Apache
>> repo,
>> > this we can remove the newly added repository entry.
>>
>>
>>
>>
>>
>> >
>> > Thanks,
>> > Thilina
>> >
>> >
>> >>
>> >> Being said that we are managing the repository properly and we are in
>> the
>> >> process of getting Nexus or some infrastructure inplace for managing
>> the
>> >> repo decently.
>> >> Thanks,
>> >> Ruwan
>> >>
>> >>>
>> >>> Therefore my vote is -1.
>> >>>
>> >>> Andreas
>> >>>
>> >>> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
>> >>> <ut...@gmail.com> wrote:
>> >>> > Devs,
>> >>> >
>> >>> > This is the vote for Apache Rampart 1.5.1 release.
>> >>> >
>> >>> > Please review the signed artifacts:
>> >>> >
>> >>> > http://people.apache.org/~shankar/rampart/1.5.1/dist/
>> >>> >
>> >>> > The m2 repository is available at:
>> >>> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/
>> >>> >
>> >>> > The site is temporarily hosted at:
>> >>> > http://people.apache.org/~shankar/rampart/1.5.1/site/
>> >>> >
>> >>> > SVN Info:
>> >>> >
>> https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>> >>> >
>> >>> > It was tested against Axis2 release candidates hosted in:
>> >>> > http://people.apache.org/~veithen/1.5.4/
>> >>> >
>> >>> > Here's my +1 (binding) to declare the above dist as Apache Rampart
>> >>> > 1.5.1
>> >>> >
>> >>> > thanks,
>> >>> > Shankar
>> >>> >
>> >>> >
>> ---------------------------------------------------------------------
>> >>> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >>> > For additional commands, e-mail: java-dev-help@axis.apache.org
>> >>> >
>> >>> >
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >>> For additional commands, e-mail: java-dev-help@axis.apache.org
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Ruwan Linton
>> >> Software Architect & Product Manager
>> >> WSO2 Inc.; http://wso2.org
>> >>
>> >> Lean . Enterprise . Middleware
>> >>
>> >> phone: +1 408 754 7388 ext 51789
>> >> email: ruwan@wso2.com; cell: +94 77 341 3097
>> >> blog: http://blog.ruwan.org
>> >> linkedin: http://www.linkedin.com/in/ruwanlinton
>> >> google: http://www.google.com/profiles/ruwan.linton
>> >> tweet: http://twitter.com/ruwanlinton
>> >
>> >
>>
>>
>>
>> --
>> S.Uthaiyashankar
>> Senior Architect & Senior Manager
>> WSO2 Inc.
>> http://wso2.com/ - "lean . enterprise . middleware"
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Thilina Mahesh Buddhika <th...@gmail.com>.

Hi Shankar,

We can replace the OpenSAML 1.1 dependency with the following entry and
remove the WSO2 M2 repo from the root pom.xml.

        <dependency>
            <groupId>org.opensaml</groupId>
            <artifactId>opensaml1</artifactId>
            <version>1.1</version>
        </dependency>

Thanks,
Thilina

Thilina Mahesh Buddhika
http://blog.thilinamb.com


On Thu, Dec 30, 2010 at 10:42 AM, Selvaratnam Uthaiyashankar <
uthaiyashankar@gmail.com> wrote:

> On Wed, Dec 29, 2010 at 9:37 PM, Thilina Mahesh Buddhika
> <th...@gmail.com> wrote:
> >
> >
> > On Wed, Dec 29, 2010 at 12:20 PM, Ruwan Linton <ru...@gmail.com>
> > wrote:
> >>
> >> Hi Andreas,
> >> Please see my comments inline;
> >>
> >> On Tue, Dec 28, 2010 at 5:48 PM, Andreas Veithen
> >> <an...@gmail.com> wrote:
> >>>
> >>> There is another issue with that release caused by the change in
> >>> r1051839, which adds http://dist.wso2.org/maven2 as a repository. The
> >>> problem is that this repository is not properly managed.
> >>
> >> Well as of what you have found this statement seems to be correct, but
> it
> >> is a mistake that we have done, and we are managing the WSO2 m2 repo
> >> properly.
> >>
> >>>
> >>> It contains
> >>> artifacts with the same groupId, artifactId and version as Maven
> >>> central, but with different content. Example:
> >>>
> >>>
> >>>
> http://dist.wso2.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
> >>>
> >>>
> http://repo1.maven.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
> >>
> >> Regarding this particular issue, if you carefully have a look, the pom
> on
> >> the WSO2 m2 repo points to the 1.5-wso2v4 as it's parent, and the
> mistake
> >> there was that the addressing version has not been updated and it is
> >> deployed as a 1.5 version. I guess this happened because Axis2 fails to
> >> resolve the module version with letters in the trailing part like
> wso2v4.
> >>
> >>>
> >>> This threatens the stability of the build of the Rampart project as
> >>> well as downstream projects. We had lots of issues with the java.net
> >>> repository, which is also not managed properly, and Axis2 now no
> >>> longer relies on this repository. We should not make the same mistake
> >>> again.
> >>
> >> I am not quite sure why the WSO2 m2 repo is being added to rampart as I
> do
> >> not see any specific WSO2 dependency being added to rampart.
> >
> > Sorry for being late to reply. We had to add this repository in order to
> get
> > opensaml-1.1.406 artifacts which contains a bug fix which is required for
> > certain WS-Trust related scenarios to work out of the box.
> >
> > Rampart 1.5 [1] was also released with having WSO2 M2 repo listed as a
> > repository due to some issues we had (I can't recall the exact reason).
> So
> > we added WSO2 M2 repo, which contains this patched version of OpenSAML
> 1.1
> > artifacts.
>
>
> Thilina, AFAIK this particular version (opensaml-1.1.40) is needed
> only for some features demonstrated in sample 5 right? How about if we
> ask users to download this version of opensaml as part of sample
> configuration procedure? I can see that the instructions are  already
> available in [1].  In that case, can we remove the repo and have the
> dependency to opensaml 1.1, which is available in [2]?
>
> Regards,
> Shankar
>
> [1]
> https://svn.apache.org/repos/asf/axis/axis2/java/rampart/trunk/modules/rampart-samples/policy/sample05/README.txt
> [2] http://repo2.maven.org/maven2/org/opensaml/opensaml/
>
> >
> > If we can push these OpenSAML-1.1.406 related artifacts into an Apache
> repo,
> > this we can remove the newly added repository entry.
>
>
>
>
>
> >
> > Thanks,
> > Thilina
> >
> >
> >>
> >> Being said that we are managing the repository properly and we are in
> the
> >> process of getting Nexus or some infrastructure inplace for managing the
> >> repo decently.
> >> Thanks,
> >> Ruwan
> >>
> >>>
> >>> Therefore my vote is -1.
> >>>
> >>> Andreas
> >>>
> >>> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
> >>> <ut...@gmail.com> wrote:
> >>> > Devs,
> >>> >
> >>> > This is the vote for Apache Rampart 1.5.1 release.
> >>> >
> >>> > Please review the signed artifacts:
> >>> >
> >>> > http://people.apache.org/~shankar/rampart/1.5.1/dist/
> >>> >
> >>> > The m2 repository is available at:
> >>> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/
> >>> >
> >>> > The site is temporarily hosted at:
> >>> > http://people.apache.org/~shankar/rampart/1.5.1/site/
> >>> >
> >>> > SVN Info:
> >>> > https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
> >>> >
> >>> > It was tested against Axis2 release candidates hosted in:
> >>> > http://people.apache.org/~veithen/1.5.4/
> >>> >
> >>> > Here's my +1 (binding) to declare the above dist as Apache Rampart
> >>> > 1.5.1
> >>> >
> >>> > thanks,
> >>> > Shankar
> >>> >
> >>> > ---------------------------------------------------------------------
> >>> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >>> > For additional commands, e-mail: java-dev-help@axis.apache.org
> >>> >
> >>> >
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >>> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>>
> >>
> >>
> >>
> >> --
> >> Ruwan Linton
> >> Software Architect & Product Manager
> >> WSO2 Inc.; http://wso2.org
> >>
> >> Lean . Enterprise . Middleware
> >>
> >> phone: +1 408 754 7388 ext 51789
> >> email: ruwan@wso2.com; cell: +94 77 341 3097
> >> blog: http://blog.ruwan.org
> >> linkedin: http://www.linkedin.com/in/ruwanlinton
> >> google: http://www.google.com/profiles/ruwan.linton
> >> tweet: http://twitter.com/ruwanlinton
> >
> >
>
>
>
> --
> S.Uthaiyashankar
> Senior Architect & Senior Manager
> WSO2 Inc.
> http://wso2.com/ - "lean . enterprise . middleware"
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Selvaratnam Uthaiyashankar <ut...@gmail.com>.

On Wed, Dec 29, 2010 at 9:37 PM, Thilina Mahesh Buddhika
<th...@gmail.com> wrote:
>
>
> On Wed, Dec 29, 2010 at 12:20 PM, Ruwan Linton <ru...@gmail.com>
> wrote:
>>
>> Hi Andreas,
>> Please see my comments inline;
>>
>> On Tue, Dec 28, 2010 at 5:48 PM, Andreas Veithen
>> <an...@gmail.com> wrote:
>>>
>>> There is another issue with that release caused by the change in
>>> r1051839, which adds http://dist.wso2.org/maven2 as a repository. The
>>> problem is that this repository is not properly managed.
>>
>> Well as of what you have found this statement seems to be correct, but it
>> is a mistake that we have done, and we are managing the WSO2 m2 repo
>> properly.
>>
>>>
>>> It contains
>>> artifacts with the same groupId, artifactId and version as Maven
>>> central, but with different content. Example:
>>>
>>>
>>> http://dist.wso2.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
>>>
>>> http://repo1.maven.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
>>
>> Regarding this particular issue, if you carefully have a look, the pom on
>> the WSO2 m2 repo points to the 1.5-wso2v4 as it's parent, and the mistake
>> there was that the addressing version has not been updated and it is
>> deployed as a 1.5 version. I guess this happened because Axis2 fails to
>> resolve the module version with letters in the trailing part like wso2v4.
>>
>>>
>>> This threatens the stability of the build of the Rampart project as
>>> well as downstream projects. We had lots of issues with the java.net
>>> repository, which is also not managed properly, and Axis2 now no
>>> longer relies on this repository. We should not make the same mistake
>>> again.
>>
>> I am not quite sure why the WSO2 m2 repo is being added to rampart as I do
>> not see any specific WSO2 dependency being added to rampart.
>
> Sorry for being late to reply. We had to add this repository in order to get
> opensaml-1.1.406 artifacts which contains a bug fix which is required for
> certain WS-Trust related scenarios to work out of the box.
>
> Rampart 1.5 [1] was also released with having WSO2 M2 repo listed as a
> repository due to some issues we had (I can't recall the exact reason). So
> we added WSO2 M2 repo, which contains this patched version of OpenSAML 1.1
> artifacts.


Thilina, AFAIK this particular version (opensaml-1.1.40) is needed
only for some features demonstrated in sample 5 right? How about if we
ask users to download this version of opensaml as part of sample
configuration procedure? I can see that the instructions are  already
available in [1].  In that case, can we remove the repo and have the
dependency to opensaml 1.1, which is available in [2]?

Regards,
Shankar

[1] https://svn.apache.org/repos/asf/axis/axis2/java/rampart/trunk/modules/rampart-samples/policy/sample05/README.txt
[2] http://repo2.maven.org/maven2/org/opensaml/opensaml/

>
> If we can push these OpenSAML-1.1.406 related artifacts into an Apache repo,
> this we can remove the newly added repository entry.





>
> Thanks,
> Thilina
>
>
>>
>> Being said that we are managing the repository properly and we are in the
>> process of getting Nexus or some infrastructure inplace for managing the
>> repo decently.
>> Thanks,
>> Ruwan
>>
>>>
>>> Therefore my vote is -1.
>>>
>>> Andreas
>>>
>>> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
>>> <ut...@gmail.com> wrote:
>>> > Devs,
>>> >
>>> > This is the vote for Apache Rampart 1.5.1 release.
>>> >
>>> > Please review the signed artifacts:
>>> >
>>> > http://people.apache.org/~shankar/rampart/1.5.1/dist/
>>> >
>>> > The m2 repository is available at:
>>> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/
>>> >
>>> > The site is temporarily hosted at:
>>> > http://people.apache.org/~shankar/rampart/1.5.1/site/
>>> >
>>> > SVN Info:
>>> > https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>>> >
>>> > It was tested against Axis2 release candidates hosted in:
>>> > http://people.apache.org/~veithen/1.5.4/
>>> >
>>> > Here's my +1 (binding) to declare the above dist as Apache Rampart
>>> > 1.5.1
>>> >
>>> > thanks,
>>> > Shankar
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> > For additional commands, e-mail: java-dev-help@axis.apache.org
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>
>>
>>
>> --
>> Ruwan Linton
>> Software Architect & Product Manager
>> WSO2 Inc.; http://wso2.org
>>
>> Lean . Enterprise . Middleware
>>
>> phone: +1 408 754 7388 ext 51789
>> email: ruwan@wso2.com; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>> linkedin: http://www.linkedin.com/in/ruwanlinton
>> google: http://www.google.com/profiles/ruwan.linton
>> tweet: http://twitter.com/ruwanlinton
>
>



-- 
S.Uthaiyashankar
Senior Architect & Senior Manager
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Thilina Mahesh Buddhika <th...@gmail.com>.

On Wed, Dec 29, 2010 at 12:20 PM, Ruwan Linton <ru...@gmail.com>wrote:

> Hi Andreas,
>
> Please see my comments inline;
>
> On Tue, Dec 28, 2010 at 5:48 PM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> There is another issue with that release caused by the change in
>> r1051839, which adds http://dist.wso2.org/maven2 as a repository. The
>> problem is that this repository is not properly managed.
>
>
> Well as of what you have found this statement seems to be correct, but it
> is a mistake that we have done, and we are managing the WSO2 m2 repo
> properly.
>
>
>> It contains
>> artifacts with the same groupId, artifactId and version as Maven
>> central, but with different content. Example:
>>
>>
>> http://dist.wso2.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
>>
>> http://repo1.maven.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
>
>
> Regarding this particular issue, if you carefully have a look, the pom on
> the WSO2 m2 repo points to the 1.5-wso2v4 as it's parent, and the mistake
> there was that the addressing version has not been updated and it is
> deployed as a 1.5 version. I guess this happened because Axis2 fails to
> resolve the module version with letters in the trailing part like wso2v4.
>
>
>>
>>
>> This threatens the stability of the build of the Rampart project as
>> well as downstream projects. We had lots of issues with the java.net
>> repository, which is also not managed properly, and Axis2 now no
>> longer relies on this repository. We should not make the same mistake
>> again.
>>
>
> I am not quite sure why the WSO2 m2 repo is being added to rampart as I do
> not see any specific WSO2 dependency being added to rampart.
>

Sorry for being late to reply. We had to add this repository in order to get
opensaml-1.1.406 artifacts which contains a bug fix which is required for
certain WS-Trust related scenarios to work out of the box.

Rampart 1.5 [1] was also released with having WSO2 M2 repo listed as a
repository due to some issues we had (I can't recall the exact reason). So
we added WSO2 M2 repo, which contains this patched version of OpenSAML 1.1
artifacts.

If we can push these OpenSAML-1.1.406 related artifacts into an Apache repo,
this we can remove the newly added repository entry.

Thanks,
Thilina



> Being said that we are managing the repository properly and we are in the
> process of getting Nexus or some infrastructure inplace for managing the
> repo decently.
>
> Thanks,
> Ruwan
>
>
>>
>> Therefore my vote is -1.
>>
>> Andreas
>>
>> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
>> <ut...@gmail.com> wrote:
>> > Devs,
>> >
>> > This is the vote for Apache Rampart 1.5.1 release.
>> >
>> > Please review the signed artifacts:
>> >
>> > http://people.apache.org/~shankar/rampart/1.5.1/dist/<http://people.apache.org/%7Eshankar/rampart/1.5.1/dist/>
>> >
>> > The m2 repository is available at:
>> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/<http://people.apache.org/%7Eshankar/rampart/1.5.1/m2_repo/>
>> >
>> > The site is temporarily hosted at:
>> > http://people.apache.org/~shankar/rampart/1.5.1/site/<http://people.apache.org/%7Eshankar/rampart/1.5.1/site/>
>> >
>> > SVN Info:
>> > https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>> >
>> > It was tested against Axis2 release candidates hosted in:
>> > http://people.apache.org/~veithen/1.5.4/<http://people.apache.org/%7Eveithen/1.5.4/>
>> >
>> > Here's my +1 (binding) to declare the above dist as Apache Rampart 1.5.1
>> >
>> > thanks,
>> > Shankar
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> > For additional commands, e-mail: java-dev-help@axis.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>
>
> --
> Ruwan Linton
> Software Architect & Product Manager
> WSO2 Inc.; http://wso2.org
>
> Lean . Enterprise . Middleware
>
> phone: +1 408 754 7388 ext 51789
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> google: http://www.google.com/profiles/ruwan.linton
> tweet: http://twitter.com/ruwanlinton
>

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Ruwan Linton <ru...@gmail.com>.

Hi Andreas,

Please see my comments inline;

On Tue, Dec 28, 2010 at 5:48 PM, Andreas Veithen
<an...@gmail.com>wrote:

> There is another issue with that release caused by the change in
> r1051839, which adds http://dist.wso2.org/maven2 as a repository. The
> problem is that this repository is not properly managed.


Well as of what you have found this statement seems to be correct, but it is
a mistake that we have done, and we are managing the WSO2 m2 repo properly.


> It contains
> artifacts with the same groupId, artifactId and version as Maven
> central, but with different content. Example:
>
>
> http://dist.wso2.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
>
> http://repo1.maven.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom


Regarding this particular issue, if you carefully have a look, the pom on
the WSO2 m2 repo points to the 1.5-wso2v4 as it's parent, and the mistake
there was that the addressing version has not been updated and it is
deployed as a 1.5 version. I guess this happened because Axis2 fails to
resolve the module version with letters in the trailing part like wso2v4.


>
>
> This threatens the stability of the build of the Rampart project as
> well as downstream projects. We had lots of issues with the java.net
> repository, which is also not managed properly, and Axis2 now no
> longer relies on this repository. We should not make the same mistake
> again.
>

I am not quite sure why the WSO2 m2 repo is being added to rampart as I do
not see any specific WSO2 dependency being added to rampart. Being said that
we are managing the repository properly and we are in the process of getting
Nexus or some infrastructure inplace for managing the repo decently.

Thanks,
Ruwan


>
> Therefore my vote is -1.
>
> Andreas
>
> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
> <ut...@gmail.com> wrote:
> > Devs,
> >
> > This is the vote for Apache Rampart 1.5.1 release.
> >
> > Please review the signed artifacts:
> >
> > http://people.apache.org/~shankar/rampart/1.5.1/dist/
> >
> > The m2 repository is available at:
> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/
> >
> > The site is temporarily hosted at:
> > http://people.apache.org/~shankar/rampart/1.5.1/site/
> >
> > SVN Info:
> > https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
> >
> > It was tested against Axis2 release candidates hosted in:
> > http://people.apache.org/~veithen/1.5.4/
> >
> > Here's my +1 (binding) to declare the above dist as Apache Rampart 1.5.1
> >
> > thanks,
> > Shankar
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> > For additional commands, e-mail: java-dev-help@axis.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>


-- 
Ruwan Linton
Software Architect & Product Manager
WSO2 Inc.; http://wso2.org

Lean . Enterprise . Middleware

phone: +1 408 754 7388 ext 51789
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Andreas Veithen <an...@gmail.com>.

There is another issue with that release caused by the change in
r1051839, which adds http://dist.wso2.org/maven2 as a repository. The
problem is that this repository is not properly managed. It contains
artifacts with the same groupId, artifactId and version as Maven
central, but with different content. Example:

http://dist.wso2.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom
http://repo1.maven.org/maven2/org/apache/axis2/addressing/1.5/addressing-1.5.pom

This threatens the stability of the build of the Rampart project as
well as downstream projects. We had lots of issues with the java.net
repository, which is also not managed properly, and Axis2 now no
longer relies on this repository. We should not make the same mistake
again.

Therefore my vote is -1.

Andreas

On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
<ut...@gmail.com> wrote:
> Devs,
>
> This is the vote for Apache Rampart 1.5.1 release.
>
> Please review the signed artifacts:
>
> http://people.apache.org/~shankar/rampart/1.5.1/dist/
>
> The m2 repository is available at:
> http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/
>
> The site is temporarily hosted at:
> http://people.apache.org/~shankar/rampart/1.5.1/site/
>
> SVN Info:
> https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>
> It was tested against Axis2 release candidates hosted in:
> http://people.apache.org/~veithen/1.5.4/
>
> Here's my +1 (binding) to declare the above dist as Apache Rampart 1.5.1
>
> thanks,
> Shankar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org

Re: [VOTE] Apache Rampart 1.5.1 release

Posted by Afkham Azeez <af...@gmail.com>.

+1 (Binding)

Azeez

On Thu, Dec 23, 2010 at 10:07 AM, Selvaratnam Uthaiyashankar <
uthaiyashankar@gmail.com> wrote:

> Devs,
>
> This is the vote for Apache Rampart 1.5.1 release.
>
> Please review the signed artifacts:
>
> http://people.apache.org/~shankar/rampart/1.5.1/dist/
>
> The m2 repository is available at:
> http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/
>
> The site is temporarily hosted at:
> http://people.apache.org/~shankar/rampart/1.5.1/site/
>
> SVN Info:
> https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>
> It was tested against Axis2 release candidates hosted in:
> http://people.apache.org/~veithen/1.5.4/
>
> Here's my +1 (binding) to declare the above dist as Apache Rampart 1.5.1
>
> thanks,
> Shankar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>


-- 
*Afkham Azeez*
Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
*
*
*Member; Apache Software Foundation;
**http://www.apache.org/*<http://www.apache.org/>
*
email: **azeez@wso2.com* <az...@wso2.com>* cell: +94 77 3320919
blog: **http://blog.afkham.org* <http://blog.afkham.org>*
twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
*
*