<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">moving to jbosstools-dev<br><div><br><div>Begin forwarded message:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>From: </b></span><span style="font-family:'Helvetica'; font-size:medium;">Denis Golovin <<a href="mailto:dgolovin@exadel.com">dgolovin@exadel.com</a>><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>Subject: </b></span><span style="font-family:'Helvetica'; font-size:medium;"><b>Re: Proposed New Github Component Chunks for JBoss Tools 4.0</b><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>Date: </b></span><span style="font-family:'Helvetica'; font-size:medium;">24 Aug 2012 02:56:58 GMT+02:00<br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><br></div>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Below is the diagram I've got by
analyzing dependencies it let reduce amount of components to 13
without any changes to dependencies we have now (
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
transitive dependencies aren't shown like openshift->common,
because openshift->as and as->common).<br>
<br>
Opened questions:<br>
* openshift in as component?<br>
* forge and freemarker inside common?<br>
<br>
If we would revert central and examples dependencies and let
interested components inject examples and certain functionality
into central (not sure if that possible) that would be logical to
have them in common component<br>
<br>
That would reduce 13 to 9 counting forge, freemarker and
openshift consumed by bigger components. <br>
<br>
<br>
# Current dependencies:<br>
<br>
<img alt="" height="788" width="969" id="ae271b9f-166b-4ad3-8bb2-a688b958cee8" apple-width="yes" apple-height="yes" src="cid:part1.07070504.00090803@exadel.com"> <br>
<br>
# final git modules dependencies<br>
<br>
<img alt="" height="442" width="632" id="8aed487d-7c8b-4a3a-ae35-4c184353b5cb" apple-width="yes" apple-height="yes" src="cid:part2.08060304.01020003@exadel.com"><br>
<br>
Denis<br>
<br>
<br>
On 08/23/2012 12:00 PM, Nick Boldt wrote:<br>
</div>
<blockquote cite="mid:50367DD5.1000000@redhat.com" type="cite">As
part of the planned migration to git [0] it's been suggested that
we combine some of the existing components into larger groups [1]
so that it's more manageable in terms of checking out sources and
tagging/branching [2].
<br>
<br>
Because 25 is a large number, and 1 is a small number, and we need
some happy compromise.
<br>
<br>
Here's my proposal for how to divide the JBT 4.0 sources into 7
github repos (chunks), comprising 4 tiers of dependency. This is
akin to the +0, +1, +2, +3 labels assigned to projects within the
annual Eclipse release trains [3], used to define delivery times
based on dependencies between projects.
<br>
<br>
== TIER 0: no upstream <a href="http://JBoss.org">JBoss.org</a> chunks ==
<br>
<br>
Base = tests + common + usage
<br>
<br>
== TIER 1: 1 upstream chunk, Base ==
<br>
<br>
AppServer = openshift + as + archives + jmx
<br>
-> depends on Base
<br>
<br>
Hibernate/Birt/Freemarker = hibernate + birt + freemarker
<br>
-> depends on Base
<br>
<br>
Visual Editing = vpe + xulrunner + gwt + struts + jsf + jst + cdi
<br>
-> depends on Base
<br>
<br>
Web Services = WS + Forge
<br>
-> Depends on Base
<br>
<br>
== TIER 2: 4 upstream chunks ==
<br>
<br>
Seam/Runtime = Seam + Runtime
<br>
-> depends on Hib + Vis + AppServer + Base
<br>
<br>
== TIER 3: 5 upstream chunks ==
<br>
<br>
Central/Examples/Maven/Portlet = central + examples + maven +
portlet
<br>
-> depends on Seam/Runtime + Hib + Vis + AppServer + Base
<br>
<br>
I'm not thrilled with the names of the chunks, as something like
"Central/Examples/Maven/Portlet" doesn't exactly roll off the
tongue. If you have better names for the chunks, please suggest
them.
<br>
<br>
But regardless of name, I think the above separation of concerns,
and the implied build sequence workflow makes a lot of sense.
<br>
<br>
[0] <a class="moz-txt-link-freetext" href="http://tinyurl.com/git-migration-plan">http://tinyurl.com/git-migration-plan</a>
<br>
[1] <a class="moz-txt-link-freetext" href="http://ether-man.rhcloud.com/p/build.next">http://ether-man.rhcloud.com/p/build.next</a>
<br>
[2] <a class="moz-txt-link-freetext" href="http://ether-man.rhcloud.com/p/jbosstools-2012-08-23">http://ether-man.rhcloud.com/p/jbosstools-2012-08-23</a>
<br>
[3]
<a class="moz-txt-link-freetext" href="http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan#Milestones_and_Release_Candidates">http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan#Milestones_and_Release_Candidates</a>
- "These delivery times are based on the dependencies between
projects. They are labeled +0, +1, +2, and +3, with +0 coming
first (the Platform) and +3 coming last (EPP). Projects themselves
decide if they are +0, +1, +2, or +3."
<br>
<br>
If you have comments or suggestions regarding this migration plan,
please post them here or in
<a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/JBIDE-12475">https://issues.jboss.org/browse/JBIDE-12475</a>.
<br>
<br>
Thanks!
<br>
<br>
</blockquote>
<br>
</div>
</blockquote></div><br></body></html>