-----Original Message-----
From: John Morrison [mailto:[EMAIL PROTECTED]]
>That would be OK for most systems, but I *need* to automate the build
>process at work. It doesn't have a http connection. I managed to get cvs
>opened on all development machines, but http requires username/passwords
:-(
Let the import href allow "cvs:CVSROOT:/module/file " or some other syntax.
>Also, how would people add their own projects?
People would add their own projects to their local workspace definition.
I suppose that we could go full circle and have each repository have its own
list of projects. Then we could have
<build-list>
<repository href="http://jakarta.apache.org/gump-workspace.xml"/>
<repository href="http://oss.ibm.com/alphaworks-workspace.xml" />
<repository href="/local/dir/my-workspace" />
<project name="alexandira" rebuild="weekly"/>
<project name="myproject" rebuild="nightly" />
</build-list>
<workplace name="mine" >
<repository name="mine" >
<cvsroot ...
/>
</repository>
<import href="http://jakarta.apache.org/gump-workspace.xml" />
<project name="myroject" repository="name">
<depends name="JTOpen"/>
<depends name="cactus"/>
</project>
</workplace>
This implies that a workspace contains a list of project that can be built
and there dependencies.
The build-list is what is actually built, and how often.
I realize that workplace will have circular dependencies.
That way we don't have just one Master Workplace instead many codependent
workplaces.
R,
Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
