JRefactory adapts their code to changes in jaxen/saxpath
<!--
 Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  See the NOTICE file distributed with
  this work for additional information regarding copyright ownership.
  The ASF licenses this file to You under the Apache License, Version 2.0
  (the "License"); you may not use this file except in compliance with
  the License.  You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.
-->

<h3>
issue of line ending with PrettyPrinter task
</h3>
<p>
Antoine L&eacute;vy-Lambert  had found a problem with the PrettyPrinter task supplied by 
<a href="http://jrefactory.sourceforge.net/">JRefactory</a>.
Without any clear announcement, the JRefactory team had changed their 
<a href="http://jrefactory.sourceforge.net/Main_components_prettyprint.html">PrettyPrinter
task</a> to delegate processing of line endings to the ant fixcrlf task - which is good.
<more/>
As a consequence, the acceptable values for the lineending setting of PrettyPrinter
changed to become the one's of ant's fixcrlf task.
</p><p>
This caused the build of xdoclet to fail around mid January.
</p><p>
Antoine 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>
</p><p>
Mike Atkinson seems to have worked on this issue yesterday (March 25th 2004).
</p>
<h3>
jaxen/saxpath changes
</h3>
<p>
Due to changes in jaxen, which has absorbed saxpath, JRefactory had
a compilation failure.
</p><p>
Antoine 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).
</p><p>
So, yes, human nagging is effective. When it is effective, and how you do 
it diplomatically is another issue.
</p>