On Fri, 15 Feb 2002 07:30, [EMAIL PROTECTED] wrote:
> Pete,
>
> I'm sorry if I've broken backwards compatibility, and I'll do what I can to
> fix it. -But the URL refactoring was necessary in order to
> be able to load templates from within a different jar than XDoclet's own.

but it could have been done by adding a new attribute (ie url="") or via some 
other backwards compatabile way :)

> If you send me some stack traces of your failing builds, and a more
> detailed description about what fails, I'll fix it ASAP.

http://jakarta.apache.org/builds/gump/latest/jakarta-ant-myrmidon.html

shows a trace of it. 

BTW xdoclet is being built 4 times a day via the GUMP build manager (see 
jakarta.apache.org/gump for description). Basically it builds against the 
latest and greatest from all the different CVS projects that are relied upon. 
For instance xdoclet relies upon jrefactory, webwork, openjmx etc. So the 
latest version of each of these are sucked down from CVS built and then used 
to build xdoclet to see if anything breaks.

It is useful as a daily build tool but it is also useful in that it gives you 
early warning when one of your dependent projects changes in a way that 
breaks you. So if webwork changes something that breaks your build you get 
warning and can go annoy the webwork people till they make it backwards 
compatible - much like I am doing here ;) Alternatively you can update your 
own project to make it compatible with latest webwork.

If you want I can set it up so that you will receive messages when the 
xdoclet project fails to build for whatever reason. Interested ?

-- 
Cheers,

Pete

--------------------------------------------------
 Where ignorance is bliss, 'tis folly to be wise.
--------------------------------------------------

_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel

Reply via email to