antoine 2004/03/26 09:13:38 Modified: blog/SuccessStories jrefactory.txt Log: try to improve formatting Revision Changes Path 1.3 +10 -9 gump/blog/SuccessStories/jrefactory.txt Index: jrefactory.txt =================================================================== RCS file: /home/cvs/gump/blog/SuccessStories/jrefactory.txt,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- jrefactory.txt 26 Mar 2004 17:02:55 -0000 1.2 +++ jrefactory.txt 26 Mar 2004 17:13:38 -0000 1.3 @@ -29,28 +29,29 @@ <more/> As a consequence, the acceptable values for the lineending setting of PrettyPrinter changed to become the one's of ant's fixcrlf task. - +<br> This caused the build of xdoclet to fail around mid January. - +<br> I entered a bug report in the bug tracking system of JRefactory, and also asked the xdoclet team to adapt their build file to the new behavior of PrettyPrinter, which they did. <a href="http://sourceforge.net/tracker/index.php?func=detail&aid=877400&group_id=13219&atid=113219";> pretty.settings end.line property comments need a fix</a> - +<br> Mike Atkinson seems to have worked on this issue yesterday (March 25th 2004). - -<h1> +<br> +<h3> jaxen/saxpath changes -</h1> +</h3> Due to changes in jaxen, which has absorbed saxpath, JRefactory had a compilation failure. - +<br> I sent a mail to the JRefactory mailing list on the 24th of March, and Mike Atkinson fixed the faulty org.acm.seguin.pmd.jaxen.DocumentNavigator yesterday (March 25th). - +<br> So, yes, human nagging is effective. When it is effective, and how you do -it diplomatically is another issue. \ No newline at end of file +it diplomatically is another issue. +<br>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
