> I'll try not to break AntGump, but if I do...you have been warned!  ;-)

Completly understood.


>> PS.  I have made some changes to the projects (content, not structure)
>> that force the dependency upon the <cvs/> tag.  An example is in
>> xml-stylebook.  I created an xml-stylebook-cvs project, which
>> xml-stylebook and xml-stylebook2 depend explicitly. Would you guys like
>> to see the patch for all of this, ar can I just commit it?
> 
> 
> I'd rather not have "-cvs" projects.  Since you didn't seem to have
> problems with xml-xalan2 in the past, would your problems go away if the
> build instructions for xml-stylebook1 were moved into a nested project?  If
> not, I could add code in merge.xsl to add an implicit dependency on parent
> projects.  Would that be sufficient?
> 

The problem that I have is that I use sortdep.xsl jsut as you do, but 
since I do the cvs step 'ad-hoc' as needed, and not all before, the 
dependency sorting is not enough right now...  When I run AntGump, I get 
errors because various cvs repos are not there yet.

I did have problems with xml-xalan2 in the past, but since it was just 
that one I would move the <cvs/> tag inside the xml-xalan2 project. 
Since it reared its ugly head on stylebook, I decided to try and change 
the projects to work for both of us.

The major problem I have is that the dependency of xml-xalan2 upon the 
<cvs/> tag in a parent project is a structure based dependecy 
(implicit), not an explicit one.  I think that this a bad, IMHO.  My 
'quick-fix' to the problem was to create the '-cvs' inner projects that 
the others depended on explicitly.  Are you saying that you want to stay 
on the implicit dependency road?  I am not so great about that, but I 
will do that if necessary.  The problem that I have with it is that 
<cvs/> tags are treated differently that say <ant/> tags, or any other 
tags for that matter.

I'll leave it to you, but I would say that anything implicit based upon 
structure is bad :-(

Scott Sanders


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to