Re: [VOTE] Retire Maven Application Skin, Maven Classic Skin, Maven Stylus Skin

+1 On Thursday 24 December 2015, Michael Osipov <1983-01...@gmx.net> wrote: > Hi, > > as previously suggested, it makes sense to retire those skins because > they haven't been updated for a long time and we don't have the resources > to maintain them properly [1]. > > Last releases: > Maven

What happened to Maven Eclipse Plugin?

Hi Robert, back in October the result of the retirement vote [1] was positive. The plugin is still online without notice, issues are still open in JIRA and no repo is at GitHub. Did you simply forget that? Michael [1] https://www.mail-archive.com/dev%40maven.apache.org/msg107104.html

Re: Retiring Maven Skins

+1 Regards Mirko -- Sent from my mobile Am 23.12.2015 21:30 schrieb "Michael Osipov" <1983-01...@gmx.net>: > Hi folks, > > Hervé is quite busy right now preparing Doxia (Sitetools) 1.7 along with > Maven > Site Plugin 3.5. I have several tickets on my own I'd like to fix. Some of > these >

Another yearly bug squash

Hi folks, I'd like to do another bug squash like a did last year. We currently have 132 unresolved bugs which haven't been updated for more than three years. I hardly believe that they will be updated ever. Maybe they have been resolved with new versions automatically. Anyway, here is the query

[VOTE] Retire Maven Application Skin, Maven Classic Skin, Maven Stylus Skin

Hi, as previously suggested, it makes sense to retire those skins because they haven't been updated for a long time and we don't have the resources to maintain them properly [1]. Last releases: Maven Application Skin: 2012-01-18 Maven Classic Skin: 2012-01-18 Maven Stylus Skin: 2012-07-30 I

Re: [VOTE] Retire Maven Application Skin, Maven Classic Skin, Maven Stylus Skin

Hi Michael, here my +1.. Kind regards Karl Heinz Marbaise On 12/24/15 11:34 PM, Michael Osipov wrote: Hi, as previously suggested, it makes sense to retire those skins because they haven't been updated for a long time and we don't have the resources to maintain them properly [1]. Last

Re: Automating upload(commit) to "dist" area ?

What would you like to happen? I can look at writing a Nexus plugin to push content wherever we like after a release. > On Dec 24, 2015, at 3:19 AM, Kristian Rosenvold > wrote: > > Is there any way we can do this to avoid manual steps in the release > process ? >

Automating upload(commit) to "dist" area ?

Is there any way we can do this to avoid manual steps in the release process ? K

Re: Retiring Maven Skins

Hi Michael, +2 -- Uwe bart...@x-reizend.de > On 23 Dec 2015, at 21:30, Michael Osipov <1983-01...@gmx.net> wrote: > > Hi folks, > > Hervé is quite busy right now preparing Doxia (Sitetools) 1.7 along with Maven > Site Plugin 3.5. I have several tickets on my own I'd like to fix. Some of >

Re: Retiring Maven Skins

Yes! +2 2015-12-24 11:03 GMT+01:00 : > yes, that's a good cleanup > > Regards, > > Hervé > > - Mail original - > De: "Michael Osipov" <1983-01...@gmx.net> > À: dev@maven.apache.org > Envoyé: Mercredi 23 Décembre 2015 21:30:28 > Objet: Retiring Maven Skins > > Hi

Re: Automating upload(commit) to "dist" area ?

I'd like it, but I have no idea how to do it because of: - the time it has to happen (ie after vote success) - the credentials required - need not only to add new release but also remove older (this one is the simple one to fix, a wildcard for version may do the job) something that can be done

Re: Retiring Maven Skins

yes, that's a good cleanup Regards, Hervé - Mail original - De: "Michael Osipov" <1983-01...@gmx.net> À: dev@maven.apache.org Envoyé: Mercredi 23 Décembre 2015 21:30:28 Objet: Retiring Maven Skins Hi folks, Hervé is quite busy right now preparing Doxia (Sitetools) 1.7 along with Maven

Re: Retiring Maven Skins

+1 On Thursday 24 December 2015, Kristian Rosenvold < kristian.rosenv...@gmail.com> wrote: > Yes! +2 > > 2015-12-24 11:03 GMT+01:00 >: > > > yes, that's a good cleanup > > > > Regards, > > > > Hervé > > > > - Mail original - > > De: "Michael Osipov"