JDK8 Preliminary Repository Layout

Kelly O'Hair kelly.ohair at oracle.com
Thu Mar 10 19:59:14 UTC 2011


On Mar 10, 2011, at 11:17 AM, John Coomes wrote:

> Johan Walles (johan.walles at oracle.com) wrote:
>> 2011-03-10 10:33, Anthony Petrov skrev:
>>> Hi Andrew,
>>> 
>>> On 3/10/2011 3:48 AM, Dr Andrew John Hughes wrote:
>> [snip]
>>>> Hey, I'd just make it all one repository as they all interdepend on
>>>> each other
>>> 
>>> One huge "all-in-all" repository is great for integrators, porters, or
>>> maintainers, but it isn't that convenient for developers working on
>>> specific areas of JDK. Primarily because of the unnecessarily increased
>>> build time.
>> 
>> Build time wouldn't be an issue if you could build a single component by 
>> itself by just cd:ing into the component directory and do "make" there.
> 
> So I pull the entire tree, make some changes, do a build.  I want to
> sync with the latest changes in my component (whatever it is), but
> have to pull everything.  To save build time, I build just my
> component.  But then my built bits no longer correspond to my source
> tree.  Debugging becomes a new challenge.
> 
>> The problem for many developers with the all-in-one repository solution 
>> is the time it takes to clone everything (5-6 minutes).
> 
> That's the best case, when I'm on the corporate network, close to the
> server.  Over my dsl line at home, it takes 24 minutes for everything,
> vs. 1 min 10 secs for hotspot (the only part I need).

DSL?  Is that the bundle of wires I see in those comcast cable commerials? ;^)

-kto

> 
> -John
> 
>>> Since it's always possible to make a clone of the whole 'forest', and
>>> hence get all the repos virtually at once, I don't really see any
>>> problems with making some parts of the class (and native) libraries
>>> separate repositories.
>>> 
>>> --
>>> best regards,
>>> Anthony
> 




More information about the build-dev mailing list