Doesn't the xml-cocoon2.xml file define it's dependencies...
<project name="xml-cocoon2">
<depend project="jakarta-ant"/>
<depend project="xml-xerces"/>
<depend project="xml-xalan2"/>
<depend project="xml-batik"/>
<depend project="jakarta-servletapi-4"/>
<depend project="jakarta-avalon-logkit"/>
<depend project="jakarta-avalon"/>
<depend project="xml-fop"/>
<depend project="jakarta-regexp"/>
<depend project="jdom"/>
<depend project="xt"/>
<option project="xml-batik"/>
<depend project="rhino"/>
<depend project="jstyle"/>
<depend project="maybeupload"/>
<depend project="bsf"/>
</project>
?
> -----Original Message-----
> From: Jeff Martin [mailto:[EMAIL PROTECTED]]
> Sent: 11 April 2001 3:32 pm
> To: '[EMAIL PROTECTED]'
> Subject: RE: [GUMP] Changes ahead...
>
>
> Seems like a nice idea but the implementation may prove a
> little problematic
> as you would have to still have a definition of the dependencies.
>
> At the moment the workspace is used to link the dependency
> definitions to
> the actually projects definitions. This would still have to take place
> somewhere. So either we move the location of the project
> definitions which a
> project is dependant on into the project definition, which
> kinda defeats the
> object of separating the workspace from the projects, or we have two
> workspace definitions, one which describes the world (i.e.
> the links between
> project names and project definitions) and then a second
> workspace def which
> defines only what is needed for this run.
>
> Does that make sense?
>
> > -----Original Message-----
> > From: John Morrison [mailto:[EMAIL PROTECTED]]
> > Sent: 10 April 2001 13:25
> > To: [EMAIL PROTECTED]
> > Subject: RE: [GUMP] Changes ahead...
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: Sam Ruby [mailto:[EMAIL PROTECTED]]
> > >
> > > Would something like the following suit your needs?
> > >
> > > build -r xml-cocoon2
> >
> > This would be OK (and possibly easier than what's below) but
> > Scott figured
> > out what I intended. Excellent example of telepathy in
> action! *GRIN*
> >
> > > -----Original Message-----
> > > From: Scott Sanders [mailto:[EMAIL PROTECTED]]
> >
> > > I think what John is trying to say is that his workspace
> > > looks like this:
> > >
> > > <workspace basedir="foo" cvsdir="bar">
> > > <project name="xml-cocoon2"/>
> > > </workspace>
> > >
> > > and then when Gump runs, it sees all the <depend/>s and
> > > can still resolve them.
> >
> > Yes! Just right! I realise that this is prob quite some time
> > (and effort)
> > away, but most people will just want to reference the
> > projects they are
> > interested in and expect the dependencies to take care of
> > themselves. What
> > do you think guys? is it possible/reasonable/desirable?
> >
> > John.
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > For additional commands, e-mail:
> > [EMAIL PROTECTED]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
=======================================================================
Information in this email and any attachments are confidential, and may
not be copied or used by anyone other than the addressee, nor disclosed
to any third party without our permission. There is no intention to
create any legally binding contract or other commitment through the use
of this email.
Experian Limited (registration number 653331).
Registered office: Talbot House, Talbot Street, Nottingham NG1 5HF
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
