Re: maven git commit: [MNG-6182] ModelResolver interface enhancements.

2017-03-10 Thread Stephen Connolly 
Christian you need to be proactive and sort this out...

FTR as release manager for Maven core 3.5.0 I have an easy answer to any
decisions asked of me: my answer is Out! For example, If there is a S1/S2
bug in coloured logging, then either it gets fixed promptly or it is out. I
will be brutal to get 3.5.0 shipped. If there is controversy, the easiest
way to consensus is to delay the controversy and leave it out.

More seriously if the changes post 3.5.0 mean that we don't call it 3.5.1
rather call it 3.6.0, that's fine. I will not let conflict stand in the way
of getting 3.5.0 released.

Now to the case in point: Shipping a broken api in 3.5.0 sounds like S1 for
that api change, i.e. Feature does not work at all. So I advise treading
carefully.

Version numbers are just version numbers.

-Stephen

On Fri 10 Mar 2017 at 22:47, Christian Schulte  wrote:

> Am 03/10/17 um 23:33 schrieb Christian Schulte:
> > Am 03/10/17 um 20:16 schrieb Robert Scholte:
> >> On Fri, 10 Mar 2017 16:47:45 +0100, Christian Schulte 
> >> wrote:
> >>
> >>> Am 03/10/17 um 10:42 schrieb Robert Scholte:
>  Having a closer look at this commit, I actually don't like the idea
> that
>  ModelResolver now supports versionRanges.
>  IMO the version should always be specific *before* resolving the
> model.
>  IIUC correctly this is required to supported version-ranges for
> managed
>  dependencies, and that is also something I wonder if we want that.
> 
>  Please let us reconsider this commit.
> >>>
> >>> You do notice the parent resolution is part of that interface since
> >>> Maven 3.2.2? I just added the same logic for dependencies to support
> >>> version ranges in dependency management import declarations. Version
> >>> ranges are supported everywhere but dependency management _import_
> >>> declarations. We already agreed that this is a bug fix and this would
> >>> have been part of Maven 3.4.0, if we would not have dropped it due to
> >>> the resolver changes. MNG-4463 has been reported in JIRA 23/Nov/09
> >>> 09:39! It's tiresome to discuss things committed in 2014 now. See the
> >>> 'ModelResolver' interface from Maven 3.2.2. It already contains that
> >>> logic for 'Parent' model objects.
> >>>
> >>> <
> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=045bd1503b70738ffd0fa08e336574107aded801
> >
> >>>
> >>> The new method in 3.5.0 for 'Dependency' model objects will only be
> used
> >>> to support version ranges in dependency management _import_
> declarations
> >>> coming in 3.5.1.
> >>>
> >>> <
> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=d0911ac57dccb758435cdfd3495121ec9f0ae1b4
> >
> >>>
> >>> Regards,
> >>
> >> MNG-4463 is marked for 3.5.1, not for 3.5.0, so this would *not* the the
> >> moment to commit it.
> >
> > Did you read the description of MNG-6182? There is a good reason not to
> > enhance a public API in a patch release. Just take a look at the history
> > of the ModelResolver interface. It changed in incompatible ways between
> > releases. I'd like this to be stable again in the next feature release.
> > That is 3.5.0 - not 3.5.1. That interface is just an adapter (the
> > maven-model-builder module does not depend on the resolver). I would not
> > want to add yet another adapter interface instead of enhancing the
> > existing one. It's *the* moment to commit this. That's why I added a
> > method not used by anything at the moment. Maven 3.5.0 still is a
> > drop-in replacement that way. No one needs to update an implementation.
> > This will change as soon as something starts to call the new method in
> > 3.5.1, of course. Just as we add dependencies to Maven 3.0.0 in the
> > plugins ourselves instead of - say - Maven 3.3.9, I'd like others to be
> > able to depend on Maven 3.5.0 to compile against that API instead of
> > 3.5.x. I am repeating the description of MNG-6182 already. I know the
> > Netbeans IDE is implementing the ModelResolver interface. No one would
> > expect that interface to change between 3.5.0 and 3.5.1 in a way that
> > you get a compile time error when compiling against 3.5.1 instead of
> 3.5.0.
> >
> >>
> >> Let's first push 3.5.0 and give everybody the change to dive into the
> >> complexity of dependency resolution once we start with 3.5.1
> >
> > What complexity are you talking about? Someone using version ranges in a
> > dependency management import declaration will not do this without
> > intention. Maven currently fails the build with an error message. Just
> > like mentioned in the description of MNG-4463. No one expects a public
> > API to be enhanced between 3.5.0 and 3.5.1. Are we really discussing the
> > addition of a new method *not used anywhere*? When in doubt, we should
> > start a vote on this.
> >
> > Regards,
> >
>
> And for the very same reason I am currently reviewing this commit
>
> <
>

Re: maven git commit: [MNG-6182] ModelResolver interface enhancements.

2017-03-10 Thread Christian Schulte 
Am 03/10/17 um 23:33 schrieb Christian Schulte:
> Am 03/10/17 um 20:16 schrieb Robert Scholte:
>> On Fri, 10 Mar 2017 16:47:45 +0100, Christian Schulte   
>> wrote:
>>
>>> Am 03/10/17 um 10:42 schrieb Robert Scholte:
 Having a closer look at this commit, I actually don't like the idea that
 ModelResolver now supports versionRanges.
 IMO the version should always be specific *before* resolving the model.
 IIUC correctly this is required to supported version-ranges for managed
 dependencies, and that is also something I wonder if we want that.

 Please let us reconsider this commit.
>>>
>>> You do notice the parent resolution is part of that interface since
>>> Maven 3.2.2? I just added the same logic for dependencies to support
>>> version ranges in dependency management import declarations. Version
>>> ranges are supported everywhere but dependency management _import_
>>> declarations. We already agreed that this is a bug fix and this would
>>> have been part of Maven 3.4.0, if we would not have dropped it due to
>>> the resolver changes. MNG-4463 has been reported in JIRA 23/Nov/09
>>> 09:39! It's tiresome to discuss things committed in 2014 now. See the
>>> 'ModelResolver' interface from Maven 3.2.2. It already contains that
>>> logic for 'Parent' model objects.
>>>
>>> 
>>>
>>> The new method in 3.5.0 for 'Dependency' model objects will only be used
>>> to support version ranges in dependency management _import_ declarations
>>> coming in 3.5.1.
>>>
>>> 
>>>
>>> Regards,
>>
>> MNG-4463 is marked for 3.5.1, not for 3.5.0, so this would *not* the the  
>> moment to commit it.
> 
> Did you read the description of MNG-6182? There is a good reason not to
> enhance a public API in a patch release. Just take a look at the history
> of the ModelResolver interface. It changed in incompatible ways between
> releases. I'd like this to be stable again in the next feature release.
> That is 3.5.0 - not 3.5.1. That interface is just an adapter (the
> maven-model-builder module does not depend on the resolver). I would not
> want to add yet another adapter interface instead of enhancing the
> existing one. It's *the* moment to commit this. That's why I added a
> method not used by anything at the moment. Maven 3.5.0 still is a
> drop-in replacement that way. No one needs to update an implementation.
> This will change as soon as something starts to call the new method in
> 3.5.1, of course. Just as we add dependencies to Maven 3.0.0 in the
> plugins ourselves instead of - say - Maven 3.3.9, I'd like others to be
> able to depend on Maven 3.5.0 to compile against that API instead of
> 3.5.x. I am repeating the description of MNG-6182 already. I know the
> Netbeans IDE is implementing the ModelResolver interface. No one would
> expect that interface to change between 3.5.0 and 3.5.1 in a way that
> you get a compile time error when compiling against 3.5.1 instead of 3.5.0.
> 
>>
>> Let's first push 3.5.0 and give everybody the change to dive into the  
>> complexity of dependency resolution once we start with 3.5.1
> 
> What complexity are you talking about? Someone using version ranges in a
> dependency management import declaration will not do this without
> intention. Maven currently fails the build with an error message. Just
> like mentioned in the description of MNG-4463. No one expects a public
> API to be enhanced between 3.5.0 and 3.5.1. Are we really discussing the
> addition of a new method *not used anywhere*? When in doubt, we should
> start a vote on this.
> 
> Regards,
> 

And for the very same reason I am currently reviewing this commit



so that the changes to the public APIs can be part of 3.5.0 in the same
way. Add deprecations to old methods, add new methods but do not change
anything else by just not calling the new methods and keep things
unchanged. I am very sure we want to ship a stable 3.5.0 API.


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: maven git commit: [MNG-6182] ModelResolver interface enhancements.

2017-03-10 Thread Christian Schulte 
Am 03/10/17 um 20:16 schrieb Robert Scholte:
> On Fri, 10 Mar 2017 16:47:45 +0100, Christian Schulte   
> wrote:
> 
>> Am 03/10/17 um 10:42 schrieb Robert Scholte:
>>> Having a closer look at this commit, I actually don't like the idea that
>>> ModelResolver now supports versionRanges.
>>> IMO the version should always be specific *before* resolving the model.
>>> IIUC correctly this is required to supported version-ranges for managed
>>> dependencies, and that is also something I wonder if we want that.
>>>
>>> Please let us reconsider this commit.
>>
>> You do notice the parent resolution is part of that interface since
>> Maven 3.2.2? I just added the same logic for dependencies to support
>> version ranges in dependency management import declarations. Version
>> ranges are supported everywhere but dependency management _import_
>> declarations. We already agreed that this is a bug fix and this would
>> have been part of Maven 3.4.0, if we would not have dropped it due to
>> the resolver changes. MNG-4463 has been reported in JIRA 23/Nov/09
>> 09:39! It's tiresome to discuss things committed in 2014 now. See the
>> 'ModelResolver' interface from Maven 3.2.2. It already contains that
>> logic for 'Parent' model objects.
>>
>> 
>>
>> The new method in 3.5.0 for 'Dependency' model objects will only be used
>> to support version ranges in dependency management _import_ declarations
>> coming in 3.5.1.
>>
>> 
>>
>> Regards,
> 
> MNG-4463 is marked for 3.5.1, not for 3.5.0, so this would *not* the the  
> moment to commit it.

Did you read the description of MNG-6182? There is a good reason not to
enhance a public API in a patch release. Just take a look at the history
of the ModelResolver interface. It changed in incompatible ways between
releases. I'd like this to be stable again in the next feature release.
That is 3.5.0 - not 3.5.1. That interface is just an adapter (the
maven-model-builder module does not depend on the resolver). I would not
want to add yet another adapter interface instead of enhancing the
existing one. It's *the* moment to commit this. That's why I added a
method not used by anything at the moment. Maven 3.5.0 still is a
drop-in replacement that way. No one needs to update an implementation.
This will change as soon as something starts to call the new method in
3.5.1, of course. Just as we add dependencies to Maven 3.0.0 in the
plugins ourselves instead of - say - Maven 3.3.9, I'd like others to be
able to depend on Maven 3.5.0 to compile against that API instead of
3.5.x. I am repeating the description of MNG-6182 already. I know the
Netbeans IDE is implementing the ModelResolver interface. No one would
expect that interface to change between 3.5.0 and 3.5.1 in a way that
you get a compile time error when compiling against 3.5.1 instead of 3.5.0.

> 
> Let's first push 3.5.0 and give everybody the change to dive into the  
> complexity of dependency resolution once we start with 3.5.1

What complexity are you talking about? Someone using version ranges in a
dependency management import declaration will not do this without
intention. Maven currently fails the build with an error message. Just
like mentioned in the description of MNG-4463. No one expects a public
API to be enhanced between 3.5.0 and 3.5.1. Are we really discussing the
addition of a new method *not used anywhere*? When in doubt, we should
start a vote on this.

Regards,
-- 
Christian


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: maven git commit: [MNG-6182] ModelResolver interface enhancements.

2017-03-10 Thread Robert Scholte 
On Fri, 10 Mar 2017 16:47:45 +0100, Christian Schulte   
wrote:



Am 03/10/17 um 10:42 schrieb Robert Scholte:

Having a closer look at this commit, I actually don't like the idea that
ModelResolver now supports versionRanges.
IMO the version should always be specific *before* resolving the model.
IIUC correctly this is required to supported version-ranges for managed
dependencies, and that is also something I wonder if we want that.

Please let us reconsider this commit.


You do notice the parent resolution is part of that interface since
Maven 3.2.2? I just added the same logic for dependencies to support
version ranges in dependency management import declarations. Version
ranges are supported everywhere but dependency management _import_
declarations. We already agreed that this is a bug fix and this would
have been part of Maven 3.4.0, if we would not have dropped it due to
the resolver changes. MNG-4463 has been reported in JIRA 23/Nov/09
09:39! It's tiresome to discuss things committed in 2014 now. See the
'ModelResolver' interface from Maven 3.2.2. It already contains that
logic for 'Parent' model objects.



The new method in 3.5.0 for 'Dependency' model objects will only be used
to support version ranges in dependency management _import_ declarations
coming in 3.5.1.



Regards,


MNG-4463 is marked for 3.5.1, not for 3.5.0, so this would *not* the the  
moment to commit it.


Let's first push 3.5.0 and give everybody the change to dive into the  
complexity of dependency resolution once we start with 3.5.1


Robert

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: maven git commit: [MNG-6182] ModelResolver interface enhancements.

2017-03-10 Thread Christian Schulte 
Am 03/10/17 um 10:42 schrieb Robert Scholte:
> Having a closer look at this commit, I actually don't like the idea that  
> ModelResolver now supports versionRanges.
> IMO the version should always be specific *before* resolving the model.
> IIUC correctly this is required to supported version-ranges for managed  
> dependencies, and that is also something I wonder if we want that.
> 
> Please let us reconsider this commit.

You do notice the parent resolution is part of that interface since
Maven 3.2.2? I just added the same logic for dependencies to support
version ranges in dependency management import declarations. Version
ranges are supported everywhere but dependency management _import_
declarations. We already agreed that this is a bug fix and this would
have been part of Maven 3.4.0, if we would not have dropped it due to
the resolver changes. MNG-4463 has been reported in JIRA 23/Nov/09
09:39! It's tiresome to discuss things committed in 2014 now. See the
'ModelResolver' interface from Maven 3.2.2. It already contains that
logic for 'Parent' model objects.



The new method in 3.5.0 for 'Dependency' model objects will only be used
to support version ranges in dependency management _import_ declarations
coming in 3.5.1.



Regards,
-- 
Christian


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[GitHub] maven-plugins pull request #107: [MSHADE-253] NullPointerException if minimi...

2017-03-10 Thread aviemzur 
GitHub user aviemzur opened a pull request:

https://github.com/apache/maven-plugins/pull/107

[MSHADE-253] NullPointerException if minimizeJar == true && packaging == pom



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/aviemzur/maven-plugins 
minimize-jar-pom-packaging-npe

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-plugins/pull/107.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #107


commit 2cb0fab0cd154498cf637e6b6c54a23b4be4ecf4
Author: Zur, Aviem 
Date:   2017-03-10T12:56:20Z

[MSHADE-253] NullPointerException if minimizeJar == true && packaging == pom




---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: maven git commit: [MNG-6182] ModelResolver interface enhancements.

2017-03-10 Thread Robert Scholte 
Having a closer look at this commit, I actually don't like the idea that  
ModelResolver now supports versionRanges.

IMO the version should always be specific *before* resolving the model.
IIUC correctly this is required to supported version-ranges for managed  
dependencies, and that is also something I wonder if we want that.


Please let us reconsider this commit.

thanks,
Robert


On Wed, 08 Mar 2017 19:29:51 +0100,  wrote:


Repository: maven
Updated Branches:
  refs/heads/master 114ef6c5a -> ab800b0cf


[MNG-6182] ModelResolver interface enhancements.


Project: http://git-wip-us.apache.org/repos/asf/maven/repo
Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/ab800b0c
Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/ab800b0c
Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/ab800b0c

Branch: refs/heads/master
Commit: ab800b0cfae4e3ca9453304e3b9727ba4a4b712b
Parents: 114ef6c
Author: Christian Schulte 
Authored: Sat Jan 30 19:17:34 2016 +0100
Committer: Christian Schulte 
Committed: Wed Mar 8 18:24:18 2017 +0100

--
 .../maven/project/ProjectModelResolver.java | 84 +++
 .../maven/model/resolution/ModelResolver.java   | 32 
 .../internal/DefaultModelResolver.java  | 85  


 3 files changed, 167 insertions(+), 34 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/maven/blob/ab800b0c/maven-core/src/main/java/org/apache/maven/project/ProjectModelResolver.java
--
diff --git  
a/maven-core/src/main/java/org/apache/maven/project/ProjectModelResolver.java  
b/maven-core/src/main/java/org/apache/maven/project/ProjectModelResolver.java

index 7b93217..3a31d33 100644
---  
a/maven-core/src/main/java/org/apache/maven/project/ProjectModelResolver.java
+++  
b/maven-core/src/main/java/org/apache/maven/project/ProjectModelResolver.java

@@ -28,7 +28,7 @@ import java.util.Set;
import com.google.common.base.Predicate;
 import com.google.common.collect.Iterables;
-
+import org.apache.maven.model.Dependency;
 import org.apache.maven.model.Parent;
 import org.apache.maven.model.Repository;
 import org.apache.maven.model.building.FileModelSource;
@@ -203,24 +203,26 @@ public class ProjectModelResolver
 return new FileModelSource( pomFile );
 }
-public ModelSource resolveModel( Parent parent )
+@Override
+public ModelSource resolveModel( final Parent parent )
 throws UnresolvableModelException
 {
-Artifact artifact = new DefaultArtifact( parent.getGroupId(),  
parent.getArtifactId(), "", "pom",

- parent.getVersion() );
-
-VersionRangeRequest versionRangeRequest = new  
VersionRangeRequest( artifact, repositories, context );

-versionRangeRequest.setTrace( trace );
-
 try
 {
-VersionRangeResult versionRangeResult =  
resolver.resolveVersionRange( session, versionRangeRequest );
+final Artifact artifact = new DefaultArtifact(  
parent.getGroupId(), parent.getArtifactId(), "", "pom",
+
parent.getVersion() );

+
+final VersionRangeRequest versionRangeRequest = new  
VersionRangeRequest( artifact, repositories, context );

+versionRangeRequest.setTrace( trace );
+
+final VersionRangeResult versionRangeResult =  
resolver.resolveVersionRange( session, versionRangeRequest );

if ( versionRangeResult.getHighestVersion() == null )
 {
-throw new UnresolvableModelException( "No versions  
matched the requested range '" + parent.getVersion()
-  + "'",  
parent.getGroupId(), parent.getArtifactId(),
-   
parent.getVersion() );

+throw new UnresolvableModelException(
+String.format( "No versions matched the requested  
parent version range '%s'",

+   parent.getVersion() ),
+parent.getGroupId(), parent.getArtifactId(),  
parent.getVersion() );

}
@@ -229,21 +231,69 @@ public class ProjectModelResolver
  &&  
versionRangeResult.getVersionConstraint().getRange().getUpperBound() ==  
null )

 {
 // Message below is checked for in the MNG-2199 core IT.
-throw new UnresolvableModelException( "The requested  
version range '" + parent.getVersion()
-  + "' does not  
specify an upper bound", parent.getGroupId(),
-   
parent.getArtifactId(),