[
https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-18820:
----------------------------------------
{code}So either we hardcode it in a Foundation plugin (where it was) and a JBDS plugin
(where it was) and risk forgetting to update it with every milestone release, or we move
it into the parent pom and make it less likely that it's forgotten. {code}
At least, the JBDS part should be in JBDS main pom. Mixing JBDS into JBT is really a bad
design, and we need to keep the design clean, even if we sometimes forget an update (that
we actually spotted fast enough to not consider it as a big risk).
About where to put the jbosstools-version, I don't think it should be in Foundation,
because Foundation is something that is not expected to be rebuilt for every JBoss Tools
release. Maybe we should have a JBoss Tools branding plugin, which would be maintained
downstream of all components, similarly to aggregator, and that we'd rebuild for every
milestone..
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
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.3.8#6338)