Hi Manfred, With my Maven committer hat I would prefer to restrict the default choices to the latest stable releases we have.
With my Jenkins committer hat I see this as an enhancement request. Jenkins should allow for each product to limit/classify the proposed version. For sure the rule won't be the same for Maven, Gradle, Ant and the list for each product will evolve. For sure I cannot for now remove older versions to add the most recent because it will be considered as a bug/regression for current users who are using it to automatically install an old Maven version (the catalog is used by all instances, its not something integrated/hardcoded in jenkins). It is exactly the problem that groovy has today with the shutdown of codehaus ( https://issues.jenkins-ci.org/browse/INFRA-310) On Fri, May 22, 2015 at 1:06 AM, Manfred Moser <[email protected]> wrote: > Hm ... isnt the fact that Maven 2.x is deprecated reason enough to NOT > offer it in Jenkins. From my memory 2.0.8 and 2.0.9 had some severe > problems and only 2.0.10 sort of fixed things. > > Personally I would think that you should restrict the list in Jenkins even > excluding 2.x altogether. Or maybe just having 2.2.1 only. > > And if someone really needs it they can always install whatever version > (and pain) they choose via the tar.gz/zip archive method based off a > different server. > > Manfred > > Arnaud Héritier wrote on 21.05.2015 15:21: > > > Jason, > > > > It don't find binaries of < 2.0.9 in central. Did I miss something ? > > > > I would like (for jenkins) to not remove old releases from the catalog > > without a real reason ... > > > > Arnaud > > > > On Fri, May 22, 2015 at 12:04 AM, Jason van Zyl <[email protected]> wrote: > > > >> Why don't you just use Maven Central. Those copies are not going > anywhere. > >> > >> On May 21, 2015, at 6:02 PM, Arnaud Héritier <[email protected]> > wrote: > >> > >> > Resurrecting this thread. > >> > Having a standardised place to find all versions was a good thing > >> > Because of the change jenkins doesn't propose anything > 3.2.2 > because it > >> > is checking only in http://archive.apache.org/dist/maven/binaries/ > >> > And it doesn't see the content of https://dist.apache.org/repos/dist > >> > /release/maven/maven-3/ > >> > Sadly no central isn't a better solution > >> > * >= 2.0.9 : > >> > http://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/ > >> > * < 2.0.9 : not available in central AFAIK (yes they are old but ..) > >> > > >> > Before fixing the Jenkins Catalog ( > >> > https://issues.jenkins-ci.org/browse/INFRA-181) I would need to have > our > >> > feedback to have a long term solution if possible > >> > > >> > Cheers > >> > > >> > > >> > On Mon, Dec 29, 2014 at 8:48 AM, Jason van Zyl <[email protected]> > wrote: > >> > > >> >> Why do you need it there? > >> >> > >> >> The way binaries are kept at Apache is inconsistent. How it evolved > over > >> >> time where things disappear from one place to another (official > >> >> distribution to archives) I don't find makes much sense but that's > the > >> way > >> >> it is. If you require a distribution in a standard place take it from > >> Maven > >> >> Central. It will always be in the same place. > >> >> > >> >> On Dec 29, 2014, at 12:51 AM, Milos Kleint <[email protected]> > wrote: > >> >> > >> >>> Hello, > >> >>> > >> >>> for some reason 3.2.3 is not available in the archives, is that > >> >> intentional > >> >>> or something went wrong with the 3.2.5 release? > >> >>> > >> >>> Thanks > >> >>> > >> >>> Milos > >> >> > >> >> Thanks, > >> >> > >> >> Jason > >> >> > >> >> ---------------------------------------------------------- > >> >> Jason van Zyl > >> >> Founder, Apache Maven > >> >> http://twitter.com/jvanzyl > >> >> http://twitter.com/takari_io > >> >> --------------------------------------------------------- > >> >> > >> >> What matters is not ideas, but the people who have them. Good people > can > >> >> fix bad ideas, but good ideas can't save bad people. > >> >> > >> >> -- Paul Graham > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> > > >> > > >> > -- > >> > ----- > >> > Arnaud Héritier > >> > http://aheritier.net > >> > Mail/GTalk: aheritier AT gmail DOT com > >> > Twitter/Skype : aheritier > >> > >> Thanks, > >> > >> Jason > >> > >> ---------------------------------------------------------- > >> Jason van Zyl > >> Founder, Takari and Apache Maven > >> http://twitter.com/jvanzyl > >> http://twitter.com/takari_io > >> --------------------------------------------------------- > >> > >> Our achievements speak for themselves. What we have to keep track > >> of are our failures, discouragements and doubts. We tend to forget > >> the past difficulties, the many false starts, and the painful > >> groping. We see our past achievements as the end result of a > >> clean forward thrust, and our present difficulties as > >> signs of decline and decay. > >> > >> -- Eric Hoffer, Reflections on the Human Condition > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > > > > > -- > > ----- > > Arnaud Héritier > > http://aheritier.net > > Mail/GTalk: aheritier AT gmail DOT com > > Twitter/Skype : aheritier > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- ----- Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
