Github user akacme commented on the pull request:
https://github.com/apache/maven/pull/74#issuecomment-168756278
I've added POM-property-based configuration. Based on my current skill
level embedding configuration somewhere else would require change in
dependencies section for
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/74#issuecomment-168565897
POM property, CLI property override, or we might want to start collecting
these provisional changes in a special maven plugin configuration section for
activating
Github user akacme commented on the pull request:
https://github.com/apache/maven/pull/74#issuecomment-168543843
Perhaps a POM property with predefined name could activate this behaviour
in 3.x? In this way it can be set on a per-project basis as well as global
(with properties
Github user akacme commented on the pull request:
https://github.com/apache/maven/pull/74#issuecomment-168519406
I've introduced DependencyManagementGraph object to store and compute
"distance" for dependencyManagement section - so there is no change to the
model itself. Signature of
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/74#issuecomment-168534190
General rule of thumb is that a change in resolution will definitely not go
in if it changes the default behaviour within a minor version. First smoke test
is making sure
Github user akacme commented on the pull request:
https://github.com/apache/maven/pull/74#issuecomment-168403276
Code has been compiled using Java 7. Model has been enhanced to store graph
of imports in dependency management section - I can rewrite it to store it
elsewhere, but such
Github user michael-o commented on the pull request:
https://github.com/apache/maven/pull/74#issuecomment-168402507
You are using Java 8 features which we can't accept. Java 7 only. The model
is changed. I would opt-in for that not before Maven 4.
---
If your project is set up for
Github user michael-o commented on the pull request:
https://github.com/apache/maven/pull/74#issuecomment-168405448
Now I see, the `Optional´ comes from Guava and not from Java. I think the
likelyhood is higher w/o a model change.
---
If your project is set up for it, you can reply
Github user akacme commented on the pull request:
https://github.com/apache/maven/pull/74#issuecomment-168404937
In other words - will it go to Maven 3.x when there is no modification to
the model itself?
---
If your project is set up for it, you can reply to this email and have
GitHub user akacme opened a pull request:
https://github.com/apache/maven/pull/73
[MNG-5947] dependencyManagement import section does not resolve
dependencies using "nearest" definition
dependencies using "nearest" definition
o DepenencyManagement model updated to contain
Github user akacme closed the pull request at:
https://github.com/apache/maven/pull/73
---
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
GitHub user akacme opened a pull request:
https://github.com/apache/maven/pull/74
[MNG-5947] dependencyManagement import section does not resolve
dependencies using "nearest" definition
o DepenencyManagement model updated to contain declared dependencies
and imported
12 matches
Mail list logo
