How about if we have a
<import href="http://url-to-sams-gump-projects-list" build-all="false" />
allowing
<project name="my-project>
<depend name="junit"/>
</project>
imported projects would be available for use as dependencies from other
projects. But when build-all is false then they are only built if they are
needed by projects in the declared in the workspace.
-----Original Message-----
From: Jeff Martin [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 11, 2001 11:23 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [GUMP] Changes ahead...
Doesn't that only work if the dependencies are within the same repository?
Or do you see all the repositories still being declared in the workspace?
> -----Original Message-----
> From: Sam Ruby [mailto:[EMAIL PROTECTED]]
> Sent: 11 April 2001 16:06
> To: [EMAIL PROTECTED]
> Subject: RE: [GUMP] Changes ahead...
>
>
> Jeff Martin wrote:
> >
> > Yup, but the workspace def define where to find the project defs for
> > jakarta-ant, xml-xerces, xml-xalan2 etc.
>
> Hmmm. One way to resolve this is to come full circle. Have the
> respositories define what projects they contain. Have the workspace
> reference the projects they want from these repositories.
>
> - Sam Ruby
>
>
> ---------------------------------------------------------------------
> 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
