[jbosstools-issues] [JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated

[Max Rydahl Andersen (JIRA)]

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

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

I definitely would prefer the version gets to be independent of parent pom and i'm not fully grokking how you suggest to do it using base root pom version thus a PR would be helpful for sure.

Aside: Its not new QE (or others) use nightlies and it is also not new that in *very* special cases QE need to rely on -D to test specific setups - we have done that all former releases. I don't think there would ever be  need to differentiate between latest nightly for 4.2.x and latest staged for 4.2.x - that would be extreme exceptional cases and in all this it would still require using exact timestamps in ide-properties to differentiate. And yes, there aren't an awesome silver bullet for this - I wish there were; but so far I think by decoupling from parent pom and try testing our way out of detecting if the version is properly bumped we have a solution that are not bullet proof (You can break the situation if you really are clever in install sequence of things) but that are Good Enough without being too rigid.


> because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-18837
>                 URL: https://issues.jboss.org/browse/JBIDE-18837
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build, central, common/jst/core, project-examples
>    Affects Versions: 4.2.1.CR1
>            Reporter: Nick Boldt
>             Fix For: 4.3.0.Alpha1
>
>
> When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples.
> Therefore we need manifest-level [4.2.1,) requirements on upstream foundation.core in examples and central, to force this lock-step updating.
> And we need to use the maven enforcer plugin to fail the build if these versions get out of sync.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)