]
Nick Boldt closed JBIDE-12230.
------------------------------
Closing. Dupe.
define groups of components for migration to git
------------------------------------------------
Key: JBIDE-12230
URL:
https://issues.jboss.org/browse/JBIDE-12230
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 4.0.0.Alpha1
Reporter: Nick Boldt
Assignee: Denis Golovin
Fix For: 4.0.0.Alpha2
* Migration to Git
-> all at once or few modules at time
-> fine/coarse grained modules
TODO: JIRA for Denis re: combining modules into single git repos (eg.,
jmx+archives+as; tests+common); list the rest that should be separate
-> initially, 1 committer per module: assign JIRA component lead as git repo admin;
have them add others as needed (pretend we're an
Eclipse.org project, minus the voting
and
portal.eclipse.org madness)
-> how does a developer check out "jbosstools"-core
http://download.jboss.org/jbosstools/builds/cascade/swimlanes.txt -- defines the same
interdependencies between components
https://anonsvn.jboss.org/repos/jbosstools/trunk/build/pom.xml -- defines
"*-bootstrap" profiles which build multiple components on disk in one step.
Handy for compiling a collection of modules like tests+common+usage+jmx+archives+as
https://anonsvn.jboss.org/repos/jbosstools/trunk/build/pom.xml -- could define
"*-fetch-bootstrap" profiles that would fetch sources from git as well as
building if the module doesn't already exist on disk
-> "root" jbosstools must be maintained manually to point to specific
commits, to use it for "integration build" or tag of releases as a set of tags
of modules
--
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: