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,
In patches, what we were doing was overriding just the classes which are
affected by the diff of the fix, over the released tag. This will
guarantee that no new issues are introduced in the patch that has not
been issues in the released version, because there might be some other
changes on the fixed revision of the trunk. (I mean there can be other
changes in other classes or may be in the same classes)
As for the process, Keith, you should be able to find a mechanism to
check in the patched source files as a different maven module and build
those source files to get the path and place it at the patches folder at
the build time. (If you want the source to be present in the SVN)
Thanks,
Ruwan
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
begin:vcard
fn:Ruwan Linton
n:Linton;Ruwan
email;internet:[EMAIL PROTECTED]
url:http://ruwansblog.blogspot.com
version:2.1
end:vcard
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
