I don't know if that change cause any issues in our plugins, but I would
prefer to do the change. It minimize the errors and the manual effort
when doing a release.
-- Michael
Marshall Schor wrote:
The basic maven build creates Jars in the target with alternate names:
project uimaj-core =
I don't know of any specific reason why not to do this, but just be
sure to review the history of this to make sure we aren't going around
in circles. It used to be that way, and it changed along with issue
https://issues.apache.org/jira/browse/UIMA-355. Also look for
discussion of UIMA-355 in
On Jan 21, 2008, at 10:58 AM, Michael Baessler wrote:
Is this OK to do, or is there a reason we keep the uimaj-ep-runtime
inner jars naming conventions different?
The motivation was to add a PDE nature to the eclipse plugin projects
with the maven eclipse plugin. The only way I found
to
Thanks Jörn.
I think that with some experimentation we can get the PDE nature to work
properly - at least, that's my goal for now :-) I'll do some more tests
to see if I can come up with an approach which allows both maven and
Eclipse to work .
Thanks. -Marshall
Jörn Kottmann wrote:
On
The basic maven build creates Jars in the target with alternate names:
project uimaj-core = drop the j from uimaj, and don't suffix the
version - uima-core.jar
An exception to this is jVinci - jVinci becomes jVinci.jar (no version)
Another exception: when the uimaj-ep-runtime plugin is
