Re: Parent Version maybe not needed in child POM

Absolutely agreeing with Igor. And if you want to be able to build a single module of a multimodule without -am it is *your* responsibility to add the versions to those dependencies, so these are pulled from a repository. That will still work, but will remove the safety belt (jigsaw(tm)?)

Re: Parent Version maybe not needed in child POM

Am 12/13/16 um 01:07 schrieb Manfred Moser: > All of these task should only happen when you open a new project. Otherwise > all of it should be cached in the local repo. > > When all of it is local it should NOT take so long. At least it doesnt in > M2e. If you resort to a hack like opening

Re: Parent Version maybe not needed in child POM

This suggests inefficiency in existing implementation. We use this model internally with some custom optimizations for a very large codebase. -- Regards, Igor On December 12, 2016 3:25:35 PM Christian Schulte wrote: Am 12/12/16 um 23:23 schrieb Igor Fedorenko: Disagree.

Re: Parent Version maybe not needed in child POM

Am 12/12/16 um 23:23 schrieb Igor Fedorenko: > Disagree. I think in most if not all cases we build entire project, not > just random part of a project. Try opening a big multi-module project in Netbeans, for example. Something like an J2EE application server. You can take a long walk until it

Re: Parent Version maybe not needed in child POM

Am 12/13/16 um 01:33 schrieb Igor Fedorenko: > This suggests inefficiency in existing implementation. We use this model > internally with some custom optimizations for a very large codebase. Maybe. Netbeans is using the Maven API for all of this. It's like building the full reactor on the

Re: Maven 3.4.0 Release

Am 2016-12-12 um 02:48 schrieb Christian Schulte: Am 12/11/16 um 22:56 schrieb Michael Osipov: I just ran ITs with current master, only one IT fails: Should be fixed now. Are you certain about this? I cannot confirm. 723b942ad10ab471dfbc5d81ed1071891573dc01 fixes MNG-5227 IT but the IT

Re: future of aether

https://projects.eclipse.org/projects/technology.aether/reviews/termination-review -- Regards, Igor On December 12, 2016 11:13:28 AM "Manfred Moser" wrote: There should be some eclipse notes about the move of the project to the attic and the migration. But I

Re: Maven 3.4.0 Release

Am 12/12/16 um 22:55 schrieb Michael Osipov: > Am 2016-12-12 um 02:48 schrieb Christian Schulte: >> Am 12/11/16 um 22:56 schrieb Michael Osipov: >>> I just ran ITs with current master, only one IT fails: >> >> Should be fixed now. > > Are you certain about this? I cannot confirm. >

2nd question regarding repository overriding.

Am 12/13/16 um 02:32 schrieb Christian Schulte: > Consider these projects: > > P1 declares a repository with id 'central' and a dependency on D1 > available in that repository. > > D1 declares a repository with id 'central' with a different URL and has > a dependency management import

Re: Parent Version maybe not needed in child POM

Disagree. I think in most if not all cases we build entire project, not just random part of a project. Regards, Igor On December 12, 2016 11:22:50 AM Christian Schulte wrote: Am 12/12/16 um 10:16 schrieb Tibor Digana: Is it really necessary to specify version of parent

Re: Parent Version maybe not needed in child POM

All of these task should only happen when you open a new project. Otherwise all of it should be cached in the local repo. When all of it is local it should NOT take so long. At least it doesnt in M2e. If you resort to a hack like opening only part of the reactor you should not be surprised if

[VOTE] Release Apache Maven Dependency Plugin version 3.0.0

Hi, We solved 25 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227=12330458=Text There are still a couple of issues left in JIRA:

Re: Parent Version maybe not needed in child POM

-am should be aware of entire multimodule project and resolve in reactor dependencies accordingly. -- Regards, Igor On December 12, 2016 2:36:08 PM "Robert Scholte" wrote: Absolutely agreeing with Igor. And if you want to be able to build a single module of a

Question regarding repository overriding.

Consider these projects: P1 declares a repository with id 'central' and a dependency on D1 available in that repository. D1 declares a repository with id 'central' with a different URL and has a dependency management import declaration on D2. When importing D2 into the effective model of D1,

Re: Maven 3.4.0 Release

Am 12/12/16 um 22:55 schrieb Michael Osipov: > Am 2016-12-12 um 02:48 schrieb Christian Schulte: >> Am 12/11/16 um 22:56 schrieb Michael Osipov: >>> I just ran ITs with current master, only one IT fails: >> >> Should be fixed now. > > Are you certain about this? I cannot confirm. >

Parent Version maybe not needed in child POM

Is it really necessary to specify version of parent artifact in ? Suppose we have multimodule reactor project and maven-release-plugin would inline the version in the section and remove it again in new development iteration. The plugin fails then if the parent version is not determined. WDYT?

Re: Parent Version maybe not needed in child POM

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. -- Regards, Igor On December 12, 2016 4:38:30 PM Christian Schulte

Re: Parent Version maybe not needed in child POM

>>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 modules apart and keep some in it which makes the

Jenkins: Modules changed, recalculating dependency graph

Would it be possible to assign me role in Jenkins allowing me to fix things myself? I renamed 'maven-aether-provider' to 'maven-resolver-provider' and all hell breaks loose on Jenkins. I have a strong need on a reliable CI system :-). I'd like to stop this one from failing, for example, but cannot

Re: Parent Version maybe not needed in child POM

Exactly! That's why we are thinking about a build pom and a distribution pom, which are now always the same file. By splitting it, it will be possible to replace the relativePath with the actual version.  To be clear, developers will only have a build pom, the distribution pom will be generated

Re: Parent Version maybe not needed in child POM

Tibor Digana wrote: > Is it really necessary to specify version of parent artifact in ? > > Suppose we have multimodule reactor project and maven-release-plugin would > inline the version in the section and remove it again in new > development iteration. The plugin fails then if the parent

[GitHub] maven-surefire issue #114: Parallel runner should not drop away runners that...

Github user Fuud commented on the issue: https://github.com/apache/maven-surefire/pull/114 "Master Origin" integration tests suite does not pass on my Windows box. ``` Results : Failed tests:

Re: Parent Version maybe not needed in child POM

I think this is a good idea. And I'd go one step further and use "versionless" to represent in-reactor version. -- Regards, Igor On December 12, 2016 1:16:49 AM Tibor Digana wrote: Is it really necessary to specify version of parent artifact in ? Suppose we have

future of aether

Hi, is there any official statement about the future of Aether published somewhere? I just noticed that Spring plans to use it in one of there upcoming releases: https://github.com/spring-projects/spring-boot/commit/1cd781b2426f1b63b80d990e19d7d7c6a6fd735a

Re: Parent Version maybe not needed in child POM

Am 12/12/16 um 10:16 schrieb Tibor Digana: > Is it really necessary to specify version of parent artifact in ? It must be possible to checkout a single module and build that in isolation. A parent without a version cannot be resolved from a repository. Supporting that means you need to checkout

Re: future of aether

There should be some eclipse notes about the move of the project to the attic and the migration. But I dont know where they would be. Once the migration is done the Eclipse site should probably be updated or use a redirector.. Manfred domi wrote on 2016-12-12 01:44: > Hi, > > is there any

Re: Parent Version maybe not needed in child POM

I forgot to mention that this must work for SNAPSHOTs as well, which confirms this is not something which needs to be resolved with the maven-release-plugin, but in Maven Core. Robert On Mon, 12 Dec 2016 10:16:46 +0100, Tibor Digana wrote: Is it really necessary

Re: Parent Version maybe not needed in child POM

The IDEs like Eclipse, IDEA etc must adapt to versionless parent. @Christian Execution of large projects and parent version depends on development team. Nowadays they are going to be Microservices very small and isolated in build time and runtime as well. It really depends on the needs. For

Re: maven-aether-provider renamed to maven-resolver-provider.

Am 2016-12-11 um 23:43 schrieb Christian Schulte: Do we want to deploy a 'maven-aether-provider' relocating to 'maven-resolver-provider'? Since we change the groupId already, why not? Michael - To unsubscribe, e-mail:

Re: Parent Version maybe not needed in child POM

Am 12.12.2016 um 21:32 schrieb Tibor Digana: > The IDEs like Eclipse, IDEA etc must adapt to versionless parent. > > @Christian > Execution of large projects and parent version depends on development team. > Nowadays they are going to be Microservices very small and isolated in > build time and

Re: [HEADS UP] Releasing maven-wagon-2.11

Am 2016-12-11 um 19:59 schrieb Dan Tran: Hi I am planning to stage maven-wagon-2.11 tomorrow night US Pacific time. Let me know if you need me to wait Can you hold it for a week? I am currently investigating an issue with duplicate dependencies for the HTTP provider. At the end, several

Re: [HEADS UP] Releasing maven-wagon-2.11

Sure -Dan On Mon, Dec 12, 2016 at 1:06 PM, Michael Osipov wrote: > Am 2016-12-11 um 19:59 schrieb Dan Tran: > >> Hi >> >> I am planning to stage maven-wagon-2.11 tomorrow night US Pacific time. >> Let me know if you need me to wait >> > > Can you hold it for a week? I am

Re: Parent Version maybe not needed in child POM

On Mon, Dec 12, 2016 at 8:22 PM, Christian Schulte wrote: > Am 12/12/16 um 10:16 schrieb Tibor Digana: >> Is it really necessary to specify version of parent artifact in ? > > It must be possible to checkout a single module and build that in > isolation. A parent without a