[
https://issues.redhat.com/browse/JGRP-2471?page=com.atlassian.jira.plugin...
]
Bela Ban updated JGRP-2471:
---------------------------
Description:
Currently, the version is set in the POM (maven), but also in
{{conf/JGROUPS_VERSION.properties}}. This is cumbersome, as we have to update both files
on a release (and change the version back to {{XXX-SNAPSHOT}} after the release).
With the introduction of maven {{release-plugin}}, modifying the file is manual work
that's unwanted.
Therefore get rid of {{JGROUPS-VERSION.properties}} and read the version directly from the
POM.
was:
Currently, the version is set in the POM (maven), but also in
{{conf/JGROUPS_VERSION.properties}}. This is cumbersome, as we have to update both files
on a release (and change the version back to {{XXX-SNAPSHOT}} after the release).
With the introduction of maven release-plugin, modifying the file is manual work
that's unwanted.
Therefore get rid of {{JGROUPS-VERSION.properties}} and read the version directly from the
POM.
Parse version from POM
----------------------
Key: JGRP-2471
URL:
https://issues.redhat.com/browse/JGRP-2471
Project: JGroups
Issue Type: Enhancement
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Minor
Fix For: 5.0.0.Alpha6
Currently, the version is set in the POM (maven), but also in
{{conf/JGROUPS_VERSION.properties}}. This is cumbersome, as we have to update both files
on a release (and change the version back to {{XXX-SNAPSHOT}} after the release).
With the introduction of maven {{release-plugin}}, modifying the file is manual work
that's unwanted.
Therefore get rid of {{JGROUPS-VERSION.properties}} and read the version directly from
the POM.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)