Jason van Zyl wrote: > Fabrizio Giustina wrote: >> Some time ago I started a simple plugin for m2 which converts maven 1 >> project.xml to pom.xml (pom conversion + few basic plugin >> configuration from project.properties to pom.xml). This allows an easy >> conversion of maven 1 projects, for users willing to migrate to m2. >> The initial code is available at http://jira.codehaus.org/browse/MNG-1530 >> >> I would like to add this plugin to svn + refactoring the pom converter >> to a separate artifact, which can be shared between the plugin and >> repository tools (see http://jira.codehaus.org/browse/MRM-29 ) >> >> Please vote the following: >> [ ] add the new plugin > > +1
+1 (to add it to the sandbox doesn't require a vote, but I'm happy for this to go straight to /plugins/trunk). > >> [ ] add a new module with the pom converter > > +1 > > We need all the help we can with the conversion stuff. Sounds good. I actually had this on my list already. Doing it now. Doesn't need a vote, I think. On that token, please don't upload anything directly to java-repository. I have no idea where that code came from - I can only assume from maven-model-2.0-all and trimmed? Where did the pom come from? Officially, only PMC members can endorse a release through their votes when the entire community brings it up. It's not something we can "just do" as that hits the mirrors. Since this is a derivative of an existing voted on release, I think it is ok - but discussing on this list in future would be a better idea. If you don't get a response, be persistent - most likely someone has flagged it and not got around to it :) > >> ... about the pom converter stuff (if we decide to add it) we should >> also decide where to put it. If outside the plugin dir, I will need a >> "sponsor" who can do that, since I only have access to the svn plugins >> area. I think it should be part of the tools stuff we discussed. Since it isn't set up yet, I'll keep it in components. > > It would be nice if you made it a tool that would be used inside a mojo. > As most of our tools are plexus components I think doing the same would > make sense. Plexus components are easy to reuse inside Mojos and are > also resuable in other tools which are usually Plexus-based in our case. > > We might want to start collecting our repo management code here: > > http://svn.apache.org/viewcvs.cgi/maven/repository-manager/ This isn't repo management, so I'll keep it in components. > > And move the maven-repository-tools in there as well. Yep, eventually. > > If you have time and code to contribute I would be +1 for giving you > access the the repository-manager module. Likewise. I'll be starting some discussion soon. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
