brett 2003/12/10 15:10:38 Modified: . Tag: MAVEN-1_0-BRANCH maven-refactor-notes.txt Log: update notes Revision Changes Path No revision No revision 1.1.4.4 +12 -14 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.3 retrieving revision 1.1.4.4 diff -u -r1.1.4.3 -r1.1.4.4 --- maven-refactor-notes.txt 9 Dec 2003 23:28:08 -0000 1.1.4.3 +++ maven-refactor-notes.txt 10 Dec 2003 23:10:38 -0000 1.1.4.4 @@ -1,27 +1,23 @@ High priority (before merge/RC2): contexts: -- maven.xml/driver gets loaded and run twice. Removing runJelly fixes it but exposes 2 problems: 1) failure in touchstone at goal-A (overriding not always correct), 2) failure in touchstone at test-mavenjellyscope -- maven site generates wrong thing (touchstone instead of main) - seems reactor doesn't pop context. - -classloaders: -- checkstyle give incompatibleclasschangeerror due to beanutils/collections loaded into root, or exceptions with commons-logging (differing version) - -other: +- maven site generates wrong thing (touchstone instead of main) - seems xdoc plugin has its context/pom reference scrogged somehow - fail doesn't give line number - goal names not being echoed - conflict between rootcontext.xmloutput and jellyoutputsink. They actually get echoed but appear to be buffered and only displayed (and then out of sequence) inside a long reactor build (eg maven:plugins-build) -- no project is busted - NPE Project:1438 (verifyDeps), have also set file to a fake +- NPE building simian as it depends on clover which is not yet installed +- announcement plugin gives classnotfoundexception: xml +- cruisecontrol, html2xdoc plugin causes failure - already fixed? +- checkstyle plugin causes failure, incompatibleclasschangeerror - already fixed? +- startup time has doubled (+10 seconds) - reintroduce caching to improve this + * need to cut back to just loading those plugins desired, not all of them. 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. -- cleanup dyna taglibs that are cros references with missing plugins -- Remove root.maven? -- properties loading from Maven.java might be worth integrating properly -- goal not found should be shown before any are attained +- cleanup dyna taglibs that are cross references with missing plugins low priority: +- what is the tasks.properties warning? +- xmlns, when valid, spits an error (jdeveloper) - move touchstone for non-core plugins out - reactor should not show exception if -e not given - how many jelly taglibs in basedir, how many per project? Clean this up @@ -32,4 +28,6 @@ - should plugin releases really be made via maven:release, ala RC1? It doesn't do standard tagging/announce/changes.xml update, etc right now. Perhaps manually release all snapshots before building bundled RC2, or use old versions in bundle. - plugin:test goal should be able to execute test project - is rootrelativepathtag used? +- Remove root.maven? root? +- goal not found should be shown before any are attained
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
