Github user asfgit closed the pull request at:
https://github.com/apache/maven/pull/138
---
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
GitHub user slachiewicz opened a pull request:
https://github.com/apache/maven/pull/138
MNG-6306 remove Guava usage from maven-resolver-provider
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/slachiewicz/maven feature/MNG-6306
Github user arteam commented on the issue:
https://github.com/apache/maven-scm/pull/56
I like the proposal, but I am a a little bit confused. Does the new
parameter should be added to the `executeCheckOutCommand` method (like
`recursive`) and be implemented by the all
GitHub user cstamas opened a pull request:
https://github.com/apache/maven-indexer/pull/23
Full codebase reformat, minor cleanup, no code/logic change
Reformatted full codebase, as there was mixed formatting, and
checkstyle did report a huge amount of errors. Now, mostly the
Github user cstamas closed the pull request at:
https://github.com/apache/maven-indexer/pull/21
---
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Github user cstamas commented on the issue:
https://github.com/apache/maven-indexer/pull/21
Manually merged, only 1st two commits from this PR, while 3rd commit pulled
out and merged separately
(https://github.com/apache/maven-indexer/commit/339eec6052a74fea91a99da2e33cbbd6a95aee3f)
Github user asfgit closed the pull request at:
https://github.com/apache/maven-indexer/pull/22
---
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
GitHub user cstamas opened a pull request:
https://github.com/apache/maven-indexer/pull/22
MINDEXER-108: Lift the wildcard prefix restriction
MINDEXER-108: lift the prefix restriction
Historically Lucene needed this, but latest versions
can cope with it. This is still OOM
Jonathan Haber wrote:
> As a workaround you can check out the dependency-scope-maven-plugin we
> wrote:
> https://github.com/HubSpot/dependency-scope-maven-plugin
Thanks for the pointer; this indeed looks like a useful plugin.
That being said, I wasn't experiencing this bug/misfeature myself.
Robert Scholte wrote:
> You're hitting MNG-5739
>
> Within a dependency-tree a groupId+artifactId is unique (nearest wins).
> Such a dependency has 1 version, but also 1 scope.
> By setting it explicit to test, you reduce the scope and it is not
> available during compile anymore.
>
> Is this
10 matches
Mail list logo
