Hi again,

In order to investigate a bit more this strange behavior, I downloaded the apache-maven archive by hand (from http://search.maven.org/#artifactdetails|org.apache.maven|apache-maven|3.2.3|pom). Note that this is not the version that I have currently installed in my linux. I'm using 3.2.5. I put this file with 7Mb in the local repository and then the takari-lifecycle tests passed properly.

Then I removed apache-maven again and tried to build takari-lifecycle one more time. again it tried to download 3.2.3 (don't know why) and it ended corrupted. that failed the takari-lifecycle tests again.

It seems that exists some issue related to downloading this apache-maven archive.


regards,

Cristiano

On 21-02-2015 20:40, Cristiano Gavião wrote:
Hi Igor,

That is strange...

I deleted all versions of apache-maven from local my repo.

Then I built (package) the takari-lifecycle (without testing) and no version of apache-maven was downloaded.

But when I tried mvn install, the version 3.2.3 was downloaded but it has only 178 bytes.

Don't know if it was downloaded wrongly or the file was corrupted by other means.




On 21-02-2015 18:48, Igor Fedorenko wrote:
Looks like maven distribution gz is corrupted in your local repo. See if
removing ~/.m2/repository/org/apache/maven/apache-maven directory will
solve the problem for you. If not, file github issue like Jason suggested.

--
Regards,
Igor

On 2015-02-21 16:08, Cristiano Gavião wrote:
Hello,

I'm trying to learn how to use the new testing tools provided by takari.
Started by the tests in takari-lifecycle-plugin-its from github master
branch.

but I'm getting errors when running the build. I'm using maven 3.2.5 in
linux with java 1.8.0_31:

    Tests in error:
BasicTest.initializationError » IO Input is not in the .gz format CompileAnnotationProcessingTest.initializationError » IO Input is
    not in the ....
CompileClasspathTest.initializationError » IO Input is not in the
    .gz format
       CompileMultimoduleTest.initializationError » IO Input is not in
    the .gz format
       FilteringResourcesTest.initializationError » IO Input is not in
    the .gz format
       MultimoduleSkipInstallDeployTest.initializationError » IO Input
    is not in the ...
PomPackagingTest.initializationError » IO Input is not in the .gz
    format



details of one run:

    Running io.tesla.maven.plugins.test.BasicTest
    Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
    0.007 sec <<< FAILURE! - in io.tesla.maven.plugins.test.BasicTest
    initializationError(io.tesla.maven.plugins.test.BasicTest) Time
    elapsed: 0.001 sec  <<< ERROR!
    java.io.IOException: Input is not in the .gz format
         at

org.apache.commons.compress.compressors.gzip.GzipCompressorInputStream.init(GzipCompressorInputStream.java:162)

         at

org.apache.commons.compress.compressors.gzip.GzipCompressorInputStream.<init>(GzipCompressorInputStream.java:135)

         at

org.apache.commons.compress.compressors.gzip.GzipCompressorInputStream.<init>(GzipCompressorInputStream.java:100)

         at

io.takari.maven.testing.executor.junit.MavenVersionResolver.unarchive(MavenVersionResolver.java:70)

         at

io.takari.maven.testing.executor.junit.MavenVersionResolver.resolve(MavenVersionResolver.java:60)

         at

io.takari.maven.testing.executor.junit.MavenJUnitTestRunner.getRunners(MavenJUnitTestRunner.java:131)

         at

io.takari.maven.testing.executor.junit.MavenJUnitTestRunner.<init>(MavenJUnitTestRunner.java:89)

         at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at

sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)

         at

sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

at java.lang.reflect.Constructor.newInstance(Constructor.java:408)
         at

org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:29)

         at

org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:21)

         at

org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)

         at

org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)

         at

org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)

         at

org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:26)
         at

org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)

         at

org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)

         at

org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)

         at

org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)

         at

org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)

         at

org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)

         at

org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)

would be these errors caused by java 8 ?

regards,

Cristiano


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to