[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=13109003#comment-13109003 ] 

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

After discussion w/ Max today, what he wants is a devdoc which explains:

* How to do jbosstools-base/foundation & jbdevstudio-product versioning (ie., how to ensure we have the correct value of default.version in o.j.t.foundation.core & c.j.d.central.core's currentversion.properties)
* parent pom version rules (when to update, what depends on the version (ie., root poms and default.version in foundation.core, central.core, above)
* ide-config properties versioning (when to update, how to control which versions map to which releases (CI, staging, development/stable)

[~maxandersen], if I've missed anything, please let me know or you can comment on the forthcoming devdoc once I write it.


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