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

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

This looks like a special case of JBIDE-18820 to me.

And I do not see why this is required. 4.2.0 and 4.2.1 settings should be the exact same, they should be stored under 4.2 in the settings. There should be zero difference.

Only time 4.2.1 are relevant is during its development phase *if* we have some changes/differences.

None of this should be this lockstepped - if it is there is something very wrong since it is a *backwards* compatible release.

Please give example of where such hard coupling would ever and have ever been an issue ?

For now a very big -1 on applying such changes.


> 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: Bug
>          Components: build, central, common/jst/core, project-examples
>    Affects Versions: 4.2.1.CR1
>            Reporter: Nick Boldt
>              Labels: respin-a
>             Fix For: 4.2.1.CR1
>
>
> 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)