geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hernan Cunico <hcun...@gmail.com>
Subject Re: /lib vs /repository
Date Thu, 28 Feb 2008 20:06:30 GMT
Jacek Laskowski wrote:
> On Thu, Feb 28, 2008 at 11:47 AM, Hernan Cunico <hcunico@gmail.com> wrote:
>> OK, any reason why we don't follow a similar dir structure as in the repo?
> 
> Good question! Perhaps because it's easier to make a single directory
> with the minimum files in it and don't bother with the long-ish paths.
> Can't see any other reason as simplicity. On the other hand, one could

but we have

./lib/
     + boot/
     + endorsed/
     + gshell/

which it is not entirely flat. 

So it would seem to me that either way we could make some changes here to either make it really
flat or consistent with the repo. Just a thought, but I think it would help make the things
look more clear.

Cheers!
Hernan

> argue it's harder to maintain but since we build Geronimo with maven
> we don't really bother with it as Maven takes care of it. Hope I'm not
> mistaken.
> 
> I see it that you can have the bare framework with the single lib
> directory. Now, the question is what part of Geronimo introduces the
> repository dir? If it's something that's not needed for the
> framework's work you get the picture - you don't need to worry about
> repository directory as it's outside the framework. The framework uses
> lib and others can do whatever they want. If it's not the case, well,
> we could think of pros and cons moving them to repository then.
> 
> Jacek
> 

Mime
View raw message