[
https://issues.apache.org/jira/browse/UIMA-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor closed UIMA-1834.
--------------------------------
Fix Version/s: 2.3.1
Resolution: Fixed
The pom's <version> is now substituted (using filtering) into the Java sources
that return these values. Added / modified new classes, UimaVersion and
UimaAsVersion, which are not in the source-path, and have substitutable values
for the version (major, minor, incremental), and updated the pom to use
filtered resource processing to produce a new class under target which has the
version info from the pom substituted in; this generated-source is then added
to the set of source files to be compiled.
Note - just as in every other project using generated sources, after checking
this out, use the m2Eclipse menu pick on the project, Maven -> update
configuration, to get it to recognize the generated sources and update its
(Eclipse) classpath.
> Automate inclusion of current release / version info in uimaj and uima-as
> -------------------------------------------------------------------------
>
> Key: UIMA-1834
> URL: https://issues.apache.org/jira/browse/UIMA-1834
> Project: UIMA
> Issue Type: Improvement
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Fix For: 2.3.1
>
>
> Both uimaj and uima-as have static Java strings identifying the release
> version. These have been manually maintained. Automate this so the right
> version is inserted (from the pom), and perhaps also consider including svn
> tag info. Also consider whether to maintain this info at a finer grain
> (e.g., for each Jar), and if so, how to make it available at run time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
