[jbosstools-issues] [JBoss JIRA] (JBIDE-13058) decouple versioning of parent pom from that of target platforms because some TPs are used for multiple parent poms

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-13058:
----------------------------------------

We should keep multiple since it's recommended to use it in IDE (it includes sources). We should keep it deployed in case one day we ave troubles to build unified, or if we want to build stuff from past and discover the aggregated sites disappeared. It's a nice backup.
If we can make it for CR2, the sooner the better.
                
> decouple versioning of parent pom from that of target platforms because some TPs are used for multiple parent poms
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-13058
>                 URL: https://issues.jboss.org/browse/JBIDE-13058
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng, target-platform
>    Affects Versions: 4.0.0.Beta2
>            Reporter: Nick Boldt
>            Assignee: Mickael Istria
>              Labels: respin-a
>             Fix For: 4.0.0.CR2
>
>
> Currently, we have parent pom versioned 4.0.0.Beta2-SNAPSHOT (Beta2x branch) or 4.0.0.CR1-SNAPSHOT (master). This is fine.
> However, we also have the same versions set for the various target platforms. This is no longer fine, because while the TP definition is the same between the stable_branch and trunk jobs, the VERSION differs and that means we have to publish the job TWICE to get the correct artifacts into Nexus. 
> Overkill solution is to have 2 jobs for every TP definition - one for stable branch (versioned 4.0.0.Beta2-SNAPSHOT) and another for trunk (versioned 4.0.0.CR1-SNAPSHOT). Have this as of yesterday.
> BETTER solution is to have the TP definitions versioned to match their path/filename. Thus:
> * poms in build/target-platforms/jbdevstudio-JunoSR1a (regardless of master or Beta2x branch) should be versioned 6.0.0.JunoSR1a
> * poms in build/target-platforms/jbosstools-JunoSR0c (regardless of master or Beta2x branch)  should be versioned 4.0.0.JunoSR0c

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