[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

Fred Bricon (JIRA) issues at jboss.org
Thu Nov 27 09:51:39 EST 2014


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

Fred Bricon commented on JBIDE-18837:
-------------------------------------

Max, you're right, 4.2.1 and 4.2.0 should and will be the same. But do I need to remind you that *you* asked to be able to fine tune properties lookups, down to the incremental version? Without this lockstep, we have *no* way to ensure we'll be able to use specific x.y.z settings *should we need to*. 
So I have no problem not locking the incremental version down, because we'll be fine, however we need enforcer rules to ensure the foundation requirement is bumped between minor versions : make sure central in 4.3 requires foundation 4.3. 

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


More information about the jbosstools-issues mailing list