[
https://issues.apache.org/jira/browse/UIMA-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796857#action_12796857
]
Richard Eckart de Castilho commented on UIMA-1716:
--------------------------------------------------
That's great, thanks. I was a bit puzzled, because all the poms in that tags I
opened in Eclipse displayed as 2.3.0-incubating-SNAPSHOT, but my hudson build
only complained about SimpleServer. First I was attributing that to an svn
glitch, I guess now it was an Eclipse glitch.
I wonder, wouldn't it be reasonable to move UIMA to using the maven release
plugin, which handles those things? That would mean that the uimaj artifact POM
would have to be moved up one directory to create a nested structure. I've been
using physically nested Maven projects for a while now and they work quite fine
at least with Eclipse+m2eclipse as well as IntelliJ as I have heard.
> UIMA Sandbox components in tag 2.2.2 are 2.3.0-SNAPSHOT
> -------------------------------------------------------
>
> Key: UIMA-1716
> URL: https://issues.apache.org/jira/browse/UIMA-1716
> Project: UIMA
> Issue Type: Bug
> Components: Sandbox
> Affects Versions: 2.2.2
> Reporter: Richard Eckart de Castilho
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> All the POMs in the UIMA Sandbox tag 2.2.2-incubating claim that they are
> 2.3.0-incubating-SNAPSHOT. I know that tags should not be changed, but I
> would still vote for fixing those versions and also have them depend on UIMA
> 2.2.2-incubating if possible. Obviously Marshall Schor has changed this after
> the tagging as part of UIMA-1461 in revision 798670, which unfortunately
> lacks any explanation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
