Jeff Martin wrote:
>
> Was actually wondering if it would be possible to keep the definitions in
> each projects cvs module. This would make it easier for people to keep
them
> uptodate. Maybe give each project a META-DATA dir to place there project
> definition in.
My original hope was that some definitional provisions could be included to
Ant's DTD (I use the term loosely as Ant is extensible, but you know what I
mean) which would enable the definition of inputs, outputs, and the like.
The rest could be handled by adopting conventions (like what the default
target would be).
A few things to consider (not all fatal):
- Some things can't be put into the project - such as the information as
to where to find the project in the first place! Some more refactoring
would be required to make this happen.
- The gen process currently makes use of much of this data prior to
update. This could be rearranged. The problem is somewhat worse in the
current version of AntGump.
- Some changes (like Avalon no longer bundling logkit) require global
changes. This is easier to coordinate if the project definitions are
together. (Note: this is the exception rather than the rule: most
changes are localized, and those changes would be easier to coordinate
if the definitions were distributed).
- Not everybody will annotate their build definitions (e.g., rhino?), so
some definitions will still need to be added external to the repository.
- Sam Ruby
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
