Folks,
I am planning to proceed for the axis2 1.6 release from the 1.6 branch. I
hope there are no more changes to be done for the 1.6.0 release
Thanks,
Ruwan
--
Ruwan Linton
Member, Apache Software Foundation; http://www.apache.org
Software Architect Product Manager, WSO2 Inc.;
Hi Ruwan,
Can you please give me sometime to fix
AXIS2-4671https://issues.apache.org/jira/browse/AXIS2-4671.
This is critical for Rampart 1.6 release. I have previously submitted a
patch for this. I will verify it again and commit as soon as possible.
Thanks,
Thilina
On Sat, Feb 19, 2011 at
Just a quick question. What is the reason for using 1.6.0 as a version
number instead of 1.6? That doesn't follow the conventions the Axis2
project has used in the past.
Andreas
On Sat, Feb 19, 2011 at 09:07, Ruwan Linton ruwan.lin...@gmail.com wrote:
Folks,
I am planning to proceed for the
On Sat, Feb 19, 2011 at 2:19 PM, Ruwan Linton ruwan.lin...@gmail.comwrote:
Sure, let me know once you are done, I have already issued mvn
release:prepare which should create a tag, I guess. I will let it run as an
experiment and re-run once you re done.
This patch is already applied by
[
https://issues.apache.org/jira/browse/AXIS2-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi resolved AXIS2-4671.
-
Resolution: Fixed
applied the patch.
getEffectivePolicy method
On Sat, Feb 19, 2011 at 2:42 PM, Thilina Mahesh Buddhika
thilin...@gmail.com wrote:
On Sat, Feb 19, 2011 at 2:19 PM, Ruwan Linton ruwan.lin...@gmail.comwrote:
Sure, let me know once you are done, I have already issued mvn
release:prepare which should create a tag, I guess. I will let it
To be frank, I didn't check for the convention that the axis2 has been
using.
Since we normally have releases of 3 decimal points, I though keeping the 3
decimal behaviour for all the releases would be good. For example, we do not
call the 1.0 just 1 as we expect to go for a 1.x releases, in the
cool
Ruwan
On Sat, Feb 19, 2011 at 3:12 PM, Thilina Mahesh Buddhika
thilin...@gmail.com wrote:
On Sat, Feb 19, 2011 at 2:19 PM, Ruwan Linton ruwan.lin...@gmail.comwrote:
Sure, let me know once you are done, I have already issued mvn
release:prepare which should create a tag, I guess. I
It has only been committed on the trunk, but not on the 1.6 branch.
I'm going to merge the change to the 1.6 branch.
Andreas
On Sat, Feb 19, 2011 at 10:25, Ruwan Linton ruwan.lin...@gmail.com wrote:
cool
Ruwan
On Sat, Feb 19, 2011 at 3:12 PM, Thilina Mahesh Buddhika
thilin...@gmail.com
Do let me know once you are done.
Also I will change the version of the release to be 1.6 (not 1.6.0) with the
release:prepare.
Ruwan
On Sat, Feb 19, 2011 at 3:30 PM, Andreas Veithen
andreas.veit...@gmail.comwrote:
It has only been committed on the trunk, but not on the 1.6 branch.
I'm going
Until 1.5.1, Axis2 actually didn't support 3 digit version numbers
(that's why the MARs in 1.4.1 had version number 1.41). There are
actually two reasons why one would use 1.6.0:
- In the past, some people have argued that using 3 digit Maven
versions numbers makes the OSGi stuff easier (because
+1
I had this OSGi bundle versions as a fact when I was branching. I think for
the consistency it is good to have the same version number on both bundle as
well as on the jar artifacts.
Thanks,
Ruwan
On Sat, Feb 19, 2011 at 4:13 PM, Andreas Veithen
andreas.veit...@gmail.comwrote:
Until 1.5.1,
Hi Andreas,
Dan has provided another patch to fix Rampart build failures occurred due to
changes in the Neethi
trunk(RAMPART-322https://issues.apache.org/jira/browse/RAMPART-322).
I will apply it to Rampart trunk. Otherwise there will be build failures in
Rampart.
Thanks,
Thilina
On Sat, Feb
I guess this is done now, right Andreas. And as per the discussion lets keep
the version to be 1.6.0
Ruwan
On Sat, Feb 19, 2011 at 4:11 PM, Ruwan Linton ruwan.lin...@gmail.comwrote:
Do let me know once you are done.
Also I will change the version of the release to be 1.6 (not 1.6.0) with
[
https://issues.apache.org/jira/browse/RAMPART-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilina Buddhika reassigned RAMPART-322:
Assignee: Thilina Buddhika
Updates for Neethi 3
Yes, we should be ready now for the 1.6.0 release. One final point: I
documented [1] the release process that I used for the 1.5.x releases.
The process should also apply to 1.6.0. Can you make sure that after
the release, this document is up to date (i.e. either follow the
process as is, or if
Already done. Can you close the issue? (It appears that I'm not
registered as a developer in the RAMPART project in JIRA) Now we need
to look at Sandesha2. This might be more challenging because there are
not many people around who are familiar with that code.
Andreas
On Sat, Feb 19, 2011 at
+1
Ruwan
On Sat, Feb 19, 2011 at 4:34 PM, Andreas Veithen
andreas.veit...@gmail.comwrote:
Yes, we should be ready now for the 1.6.0 release. One final point: I
documented [1] the release process that I used for the 1.5.x releases.
The process should also apply to 1.6.0. Can you make sure
[
https://issues.apache.org/jira/browse/RAMPART-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilina Buddhika resolved RAMPART-322.
--
Resolution: Fixed
Andreas has applied this patch as of r1072300.
Thanks Dan for
Resolved the issue.
Thanks,
Thilina
On Sat, Feb 19, 2011 at 4:08 PM, Andreas Veithen
andreas.veit...@gmail.comwrote:
Already done. Can you close the issue? (It appears that I'm not
registered as a developer in the RAMPART project in JIRA) Now we need
to look at Sandesha2. This might be more
That really helped me, I guess I missed to update the release notes. :-)
Does anybody know the Major Changes Since 1.5 release??
Thanks,
Ruwan
On Sat, Feb 19, 2011 at 4:42 PM, Ruwan Linton ruwan.lin...@gmail.comwrote:
+1
Ruwan
On Sat, Feb 19, 2011 at 4:34 PM, Andreas Veithen
[
https://issues.apache.org/jira/browse/RAMPART-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilina Buddhika resolved RAMPART-321.
--
Resolution: Fixed
Fix Version/s: 1.6.0
Fixed as of r1072315.
Possible
[
https://issues.apache.org/jira/browse/RAMPART-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilina Buddhika reassigned RAMPART-305:
Assignee: Thilina Buddhika
If Rampart detects a security error a HTML page is
[
https://issues.apache.org/jira/browse/RAMPART-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12996761#comment-12996761
]
Andreas Veithen commented on RAMPART-321:
-
-1 for these changes. Reasons:
*
[
https://issues.apache.org/jira/browse/RAMPART-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12996764#comment-12996764
]
Thilina Buddhika commented on RAMPART-321:
--
Hi Andreas,
There are a couple of
[
https://issues.apache.org/jira/browse/RAMPART-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilina Buddhika reopened RAMPART-321:
--
Possible improvements to the logging in Rampart
See
https://hudson.apache.org/hudson/job/Rampart/org.apache.rampart$rampart-policy/306/changes
Changes:
[veithen] Changed the trunk version number to match the new conventions.
[veithen] RAMPART-322: Applied Dan Kulp's patch to update Rampart to Neethi
3.0.0-SNAPSHOT.
See https://hudson.apache.org/hudson/job/Rampart/306/changes
Changes:
[veithen] Updated the MAR plugin to a more recent version and removed some
unused plugin repositories.
[thilinamb] Improving logging in Rampart-Trust module.
[veithen] Replaced tabs by spaces.
[veithen] Changed the trunk
[
https://issues.apache.org/jira/browse/RAMPART-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilina Buddhika resolved RAMPART-321.
--
Resolution: Fixed
Incorporated the suggestions provided by Andreas.
Possible
[
https://issues.apache.org/jira/browse/RAMPART-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilina Buddhika resolved RAMPART-305.
--
Resolution: Fixed
Fix Version/s: 1.6.0
Thanks AmilaJ for the patch.
After
See
https://hudson.apache.org/hudson/job/axis2-1.6/org.apache.axis2$axis2/9/changes
Changes:
[ruwan] preparing the download page for the 1.6.0 release
[ruwan] Fixing the index page for the 1.6 release
[ruwan] fixing the release notes for the 1.6 release
[veithen] AXIS2-4671: Merged r1070439
See https://hudson.apache.org/hudson/job/axis2-1.6/9/changes
Changes:
[ruwan] preparing the download page for the 1.6.0 release
[ruwan] Fixing the index page for the 1.6 release
[ruwan] fixing the release notes for the 1.6 release
[veithen] AXIS2-4671: Merged r1070439 to the 1.6 branch.
[
https://issues.apache.org/jira/browse/AXIS2-4944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Heshan Suriyaarachchi updated AXIS2-4944:
-
Attachment: AXIS2-4944-patch-ver5.txt
Hi Amila,
I have incorporated the
See
https://hudson.apache.org/hudson/job/axis2-1.6/org.apache.axis2$axis2/10/changes
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
See https://hudson.apache.org/hudson/job/axis2-1.6/10/changes
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[
https://issues.apache.org/jira/browse/AXIS2-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12996798#comment-12996798
]
Hudson commented on AXIS2-4671:
---
Integrated in axis2-1.6 #10 (See
See
https://hudson.apache.org/hudson/job/Rampart/org.apache.rampart$rampart-policy/307/
--
[INFO]
[INFO] Building Rampart - Policy
[INFO]task-segment: [clean, install]
[INFO]
See https://hudson.apache.org/hudson/job/Rampart/307/changes
Changes:
[thilinamb] Applying patch for RAMPART-305 provided by AmilaJ
[thilinamb] Removing unnecessary isDebugEnabled checks and using
isDebugEnabled() instead of the static variable.
--
Hi,
I think that if we want to make sure that the release branches we
created for Axis2, Rampart and Sandesha2 remain usable to do
maintenance releases, we need to agree on a couple of guidelines about
how to manage these branches. Based on my experience from the (quite
successful) 1.5.x
hi,
Can you please have a look at this patch[1].
I think this is useful for next synapse release shall I merge it to
branch as well?
thanks,
Amila.
[1] https://issues.apache.org/jira/browse/AXIS2-4944
On Sat, Feb 19, 2011 at 3:41 PM, Ruwan Linton ruwan.lin...@gmail.comwrote:
Do let me know
I think that Ruwan already got past the point where we could still
include things into 1.6.0. This will have to wait for 1.6.1. Also, I
will probably make a couple of comments about AXIS2-4944, but I need
to have a closer look first...
Andreas
On Sat, Feb 19, 2011 at 18:27, Amila Suriarachchi
See
https://hudson.apache.org/hudson/job/Rampart/org.apache.rampart$rampart-policy/308/
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
See https://hudson.apache.org/hudson/job/Rampart/308/changes
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
All builds are now stable again, with the 1.6 branches depending on
Neethi 2.0.4 and the trunks depending on 3.0.0-SNAPSHOT.
All three projects now have a release branch with version number
1.6.0-SNAPSHOT (actually 1.6.1-SNAPSHOT for Axis2, since Ruwan already
created the 1.6.0 release tag) and a
Hi Devs,
This is a call for votes to release Axis2-1.6.0.
The complete list of JIRA issues fixed in this release can be found here:
http://bit.ly/issues-fixed-for-1_6
The staging repository is here:
https://repository.apache.org/content/repositories/orgapacheaxis2-025/
The distributions are
Yeap, sorry Amila... I didn't see your message before proceeding for the
release. Lets prepare for the 1.6.1 on the branch, and do it soon too.
Thanks,
Ruwan
On Sat, Feb 19, 2011 at 11:32 PM, Andreas Veithen andreas.veit...@gmail.com
wrote:
I think that Ruwan already got past the point where
+1
I think this is a candidate for a set of developer resources, including the
release process guide too. I have some comments related to that which I will
share shortly.
Regarding the Axis2 transports, yes due to the release pressure I forgot to
commit the changes to the transports trunk. I was
As I said this really helped.
In addition to the steps mentioned in this guide I had to do one additional
thing, which is to manually change some versions on the sample modules. As
that has not been picked up by the maven release plugin. I didn't want to
edit the guide to add this step as that is
is there a window to merge this[1] change to branch?
Unlike in other axis2 releases, all the directories has the 777 mode
eg.
drwxrwxrwx 2 amila amila 328 2011-02-20 01:43 bin
drwxrwxrwx 2 amila amila 192 2011-02-20 01:43 conf
-rwxrwxrwx 1 amila amila 6145 2011-02-20 01:43
On Sun, Feb 20, 2011 at 10:46 AM, Amila Suriarachchi
amilasuriarach...@gmail.com wrote:
is there a window to merge this[1] change to branch?
I think my previous commit regarding this has broken the faulthandling
sample.
we need to fix that.
thanks,
Amila.
Unlike in other axis2 releases,
On Sun, Feb 20, 2011 at 11:07 AM, Amila Suriarachchi
amilasuriarach...@gmail.com wrote:
On Sun, Feb 20, 2011 at 10:46 AM, Amila Suriarachchi
amilasuriarach...@gmail.com wrote:
is there a window to merge this[1] change to branch?
I think my previous commit regarding this has broken the
51 matches
Mail list logo
