Re: Documenting Maven 3.4.0

Stating any differences campared to older versions would be good as well. /Anders (mobile) Den 14 dec. 2016 01:41 skrev "Manfred Moser" : > I would suggest latest publically available version (so 3.3.9). > > Manfred > > Christian Schulte wrote on 2016-12-13 16:22: > >

Re: Documenting Maven 3.4.0

Am 12/14/16 um 01:41 schrieb Manfred Moser: > I would suggest latest publically available version (so 3.3.9). > Ok. Thanks. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail:

Re: Documenting Maven 3.4.0

I would suggest latest publically available version (so 3.3.9). Manfred Christian Schulte wrote on 2016-12-13 16:22: > When providing examples, which Maven version should be used to > demonstrate differences. Maven 3.0.5, 3.1.1, 3.2.5 or 3.3.9? > > Regards, > -- > Christian > > >

Documenting Maven 3.4.0

When providing examples, which Maven version should be used to demonstrate differences. Maven 3.0.5, 3.1.1, 3.2.5 or 3.3.9? Regards, -- Christian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional

Re: Maven 3.4.0 Release

Am 12/14/16 um 01:05 schrieb Christian Schulte: > That a direct optional dependency That should read: That a transitive optional dependency... - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands,

Re: Maven 3.4.0 Release

Am 12/12/16 um 00:51 schrieb Igor Fedorenko: > I'm traveling until next weekend and won't be able to review your changes > properly until I'm back. I do want to stress that maven plugins are not > dependencies, they are resolved the same way as projects. Coming back to this. Currently plugins

Re: Dependency resolution broken on Wagon master with Maven 3.4.0-SNAPSHOT

That's MRESOLVER-9. Fixed the POMs with this commit. This is what is lacking documentation the most. Does the commit message clarify what is going on? Am 12/13/16 um 20:32 schrieb

Re: Dependency resolution broken on Wagon master with Maven 3.4.0-SNAPSHOT

Am 12/13/16 um 20:32 schrieb Michael Osipov: > Hi folks, > > current Wagon master cannot be built with > > Apache Maven 3.4.0-SNAPSHOT (33c79c6e4662abb836df95a5d70c236f2e5cda3d; > 2016-12-13T20:22:49+01:00) > Maven home: D:\Entwicklung\Programme\apache-maven-3.4.0-SNAPSHOT\bin\.. > Java

Dependency resolution broken on Wagon master with Maven 3.4.0-SNAPSHOT

Hi folks, current Wagon master cannot be built with Apache Maven 3.4.0-SNAPSHOT (33c79c6e4662abb836df95a5d70c236f2e5cda3d; 2016-12-13T20:22:49+01:00) Maven home: D:\Entwicklung\Programme\apache-maven-3.4.0-SNAPSHOT\bin\.. Java version: 1.7.0_80, vendor: Oracle Corporation Java home:

Re: Parent Version maybe not needed in child POM

Am 12/13/16 um 07:33 schrieb Igor Fedorenko: > But reactor dependencies make perfect sense in m2e! Also, keep in mind that > we are talking about new maven concept, it does not currently exist and > can't be supported by m2e, netbeans or any other existing tool. > Last time I worked on a Maven

Re: Parent Version maybe not needed in child POM

Am 12/13/16 um 06:04 schrieb Tibor Digana: >>> Something like an J2EE >>> You can take a long walk >>> until it finishes downloading sources, javadoc, dependencies >>> I really only open the module(s) I need > This is not Maven problem then. > You architect must give you a freedom to move some

Re: Jenkins: Modules changed, recalculating dependency graph

As pmc-chair I should be able to grant access[1], but I don't. I've asked infrastructure@a.o for help Robert [1] https://wiki.apache.org/general/Jenkins On Tue, 13 Dec 2016 05:19:25 +0100, Christian Schulte wrote: Would it be possible to assign me role in Jenkins

[GitHub] maven-plugins pull request #100: Fixed MEAR-217: Correct match of snapshot v...

GitHub user fabianschlier opened a pull request: https://github.com/apache/maven-plugins/pull/100 Fixed MEAR-217: Correct match of snapshot version in skinny wars The patch was already proposed (and tested by the community) within JIRA issue