Michael Baessler wrote:
Jörn Kottmann wrote:
On Jun 13, 2008, at 10:47 AM, Michael Baessler wrote:
Thilo Goetz wrote:
Jörn Kottmann wrote:
Yes I think you can build the next Release Candidate.
I just replied to the CAS Editor build script mail with some comments.
Ok, I will answer here.
UIMA-536 is now closed.
I will take care of the build, testing, etc.
The only thing I am note familiar is how the tagging of the release
candiate works.
Which version of the dependent projects will be used ? The current
head or
already tagged projects which were be used for annotator sandbox
release ?
The latter. You should also do your testing with the released versions
of both the sandbox and the core framework. This way we ensure that
when
users download our released distributions, everything works together.
Seems today we are responding all at the same time. Please see my
suggestions.
I don't think CasEditor make use of the Sandbox 2.2.2 release, so I
don't see any reason
using this for tagging. For UIMA core projects the 2.2.2 tag should be
used. Just my point of view.
Ok, sounds good for me.
How do you usually do tagging with the svn copy command or from within
eclipse ?
Within eclipse in the SVN Repository view.
IMHO, it's a good goal to have a build process which is reproducable by
others, at a later time. For example, we have for other released
components put a bunch things needed for building into the xxxx-distr
project project, in the src/main/build directory. As an example, the
uima-as-distr project includes in its src/main/build directory, a "tag"
script, which does the svn copies needed to create the tag. The script
remembers which things to tag from the "head" and which things to tag
from another "tag".
-Marshall
-- Michael
