On 28 December 2014 at 08:46, Jason van Zyl wrote:
> Would certainly be easier to have it at Apache at this point. I don't
> think it's particularly hard, just time consuming. I think the only safe
> option is exporting the entire database and removing all projects except
> ours. It will probably
I checked out maven-wagon under windows and commit via my Eclipse Luna,
however it seems like I screw up the line ending. It is committed as
windows mode at git
However do I go about fix this issue?
Thanks
-D
On Sat, Dec 27, 2014 at 3:35 PM, wrote:
> Repository: maven-wagon
> Updated Branches
Would certainly be easier to have it at Apache at this point. I don't think
it's particularly hard, just time consuming. I think the only safe option is
exporting the entire database and removing all projects except ours. It will
probably take several attempts and there are a lot of projects at
> -Original Message-
> From: Benson Margulies
> Sent: Saturday, December 27, 2014 13:01
>
> On Sat, Dec 27, 2014 at 12:57 PM, Karl Heinz Marbaise
> wrote:
> > Hi Benson,
> >
> > On 12/27/14 5:59 PM, Benson Margulies wrote:
> >>
> >> On Sat, Dec 27, 2014 at 11:45 AM, Michael Osipov
>
>
Github user Tibor17 closed the pull request at:
https://github.com/apache/maven-surefire/pull/76
---
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 the feature
Hi all,
this week I, Hervé and Karl-Heinz decided to visit fosdem[1] this year to
meet each other IRL[2].
The decision was way past the deadline of the CfP, so we can't claim a
room to talk with our users.
The plan is to meet each other on Sunday, February 1st in Brussels.
If there are other
On Sat, Dec 27, 2014 at 12:57 PM, Karl Heinz Marbaise wrote:
> Hi Benson,
>
> On 12/27/14 5:59 PM, Benson Margulies wrote:
>>
>> On Sat, Dec 27, 2014 at 11:45 AM, Michael Osipov
>> wrote:
>>>
>>> Am 2014-12-27 um 17:38 schrieb Benson Margulies:
I've re-asked infra if there is any p
Hi Benson,
On 12/27/14 5:59 PM, Benson Margulies wrote:
On Sat, Dec 27, 2014 at 11:45 AM, Michael Osipov wrote:
Am 2014-12-27 um 17:38 schrieb Benson Margulies:
I've re-asked infra if there is any possible path to moving all the
JIRA projects to ASF infrastructure. I'll report back.
Very
Hi Kristian,
I am +1 for any Release Manager wanting to up the minimum Java version
to 1.6 for any of our components, on one condition: if there are any
bugs fixed since the last release of the component, then please do a
final Java 5 compatible release of the component before moving it to
Java 6.
On Sat, Dec 27, 2014 at 11:45 AM, Michael Osipov wrote:
> Am 2014-12-27 um 17:38 schrieb Benson Margulies:
>>
>> I've re-asked infra if there is any possible path to moving all the
>> JIRA projects to ASF infrastructure. I'll report back.
>
>
> Very good! I think that most people are confused why
Am 2014-12-27 um 17:38 schrieb Benson Margulies:
I've re-asked infra if there is any possible path to moving all the
JIRA projects to ASF infrastructure. I'll report back.
Very good! I think that most people are confused why all Maven related
stuff is not on *.apache.org but on codehaus.org
I've re-asked infra if there is any possible path to moving all the
JIRA projects to ASF infrastructure. I'll report back.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.
GitHub user ferstl opened a pull request:
https://github.com/apache/maven-release/pull/6
[MRELEASE-896] Depcreate and disable useReleaseProfile
There are some indications [1, 2] that the release-profile will disappear
from Maven's super POM somewhen in the future. There was also an
Did we already cover what we want to keep supporting via Toolchains?
We would have to take some care in Surefire if we wanted to keep some
support for <1.6 when using toolchains or when allowing users to configure
a different JVM.
2014-12-25 15:57 GMT+01:00 Karl Heinz Marbaise :
> Hi,
>
> let
+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
--
Github user asfgit closed the pull request at:
https://github.com/apache/maven-surefire/pull/77
---
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 the feature
+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
21 matches
Mail list logo
