Hi Michal,
I'll update the build system for the next release so that you can
download from a tagged directory instead of a specific revision number.
You can then merge the changes from the release branches.
--dan
On 9/12/14 11:00 AM, Michal Owsiak wrote:
Thanks for the info.
Just one more question. I assume that I can take the code from rev31866
and then apply patches by merging codes from development branches.
What I am looking for is the solution for us when version 2.5/3.0 will
be released.
I would like to proceed that way, we get the released version (from SVN)
and then, we patch it by merging changes from the release branch.
I assume that should be OK.
Michal
Hi Michal,
The following will download the sources used for the Kepler 2.4
installers:
svn co -r31866
https://code.kepler-project.org/code/kepler/releases/release-branches/build-area-2.4/
build-area
ant change-to -Dsuite=kepler-2.4
ant update -Drev 31866
I created a tag for the 2.4.0 release, but "ant change-to" always
downloads from the branch.
The branches are updated with bug fixes, which are released as patches.
There have been several patches for Kepler 2.4, so if you use the
sources from revision 31866, you will not get these bug fixes.
--dan
_______________________________________________
Kepler-dev mailing list
[email protected]
http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
_______________________________________________
Kepler-dev mailing list
[email protected]
http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
