[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

[Nick Boldt (JIRA)]

Nick Boldt created JBIDE-18837:
----------------------------------

             Summary: 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, common/jst/core
    Affects Versions: 4.2.1.CR1
            Reporter: Nick Boldt


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