RE: How do I set a Java system property for a Maven build?

2005-10-26 Thread Jörg Schaible
Hi Stefan,

Stefan Bodewig wrote on Wednesday, October 26, 2005 6:13 AM:

 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 this.

 We currently don't touch project.properties, only
 build.properties. Would setting the properties there have the same
 effect? 

Depends. Maven reads a build.properties from the user's home dir. I cannot say 
under what user you're running Maven, but if you put them there, they are 
picked up.

- Jörg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: How do I set a Java system property for a Maven build?

2005-10-26 Thread Dion Gillard
On 10/26/05, Stefan Bodewig [EMAIL PROTECTED] wrote:
 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 this.

 We currently don't touch project.properties, only build.properties.
 Would setting the properties there have the same effect?

Yes.


 Stefan

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




--
http://www.multitask.com.au/people/dion/
You are going to let the fear of poverty govern your life and your
reward will be that you will eat, but you will not live. - George
Bernard Shaw

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: How do I set a Java system property for a Maven build?

2005-10-26 Thread Jörg Schaible
Jörg Schaible wrote on Wednesday, October 26, 2005 9:59 AM:

 Hi Stefan,
 
 Stefan Bodewig wrote on Wednesday, October 26, 2005 6:13 AM:
 
 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 this.
 
 We currently don't touch project.properties, only build.properties.
 Would setting the properties there have the same effect?
 
 Depends. Maven reads a build.properties from the user's home
 dir. I cannot say under what user you're running Maven, but
 if you put them there, they are picked up.

Correction. Dion is right, Maven will also read build.properties from the 
current dir.

- Jörg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



BATCH: All dressed up, with nowhere to go...

2005-10-26 Thread gump
Dear Gumpmeisters,

The following 1 notifys should have been sent

*** G U M P
[EMAIL PROTECTED]: Project portals-bridges-jsf (in module portals-bridges) 
failed
*** G U M P
[EMAIL PROTECTED]: Project portals-bridges-jsf (in module portals-bridges) 
failed
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project portals-bridges-jsf has an issue affecting its community integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- portals-bridges-jsf :  Support for JSR168 compliant Portlet development


Full details are available at:

http://vmgump.apache.org/gump/public/portals-bridges/portals-bridges-jsf/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [portals-bridges-jsf-26102005.jar] identifier set to 
project name
 -DEBUG- Dependency on portals-pluto-api exists, no need to add for property 
maven.jar.portlet-api.
 -DEBUG- Dependency on jakarta-servletapi-5-servlet exists, no need to add for 
property maven.jar.servletapi.
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/portals-bridges/jsf/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/portals-bridges/jsf/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/portals-bridges/jsf/project.properties
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/portals-bridges/portals-bridges-jsf/gump_work/build_portals-bridges_portals-bridges-jsf.html
Work Name: build_portals-bridges_portals-bridges-jsf (Type: Build)
Work ended in a state of : Failed
Elapsed: 3 secs
Command Line: maven --offline jar 
[Working Directory: /usr/local/gump/public/workspace/portals-bridges/jsf]
CLASSPATH: 
/opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-26102005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-26102005.jar:/usr/local/gump/public/workspace/jakarta-servletapi-5/jsr154/dist/lib/servlet-api.jar:/usr/local/gump/public/workspace/myfaces/api/build/dist/myfaces-api.jar:/usr/local/gump/public/workspace/portals-bridges/common/target/portals-bridges-common-26102005.jar:/usr/local/gump/public/workspace/portals-pluto/api/target/portlet-api-1.0.jar
-
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.2

You are working offline so the build will continue, but 
portals-bridges-common-0.4-SNAPSHOT.jar may be out of date!
The build cannot continue because of the following unsatisfied dependency:

myfaces-api-1.1.0.jar

Total time: 2 seconds
Finished at: Wed Oct 26 13:08:42 PDT 2005

-

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/portals-bridges/portals-bridges-jsf/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/portals-bridges/portals-bridges-jsf/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 18000826102005, vmgump.apache.org:vmgump-public:18000826102005
Gump E-mail Identifier (unique within run) #1.


--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



BATCH: All dressed up, with nowhere to go...

2005-10-26 Thread gump
Dear Gumpmeisters,

The following 1 notifys should have been sent

*** G U M P
[EMAIL PROTECTED]: Project portals-bridges-jsf (in module portals-bridges) 
failed
*** G U M P
[EMAIL PROTECTED]: Project portals-bridges-jsf (in module portals-bridges) 
failed
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project portals-bridges-jsf has an issue affecting its community integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- portals-bridges-jsf :  Support for JSR168 compliant Portlet development


Full details are available at:

http://vmgump.apache.org/gump/public/portals-bridges/portals-bridges-jsf/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [portals-bridges-jsf-26102005.jar] identifier set to 
project name
 -DEBUG- Dependency on portals-pluto-api exists, no need to add for property 
maven.jar.portlet-api.
 -DEBUG- Dependency on jakarta-servletapi-5-servlet exists, no need to add for 
property maven.jar.servletapi.
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/portals-bridges/jsf/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/portals-bridges/jsf/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/portals-bridges/jsf/project.properties
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/portals-bridges/portals-bridges-jsf/gump_work/build_portals-bridges_portals-bridges-jsf.html
Work Name: build_portals-bridges_portals-bridges-jsf (Type: Build)
Work ended in a state of : Failed
Elapsed: 3 secs
Command Line: maven --offline jar 
[Working Directory: /usr/local/gump/public/workspace/portals-bridges/jsf]
CLASSPATH: 
/opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-26102005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-26102005.jar:/usr/local/gump/public/workspace/jakarta-servletapi-5/jsr154/dist/lib/servlet-api.jar:/usr/local/gump/public/workspace/myfaces/api/build/dist/myfaces-api.jar:/usr/local/gump/public/workspace/portals-bridges/common/target/portals-bridges-common-26102005.jar:/usr/local/gump/public/workspace/portals-pluto/api/target/portlet-api-1.0.jar
-
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.2

You are working offline so the build will continue, but 
portals-bridges-common-0.4-SNAPSHOT.jar may be out of date!
The build cannot continue because of the following unsatisfied dependency:

myfaces-api-1.1.0.jar

Total time: 2 seconds
Finished at: Wed Oct 26 13:08:42 PDT 2005

-

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/portals-bridges/portals-bridges-jsf/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/portals-bridges/portals-bridges-jsf/atom.xml

== Gump Tracking Only ===
Produced by Gump version 2.2.
Gump Run 18000826102005, vmgump.apache.org:vmgump-public:18000826102005
Gump E-mail Identifier (unique within run) #1.


--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Derby build (Re: BATCH: All dressed up, with nowhere to go...)

2005-10-26 Thread Stefan Bodewig
On Tue, 25 Oct 2005, Andrew McIntyre [EMAIL PROTECTED] wrote:

 Just noticed that this is still failing. I am unable to reproduce
 the problem.

At least on vmgump there is an empty line in smf.mf between
Bundle-Version in the main section and Sealed: true.  This line makes
the Sealed attribute the first one of a new section, which in turn
makes the manifest invalid.

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: How do I set a Java system property for a Maven build?

2005-10-26 Thread Stefan Bodewig
On Wed, 26 Oct 2005, Dion Gillard [EMAIL PROTECTED] wrote:

 MAVEN_OPTS=-Dprop=value

Yep, this gave me the least intrusive way to set it, using .mavenrc.

I'll probably have to go the build.properties way in addition for
forked junit tests.

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Derby build (Re: BATCH: All dressed up, with nowhere to go...)

2005-10-26 Thread Andrew McIntyre


On Oct 26, 2005, at 9:22 PM, Stefan Bodewig wrote:


At least on vmgump there is an empty line in smf.mf between
Bundle-Version in the main section and Sealed: true.  This line makes
the Sealed attribute the first one of a new section, which in turn
makes the manifest invalid.


That's what I suspected, but any idea why Ant would do that on  
vmgump, but not elsewhere?


Here's the first few lines of the manifest task:

manifest file=${derby.jar.dir}/lists/smf.mf
  attribute name=Bundle-Vendor value=Apache Software  
Foundation/
  attribute name=Bundle-Name value=Apache Derby ${major}.$ 
{minor}/
  attribute name=Bundle-Version value=${major}.${minor}.$ 
{maint}.${changenumber}/


attribute name=Sealed value=true/
section name=org/apache/derby/impl/tools/sysinfo/
  attribute name=Sealed value=false/
/section
..
/manifest

What I get is:

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.6.2
Created-By: 1.4.2
Bundle-Vendor: Apache Software Foundation
Bundle-Name: Apache Derby 10.2
Bundle-Version: 10.2.0.233223
Sealed: true

Name: org/apache/derby/impl/tools/sysinfo/
Sealed: false
..

Any clues? Maybe an old, invalid manifest hanging around that's not  
being overwritten?


Thanks,
andrew


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]