Besides, are they separate modules or not? XDoclet depends on commons-logging/log4j too, yet no-one's suggested we should remove those jars from xdoclet/lib. If xjavadoc's a separate component, should it be handled any differently just because we also maintain it? Else, if xdoclet & xjavadoc are so tightly tied together, they might as well just be in a single source tree instead.
How do things stand with migrating the build process to Maven? And will that improve things any in this respect, or are we going to have similar issues with having to update xjavadoc.jar in the maven repository every time something changes in it?
Andrew.
+1
But make sure the build process still works.
Mathias
----- Original Message -----
From: "Aslak Hellesøy" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 23, 2002 4:08 PM
Subject: [Xdoclet-devel] xjavadoc.jar
> Any objections if I remove it from CVS?
>
> I just updated 2 lines in the grammar. -Now I have to commit the >whole
> binary too. -And I couldn't, because I had forgotten to update
xjavadoc.jar
> from CVS myself. I totally agree with David that it's bad scm >practice to
> keep it in CVS.
>
> Aslak
_________________________________________________________________
Get a speedy connection with MSN Broadband. Join now! http://resourcecenter.msn.com/access/plans/freeactivation.asp
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
