[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-8119) parent pom maintenance for 3.3 trunk and 3.2 stable_branch

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt resolved JBIDE-8119.
-------------------------------

    Resolution: Done


No need to increment pi4soa, teiid, savara, since they do not depend on JBT components. NOT publishing 0.0.2 parent pom means it'll always be built and used from local workspace instead of pulling from remote nexus repo, which is IMHO better than the problem we have now with 0.0.1-SNAPSHOT in JBoss Nexus repo.

> parent pom maintenance for 3.3 trunk and 3.2 stable_branch
> ----------------------------------------------------------
>
>                 Key: JBIDE-8119
>                 URL: https://issues.jboss.org/browse/JBIDE-8119
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng
>    Affects Versions: 3.3.x
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 3.3.x
>
>         Attachments: JBIDE-8119.patch
>
>
> 1. Increment parent pom in trunk to 0.0.2-SNAPSHOT
> 2. publish updated trunk parent pom @ version 0.0.2-SNAPSHOT, and deploy to nexus
> 3. Increment all pom.xml refs to parent pom to 0.0.2-SNAPSHOT in all repos (jbosstools, devstudio, teiid, pi4soa, savara, scribble)
> (repeat process for 0.0.1-SNAPSHOT -> 0.0.1 in stable_branch just before release / GA respin)

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira