Jeff Martin wrote:
>
> I've not got things to the project point to defnitions rather
> than being owned by them. And all projects and repositories
> are now imports from external files. The thing that was going
> through my head was how to link the two together currently
> Tinderbox puts this link within each project definition. I've
> come to the conclusion that it should be part of the workspace
> definition along with things like revision number etc.
>
> This would then make it possible to do things like changing
> your local workspace to point to your sandbox version of code
> and run build and intergration tests on before submitting
> changes back in the main body of code, without having to
> change the project definition, just which repository
> the code should be build from.
My original thoughts (yet unimplemented) was to allow overrides in the
workspace defintion . Note that at the moment the relation of projects to
repositories in tinderbox is many to one, so I was envisioning putting this
information on the <project href="..."> element in the workspace
definition.
In other words, the definition of project cocoon2 contains the name of the
branch xml-cocoon2. A project element which referenced definition in the
workspace could choose to accept this tag or override it.
Even longer term, I was thinking the project definition could contain a
list of tags which a GUI front end to this function could allow the user to
select from.
Just some random thoughts.
- Sam Ruby
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
