Hi,
The vote has passed with the following result:
+1 (binding): Karl Heinz Marbaise, Hervé Boutemy, Olivier Lamy, Kristian
Rosenvold
+1 (non binding): Andreas Gudian
I will promote the artifacts to the central repo.
Cheers
Tibor
-
+1
2014-12-24 17:03 GMT+01:00 :
> Hi,
>
> We solved 13 issues:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?
> projectId=10541&version=20814
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?
> reset=true&mode=hide&jqlQuery=project+
Hi,
increased memory to the following values:
-Xmx1024m -Xms256m -XX:MaxPermSize=768m
which has solved the problem...build #742 is Ok of the previous failing
tests.
https://builds.apache.org/job/maven-surefire-windows/742/
Kind regards
Karl Heinz Marbaise
On 12/27/14 1:09 PM, tibor17 wrote
Hi Karl,
Fails again but now only with two ITs. Let's redirect our discussion in JIRA
https://jira.codehaus.org/browse/SUREFIRE-1133
-
BR, tibor17
--
View this message in context:
http://maven.40175.n5.nabble.com/VOTE-Release-Apache-Maven-Surefire-Plugin-version-2-18-1-tp5820843p5821244.ht
Hi,
I have changed the memory configuration for the windows build as follows:
-Xmx1024m -Xms256m -XX:MaxPermSize=512m
Just retrigger the build after it's finish...
Kind regards
Karl Heinz Marbaise
On 12/27/14 11:59 AM, tibor17 wrote:
The surefire build maven-2.2.1 is successful again:
https:/
The surefire build maven-2.2.1 is successful again:
https://builds.apache.org/job/maven-surefire-mvn-2.2.1/
https://builds.apache.org/job/maven-surefire/
The windows surefire build still fails with java.lang.OutOfMemoryError:
PermGen space
https://builds.apache.org/job/maven-surefire-windows
--
+1
24. des. 2014 17:04 skrev :
> Hi,
>
> We solved 13 issues:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?
> projectId=10541&version=20814
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?
> reset=true&mode=hide&jqlQuery=project+%3D
+1
--
Olivier
On 25 Dec 2014 03:04, wrote:
> Hi,
>
> We solved 13 issues:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?
> projectId=10541&version=20814
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?
> reset=true&mode=hide&jqlQue
Hi Herve,
I have fixed the JDK version, please see
https://jira.codehaus.org/browse/SUREFIRE-1129
Should the change be move into other SVN repo as well?
-
BR, tibor17
--
View this message in context:
http://maven.40175.n5.nabble.com/VOTE-Release-Apache-Maven-Surefire-Plugin-version-2-18-1-
+1
notice the plugins still document JDK 1.4 as minimum [1] [2] [3]
IIUC, the minimum is JDK 1.5, no?
please confirm and I'll update maven-plugin-plugin configuration accordingly
Regards,
Hervé
[1]
http://maven.apache.org/surefire-archives/surefire-LATEST/maven-surefire-plugin/plugin-info.htm
Karl, my goal is to make happy user after 2.18. As I said this release is a
legal fix for the blocker appeared in 2.18. The issue appeared 25-50% of
plugin's lifetime.
Pls see my comments SUREFIRE-1128. If you guys find more issues, feel free
to post comments in JIRA. I am going to push the first
Hi,
so checked SHA1, Tested with Maven 3.0.5, 3.1.1, 3.2.1 without any issue...
Unfortunately testing with Maven 2.2.1 i got some failures:
Caused by: org.apache.maven.it.VerificationException: Exit code was
non-zero: 1; command line and log =
/usr/share/java/apache-maven-2.2.1/bin/mvn -e --ba
Upon the users pressure and frequent bug SUREFIRE-1121, the Surefire 2.18.1
release fixed the blocker SUREFIRE-1121, and other important major fixes
SUREFIRE-1114, SUREFIRE-1112.
-
BR, tibor17
--
View this message in context:
http://maven.40175.n5.nabble.com/VOTE-Release-Apache-Maven-Surefi
The tests in failsafe-plugin wasn't touched in 2.18 and 2.18.1.
The IT "jetty-war-test-failing" you have picked up was improved 5 months ago
which survived previous release too.
https://github.com/apache/maven-surefire/commits/master/maven-failsafe-plugin/src/it/jetty-war-test-failing/pom.xml
The
Hi,
so I have taken a look into the setup for Maven 2.2.1
where the memory settings look like this (which looks very similar to
the README.txt)...
-Xmx2g -Xms256m -XX:MaxPermSize=512m
Apart from that those build don't fail based on out of memory...
https://builds.apache.org/view/All/job/m
Good question, this was our problem whole year.
I was asking Kristian about the same, and AFAIK this was related to the
machine itself. One can see OutOfMemoryError: PermGen space
As this wasn't my priviledge to fix the system setup, i was not able to make
more here.
-
BR, tibor17
--
View th
Hi,
first just a question: Why are the CI builds
https://builds.apache.org/view/All/job/maven-surefire-mvn-2.2.1/
and those for windows:
https://builds.apache.org/view/All/job/maven-surefire-windows/
are failing ?
Is there a good reason to ignore those results ? Or are those failures
based o
Hi,
We solved 13 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&version=20814
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+
18 matches
Mail list logo
