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 Hiranya Jayathilaka <hi...@gmail.com> on 2015/07/01 19:47:46 UTC

Fixing Issues for 1.7 Release

Hi Folks,

Is there a JIRA filter or a dashboard that I can look at to get an idea of
what issues need fixing for a 1.7 release? I'm sure others will find such a
thing useful too.

Also, are we blocked on any other dependency releases at this point? I'm
trying to figure out what's the minimum we need to do to get a release out.

Thanks,
Hiranya

-- 
Hiranya Jayathilaka
Mayhem Lab/RACE Lab;
Dept. of Computer Science, UCSB;  http://cs.ucsb.edu
E-mail: hiranya@cs.ucsb.edu <hi...@wso2.com>;  Mobile: +1 (805) 895-7443
Blog: http://techfeast-hiranya.blogspot.com

Re: Fixing Issues for 1.7 Release

Posted by Andreas Veithen <an...@gmail.com>.
OK, I also upgraded Woden to XmlSchema 2.2.1 (No code changes were
required), so this is converging.

Andreas

On Fri, Jul 3, 2015 at 11:43 PM, Hiranya Jayathilaka
<hi...@gmail.com> wrote:
> Changing Neethi version to 3.0.3 went smoothly. However, changing to
> XmlSchema 2.2.1 needed some minor code changes. I'm attaching the patch here
> for a quick review. With this I was able to build Axis2 trunk with all tests
> passing.
>
> Thanks,
> Hiranya
>
>
>
> On Jul 2, 2015, at 11:58 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>
> Yes, I would say so.
>
> Andreas
>
> On Fri, Jul 3, 2015 at 2:34 AM, Hiranya Jayathilaka
> <hi...@gmail.com> wrote:
>
>
> On Jul 1, 2015, at 1:11 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>
> On Wed, Jul 1, 2015 at 6:47 PM, Hiranya Jayathilaka
> <hi...@gmail.com> wrote:
>
> Hi Folks,
>
> Is there a JIRA filter or a dashboard that I can look at to get an idea of
> what issues need fixing for a 1.7 release? I'm sure others will find such a
> thing useful too.
>
> Also, are we blocked on any other dependency releases at this point? I'm
> trying to figure out what's the minimum we need to do to get a release out.
>
>
> The current trunk has 4 snapshot dependencies: Axiom, Neethi, Woden
> and XmlSchema.
>
> Axiom is set to 1.2.16-SNAPSHOT simply to detect regressions caused by
> changes in the Axiom trunk, but the Axis2 trunk is known to work with
> 1.2.15 and so far there are no new APIs in 1.2.16-SNAPSHOT, so this is
> not a problem.
>
> I think that Woden requires a release because it has been updated to
> work with XmlSchema 2. My problem right now is that my employer
> requires me to send patches for internal review before I can make them
> public and commit them. Usually, after a couple of patches, they let
> me commit without review, but I'm not there yet for the Woden project.
> I'm currently waiting for the review of a patch that migrates the old
> Forrest documentation to Maven (which would remove one major pain
> point from the Woden release process, because nobody is really
> familiar with Forrest). The bottom line is that for the moment I can't
> work efficiently on a Woden release.
>
> For Neethi and XmlSchema, it is likely that the Axis2 trunk would work
> with release versions, but somebody needs to test this. If you want to
> help, then this would be a good starting point.
>
>
> I can take a look. If the build succeeds with tests when using these
> dependencies, is that convincing enough to conclude that Axis2 trunk works
> with them?
>
> Thanks,
> Hiranya
>
>
> Thanks,
> Hiranya
>
> --
> Hiranya Jayathilaka
> Mayhem Lab/RACE Lab;
> Dept. of Computer Science, UCSB;  http://cs.ucsb.edu
> E-mail: hiranya@cs.ucsb.edu;  Mobile: +1 (805) 895-7443
> Blog: http://techfeast-hiranya.blogspot.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
> --
> Hiranya Jayathilaka
> Mayhem Lab/RACE Lab;
> Dept. of Computer Science, UCSB;  http://cs.ucsb.edu
> E-mail: hiranya@cs.ucsb.edu;  Mobile: +1 (805) 895-7443
> Blog: http://techfeast-hiranya.blogspot.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
> --
> Hiranya Jayathilaka
> Mayhem Lab/RACE Lab;
> Dept. of Computer Science, UCSB;  http://cs.ucsb.edu
> E-mail: hiranya@cs.ucsb.edu;  Mobile: +1 (805) 895-7443
> Blog: http://techfeast-hiranya.blogspot.com
>
>

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

Re: Fixing Issues for 1.7 Release

Posted by Hiranya Jayathilaka <hi...@gmail.com>.
Changing Neethi version to 3.0.3 went smoothly. However, changing to XmlSchema 2.2.1 needed some minor code changes. I'm attaching the patch here for a quick review. With this I was able to build Axis2 trunk with all tests passing.

Thanks,
Hiranya



On Jul 2, 2015, at 11:58 PM, Andreas Veithen <an...@gmail.com> wrote:

> Yes, I would say so.
> 
> Andreas
> 
> On Fri, Jul 3, 2015 at 2:34 AM, Hiranya Jayathilaka
> <hi...@gmail.com> wrote:
>> 
>> On Jul 1, 2015, at 1:11 PM, Andreas Veithen <an...@gmail.com>
>> wrote:
>> 
>> On Wed, Jul 1, 2015 at 6:47 PM, Hiranya Jayathilaka
>> <hi...@gmail.com> wrote:
>> 
>> Hi Folks,
>> 
>> Is there a JIRA filter or a dashboard that I can look at to get an idea of
>> what issues need fixing for a 1.7 release? I'm sure others will find such a
>> thing useful too.
>> 
>> Also, are we blocked on any other dependency releases at this point? I'm
>> trying to figure out what's the minimum we need to do to get a release out.
>> 
>> 
>> The current trunk has 4 snapshot dependencies: Axiom, Neethi, Woden
>> and XmlSchema.
>> 
>> Axiom is set to 1.2.16-SNAPSHOT simply to detect regressions caused by
>> changes in the Axiom trunk, but the Axis2 trunk is known to work with
>> 1.2.15 and so far there are no new APIs in 1.2.16-SNAPSHOT, so this is
>> not a problem.
>> 
>> I think that Woden requires a release because it has been updated to
>> work with XmlSchema 2. My problem right now is that my employer
>> requires me to send patches for internal review before I can make them
>> public and commit them. Usually, after a couple of patches, they let
>> me commit without review, but I'm not there yet for the Woden project.
>> I'm currently waiting for the review of a patch that migrates the old
>> Forrest documentation to Maven (which would remove one major pain
>> point from the Woden release process, because nobody is really
>> familiar with Forrest). The bottom line is that for the moment I can't
>> work efficiently on a Woden release.
>> 
>> For Neethi and XmlSchema, it is likely that the Axis2 trunk would work
>> with release versions, but somebody needs to test this. If you want to
>> help, then this would be a good starting point.
>> 
>> 
>> I can take a look. If the build succeeds with tests when using these
>> dependencies, is that convincing enough to conclude that Axis2 trunk works
>> with them?
>> 
>> Thanks,
>> Hiranya
>> 
>> 
>> Thanks,
>> Hiranya
>> 
>> --
>> Hiranya Jayathilaka
>> Mayhem Lab/RACE Lab;
>> Dept. of Computer Science, UCSB;  http://cs.ucsb.edu
>> E-mail: hiranya@cs.ucsb.edu;  Mobile: +1 (805) 895-7443
>> Blog: http://techfeast-hiranya.blogspot.com
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>> 
>> 
>> --
>> Hiranya Jayathilaka
>> Mayhem Lab/RACE Lab;
>> Dept. of Computer Science, UCSB;  http://cs.ucsb.edu
>> E-mail: hiranya@cs.ucsb.edu;  Mobile: +1 (805) 895-7443
>> Blog: http://techfeast-hiranya.blogspot.com
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
> 

--
Hiranya Jayathilaka
Mayhem Lab/RACE Lab;
Dept. of Computer Science, UCSB;  http://cs.ucsb.edu
E-mail: hiranya@cs.ucsb.edu;  Mobile: +1 (805) 895-7443
Blog: http://techfeast-hiranya.blogspot.com

Re: Fixing Issues for 1.7 Release

Posted by Andreas Veithen <an...@gmail.com>.
Yes, I would say so.

Andreas

On Fri, Jul 3, 2015 at 2:34 AM, Hiranya Jayathilaka
<hi...@gmail.com> wrote:
>
> On Jul 1, 2015, at 1:11 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>
> On Wed, Jul 1, 2015 at 6:47 PM, Hiranya Jayathilaka
> <hi...@gmail.com> wrote:
>
> Hi Folks,
>
> Is there a JIRA filter or a dashboard that I can look at to get an idea of
> what issues need fixing for a 1.7 release? I'm sure others will find such a
> thing useful too.
>
> Also, are we blocked on any other dependency releases at this point? I'm
> trying to figure out what's the minimum we need to do to get a release out.
>
>
> The current trunk has 4 snapshot dependencies: Axiom, Neethi, Woden
> and XmlSchema.
>
> Axiom is set to 1.2.16-SNAPSHOT simply to detect regressions caused by
> changes in the Axiom trunk, but the Axis2 trunk is known to work with
> 1.2.15 and so far there are no new APIs in 1.2.16-SNAPSHOT, so this is
> not a problem.
>
> I think that Woden requires a release because it has been updated to
> work with XmlSchema 2. My problem right now is that my employer
> requires me to send patches for internal review before I can make them
> public and commit them. Usually, after a couple of patches, they let
> me commit without review, but I'm not there yet for the Woden project.
> I'm currently waiting for the review of a patch that migrates the old
> Forrest documentation to Maven (which would remove one major pain
> point from the Woden release process, because nobody is really
> familiar with Forrest). The bottom line is that for the moment I can't
> work efficiently on a Woden release.
>
> For Neethi and XmlSchema, it is likely that the Axis2 trunk would work
> with release versions, but somebody needs to test this. If you want to
> help, then this would be a good starting point.
>
>
> I can take a look. If the build succeeds with tests when using these
> dependencies, is that convincing enough to conclude that Axis2 trunk works
> with them?
>
> Thanks,
> Hiranya
>
>
> Thanks,
> Hiranya
>
> --
> Hiranya Jayathilaka
> Mayhem Lab/RACE Lab;
> Dept. of Computer Science, UCSB;  http://cs.ucsb.edu
> E-mail: hiranya@cs.ucsb.edu;  Mobile: +1 (805) 895-7443
> Blog: http://techfeast-hiranya.blogspot.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
> --
> Hiranya Jayathilaka
> Mayhem Lab/RACE Lab;
> Dept. of Computer Science, UCSB;  http://cs.ucsb.edu
> E-mail: hiranya@cs.ucsb.edu;  Mobile: +1 (805) 895-7443
> Blog: http://techfeast-hiranya.blogspot.com
>

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

Re: Fixing Issues for 1.7 Release

Posted by Hiranya Jayathilaka <hi...@gmail.com>.
On Jul 1, 2015, at 1:11 PM, Andreas Veithen <an...@gmail.com> wrote:

> On Wed, Jul 1, 2015 at 6:47 PM, Hiranya Jayathilaka
> <hi...@gmail.com> wrote:
>> Hi Folks,
>> 
>> Is there a JIRA filter or a dashboard that I can look at to get an idea of
>> what issues need fixing for a 1.7 release? I'm sure others will find such a
>> thing useful too.
>> 
>> Also, are we blocked on any other dependency releases at this point? I'm
>> trying to figure out what's the minimum we need to do to get a release out.
> 
> The current trunk has 4 snapshot dependencies: Axiom, Neethi, Woden
> and XmlSchema.
> 
> Axiom is set to 1.2.16-SNAPSHOT simply to detect regressions caused by
> changes in the Axiom trunk, but the Axis2 trunk is known to work with
> 1.2.15 and so far there are no new APIs in 1.2.16-SNAPSHOT, so this is
> not a problem.
> 
> I think that Woden requires a release because it has been updated to
> work with XmlSchema 2. My problem right now is that my employer
> requires me to send patches for internal review before I can make them
> public and commit them. Usually, after a couple of patches, they let
> me commit without review, but I'm not there yet for the Woden project.
> I'm currently waiting for the review of a patch that migrates the old
> Forrest documentation to Maven (which would remove one major pain
> point from the Woden release process, because nobody is really
> familiar with Forrest). The bottom line is that for the moment I can't
> work efficiently on a Woden release.
> 
> For Neethi and XmlSchema, it is likely that the Axis2 trunk would work
> with release versions, but somebody needs to test this. If you want to
> help, then this would be a good starting point.

I can take a look. If the build succeeds with tests when using these dependencies, is that convincing enough to conclude that Axis2 trunk works with them? 

Thanks,
Hiranya

> 
>> Thanks,
>> Hiranya
>> 
>> --
>> Hiranya Jayathilaka
>> Mayhem Lab/RACE Lab;
>> Dept. of Computer Science, UCSB;  http://cs.ucsb.edu
>> E-mail: hiranya@cs.ucsb.edu;  Mobile: +1 (805) 895-7443
>> Blog: http://techfeast-hiranya.blogspot.com
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
> 

--
Hiranya Jayathilaka
Mayhem Lab/RACE Lab;
Dept. of Computer Science, UCSB;  http://cs.ucsb.edu
E-mail: hiranya@cs.ucsb.edu;  Mobile: +1 (805) 895-7443
Blog: http://techfeast-hiranya.blogspot.com

Re: Fixing Issues for 1.7 Release

Posted by Andreas Veithen <an...@gmail.com>.
On Wed, Jul 1, 2015 at 6:47 PM, Hiranya Jayathilaka
<hi...@gmail.com> wrote:
> Hi Folks,
>
> Is there a JIRA filter or a dashboard that I can look at to get an idea of
> what issues need fixing for a 1.7 release? I'm sure others will find such a
> thing useful too.
>
> Also, are we blocked on any other dependency releases at this point? I'm
> trying to figure out what's the minimum we need to do to get a release out.

The current trunk has 4 snapshot dependencies: Axiom, Neethi, Woden
and XmlSchema.

Axiom is set to 1.2.16-SNAPSHOT simply to detect regressions caused by
changes in the Axiom trunk, but the Axis2 trunk is known to work with
1.2.15 and so far there are no new APIs in 1.2.16-SNAPSHOT, so this is
not a problem.

I think that Woden requires a release because it has been updated to
work with XmlSchema 2. My problem right now is that my employer
requires me to send patches for internal review before I can make them
public and commit them. Usually, after a couple of patches, they let
me commit without review, but I'm not there yet for the Woden project.
I'm currently waiting for the review of a patch that migrates the old
Forrest documentation to Maven (which would remove one major pain
point from the Woden release process, because nobody is really
familiar with Forrest). The bottom line is that for the moment I can't
work efficiently on a Woden release.

For Neethi and XmlSchema, it is likely that the Axis2 trunk would work
with release versions, but somebody needs to test this. If you want to
help, then this would be a good starting point.

> Thanks,
> Hiranya
>
> --
> Hiranya Jayathilaka
> Mayhem Lab/RACE Lab;
> Dept. of Computer Science, UCSB;  http://cs.ucsb.edu
> E-mail: hiranya@cs.ucsb.edu;  Mobile: +1 (805) 895-7443
> Blog: http://techfeast-hiranya.blogspot.com

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