I've been meaning to get around to that :) Thanks dIon, I'd appreciate it.
The most important ones are the ones from "Medium" onwards as they won't be
gotten to in the short term.

We should probably also add a task to "remove all usages of System.err/out",
which are currently listed in system_out_err.txt, as they should be using
the log infrastructure.

Cheers,
Brett

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, 2 December 2003 5:58 PM
> To: Maven Developers List
> Subject: Re: cvs commit: maven maven-refactor-notes.txt
> 
> 
> Sounds like these should be raised as issues in Jira....Let 
> me know if you 
> want me to do it.
> --
> dIon Gillard, Multitask Consulting
> Blog:      http://blogs.codehaus.org/people/dion/
> 
> 
> 
> [EMAIL PROTECTED] wrote on 02/12/2003 03:25:49 PM:
> 
> > brett       2003/12/01 20:25:49
> > 
> >   Modified:    .        Tag: MAVEN-1_0-BRANCH 
> maven-refactor-notes.txt
> >   Log:
> >   update notes
> > 
> >   Revision  Changes    Path
> >   No                   revision
> >   No                   revision
> >   1.1.4.2   +12 -6     maven/Attic/maven-refactor-notes.txt
> > 
> >   Index: maven-refactor-notes.txt
> >   
> ===================================================================
> >   RCS file: /home/cvs/maven/Attic/maven-refactor-notes.txt,v
> >   retrieving revision 1.1.4.1
> >   retrieving revision 1.1.4.2
> >   diff -u -r1.1.4.1 -r1.1.4.2
> >   --- maven-refactor-notes.txt   26 Nov 2003 11:45:15 -0000 
>   1.1.4.1
> >   +++ maven-refactor-notes.txt   2 Dec 2003 04:25:49 -0000   1.1.4.2
> >   @@ -1,23 +1,29 @@
> >    High priority (before merge/RC2):
> > 
> >   -- fail doesn't give line number
> > 
> >   -- goal names not being echoed - conflict between
> rootcontext.xmloutput 
> > and jellyoutputsink
> > 
> >   -- no project is busted - NPE Project:1438 (verifyDeps), 
> have also 
> > set
> 
> > file to a fake
> > 
> >   +contexts:
> > 
> >   +- sourcesPresent appears in wrong context, or clean goal is not 
> > found
> 
> > (depending on what is used as the base context for a plugin)
> > 
> >    - site generation fails - it calls touchstone as part of 
> test:test
> which 
> > doesn't work in this context, and ends site
> > 
> >    - maven xdoc doesn't seem to work
> > 
> >   +
> > 
> >   +classloaders:
> > 
> >    - checkstyle give incompatibleclasschangeerror due to
> > beanutils/collections loaded into root, or exceptions with 
> commons-logging 
> > (differing version)
> > 
> >   -- touchstone is failing again in goal-B after clean up. 
> I may have
> > removed something I had working yesterday - will look into it.
> > 
> >   +
> > 
> >   +other:
> > 
> >   +- fail doesn't give line number
> > 
> >   +- goal names not being echoed - conflict between
> rootcontext.xmloutput 
> > and jellyoutputsink
> > 
> >   +- no project is busted - NPE Project:1438 (verifyDeps), 
> have also 
> > set
> 
> > file to a fake
> > 
> > 
> > 
> >    Medium priority (before 1.0):
> > 
> >    - set source for plugins
> > 
> >    - test parent properties
> (src/test/touchstone-build/src/reactor-build/inheritence)
> > 
> >    - need to cut back to just loading those plugins 
> desired, not all 
> > of
> them.
> > 
> >    - bug when antlr loaded still? Was last time I tried.
> > 
> >   -- how many jelly taglibs in basedir, how many per project?  Clean
> this up
> > 
> >   -- Remove root.maven?
> > 
> >    - cleanup dyna taglibs that are cros references with missing 
> > plugins
> > 
> >   +- Remove root.maven?
> > 
> >   +- properties loading from Maven.java might be worth integrating
> properly
> > 
> > 
> > 
> >    low priority:
> > 
> >    - move touchstone for non-core plugins out
> > 
> >   +- how many jelly taglibs in basedir, how many per project?  Clean
> this up
> > 
> >    - touchstone reactor clean does nothing - make it work, or remove
> > 
> >    - touchstone reactor standard fails because of error in 
> test - make
> it 
> > work or remove
> > 
> >    - touchstone reactor legacy(-fugly) fails because of 
> error in test 
> > -
> make
> > it work or remove
> > 
> > 
> > 
> > 
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

Reply via email to