<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Nick,<br>
<br>
Just forked it and here is the log <br>
<br>
eskimo@dgolovin-desktop:~/Projects/jbds/jbosstools-fork-submodules$
git submodule add
<a class="moz-txt-link-abbreviated" href="mailto:git@github.com:dgolovin/jbosstools-target-platforms.git">git@github.com:dgolovin/jbosstools-target-platforms.git</a>
jbosstools-target-platforms<br>
Cloning into 'jbosstools-target-platforms'...<br>
remote: Counting objects: 6773, done.<br>
remote: Compressing objects: 100% (2351/2351), done.<br>
remote: Total 6773 (delta 3488), reused 6756 (delta 3471)<br>
Receiving objects: 100% (6773/6773),<b> 53.70 MiB</b> | 974 KiB/s,
done.<br>
Resolving deltas: 100% (3488/3488), done.<br>
<br>
It is to much for such a small young repository?<br>
<br>
for example jbosstools-jst with all its history more than twice
less space.<br>
<br>
eskimo@dgolovin-desktop:~/Temp$ git clone
<a class="moz-txt-link-abbreviated" href="mailto:git@github.com:jbosstools/jbosstools-jst.git">git@github.com:jbosstools/jbosstools-jst.git</a><br>
Cloning into 'jbosstools-jst'...<br>
X11 forwarding request failed on channel 0<br>
remote: Counting objects: 37604, done.<br>
remote: Compressing objects: 100% (5442/5442), done.<br>
remote: Total 37604 (delta 19647), reused 37454 (delta 19501)<br>
Receiving objects: 100% (37604/37604), <b>23.94 MiB</b> | 659
KiB/s, done.<br>
Resolving deltas: 100% (19647/19647), done.<br>
<br>
Why do you keep master branch empty?<br>
Are there some reasons to have branches named different from the
actual versions?<br>
<br>
Thanks<br>
Denis<br>
<br>
<br>
<br>
<br>
On 02/07/2013 11:39 AM, Nick Boldt wrote:<br>
</div>
<blockquote cite="mid:511402FE.4050506@redhat.com" type="cite">
<pre wrap="">In case you missed it, the sources for the new Kepler M5 target
platforms for JBT 4.1 / JBDS 7.0 are located here:
<a class="moz-txt-link-freetext" href="https://github.com/jbosstools/jbosstools-target-platforms/tree/4.3.0">https://github.com/jbosstools/jbosstools-target-platforms/tree/4.3.0</a>
The resulting built target platform sites are here (unpacked sites and
zips too, for use offline):
<a class="moz-txt-link-freetext" href="http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/">http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/</a>
<a class="moz-txt-link-freetext" href="http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/">http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/</a>
(VPN required)
Currently, the only difference between the JBT and JBDS target platforms
is that the JBDS one excludes swtbot, birt, and GWT/GPE. Therefore, if
you can't access the JBDS one and don't want to build it locally, you
should be fine to use the JBT one.
This change is documented here:
<a class="moz-txt-link-freetext" href="https://github.com/jbosstools/jbosstools-build/blob/master/target-platforms/README.md">https://github.com/jbosstools/jbosstools-build/blob/master/target-platforms/README.md</a>
-and-
<a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/JBIDE-13386">https://issues.jboss.org/browse/JBIDE-13386</a>
Cheers,
</pre>
</blockquote>
<br>
</body>
</html>