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
--
********************************************
Channa Gunawardena
Technical Lead, WSO2 Inc.
channa at wso2.com; http://channa.gunawardena.org; +94 71 306 2722
"The Open Source SOA Company", http://wso2.com
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
