From: "Jason van Zyl" <[EMAIL PROTECTED]>
> On Wed, 2002-03-27 at 11:29, Sam Ruby wrote:
> > Apparently, the gump machine had network problems last night. See:
> >
> > The proposal is to change these entries thus:
> >
> > <module name="jakarta-avalon-apps" repository="jakarta"
path="gump.xml"/>
>
> How about moving toward project encapsulation w.r.t to repository
> information (in all things but this would be a start)? By this I mean
> that all the information required to check out a project is stored in
> the project itself.
>
> If descriptors are moved out of gump's immediate reach then that
> repository attribute is something that is not in direct control of the
> project, having all this information would allow better decentralization
> and a project wouldn't be dependent on knowing what particular gump
> details like the repository descriptors. This might be simpler for
> processing as I imagine you have to do some wing dinging to get the
> sourceforge stuff to work. This information would become the
> responsibility of the project, the group which is most likely to know
> what the accurate cvs info is.
>
> Plus if you get a large number of projects in different locations you
> don't have to make a repository descriptor for each project stored in a
> different location. I think project encapsulation is the way to go.
The idea seems interesting.
But if the info about the CVS is in the project that is in the CVS, how do I
get it out of CVS, since I don't yet have the info? (catch22)
Could you show me an example of how to do this?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
