[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=12750337#comment-12750337 ] 

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

We used to have one rolling version for all the TPs used in a given release... M4, M5, M6, M7, RC1, GA, SR1-pre, SR1, SR1a, SR2-pre, SR2, etc. but that introduced more problems than it solved.

Regardless of the suffix (-SNAPSHOT or Alpha/Beta/CR/Final, or a combination) the fact is we need to version each TP release uniquely and use them until they're expired by a newer one. Often in the past we've needed several in use in parallel... for example if we've released a milestone build based on one TP (eg., M4), are working in stable branch for the next milestone release using second one (M5), and developing trunk against a newer third one (M6). M4 can vanish once the stable branch release is done and released (at which point M5 becomes the minimum one we have to keep around), but we often need more than one actively used TP at a time... and that's not even including the upper limit ones (mins AND maxs) or testing against past/future releases. 

As well, we have a bug trying to publish TPs w/o the -SNAPSHOT suffix so currently everything has to be a SNAPSHOT whether it's Final or in-development. 

See JBIDE-13408 -- maybe you have some insight on how to solve that?
                
> 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