Yesterday I clarified an issue with Karl-Heinz. It was a specific environment issue appeared when using .mavenrc script (maybe without using global java_home).
Hacking :-) in two ways see [1]: 1. Java code changed only in integration tests. Loading MANIFEST via JarFile instead of ClassLoader's resource stream; 2. Integration tests framework only - SurefireLauncher. Since now the env.JAVA_HOME in forked JVM of integration-test is inherited from main process of the build - not the global JAVA_HOME. [1] https://github.com/apache/maven-surefire/commit/0c2656f71ca014d362b185c4bcf034c80b85b48d On Tue, Oct 6, 2015 at 7:37 PM, Karl Heinz Marbaise <[email protected]> wrote: > Hi Tibor, > > On 10/6/15 5:07 PM, Tibor Digana wrote: > >> In this case I should open a parallel thread having a look in your >> environment setup. >> Let's do it in #maven-dev chat between 7 - 11 pm CET. >> > > I'm on the #maven-dev chat... > > > Kind regards > Karl Heinz Marbaise > > >> On Tue, Oct 6, 2015 at 4:56 PM, Karl Heinz Marbaise <[email protected]> >> wrote: >> >> Hi Tibor, >>> >>> >>> I already tested as the CI configuration...see here... >>> >>> >>> On 10/6/15 2:40 PM, Karl Heinz Marbaise wrote: >>> >>> Hi Tibor, >>>> >>>> .... >>> >>> >>>> I have tested with Maven 3.0.5 via mvn -Prun-its clean verify and got >>>> the same issue as before... >>>> >>>> Furthermore i have retested via this command line on Maven 3.0.5 >>>> >>>> mvn -B -U -Dsurefire.useFile=false -Dfailsafe.useFile=false -Prun-its >>>> clean install >>>> >>>> and the issue is the same...so installation is not the cause of the >>>> problem... >>>> >>>> >>>> Kind regards >>>> Karl Heinz Marbaise >>>> >>>> >>>> >>>> >>>> On Tue, Oct 6, 2015 at 12:10 PM, Karl Heinz Marbaise <[email protected] >>>>> <mailto:[email protected]>> wrote: >>>>> >>>>> Hi, >>>>> >>>>> First building with Maven 2.2.1 is not possible...I don't really >>>>> care but the pom says 2.2.1 minimum...(just for the record)... >>>>> >>>>> I have tested via: >>>>> >>>>> mvn -Prun-its clean verify >>>>> >>>>> with Maven 3.0.5 (JDK 6), unfortunately i have found an issue in >>>>> the >>>>> integration test which has failed....I have attached the failing >>>>> integration-test-result output.... >>>>> >>>>> This is my environment: >>>>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; >>>>> 2013-02-19 14:51:28+0100) >>>>> Maven home: /usr/share/maven >>>>> Java version: 1.6.0_65, vendor: Apple Inc. >>>>> Java home: >>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home >>>>> Default locale: en_US, platform encoding: MacRoman >>>>> OS name: "mac os x", version: "10.8.5", arch: "x86_64", family: >>>>> "mac" >>>>> >>>>> Kind regards >>>>> Karl Heinz Marbaise >>>>> >>>>> >>>>> On 10/6/15 4:39 AM, Tibor Digana wrote: >>>>> >>>>> Hi, >>>>> >>>>> We solved 50 issues: >>>>> >>>>> >>>>> >>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12331679 >>>>> >>>>> >>>>> There are still a couple of issues left in JIRA: >>>>> >>>>> >>>>> >>>>> https://issues.apache.org/jira/i#issues/?jql=project+%3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC >>>>> >>>>> >>>>> Staging repo: >>>>> https://repository.apache.org/content/repositories/maven-1212 >>>>> >>>>> >>>>> >>>>> https://repository.apache.org/service/local/repositories/maven-1212/content/org/apache/maven/surefire/surefire/2.19/surefire-2.19-source-release.zip >>>>> >>>>> >>>>> Source release checksum(s): >>>>> surefire-2.19-source-release.zip sha1: >>>>> 55b5b8d88f31be56347b7c6c16999bfde0d39d00 >>>>> >>>>> Staging site: >>>>> http://maven.apache.org/surefire-archives/surefire-LATEST/ >>>>> >>>>> Guide to testing staged releases: >>>>> >>>>> http://maven.apache.org/guides/development/guide-testing-releases.html >>>>> >>>>> Vote open for 72 hours. >>>>> >>>>> [ ] +1 >>>>> [ ] +0 >>>>> [ ] -1 >>>>> >>>>> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Cheers Tibor
