Hi users, For several days now I tried to clean up a little bit issues recorded in Jira. For the next version of the plugin we have already the following issues solved (you can try the SNAPSHOT deployed on http://people.apache.org/repo/m2-snapshot-repository/) : ** Bug * [MECLIPSE-160] - Wrong description with the goal "add-maven-repo" documentation * [MECLIPSE-172] - Don't add Default ClasspathContainer if a alternate JRE or a "Execution Environment" is configured as ClasspathContainer. * [MECLIPSE-291] - tests fail with spaces in the path name * [MECLIPSE-296] - Wrong generated source-path when warSourceDirectory is set * [MECLIPSE-297] - eclipse:clean deletes files from pom projects * [MECLIPSE-301] - eclipse:clean doesn't respect packaging 'pom' * [MECLIPSE-305] - souce-path is absolute versus relative with WAR * [MECLIPSE-315] - RadWebSettingsWriter uses hardcoded webcontent path and ignores warSourceDirectory * [MECLIPSE-342] - Found an equals call to check unrelated types * [MECLIPSE-346] - Transitive dependencies aren't used to resolve JEE/JSP/EJB/Servlet versions * [MECLIPSE-352] - RAD application.xml is not generated with good parameters ** Improvement * [MECLIPSE-163] - eclipe:eclipse 2.3-SNAPSHOT with wtp-1.5 fixes * [MECLIPSE-213] - more jee support for wtp * [MECLIPSE-264] - Support for WTP2.0 * [MECLIPSE-281] - Documentation patch for PDE support * [MECLIPSE-292] - Behaviour for sources and Javadoc attachement for dependencies should be consistent * [MECLIPSE-331] - Allow to use a packaging model to override the packaging defined in the pom * [MECLIPSE-333] - WTP-2.0 support with howto apt, refactoring and contextroot handling ** New Feature * [MECLIPSE-127] - Ability to add other workspace configuration similar to add-maven-repo goal ** Wish * [MECLIPSE-308] - Change the method of verifying whether JRE is included in "classpathContainers"
BUT there are always 163 outstanding issues :-( http://jira.codehaus.org/browse/MECLIPSE Few of them have a patch , and when there's one, it's often without a test case. A test case isn't necessarily a real running test case for the plugin, but just a part of a POM, some notes about how to reproduce the problem, ... It's actually very difficult to maintain this plugin due to number of issues. It could help us a lot if reporters could check if their issues are always valid with the current version of the plugin and if there's not another related/duplicated issue reported. Also if you are using some specific features (PDE, WTP, ...) or eclipse versions (RAD) you can help us by letting us know if you encounter issues reported in Jira. You can vote for them, and add explanations about how to reporduce them. It'll ease the fix. Thanks a lot. .......................................................... Arnaud HERITIER .......................................................... OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .......................................................... ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ...........................................................
