You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Eric Barboni <sk...@apache.org> on 2013/06/01 19:10:25 UTC
RE: CALL TO CONTRIBUTION: dist tooling
I need some feedback on informations to display. I propose my (limited)
vision.
mvn clean install site
http://svn.apache.org/repos/asf/maven/sandbox/trunk/dist-tools
database of artifacts to check is not complete, loosely based
on artifacts plugins from
http://svn.apache.org/repos/asf/maven/plugins/trunk/
on artifacts on https://dist.apache.org/repos/dist/release/maven/
two html reports are generated
check for source-release is done by brute html parsing.
-- display missing files
check for website is done by maven (to resolve pom url) (take some times)
-- display error status, display if version is present on site (ie try to
find Version 3.3 in the index.html of plugin site)
lots of log still present (colored in my ide but no readable on prompt)
Regards
Eric
PS:
Is it ok to keep discussion on mailing list, or it is better to open an
issue on jira ?
-----Message d'origine-----
De : Eric Barboni [mailto:Eric.Barboni@irit.fr]
Envoyé : mercredi 29 mai 2013 11:35
À : 'Maven Developers List'
Objet : RE: CALL TO CONTRIBUTION: dist tooling
It finally works(svn client issue reinstalling older tortoiseSVN)
http://svn.apache.org/r1487396
sorry for stress...
-----Message d'origine-----
De : Olivier Lamy [mailto:olamy@apache.org]
Envoyé : mercredi 29 mai 2013 10:09
À : Maven Developers List
Objet : Re: CALL TO CONTRIBUTION: dist tooling
weird.
what is the error message ? and svn url you are using ?
2013/5/29 Eric Barboni <sk...@apache.org>:
> 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:herve.boutemy@free.fr] 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:herve.boutemy@free.fr] 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_Are
>> a
>>
>> [3]
>> http://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-
>> >
>> reporting-exec/maven-metadata.xml
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: CALL TO CONTRIBUTION: dist tooling
Posted by Hervé BOUTEMY <he...@free.fr>.
pfew, really nice!
It would be nice if reports started by an explanation of points checked: that
would ease understanding the content following, because dist-tool-checkstyle
report in particular is hard to understand ("check summary", "Stylus Skin"?,
"Fluido Skin"?)
But it is really a wonderful result I'm ready to work with (and to work on
improvements)
regards,
Hervé
Le samedi 1 juin 2013 19:10:25 Eric Barboni a écrit :
> I need some feedback on informations to display. I propose my (limited)
> vision.
>
> mvn clean install site
> http://svn.apache.org/repos/asf/maven/sandbox/trunk/dist-tools
>
> database of artifacts to check is not complete, loosely based
> on artifacts plugins from
> http://svn.apache.org/repos/asf/maven/plugins/trunk/
> on artifacts on https://dist.apache.org/repos/dist/release/maven/
>
> two html reports are generated
> check for source-release is done by brute html parsing.
> -- display missing files
> check for website is done by maven (to resolve pom url) (take some times)
> -- display error status, display if version is present on site (ie try to
> find Version 3.3 in the index.html of plugin site)
>
> lots of log still present (colored in my ide but no readable on prompt)
>
> Regards
> Eric
>
>
> PS:
> Is it ok to keep discussion on mailing list, or it is better to open an
> issue on jira ?
>
> -----Message d'origine-----
> De : Eric Barboni [mailto:Eric.Barboni@irit.fr]
> Envoyé : mercredi 29 mai 2013 11:35
> À : 'Maven Developers List'
> Objet : RE: CALL TO CONTRIBUTION: dist tooling
>
>
> It finally works(svn client issue reinstalling older tortoiseSVN)
> http://svn.apache.org/r1487396
>
> sorry for stress...
>
> -----Message d'origine-----
> De : Olivier Lamy [mailto:olamy@apache.org]
> Envoyé : mercredi 29 mai 2013 10:09
> À : Maven Developers List
> Objet : Re: CALL TO CONTRIBUTION: dist tooling
>
> weird.
> what is the error message ? and svn url you are using ?
>
> 2013/5/29 Eric Barboni <sk...@apache.org>:
> > 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:herve.boutemy@free.fr] 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:herve.boutemy@free.fr] 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_Are
> >> a
> >>
> >> [3]
> >> http://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-> >>
> >> reporting-exec/maven-metadata.xml
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> >> additional commands, e-mail: dev-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> > additional commands, e-mail: dev-help@maven.apache.org
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> > additional commands, e-mail: dev-help@maven.apache.org
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
> commands, e-mail: dev-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org