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

+1 -- Uwe On December 24, 2015 23:34:47 "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

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

Am 2015-12-24 um 23:34 schrieb Michael Osipov: 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

Re: What happened to Maven Eclipse Plugin?

Hi Michael, it was half forgotten, half intended. My original idea was to donate it to MojoHaus and once they made there first release we could do final release here and refer to the the maintainers. However, MojoHaus hasn't found someone to maintain it over there. Other argument: sources

Log4j Warning

Hi All, Happy Holidays. Can the next version of Maven be rid of this warning: [WARN] The SLF4J binding actually used is not supported by Maven: org.apache.logging.slf4j.Log4jLoggerFactory [WARN] Maven supported bindings are: [WARN] (from

[GitHub] maven-plugins pull request: [MJAVADOC-437] javadoc:aggregate fails...

Github user hwellmann closed the pull request at: https://github.com/apache/maven-plugins/pull/72 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

Re: Log4j Warning

Am 2015-12-25 um 16:09 schrieb Gary Gregory: Hi All, Happy Holidays. Can the next version of Maven be rid of this warning: [WARN] The SLF4J binding actually used is not supported by Maven: org.apache.logging.slf4j.Log4jLoggerFactory [WARN] Maven supported bindings are: [WARN] (from

Another yearly issue cleanup in JIRA

Hi folks, the previous had a bad wording, so I decided to rerun that. I'd like to do another issue cleanup in JIRA like a did last year. We currently have 127 unresolved issues which haven't been updated for more than three years. They drill down as follows: Wish: 3 Task: 4 New Feature: 14

Re: What happened to Maven Eclipse Plugin?

Op Fri, 25 Dec 2015 13:09:26 +0100 schreef Michael Osipov : Robert, just read the discussion on mojohaus-dev. Does this actually mean that you need to respin to vote for complete retirement? I would do so. I don't see a reason for a respin of the vote: we decided to

[VOTE] Release Apache Maven Shared Component: File Management Version 3.0.0

Hi, We solved 9 issues: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20fixVersion%20%3D%20file-management-3.0.0 There are still a couple of issues left in JIRA:

Re: Another yearly bug squash

Hervé, Am 2015-12-25 um 17:41 schrieb herve.bout...@free.fr: this is a *bug report* squash, not a bug squash correct, my bad. That was a misunderstanding on my side. And looking at the list, I see not only bug reports but a good number of enhancements notes (TODO list): perhaps limiting the

Re: What happened to Maven Eclipse Plugin?

Robert, just read the discussion on mojohaus-dev. Does this actually mean that you need to respin to vote for complete retirement? I would do so. I would continue as instructed by our retirement plan, issue, final release with notice. Moreover, I would add warning log output to every mojo

Re: What happened to Maven Eclipse Plugin?

Am 2015-12-25 um 14:25 schrieb Robert Scholte: Op Fri, 25 Dec 2015 13:09:26 +0100 schreef Michael Osipov [...] I would continue as instructed by our retirement plan, issue, final release with notice. Moreover, I would add warning log output to every mojo that this plugin has been retired.

Re: Another yearly bug squash

this is a *bug report* squash, not a bug squash And looking at the list, I see not only bug reports but a good number of enhancements notes (TODO list): perhaps limiting the search to bugs only would avoid dropping our TODO list And this notice IMHO should go to maven-users too Regards,

Re: What happened to Maven Eclipse Plugin?

On Fri, Dec 25, 2015 at 4:22 PM, Gary Gregory wrote: > Yeah, I've avoid m2e until the other day to see if it got any better. Not. > So your solution is to switch IDEs... hm, not a huge fan of IJ... is there > an Eclipse-like Java Perspective? I find file based editing

Re: What happened to Maven Eclipse Plugin?

> > Do those of you who are Eclipse users find m2e adequate? I've successfully used m2e for many years on many different systems (different customers). I suggest asking about any issues on the m2e users list. On Fri, Dec 25, 2015 at 2:37 PM, Gary Gregory wrote: > I'm

Re: What happened to Maven Eclipse Plugin?

Yeah, I've avoid m2e until the other day to see if it got any better. Not. So your solution is to switch IDEs... hm, not a huge fan of IJ... is there an Eclipse-like Java Perspective? I find file based editing retarded. Gary On Dec 25, 2015 12:49 PM, "Benson Margulies"

Re: What happened to Maven Eclipse Plugin?

Op Fri, 25 Dec 2015 21:37:55 +0100 schreef Gary Gregory : I'm still surprised that no one wants to maintain this. Do those of you who are Eclipse users find m2e adequate? I don't. Unless I do not know how to set it up. For example, importing the log4j2 projects

Re: What happened to Maven Eclipse Plugin?

I'm still surprised that no one wants to maintain this. Do those of you who are Eclipse users find m2e adequate? I don't. Unless I do not know how to set it up. For example, importing the log4j2 projects creates some projects with errors. Gary On Dec 24, 2015 2:44 PM, "Michael Osipov"

Re: What happened to Maven Eclipse Plugin?

Eclipse's single classpath makes it fundamentally broken with any maven project that has test dependences. So some of us bailed to intellij long ago. m-e-p has one set of incurable issues, and m2e, while much improved, can still eat all your memory on a moderate project. We've watched the lack

[GitHub] maven-surefire pull request: [SUREFIRE-1202] Allow rerunFailingTes...

Github user Tibor17 commented on the pull request: https://github.com/apache/maven-surefire/pull/108#issuecomment-167269576 @seanf done! You can check it out with 2.20-SNAPSHOT. I will start the Release Vote on Sunday/Monday. 2.19.1 will be in Maven Central on Wednesday.