[
https://issues.apache.org/jira/browse/UIMA-1921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927028#action_12927028
]
Marshall Schor commented on UIMA-1921:
--------------------------------------
Investigation shows:
1) the release:prepare default goals are to do "clean verify" which is one
short of install - so the local repo doesn't get the 2.3.1 version installed.
This causes some of the m2eclipse trouble when attempting to update projects
(because the dependencies for some projects are (incorrectly) set to 2.3.1. As
an experiment, I downloaded the tag and did mvn install on it, and then did the
Maven update project configuration, and then things built with m2eclipse.
2) the command "mvn release:prepare -DdryRun" successfully updates the next
versions of the POMs including the property for the uimaDependencyVersion from
2.3.1-SNAPSHOT to 2.3.2-SNAPSHOT. However, if you leave off the "-DdryRun", it
fails to update the uimaDependencyVersion, for the next development version,
leaving it at the release version of "2.3.1". This seems likely a bug in the
release plugin - I would expect the dryRun to have the same updating. I'll ask
about this on the maven users list.
> release fails because some dependencies are set using a property, and they
> don't get updated to the next release level by release:perform
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: UIMA-1921
> URL: https://issues.apache.org/jira/browse/UIMA-1921
> Project: UIMA
> Issue Type: Bug
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
>
> The release:perform updates the property from 2.3.1-SNAPSHOT to 2.3.1 for the
> tag, correctly. However, the next check-in the release plugin does for the
> next version leaves it at 2.3.1. I think this is by design.
> The m2eclipse plugin tries to use workspace projects to resolve, but that
> fails, since the workspace projects were updated to 2.3.2-SNAPSHOT. I think
> m2eclipse should, in that case, revert to setting up the Eclipse classpath to
> refer to the .m2 repository (which has the just-built tag, at 2.3.1 (no
> shapshot), but it seems not to.
> Try changing things to not use properties, and see if everything is updated
> to the next -SNAPSHOT level.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
