On 27 July 2012 08:33, <simonetrip...@apache.org> wrote: > Author: simonetripodi > Date: Fri Jul 27 07:33:14 2012 > New Revision: 1366299 > > URL: http://svn.apache.org/viewvc?rev=1366299&view=rev > Log: > reorganized issues to follow the DESC order
> Modified: > commons/proper/functor/trunk/src/changes/changes.xml > > Modified: commons/proper/functor/trunk/src/changes/changes.xml > URL: > http://svn.apache.org/viewvc/commons/proper/functor/trunk/src/changes/changes.xml?rev=1366299&r1=1366298&r2=1366299&view=diff > ============================================================================== > --- commons/proper/functor/trunk/src/changes/changes.xml (original) > +++ commons/proper/functor/trunk/src/changes/changes.xml Fri Jul 27 07:33:14 > 2012 > @@ -26,9 +26,6 @@ > <action dev="kinow" issue="FUNCTOR-22"> > Generify ComparableComparator. > </action> > - <action dev="kinow" issue="FUNCTOR-3"> > - Reduce the use of raw types in test classes. > - </action> > <action dev="kinow" issue="FUNCTOR-21"> > Fix NPE in UnarySequence. > </action> > @@ -62,6 +59,9 @@ > <action dev="simonetripodi" issue="FUNCTOR-4" due-to="Bruno P. > Kinoshita"> > Add easily accessible, user-friendly examples > </action> > + <action dev="kinow" issue="FUNCTOR-3"> > + Reduce the use of raw types in test classes. > + </action> By the way, having the issue attribute first makes the order very clear in Eclipse overviews as it displays the first attribute. For example: <action issue="FUNCTOR-3" dev="kinow"> Also, the issue type should really be specified - the <action> type attribute can be add,update,fix,remove. > <action dev="simonetripodi" issue="FUNCTOR-2" due-to="Bruno P. > Kinoshita"> > Improve Functor web page, removing Ant from building > </action> > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
