The way you have proposed wouldn't include the patched jar in Maven2
test classpath and there is a probability that existing functions might
break due to these new fixes and it has to be tested. If it can be
guaranteed that existing functionality of Axis2/WSAS/etc wouldn't break,
I would encourage you to use the patched approach.
The patches that we will need are by no means major changes. They are
simple bug fixes Such as
https://issues.apache.org/jira/browse/AXIS2-3819 which causes issues for
generated stubs (When the stub is generated off a WSDL 1.1 which has
multiple parts).
I agree with you with regard to the maven class path issue though. We
will have to find a workaround for that. We don't plan to ship a
complete patched jar but rather the diff only.
Thanks,
Keith.
Thank you!
Saminda
Keith Chapman wrote:
The next release of the Mashup Server will be based on WSAS 2.3. WSAS
includes a patched version of Axis2. These couple of issues that I'm
referring to was uncovered after the WSAS release. So this patch will
be applied on top of the axis2 jar that WSAS shipped. We will drop
this patch (will will have just a class or 2) into the patches folder.
Thanks,
Keith.
Paul Fremantle wrote:
I thought we built a specific release of the component with a number
and a fixed revision. Or is that not appropriate in this scenario?
Paul
Channa Gunawardena wrote:
Sounds like an improvement to the process; +1.
Keith Chapman wrote:
Jonathan Marsh wrote:
Is this the way WSAS and other projects deliver patches?
What the ESB team had done this far is to check in the patch it
self (the binary) into the svn. So the build will just pick that up
and drop it into the distro. The issue is that the source is not
available anywhere in that case. With the solution I propose the
source is available in the released source zip and we get the patch
as well. May be this is something that all projects should adopt.
Thanks,
Keith.
If so, +1.
Jonathan Marsh - http://www.wso2.com -
http://auburnmarshes.spaces.live.com
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Keith Chapman
Sent: Thursday, June 19, 2008 9:26 PM
To: mashup-dev
Subject: [mashup-dev] Axis2 patches needed for the next release
Hi,
There are a few JIRAS that require Axis2 fixes (Mashup-859, Mashup-
701).
I would like these fixes to go into the next release. We can ship
these
as patches in the patches directory.
How about managing this as follows.
1. Put in a new module called patches and drop the src of the
patch in
there
2. At build time create a jar from the source in the patches dir and
include it in the patches directory of the distribution
Shall I get this into the build? WDYT?
Thanks,
Keith.
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
