> * [MNG-6186] - switch to improved HawtJNI
> Robert: Improvements have not been accepted yet, branch now has conflicts
Guillaume Nodet, from Fusesource, has just merged
I don't know when he's considering to do a release, but it might be quite soon
Regards,
Hervé
Le jeudi 27 avril 2017,
Github user grahamtriggs commented on the issue:
https://github.com/apache/maven/pull/69
> Mutated pom.xml files must not invalidate original reactor
ProjectDependencyGraph. More specifically, if the original graph allowed
certain build order, the new graph must still allow the same
Hi,
I would like to start a release of maven-depenency-analyzer 1.7.0
...cause that currently block maven-dependency-plugin which needs also a
release..
Are there any objections ?
If not I will start on the Weekend...
Kind regards
Karl Heinz Marbaise
Hi,
I would like to add the following issue:
MNG-6123 - detect self references in POM and fail fast
Karl Heinz: Currently having an implementation but currently conflicts
with some IT's cause they are using self referencing dependencies.
Moved it to "3.5.1-candidate"...
Kind regards
Karl
Github user ifedorenko commented on the issue:
https://github.com/apache/maven/pull/69
I am dead serious. I am not at liberty to disclose exact numbers, but lets
say our main codebase is in the same ballpark if we allow some room for growth.
So 5K modules is not "aspirational pipe
Github user ndimiduk commented on the issue:
https://github.com/apache/maven/pull/69
> Implementation must scale well to 5K+ modules and 5K managed external
dependencies.
Are you serious? Such a project will never run, because of transitive
dependency version conflicts --
Some of them are assigned to me. I won't make it before Wednesday but
like to address them in 3.5.1.
Michael
Am 2017-04-27 um 12:55 schrieb Robert Scholte:
Let me start going through the list of candidates:
Maven - Version 3.5.1-candidate
** Sub-task
* [MNG-6186] - switch to improved
Github user ifedorenko commented on the issue:
https://github.com/apache/maven/pull/69
I still vote -1 on this change.
While I appreciate "dependency reduced pom" usecase, I'd like the following
two concerns addressed first:
* Mutated pom.xml files must not
+1 (non binding)
run "mvn clean install" from source zip
successfully built all of my webapps running Maven with Java9 (build 9-ea+163)
Thank you !
2017-04-27 11:36 GMT+02:00 Robert Scholte :
> +1
>
>
> On Wed, 26 Apr 2017 00:51:33 +0200, Karl Heinz Marbaise
Let me start going through the list of candidates:
Maven - Version 3.5.1-candidate
** Sub-task
* [MNG-6186] - switch to improved HawtJNI
Robert: Improvements have not been accepted yet, branch now has conflicts
** Bug
* [MNG-4347] - import-scoped dependencies of direct dependencies
+1
On Wed, 26 Apr 2017 00:51:33 +0200, Karl Heinz Marbaise
wrote:
Hi to all,
We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121=12338167
There are still a couple of issues left in JIRA:
Github user asfgit closed the pull request at:
https://github.com/apache/maven-site/pull/8
---
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
12 matches
Mail list logo