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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-18820:
---------------------------------------------

[~mickael_istria] thinking about your suggestion about mock, jbt and jbds is not a bad idea after all assuming we don't mix jboss.org and devstudio updatesites....

I know that I are very religious about this but others aren't...but I think this can be solved by JBT have lower priority over JBDS.

Which plugins/features would declare these require capabilities to ensure things get installed ?

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