[jbosstools-issues] [JBoss JIRA] (JBIDE-12963) allow projects to override BUILD_ALIAS without referring to a non-existent target platform definition

[Vlado Pakan (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-12963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vlado Pakan closed JBIDE-12963.
-------------------------------


    
> allow projects to override BUILD_ALIAS without referring to a non-existent target platform definition
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-12963
>                 URL: https://issues.jboss.org/browse/JBIDE-12963
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng, modeshape, target-platform
>    Affects Versions: 4.0.0.Beta2
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.0.0.Beta2
>
>
> Modeshape sets their own BUILD_ALIAS, eg., Beta5 (while JBoss Tools is still on Beta1 or Beta2).
> The result of this is:
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/modeshape-tools-continuous/44/console}
> [ERROR] Internal error: java.lang.RuntimeException: Could not resolve target platform specification artifact org.jboss.tools.target-platforms.jbosstools-JunoSR1a:jenkins:target:jenkins:4.0.0.Beta5-SNAPSHOT -> [Help 1]
> {code}
> So, to fix this, we can externalize ${JBT_VERSION}.${BUILD_ALIAS}-SNAPSHOT as used in the parent pom to a new variable, TARGET_PLATFORM_VERSION, which would then allow BUILD_ALIAS to be set independently.
> Thus the job would run with:
> {code}
> -DBUILD_ALIAS=Beta5 -DTARGET_PLATFORM_VERSION=4.0.0.Beta2-SNAPSHOT
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira