brett 2003/12/09 15:28:08 Modified: . Tag: MAVEN-1_0-BRANCH maven-refactor-notes.txt Log: clarify/update notes Revision Changes Path No revision No revision 1.1.4.3 +7 -4 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.2 retrieving revision 1.1.4.3 diff -u -r1.1.4.2 -r1.1.4.3 --- maven-refactor-notes.txt 2 Dec 2003 04:25:49 -0000 1.1.4.2 +++ maven-refactor-notes.txt 9 Dec 2003 23:28:08 -0000 1.1.4.3 @@ -1,15 +1,14 @@ High priority (before merge/RC2): 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 +- 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: - fail doesn't give line number -- goal names not being echoed - conflict between rootcontext.xmloutput and jellyoutputsink +- 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 Medium priority (before 1.0): @@ -20,13 +19,17 @@ - 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 low priority: - 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 +- goal not found should be a message, not an exception - 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 - 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?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
