Re: Parent Version maybe not needed in child POM

2016-12-13 Thread Christian Schulte
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

2016-12-13 Thread Christian Schulte
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 modu

Re: Parent Version maybe not needed in child POM

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

Re: Parent Version maybe not needed in child POM

2016-12-12 Thread 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 modules apart and keep some in it which makes the multi-mod

Re: Parent Version maybe not needed in child POM

2016-12-12 Thread Christian Schulte
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 command

Re: Parent Version maybe not needed in child POM

2016-12-12 Thread Igor Fedorenko
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. I think in most if

Re: Parent Version maybe not needed in child POM

2016-12-12 Thread Christian Schulte
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 only

Re: Parent Version maybe not needed in child POM

2016-12-12 Thread 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 only part of the reactor you should not be surprised if w

Re: Parent Version maybe not needed in child POM

2016-12-12 Thread Christian Schulte
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 fin

Re: Parent Version maybe not needed in child POM

2016-12-12 Thread Igor Fedorenko
-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 multimodule without -am it is

Re: Parent Version maybe not needed in child POM

2016-12-12 Thread Robert Scholte
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)?) R

Re: Parent Version maybe not needed in child POM

2016-12-12 Thread Igor Fedorenko
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 artifact in ? It

Re: Parent Version maybe not needed in child POM

2016-12-12 Thread Christian Schulte
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 ru

Re: Parent Version maybe not needed in child POM

2016-12-12 Thread 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 runtime as well. It really depends on the needs. For instan

Re: Parent Version maybe not needed in child POM

2016-12-12 Thread Martijn Dashorst
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 version cannot be resolv

Re: Parent Version maybe not needed in child POM

2016-12-12 Thread Christian Schulte
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 th

Re: Parent Version maybe not needed in child POM

2016-12-12 Thread Robert Scholte
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 to specify version of pa

Re: Parent Version maybe not needed in child POM

2016-12-12 Thread Igor Fedorenko
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 multimodule reactor proje

Re: Parent Version maybe not needed in child POM

2016-12-12 Thread Robert Scholte
rated based on the build pom, probably during the package phase  Robert Verzonden vanaf Samsung Mobile. Oorspronkelijk bericht Van: Jörg Schaible Datum:12-12-2016 10:27 (GMT+01:00) Aan: dev@maven.apache.org Onderwerp: Re: Parent Version maybe not needed in child POM

Re: Parent Version maybe not needed in child POM

2016-12-12 Thread Jörg Schaible
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 versi

Parent Version maybe not needed in child POM

2016-12-12 Thread Tibor Digana
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? I