[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6381) increment .tags files to correct levels for JBT 3.2.0.M1 and JBDS 4.0.0.M1

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-6381:
-----------------------------------

gah, what a pain.

if a plugin or feature was incremented from, say, 1.0.0 to 3.1.0.qualifier to match the version ACTUALLY published in JBT 3.1.0, it registers as having changed in SVN since 3.1.0, and therefore should be in fact incremented to 3.2.0 according to the rule of "if you change svn, you must increment"; but since the only actual change was to make svn sources match what is generated by the uberbuilder... does this count?

At any rate, I've: 

a) created a script to collect the x.y.z versions of plugins in a given update site (eg., JBT 3.1.0) to see what we actually published.

http://anonsvn.jboss.org/repos/jbosstools/trunk/build/util/checkCompiledArtifactVersions.sh

b) created a script to compare the baseline generated in (a) with the values found in the 240 plugins and 64 features which have changed in SVN according to SVN diff

http://anonsvn.jboss.org/repos/jbosstools/trunk/build/util/checkSVNArtifactVersions.sh

---

Next up: 

a) manually vetting which of those 284 artifacts need to be incremented, and 

b) changing manifest.mf, feature.xml, pom.xml, and *.tags accordingly.


> increment .tags files to correct levels for JBT 3.2.0.M1 and JBDS 4.0.0.M1
> --------------------------------------------------------------------------
>
>                 Key: JBIDE-6381
>                 URL: https://jira.jboss.org/browse/JBIDE-6381
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng
>    Affects Versions: 3.2.0.M1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>            Priority: Blocker
>             Fix For: 3.2.0.M1
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira