It's not this case. Benson, feel free to participate in surefire together with me. We have high ambitions in surefire 3.0 and there I am looking for every developer who may help me.
On Tue, Oct 6, 2015 at 2:47 PM, Benson Margulies <[email protected]> wrote: > On Tue, Oct 6, 2015 at 8:40 AM, Karl Heinz Marbaise <[email protected]> > wrote: > > Hi Tibor, > > > > On 10/6/15 1:01 PM, Tibor Digana wrote: > >> > >> Hm, strange, your command is the basic on however I always use install > >> instead of verify because the artifacts need to be in local repo, try > >> with that please. > > > > > > If you really need an install during a multi module build there is > something > > wrong with the dependencies between the modules...reactor order is not > > correct...a mvn clean verify should always work... > > There are counter-examples to this principle: if you need _the actual > jar_ and not just target/classes, it won't necessarily be there. I > don't know if surefire has any situation like this. > > > > > > >> Can you compare with our build park > >> https://builds.apache.org/job/maven-surefire-mvn-2.2.1/ > > > > > > Furthermore i have taken a look into the Jenkins jobs. It runs the build > > with Maven 3.0.5 and *not* with Maven 2.2.1...You select via > -Pmaven-2.2.1 a > > profile which downloads Maven 2.2.1 (surefire-integration-test) and use > it > > for the integrations tests...So we need to define build miniumum to 3.0.5 > > ....Using prerequisites / maven-enforcer rule...That is not really a > problem > > for this release... > > > > > > 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] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Cheers Tibor
