Dion Gillard wrote on Tuesday, October 25, 2005 7:11 AM:
M1 or M2?
If M1, use -Dprop=value when launching
or from inside jelly code:
${systemScope.put('java.awt.headless', 'true')}
or use follwoing entries in the project.properties:
maven.junit.sysproperties=java.awt.headless
Just noticed that this is still failing. I am unable to reproduce the
problem. Please see my previous mail concerning this problem. It would
appear on the surface to be an issue with how Ant generates the
manifest file in the derbyjarwithoutosgi target. Is there any way
that I can get access to
On Tue, 25 Oct 2005, Dion Gillard [EMAIL PROTECTED] wrote:
M1 or M2?
1.0.2 is installed on vmgump.
If M1, use -Dprop=value when launching
We use the wrapper script, how would I inject a system property that
way (in Ant I could set the ANT_ARGS env variable).
Stefan
On Tue, 25 Oct 2005, Jörg Schaible
[EMAIL PROTECTED] wrote:
or use follwoing entries in the project.properties:
maven.junit.sysproperties=java.awt.headless
java.awt.headless=true
Thanks. I'll take a look at it at some point, I'll probably need to
modify the Gump/maven integration code for
Use
MAVEN_OPTS=-Dprop=value
On 10/26/05, Stefan Bodewig [EMAIL PROTECTED] wrote:
On Tue, 25 Oct 2005, Dion Gillard [EMAIL PROTECTED] wrote:
M1 or M2?
1.0.2 is installed on vmgump.
If M1, use -Dprop=value when launching
We use the wrapper script, how would I inject a system property
Dear Gumpmeisters,
The following 1 notifys should have been sent
*** G U M P
[EMAIL PROTECTED]: Project xstream (in module xstream) failed
*** G U M P
[EMAIL PROTECTED]:
Dear Gumpmeisters,
The following 1 notifys should have been sent
*** G U M P
[EMAIL PROTECTED]: Project xstream (in module xstream) failed
*** G U M P
[EMAIL PROTECTED]: