[jbosstools-issues] [JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-13232:
------------------------------------

We considered that approach but decided it was better to build TPs versioned independently from the JBT version because we may some day hit a point where WTP (specifically, Dali) stops breaking API every year and so we could build JBT against BOTH Juno and Kepler, rather than being tied to a specific version every year we release

For the JBITS case, you can version your TPs based on Eclipse (4.2, 4.3) or based on JBT (4.0, 4.1) as you'd prefer. Since currently we are forced to release each subsequent version of JBT/JBDS against a new version of Eclipse/WTP without being 100% backward compatible, and are therefore a ratio of 1:1 (JBDS/JBT:EclipseReleaseTrain), it doesn't really matter which you select. However, in future, we would like to get to the point where we're 1:2, so maybe at that point it makes more sense to use the Eclipse version... otherwise you'd need two TPs versioned the same way. 

Thus, assuming you need 2 target platforms for JBT 4.0 (Eclipse Juno 4.2), JBT 4.1 (Eclipse Kepler 4.3), and that next year's JBT 4.2 works with both Kepler (Eclipse 4.3) and Luna (Eclipse 4.4), you might get this:

https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbtis-unified/4.00.0.Final-SNAPSHOT/ (Dec 2012)
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbtis-unified/4.01.0.Final-SNAPSHOT/ (after 4.0.1 maintenance release in Mar 2013)
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbtis-unified/4.10.0.Final-SNAPSHOT/ (Jul 2013)
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbtis-unified/4.11.0.Final-SNAPSHOT/ (after 4.0.1 maintenance release in Sep 2013)
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbtis-unified-kepler/4.20.0.Final-SNAPSHOT/ (Jul 2014?)
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbtis-unified-luna/4.20.0.Final-SNAPSHOT/ (Jul 2014?)
etc.

Which, IMHO, is less sexy than this:

https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbtis-unified/4.20.0.Final-SNAPSHOT/ (after Jun 2012)
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbtis-unified/4.21.0.Final-SNAPSHOT/ (after Sep 2012)
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbtis-unified/4.21.1.Final-SNAPSHOT/ (after Dec 2012)
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbtis-unified/4.22.0.Final-SNAPSHOT/ (after Mar 2013
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbtis-unified/4.30.0.Final-SNAPSHOT/ (currently contains M4 bits)
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbtis-unified/4.30.1.Final-SNAPSHOT/ (will contains M5 bits)
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbtis-unified/4.40.0.Final-SNAPSHOT/ (after Sep 2013, Luna M3 bits?)

So basically, you'd define a TP aligned to an Eclipse version, and every time you have to change it to adjust the contents, the service digit would increment. 

I suppose you could also use the "service + 100" convention to define branches and align w/ JBT versions... thus:

https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbtis-unified/4.00.0.Final-SNAPSHOT/ (Dec 2012)
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbtis-unified/4.01.0.Final-SNAPSHOT/ (after 4.0.1 maintenance release in Mar 2013)
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbtis-unified/4.10.0.Final-SNAPSHOT/ (Jul 2013)
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbtis-unified/4.11.0.Final-SNAPSHOT/ (after 4.0.1 maintenance release in Sep 2013)
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbtis-unified/4.20.0.Final-SNAPSHOT/ (Jul 2014, Kepler bits)
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/targetplatforms/jbtis-unified/4.20.100.Final-SNAPSHOT/ (Jul 2014, Luna bits)
etc.

But I think I still prefer to version based on the Eclipse baseline version, regardless of the other stuff in there... since that's the base on which you'll be installing, testing, running, etc.

                
> refactor target platforms' GAVs, names, labels (was target platforms has the same name)
> ---------------------------------------------------------------------------------------
>
>                 Key: JBIDE-13232
>                 URL: https://issues.jboss.org/browse/JBIDE-13232
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng
>    Affects Versions: 4.1.0.Alpha1
>         Environment: 
>            Reporter: Max Rydahl Andersen
>            Assignee: Nick Boldt
>             Fix For: 4.1.0.Alpha1
>
>         Attachments: JBIDE13232.parent.pom.tweaks.txt
>
>
> .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either.
> Makes it hard to actually see which target platform to choose

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