[MNG-309] more repoclean enhancements

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0-alpha-2
• Assignee: John Dennis Casey
• Reporter: Brett Porter
• Created: 13/Apr/05 19:39
• Updated: 01/Feb/06 14:42
• Resolved: 25/Apr/05 21:41

Description

we should gather up all the repoclean enhcancements and rerun it with a --force option to reconvert all the m1 poms again.

So, further enhancements:
[DONE] - a --force option
[DONE] - successfuly convert <properties><scope>foo</scope></properties> on a dependency so m1 users can add it to their pom
[DONE] - convert deps with <type>plugin</type> to a plugin element
[DONE] - automatically comment out Sun JARs and warn

• turn on mailing of errors/warnings

Add more as subtasks of this if they are found

Issue Links

• is related to: MNG-328 figure out why commons-logging-1.0.4 won't convert via the repoclean process
• relates to: MNG-252 allow repoclean converter to read from a repository containing both v3 and v4 poms, and convert each correctly

Sub-Tasks

• md5 files created by repoclean are binary, not hex: Closed
• add test artifacts to repository: Closed
• handle "+" is groupIds/artifactIds: Closed
• add real CLI parser to enable --force, etc.: Closed
• Do something about interpolated values in dependencies: Closed
• put all the scripts in CVS: Closed
• when packaging = pom, the repository should store it in the groupID directory: Closed
• verify/add checksum files for poms, too: Closed
• graph dependencies found vs. needed on convert, report missing: Closed
• add/test support for processing of maven2 repositories: Closed