Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/107#issuecomment-161430409
@juherr
IIUC testng 5.14.1 - 5.14.3 are buggy and can be excluded from the test set.
What exactly the bug is? You mean the ClassLoader issue? What did you
+1: from me
On Tue, Dec 1, 2015 at 11:12 PM, Karl Heinz Marbaise-3 [via Maven] <
ml-node+s40175n5853570...@n5.nabble.com> wrote:
> Hi,
>
> The vote has passed with the following result:
>
> +1 : Karl Heinz Marbaise, Robert Scholte, Michael Osipov
>
> PMC quorum: reached
>
> I will promote the art
Github user asfgit closed the pull request at:
https://github.com/apache/maven-integration-testing/pull/7
---
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 th
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/108#issuecomment-161337141
Try to build IT with your code with more realistic counts, but the
fail-fast feature would not be coherent due to concurrency problem across forks.
---
If your
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/108#issuecomment-161285312
@seanf Can you edd integration test?
You can add new test method to an existing IT.
---
If your project is set up for it, you can reply to this email and hav
I finally found the issue :
After adding the following dependencies the test works !
org.eclipse.aether
aether-connector-basic
1.0.2.v20150114
test
maybe a proxy problem ?
Jeff
On Wed, Dec 2, 2015 at 12:15 PM, Nathalie Keymeulen <
nathalie.keymeu...@agfa.com> wrote:
> Hi,
>
> I would like to use Harness for testing our maven plugin (maven 3)
>
> We are downloading an artifact to our local repository.
> When running the plugin the download i
Hi,
I would like to use Harness for testing our maven plugin (maven 3)
We are downloading an artifact to our local repository.
When running the plugin the download is correctly done but when I try to
test this behavior (download) with harness I get the following error when
running SetupMojoTest
On 2 December 2015 at 09:07, Fred Cooke wrote:
> "You can run maven with Java 8 right now, so it is not a change in any way
> for those users."
>
> This equates to ruling out developers who are forced to use older JDKs/JREs
> if you look at it the other way.
>
Actually you are misusing my argume
2015-12-02 9:38 GMT+01:00 Stephen Connolly
:
> If we look at our JVM company history, IIRC
>
> 2.0 = Java 1.4
> 2.1 = Java 1.4
> 2.2 = Java 1.5
> 3.0 = Java 1.5
> 3.1 = Java 1.6
> 3.2 = Java 1.6
> 3.3 = Java 1.7
>
>
It looks like 3.4 will be 1.7 and 3.5 1.8 :)
Having worked with 1.8 since long b
"You can run maven with Java 8 right now, so it is not a change in any way
for those users."
This equates to ruling out developers who are forced to use older JDKs/JREs
if you look at it the other way.
"I agree that jumping to Java 8 would be unwise. I think we can wait until
4.x. Don’t get me wr
If we look at our JVM company history, IIRC
2.0 = Java 1.4
2.1 = Java 1.4
2.2 = Java 1.5
3.0 = Java 1.5
3.1 = Java 1.6
3.2 = Java 1.6
3.3 = Java 1.7
(I may have the jump versions out as this is from memory on my phone)
So historically we have viewed bumping the minimum Java version as a minor
ch
12 matches
Mail list logo
