Hi Maven is often put in a bad light because of bad metadata. So if the metadata could be improved Maven would be perceived as being better. With this in mind, I'd like to start work on a new component.
SCOPE At first it will be a command-line component that outputs text reports. Later on it might become a "fixing" component, but not from the start. JOB 1. Traverse a (configurable) repository from a given (configurable) starting point (I'm thinking groupId will do fine) 2. For each artifact available in the repository, report on mismatches between actual content (directories) in the repository and the metadata TOOLS A. Library to traverse a repository. Candidates: - Wagon - HttpClient B. Library to read and parse metadata.xml files. Later on we would also need to write metadata.xml files. Candidates: - Do we have code for this somewhere? I will put this up on the wiki in a bit. But first I wanted to get some feedback on the proposal as such, and also comments and suggestions on the choice of tools. -- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
