[jbosstools-dev] jbosstools-target-platforms repo is too big / question about branches (was Re: Kepler M5 target platform sources have moved to a new github repo)

[Nick Boldt]

Denis:

an accidental binary commit is what's causing that. Max said today he'd 
do a force-push after filtering the history to pull that out.

As to master: it contains the publish script which is branch-independent.

As to the versioned branches: each one contains the target platforms for 
that stream. Soon we'll add the 4.2.2 branch (in a couple weeks when 
Juno SR2 is out) and in the fall we'll add the 4.3.1 branch.

Mickael: I suppose we could have just two branches for Juno (4.2.0 + 
4.2.x instead of three (4.2.0 + 4.2.1 + 4.2.2), since once we move to 
4.2.2 we won't ever need to build the 4.2.1-based TPs again. WDYT?

N

On 02/13/2013 02:00 PM, Denis Golovin wrote:
> Nick,
>
> Just forked it and here is the log
>
> eskimo at dgolovin-desktop:~/Projects/jbds/jbosstools-fork-submodules$ git
> submodule add git at github.com:dgolovin/jbosstools-target-platforms.git
> jbosstools-target-platforms
> Cloning into 'jbosstools-target-platforms'...
> remote: Counting objects: 6773, done.
> remote: Compressing objects: 100% (2351/2351), done.
> remote: Total 6773 (delta 3488), reused 6756 (delta 3471)
> Receiving objects: 100% (6773/6773),*53.70 MiB* | 974 KiB/s, done.
> Resolving deltas: 100% (3488/3488), done.
>
> It is to much for such a small young repository?
>
> for example jbosstools-jst with all its history more than twice less space.
>
> eskimo at dgolovin-desktop:~/Temp$ git clone
> git at github.com:jbosstools/jbosstools-jst.git
> Cloning into 'jbosstools-jst'...
> X11 forwarding request failed on channel 0
> remote: Counting objects: 37604, done.
> remote: Compressing objects: 100% (5442/5442), done.
> remote: Total 37604 (delta 19647), reused 37454 (delta 19501)
> Receiving objects: 100% (37604/37604), *23.94 MiB* | 659 KiB/s, done.
> Resolving deltas: 100% (19647/19647), done.
>
> Why do you keep master branch empty?
> Are there some reasons to have branches named different from the actual
> versions?
>
> Thanks
> Denis
>
>
>
>
> On 02/07/2013 11:39 AM, Nick Boldt wrote:
>> In case you missed it, the sources for the new Kepler M5 target
>> platforms for JBT 4.1 / JBDS 7.0 are located here:
>>
>> https://github.com/jbosstools/jbosstools-target-platforms/tree/4.3.0
>>
>> The resulting built target platform sites are here (unpacked sites and
>> zips too, for use offline):
>>
>> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/
>> http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/
>> (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:
>>
>> https://github.com/jbosstools/jbosstools-build/blob/master/target-platforms/README.md
>> -and-
>> https://issues.jboss.org/browse/JBIDE-13386
>>
>> Cheers,
>>
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com