[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

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-13058:
------------------------------------

well, we need to set versions for jbosstools-JunoSR1a, jbosstools-JunoSR0c, jbdevstudio-JunoSR1a, and jbdevstudio-JunoSR0c.

I would be happy if the version of the TP was just 1.0.0-SNAPSHOT, because then we'd always use the latest version of the collection of deps that are the given TP. When we cut a new target platform, it would be JunoSR0d v 1.0.0-SNAPSHOT or JunoSR1b v 1.0.0-SNAPSHOT, regardless if it's the JBT or JBDS one. Simpler, no?

We shouldn't need to have a different version of the TP for trunk and stable_branch; in fact that's entirely redundant.

So, instead of 

{quote}
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/target-platforms/jbosstools-JunoSR0c/unified/4.0.0.JunoSR0c-SNAPSHOT/
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/target-platforms/jbosstools-JunoSR0c/unified/4.1.0.JunoSR0c-SNAPSHOT/
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/target-platforms/jbosstools-JunoSR1a/unified/4.0.0.JunoSR0c-SNAPSHOT/
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/target-platforms/jbosstools-JunoSR1a/unified/4.1.0.JunoSR0c-SNAPSHOT/
... and similar for /multiple/ ...

https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/target-platforms/jbdevstudio-JunoSR0c/unified/6.0.0.JunoSR0c-SNAPSHOT/
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/target-platforms/jbdevstudio-JunoSR0c/unified/6.1.0.JunoSR0c-SNAPSHOT/
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/target-platforms/jbdevstudio-JunoSR1a/unified/6.0.0.JunoSR1a-SNAPSHOT/
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/target-platforms/jbdevstudio-JunoSR1a/unified/6.1.0.JunoSR1a-SNAPSHOT/
... and similar for /multiple/ ...
{quote}

Could we have:
{quote}
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/target-platforms/jbosstools-JunoSR0c/unified/1.0.0-SNAPSHOT/
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/target-platforms/jbosstools-JunoSR0c/unified/1.1.0-SNAPSHOT/
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/target-platforms/jbdevstudio-JunoSR0c/unified/1.0.0-SNAPSHOT/
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/target-platforms/jbdevstudio-JunoSR1a/unified/1.0.0-SNAPSHOT/
{quote}

Could we also skip deploying the /multiple/ ones? Who needs them, when they have the unified ones?
                
> 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: Nick Boldt
>              Labels: respin-a
>             Fix For: 4.0.0.Beta2
>
>
> 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