[jbosstools-issues] [JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022479#comment-13022479 ] 

Nick Boldt commented on JBIDE-18820:
------------------------------------

*  jbosstools.version is used to define the version of JBoss Tools that is checked in ide-config.properties. It needs to include the parent pom version (not the version of project examples, foundation, or central) AND the BUILD_ALIAS so we can differentiate between the current milestone, the staged-for-QE milestone, and the latest (nightly. In fact this 4.2.1.CR1 build cycle showcases how bad it is to have that version embedded inside a Foundation plugin since the version is used to resolve stuff for Central, which didn't upversion for this release.)

* devstudio.version is used to define the version of JBoss Tools that is checked in ide-config.properties. Unlike jbosstools.version, it cannot inherit from the parent pom because 4.2.1 != 8.0.1. It can also not inherit from a pom version in jbdevstudio-product because the poms are 8.0.1-SNAPSHOT, not 8.0.1.${BUILD_ALIAS}-SNAPSHOT. 

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. Of course Foundation still needs to be rebuilt every time we release a milestone (which will then trigger downstream aggregates), but odds are VERY good that will happen since they're always changes in there.



> 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)