Re: moving GitHub issue notifications to issues@maven.a.o

+1 (non binding) -- bart...@x-reizend.de > On 21. Oct 2017, at 12:22, Hervé BOUTEMY wrote: > > Currently, comments are sent to dev@maven.a.o > > For our classical official Jira issue tracker, notifications are sent to > issues@maven.a.o > > If nobody objects (72h as

Re: [DISCUSSION] finishing Aether import: help find a new name

everybody ok for: - name: "Artifact Resolver" - groupId: org.apache.maven.resolver - artifactId: resolver(-*) Why not more formal like: -name: Maven Artifact Resolver -groupId: org.apache.maven.[artifact | resolver] -artifactId: artifact-resolver -- barthel

Re: [DISCUSSION] finishing Aether import: help find a new name

Hi, Eclipse owns the Aether name. We cannot use the name Aether. And the Eclipse Foundation doesn't like to provide that name to the ASF (only the name without the eclipse namespace)? Aethel means over the AIR. WDYT about org.Apache.maven.air: _A_rtifact _I_inqui_R_e. Inquire is more

Re: [DISCUSSION] finishing Aether import: help find a new name

Hi, I know Aether is one of the catchy non telling name. But, why not leave Aether with new Maven namespace like org.apache.maven.aether? -- barthel - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional

Re: Aether

ot yet time to work on code. >> We'll keep everybody informed when this step is done >> >> Regards, >> >> Hervé >> >> Le jeudi 23 juin 2016 22:35:25 Uwe Barthel a écrit : >>> Hi, >>> >>> I would like to contribute to bring

Aether

Hi, I would like to contribute to bring Aether to Apache Maven. The repositories git.apache.org, github.com) are available. The clearance is running. What are the next steps? The item (https://issues.apache.org/jira/browse/MNG-6006) contains less information. -- barthel

Re: Roadmap Maven 3.4.0

Hi Michael, > I have made several comments. Please review and update otherwise I cannot > proceed on the merge. I take a look. Thats a lot of auto formatting things. It’s quite difficult to manage these over different projects in Netbeans. I'll fix that. > Additionally, I am waiting for an

Re: maven git commit: [MNG-3507] keep green for success: INFO in blue (DEBUG is cyan)

Hi, > DEBUG/INFO/WARNING/ERROR schemes I'm thinking at: > 1. bold cyan/bold green/bold yellow/bold red (initial) > 2. bold cyan/bold blue/bold yellow/bold red (current) > 3. cyan/blue/bold yellow/bold red (idea to have INFO less visible) I prefer to use the standard console color (customised by

Re: Roadmap Maven 3.4.0

fixed? -- barthel > On 14 Jun 2016, at 22:55, Paul Benedict <pbened...@apache.org> wrote: > > You can find the JIRA Maven Roadmap here: > https://issues.apache.org/jira/browse/MNG/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel > > > Cheers, > Paul >

Roadmap Maven 3.4.0

Hi, Is there a clear roadmap for version 3.4.0? I ask, because these PRs: https://github.com/apache/maven/pull/70 (integration tests: https://github.com/apache/maven-integration-testing/pull/14) for Item https://issues.apache.org/jira/browse/MNG-3092. This item lives around NINE years and

Re: Massive number of failing ITs

Hi Jason, I tried the gist bash script. First of all I’ve to change the patchUrl: ——8<—8<——snipp——8<—8<—— […] #patchUrl=${repository}/pull/${pr}.patch patchUrl=https://patch-diff.githubusercontent.com/raw/apache/maven/pull/${pr}.patch […] ——8<—8<——snipp——8<—8<—— otherwise the

Re: Massive number of failing ITs

Hi Jason, I tried to reproduce the IT failure at master. Fetched https://github.com/apache/maven - master - last commit: 4b35102f0e3302e15a80d3ddb756463601b9217a Fetched https://github.com/apache/maven-integration-testing - master - last commit: af138c8a75a0b1a852510b27ed2c469992cde69a

Re: Maven Core - Release 3.4.0?

* MNG-3092: https://github.com/apache/maven/pull/70 -- barthel > On 07 May 2016, at 20:05, Karl Heinz Marbaise wrote: > > Hi to all, > > based on the number issues which have been fixed in the current 3.4.0... > > I would like to ask if there are objections to make a new

Re: Maven Release Plugin And A BOM

Hi Petar, I found a very old enforcer rule at smartics and asked them to provide these as OS. They did it two weeks ago at github under Apache Software License. :-) Take a look at https://github.com/smartics/smartics-enforcer-rules -- barthel On May 3, 2016 4:25:55 PM Petar Tahchiev

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: 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: Updating the default versions for maven-compiler-plugin

-1 Many commercial projects still require Java 1.6. mit freundlichen Grüßen -- Uwe Barthel <bart...@x-reizend.de> On November 6, 2015 1:57:04 PM Attila-Mihály Balázs <dify@gmail.com> wrote: Hello, Given that we're almost in 2015, what do people think about updating the de

Re: Question concerning maven-filtering component

> -/** > - * @plexus.requirement > - */ > +@Component > private BuildContext buildContext; Use @Requirement instead of @Component. mit freundlichen Grüßen Uwe Barthel -- bart...@x-reizend.de > On 04 Nov 2015, at 22:33, Karl Heinz Marbaise <khmarba...@g

Re: Maven Release Version Policy

roach is as strict but clean as possible. But maybe this behaviour is too strict, so it could be a part of a 'strict server' version policy implementation. mit freundlichen Grüßen Uwe Barthel -- bart...@x-reizend.de --

[MNG-3092] merge/commit buddy needed

My PR for “Adds version range result filter behaviour” (https://github.com/apache/maven/pull/70) is ready for merging and needs a willing committer to merge into master. Please take a look and leave a comment if I could support the merging somehow. mit freundlichen Grüßen Uwe Barthel -- bart

Re: Maven Release Version Policy

Hi, I’m with Jason to move Maven forward to use (strict) semver as default version strategy. I understand the 'cloudbee' strategy as a more exotic way. But I'm interested in more than one strategy, configurable via plugin or providing by default plugin. mit freundlichen Grüßen Uwe Barthel

Re: Maven Release Version Policy

> I'm not sure "strict semver" can be automated: functional change can't be > easily detected if there is no API change The bundle-maven-plugin behaviour is a good base to discuss about I think. mit freundlichen Grüßen Uwe Barthel -- bart...@x-reizend.de > On 31 Oct 20

Re: Maven Release Version Policy

mit freundlichen Grüßen Uwe Barthel -- bart...@x-reizend.de > On 31 Oct 2015, at 13:26, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > > great: what is the bundle-maven-plugin feature you're talking about? > > Regards, > > Hervé > > Le samedi 31 octobre 2015 13

Re: Maven Release Version Policy

en-plugin (baseline) for similar behaviour at build time. But it is strong bundled on OSGi version philosophy. mit freundlichen Grüßen Uwe Barthel -- bart...@x-reizend.de > On 31 Oct 2015, at 12:28, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > > by that you mean you

Re: MNG-5899 Project models are no longer mutable in reactor

On October 27, 2015 4:08:11 PM Jason van Zyl wrote: So I think we have then opportunity to model this correctly and we have something similar already in a WAR. We have a handler that clips all transitive dependencies. There would be a bit more work but if we make a separate

Re: [VOTE] Release Apache Maven Shade Plugin version 2.4.2 (Take 2)

+1 (non binding) checksum [x] Java 5 [x] mit freundlichen Grüßen Uwe Barthel -- bart...@x-reizend.de > On 24 Oct 2015, at 12:48, Karl Heinz Marbaise <khmarba...@gmx.de> wrote: > > Hi, > > We solved 7 issues: > https://issues.apache.org/jira/secure/ReleaseNote

Re: [VOTE] Release Apache Maven Shade Plugin version 2.4.2

-1: for me. (non binding) In respect of http://semver.org/ I suggest the version 2.5.0. The Java version change is a minimum minor change. -- barthel > On 20 Oct 2015, at 23:47, Tibor Digana wrote: > > +1: from me > > No blocker from my side. Actually Java 5 is