Sorry, but Maven sandbox is write protected for me. I created a svn patch file but I don't know where to fill the issue (project, component in jira).
Regards, Eric -----Message d'origine----- De : Hervé BOUTEMY [mailto:[email protected]] Envoyé : mardi 28 mai 2013 22:44 À : Maven Developers List Objet : Re: CALL TO CONTRIBUTION: dist tooling great! thanks for your help yes, a maven plugin can be a solution, even if report is overkill IMHO: we won't publish result Maven sandbox [1] should be writeable to any Apache committer, IIUC Regards, Hervé [1] https://svn.apache.org/repos/asf/maven/sandbox/trunk/ Le mardi 28 mai 2013 17:54:31 Eric Barboni a écrit : > Hi, > > If still open, I'm interested to help on this part. > > Can it be a maven plugin with html report (A bit overkill maybe but scripts > on windows are annoying) ? > > Where should the tool be located in the scm tree (to facilitate patch > creation) ? > > Regards, > > Eric > > -----Message d'origine----- > De : Hervé BOUTEMY [mailto:[email protected]] Envoyé : mercredi 24 > avril 2013 13:23 À : Maven Developers List Objet : CALL TO > CONTRIBUTION: dist tooling > > I just did some checks in our distribution area [1] and found a good > number of missing releases In addition to asking committers to > remember our procedure [2] (and ask for PMC help if necessary) , I > just thought it would be good to have a little tool to check against latest artifact releases: > with a little config file giving groupId:artifactId and directory in > dist, it could check if latest version from central metadata [3] is > actually published in dist and warn if not. > > This is a first step, since a lot more help can be added later, I have > a good number of ideas (download the new release, propose svn commands > to remove old releases and add new ones, check consistency with site, > ...) > > But I don't want to code it right now and prefer concentrate working > on > maven- site-plugin, dependency:tree and so on related le future Maven > version. > > I thought this could be a good opportunity for someone to do somthing > without having to learn too much on existing code. > > Is there anybody interested? > > Regards, > > Hervé > > > [1] https://dist.apache.org/repos/dist/release/maven/ > > [2] http://maven.apache.org/developers/release/maven-project-release-> > procedure.html#Copy_the_source_release_to_the_Apache_Distribution_Area > > [3] > http://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-> > reporting-exec/maven-metadata.xml > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] For > additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
