Scott:
>>> 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?
Sam:
>> 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?
>>
Scott:
> 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 :-(
Since we have yet to resolve this issue, I took your suggestion for the
adding explicit dependencies, but came across a problem.
gump/project/jakarta-ant.xml contains the jakarta-ant project, which
contains the <cvs> tag, but depends on bootstrap-ant. bootstrap-ant
implicitly depends upon the <cvs> in jakarta-ant, so when you add an
explicit <depend> during the merge, you get a circular dependency.
So now what do we do?
I have thought about this quite a bit and I still don't have any better
solution than the -cvs projects.
I can't think of other implicit dependencies, so why do we have them on
the <cvs> tag?
Any ideas?
Scott Sanders
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
