At least it will easily be possible to have it NOT available so unknowing users dont get into trouble. I strongly believe that a lot of people only use this because they dont even know about the Maven build step.
Maybe we should change the job type title to include something like "deprecated" or "legacy" or so. I for one will be glad once its gone. We even have a script we run to find any jobs and alert on it. Then we tell people to change the job ... manfred On Tue, Feb 23, 2016 at 2:38 PM, Arnaud Héritier <aherit...@gmail.com> wrote: > #19 > maven-plugin 100810 126144 157844 No: We don’t really want people to use > this > LOL, even if I agree, all Maven users will install it .... > Evil but highly used :( > > On Tue, Feb 23, 2016 at 11:20 PM, Daniel Beck <m...@beckweb.net> wrote: > >> Hi everyone, >> >> I added two additional criteria to the wiki: The plugin shouldn't require >> a restart to work (otherwise it's not exactly a great getting started >> experience), and it shouldn't be just a UI/theming plugins that replaces >> part of the Jenkins UI (as including them in a list of >> suggested/recommended plugins would just be weird). >> >> Based on these criteria I tried to build a list of plugins to feature in >> the initial setup wizard. >> >> A reminder: All plugins are still available in the plugin manager. But >> with 1100+ plugins now, it'd be great if we could provide a curated subset >> to get new users started. This also means that particularly complex >> plugins, that require knowledge of Jenkins internals, even though they may >> be useful, are basically excluded by default. >> >> To approximate popularity, I used the previous install count multiplied >> by the growth in the previous year (as neither alone is a sufficient >> indicator of popularity). Then I sorted by this value, and went through the >> list, being mildly judgmental. This is the result: >> >> >> https://docs.google.com/spreadsheets/d/1TKziW5oEfX9NYAPrZkz-wXPt5s-zG-znIB5-Jwt3tmw/edit#gid=0 >> >> This is the list of plugins I came up with for the initial setup dialog. >> If a plugin wouldn't be used, the reason is stated. Regarding 'Unsafe': >> Wearing my security officer hat, I consider every plugin with Groovy >> scripting that is not using the Groovy Sandbox to be unsafe, even if it >> implements security measures. >> >> Please review the list, and let me know what you think. >> >> >> On 21.01.2016, at 19:56, Daniel Beck <m...@beckweb.net> wrote: >> >> > Hi everyone, >> > >> > For Jenkins 2.0, we're aiming for a much better 'getting started' >> experience, aimed for users new to Jenkins. >> > >> > We already talked about this last year[1], but the discussion didn't >> really have a great result, so I'd like to start over by defining a list of >> guidelines on what kind of plugins qualify for inclusion first. My initial >> proposal is in the wiki[2]. Please take a look and provide feedback in this >> thread. >> > >> > Specific selection of plugins would be the next step. >> > >> > Daniel >> > >> > 1: >> https://groups.google.com/forum/#!msg/jenkinsci-dev/w-_18aYn4QQ/t_WT442bBwAJ >> > 2: >> https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Selection+for+the+Setup+Dialog >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups "Jenkins Developers" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> an email to jenkinsci-dev+unsubscr...@googlegroups.com. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/044ECC6E-4C39-45B6-90E3-1A0C40BD5E9B%40beckweb.net >> . >> > For more options, visit https://groups.google.com/d/optout. >> > >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-dev+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/73110AB5-7D59-4858-8A12-F20F64180CA9%40beckweb.net >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > ----- > Arnaud Héritier > http://aheritier.net > Mail/GTalk: aheritier AT gmail DOT com > Twitter/Skype : aheritier > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-8pFthuD3%2BNjMTfVca0sJph6-5uZtYNqjJ%2Bs056xtGwgA%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-8pFthuD3%2BNjMTfVca0sJph6-5uZtYNqjJ%2Bs056xtGwgA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CABffhO4JAnPed4OSpM_yi7C648uojOBAZ1jJ0Q%3D8nW4QiAXmHQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
