[jbosstools-issues] [JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change
[
https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-18820:
---------------------------------------------
this is all about the ide.properties file and to avoid having to update parent pom just
because version changed.
Nothing to do with those pom.xml references.
From the description:
"Opening this jira to make sure we
walkthrough and write down which values should be in ide.properties and what level
(4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid
parent pom from always having to respin because of a maintanence release. "
to rephrase: in past we seem to list all explicit values for all versions (i.e.
|4.3.0.CR1, 4.3.0.CR2, etc. ) which equals to having to change everything everytime and
the next version would not be covered; where as if we only added |4.3 for most values we
only needed to update settings for stuff that *actually* do have version specific things -
since it would then just fall back on the 4.3 as default values.
define how to handle ide.properties and avoid parent pom to always
change
-------------------------------------------------------------------------
Key: JBIDE-18820
URL: https://issues.jboss.org/browse/JBIDE-18820
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Reporter: Max Rydahl Andersen
Assignee: Max Rydahl Andersen
Fix For: 4.3.0.CR1
As illustrated in JBIDE-18806 our current setup of how ide.properties and project
versioning are not working or at least we seem to not get it updated right.
Current workaround applied is that parent pom now again defines the global version even
though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452
for earlier attempts on this)
Opening this jira to make sure we walkthrough and write down which values should be in
ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated
(hopefully rarely) and how to avoid parent pom from always having to respin because of a
maintanence release.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)