GitHub user slachiewicz opened a pull request:
https://github.com/apache/maven/pull/137
[MNG-6069] Migrate to non deprecated parts of Commons CLI
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/slachiewicz/maven master
Alternati
yes, that's GitBox self service [1], easy to use, just:
1. start by choosing your PMC before doing any other change (or you may create
a "maven-maven-something.git" like I did)
2. change "GitHub notification list" to iss...@maven.apache.org
the only issue I see is the mix of Artifact Resolver on
Github user cstamas commented on the issue:
https://github.com/apache/maven-indexer/pull/19
@scela
With this PR against current master I have this result:
```
Tests run: 220, Failures: 3, Errors: 199, Skipped: 0
---
GitHub user sormuras opened a pull request:
https://github.com/apache/maven-plugins/pull/139
Support white-box modular test compilation
This is a proof-of-concept PR that introduces support for test sources
organized with module descriptors.
See motivation: https://twitter.
As a workaround you can check out the dependency-scope-maven-plugin we
wrote:
https://github.com/HubSpot/dependency-scope-maven-plugin
The initial motivation was avoiding NoClassDefFoundError when someone
accidentally puts a dep at test scope that is transitively required at
runtime. I made a pom
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 correct?
Well, this concept ensures t
Hervé might know... could be self-service on gitbox!
I have two repos to create after the Jenkins Server is upgraded on Sunday,
so let me know the process
On Thu 23 Nov 2017 at 16:13, Manfred Moser wrote:
> So how do I make this repo copy happen? An infra ticket or something like
> that?
>
> St
So how do I make this repo copy happen? An infra ticket or something like that?
Stephen Connolly wrote on 2017-11-22 23:53:
> On Thu 23 Nov 2017 at 04:20, Manfred Moser wrote:
>
>> Status update and questions:
>>
>> - demos are all now in master and part of the multi module build
>> - no chang
Github user eolivelli commented on the issue:
https://github.com/apache/maven-surefire/pull/168
@Tibor17 I have rewritten the patch and address your comment of not
altering the docs.
Tell me the next step in your vision, I will be happy to move forward and
finish this important t
Github user eolivelli commented on a diff in the pull request:
https://github.com/apache/maven-surefire/pull/168#discussion_r152835233
--- Diff:
surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/Java9FullApiIT.java
---
@@ -78,12 +83,13 @@ public void
shouldLo
Github user znerd commented on the issue:
https://github.com/apache/maven-scm/pull/56
@olamy Good point.
Suggested approach:
1. Introduce a configuration parameter now, e.g. `shallow` â and default
to `false`. This may not require a major version bump.
2. On the nex
GitHub user cstamas opened a pull request:
https://github.com/apache/maven-indexer/pull/21
Prepare for next major release (6.x)
Changes:
- update parent pom
- update dependencies (but remain Java7!)
- update sisu (drop sonatype guice, use vanilla guice)
- update to ma
Hi Maven developers,
I a trying to wrap my head around Maven's handling of dependency scopes
and was wondering the following: Is the test-classpath always a
super-sequence of the compile-classpath?
AFAICT, this is the case. However, my experiments (using Maven 3.5.2)
left me wondering whether I m
13 matches
Mail list logo
