[jbosstools-issues] [JBoss JIRA] (JBIDE-4731) use p2.mirror w/ comparator to verify plugin/feature versions are correctly incremented between builds/baselines
Mickael Istria (JIRA)
jira-events at lists.jboss.org
Mon Feb 4 12:04:51 EST 2013
[ https://issues.jboss.org/browse/JBIDE-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mickael Istria reassigned JBIDE-4731:
-------------------------------------
Assignee: Jiri Peterka (was: Mickael Istria)
[~jpeterka]: It seems to me that what you did provide ( http://machydra.brq.redhat.com:8080/job/devstudio.version-watch/ws/output.html ) is a good answer to what's expected by this ticket.
Thus, I let you decide of the future of this ticket ;)
> 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/Releng
> Reporter: Nick Boldt
> Assignee: Jiri Peterka
> Priority: Minor
> Fix For: LATER
>
>
> 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