[jbosstools-issues] [JBoss JIRA] (JBIDE-4731) use p2.mirror w/ comparator to verify plugin/feature versions are correctly incremented between builds/baselines

Jiri Peterka (JIRA) jira-events at lists.jboss.org
Wed Nov 6 05:28:02 EST 2013


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

Jiri Peterka reassigned JBIDE-4731:
-----------------------------------

    Assignee: Nick Boldt  (was: Jiri Peterka)


Jobs are live and running on both jenkins servers. I'm also checking periodically new every new QE build on machydra so currently there is nothing more to do. Feel free to resolve if you're satisfied. 
                
> use p2.mirror w/ comparator to verify plugin/feature versions are correctly incremented between builds/baselines
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-4731
>                 URL: https://issues.jboss.org/browse/JBIDE-4731
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: build
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>            Priority: Blocker
>             Fix For: 4.1.x, 4.2.x
>
>
> This depends on having per-component builds and a buckminster/p2 aggregator to merge them into a single update site.
> See http://aniefer.blogspot.com/2009/08/versioning-p2-slides-from-eclipsecon.html for details on using p2.mirror w/ a comparator

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


More information about the jbosstools-issues mailing list