Am 2016-04-17 um 20:53 schrieb Andreas Sewe:
Hi,
Please go ahead and test it.
Jenkins does not use the script as it seems:
[maven-3.x] $
/home/jenkins/jenkins-slave/tools/hudson.model.JDK/jdk-1.7u51/bin/java
-Xmx2g -Xms256m -XX:MaxPermSize=512m -cp
/home/jenkins/jenkins-slave/maven3-agent.jar:
Am 04/18/16 um 01:39 schrieb Christian Schulte:
> Am 04/17/16 um 18:08 schrieb Bernd Eckenfels:
>> Hello,
>>
>> I wondered about that as well. It was discussed 2012 on maven-dev. The
>> statement looks like this:
>>
>> # Runtime r = Runtime.getRuntime();
>> # long MB = 1024 * 1024;
>> # "Final Memo
Am 04/17/16 um 18:08 schrieb Bernd Eckenfels:
> Hello,
>
> I wondered about that as well. It was discussed 2012 on maven-dev. The
> statement looks like this:
>
> # Runtime r = Runtime.getRuntime();
> # long MB = 1024 * 1024;
> # "Final Memory: " + ( r.totalMemory() - r.freeMemory() ) / MB + "M/"
>
> Please go ahead and test it.
>
I'll do it on my side but not before 1 week
>
> Jenkins does not use the script as it seems:
> [maven-3.x] $
> /home/jenkins/jenkins-slave/tools/hudson.model.JDK/jdk-1.7u51/bin/java
> -Xmx2g -Xms256m -XX:MaxPermSize=512m -cp
> /home/jenkins/jenkins-slave/maven3
Hi,
> Please go ahead and test it.
>
> Jenkins does not use the script as it seems:
> [maven-3.x] $
> /home/jenkins/jenkins-slave/tools/hudson.model.JDK/jdk-1.7u51/bin/java
> -Xmx2g -Xms256m -XX:MaxPermSize=512m -cp
> /home/jenkins/jenkins-slave/maven3-agent.jar:/home/jenkins/jenkins-slave/tools/
Am 2016-04-17 um 18:19 schrieb Jason van Zyl:
You answered with a condition and an assumption. I’ll be more
specific.
On a Mac where discovery works well, a new user installs Java, brew
installs Maven and it works. Does this still work?
I have requested everyone to test the branch as I do not
You answered with a condition and an assumption. I’ll be more specific.
On a Mac where discovery works well, a new user installs Java, brew installs
Maven and it works. Does this still work?
I will check our CI servers, but if those stop working after an upgrade I would
be an unhappy user as wo
Hello,
I wondered about that as well. It was discussed 2012 on maven-dev. The
statement looks like this:
# Runtime r = Runtime.getRuntime();
# long MB = 1024 * 1024;
# "Final Memory: " + ( r.totalMemory() - r.freeMemory() ) / MB + "M/" +
r.totalMemory() / MB + "M"
So this basically prints the cu
Hi to all,
i have a question concerning the memory consumption...
If i run maven with the same JDK and the same reactor and build with the
same parameter and plugins...
will the printout at the end of the build (Final Memory) something
realiable about the consumption of the JVM during the bu
Hi Rory,
I have an issue with Multi Release JARs that I won't call a show stopper, but
I'd like to know what happens.
I upgraded our Maven multi-release demo [1] to build with JDK 9, then I added
tests that run the resulting jar with JRE 7, 8 and 9. And there is no runtime
that is picking newe
Am 2016-04-17 um 17:24 schrieb Jason van Zyl:
So will the proposed behavior be I upgrade Maven, I don’t have JAVA_HOME set
manually and Maven will error out?
No, if Java in PATH is a JDK, it will continue to work as usual. This is
probably the case on most dev machines.
Michael
On Apr 15,
So will the proposed behavior be I upgrade Maven, I don’t have JAVA_HOME set
manually and Maven will error out?
> On Apr 15, 2016, at 1:34 PM, Michael Osipov wrote:
>
> Hi folks,
>
> we all know that people once in a while complain that my JAVA_HOME is not
> properly discovered on $PLATFORM,
Hi,
We solved 16 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526&version=12334171
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MJAR%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
Staging
On Sunday 17 April 2016, Stephen Connolly
wrote:
> So the following is not of concern to the maven project - as we do not
> ship a JRE - but anyone who does ship a JRE cannot do so and ship the
> annotations *claimed* to be JSR-305
Now it could very easily become our problem,
For example if we
So the following is not of concern to the maven project - as we do not ship
a JRE - but anyone who does ship a JRE cannot do so and ship the
annotations *claimed* to be JSR-305
This is because the JRE binary license specifically contains a clause
mandating that you do not add or redefine classes i
15 matches
Mail list logo
