Greetings,

On Fri, May 31, 2013 at 1:34 AM, Hervé BOUTEMY <herve.bout...@free.fr> wrote:
> I don't know what you mean by "send pull requests to Jenkins", if you're
> talking about Apache's Jenkins instance or something more general from the
> Jenkins project

There is something called the backend-crawler which locates common
tools that can be auto-installed by the Jenkins service itself. All
Jenkins instances will load a JSON file, similar to the way it knows
which plugins can be auto-installed. I meant we should perhaps send a
pull request here:

https://github.com/jenkinsci/backend-crawler/blob/master/ant_maven.groovy

More information here:

https://wiki.jenkins-ci.org/display/JENKINS/Adding+tool+auto-installer
https://wiki.jenkins-ci.org/display/JENKINS/Tool+Auto-Installation

> but I'm interested by the "it would be auto-installable" objective at least on
> Apache's Jenkins instance

Yep, that or someone with karma can just manually install it and
enable it as the default builder? That way it won't break any builds
which require a specific Apache Maven. But the auto-installable route
would enable more places to just quickly enable it.. I'm not sure if
Jenkins folks would be receptive to having an Apache Maven pre-release
kind of thing showing up in their tool list, but off the top of my
head I can not find a reasonable objection.

-Jesse

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to