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

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

Nick Boldt commented on JBIDE-18837:
------------------------------------

OK, so at the moment, the master branch for Base's org.j.t.foundation.core plugin relies on parent pom version for its definition of jbosstools.version.

If you want that changed to use Base's root pom version, let me know and I can create a new PR. 

Aside: I wasn't suggesting NEW -D flags. I was suggesting that under your new scheme, QE may need to revert to using the OLD flags, since you have no way to differentiate "latest nightly for 4.2.x" from "latest staged for 4.2.x". Since we've discovered that QE sometimes wants to test nightlies before they're staged (JBIDE-18833), we need a workaround for that use case. Being tied to parent pom version HELPS but it's not the silver bullet I'd like.

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