Brett Porter wrote:
yep, there was a couple more libraries it needed - it's all working now.
Great! Thanks!
Oliver
On 31/08/2007, James Carman <[EMAIL PROTECTED]> wrote:
The headless option won't fix all problems. It depends on what you're
doing. Can we install the X Virtual Frame Buffer
I just had to install it - it's not running.
On 01/09/2007, James Carman <[EMAIL PROTECTED]> wrote:
> So, we're using xvfb?
>
> On 8/31/07, Brett Porter <[EMAIL PROTECTED]> wrote:
> > yep, there was a couple more libraries it needed - it's all working now.
> >
> > On 31/08/2007, James Carman <[EMA
So, we're using xvfb?
On 8/31/07, Brett Porter <[EMAIL PROTECTED]> wrote:
> yep, there was a couple more libraries it needed - it's all working now.
>
> On 31/08/2007, James Carman <[EMAIL PROTECTED]> wrote:
> > The headless option won't fix all problems. It depends on what you're
> > doing. Can
yep, there was a couple more libraries it needed - it's all working now.
On 31/08/2007, James Carman <[EMAIL PROTECTED]> wrote:
> The headless option won't fix all problems. It depends on what you're
> doing. Can we install the X Virtual Frame Buffer (xvfb) on the linux
> box? That usually fixe
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=3105&projectId=161
Build statistics:
State: Failed
Previous State: Failed
Started at: Fri 31 Aug 2007 06:48:27 -0700
Finished at: Fri 31 Aug 2007 06:49:00 -0700
Total time: 33s
Build Trigger: Forced
Build Numbe
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=3104&projectId=161
Build statistics:
State: Failed
Previous State: Failed
Started at: Fri 31 Aug 2007 06:42:16 -0700
Finished at: Fri 31 Aug 2007 06:43:14 -0700
Total time: 58s
Build Trigger: Forced
Build Numbe
The headless option won't fix all problems. It depends on what you're
doing. Can we install the X Virtual Frame Buffer (xvfb) on the linux
box? That usually fixes my builds/servers when they need a graphics
environment, because it tricks the operating system into thinking
there is one.
On 8/31/
Well, we're building with:
Operating system : Linux(unknown)
Java Home version :
java version "1.4.2_15"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_15-b02)
Java HotSpot(TM) Client VM (build 1.4.2_15-b02, mixed mode)
I'm not sure why it's not working
Jörg Schaible wrote on Friday, August 31, 2007 9:00 AM:
> Brett Porter wrote on Friday, August 31, 2007 2:54 AM:
>
>> It actually works under Java 5 or Java 6 - I thought the headless
>> property was available in 1.4, but I don't see it in the API docs.
>
> Since 1.4.2:
> http://java.sun.com/j2s
Brett Porter wrote on Friday, August 31, 2007 2:54 AM:
> It actually works under Java 5 or Java 6 - I thought the headless
> property was available in 1.4, but I don't see it in the API docs.
Since 1.4.2:
http://java.sun.com/j2se/1.4.2/docs/guide/awt/AWTChanges.html#headless
- Jörg
It actually works under Java 5 or Java 6 - I thought the headless
property was available in 1.4, but I don't see it in the API docs.
Cheers,
Brett
On 31/08/2007, Oliver Heger <[EMAIL PROTECTED]> wrote:
> Ben Speakmon wrote:
> > I think gets passed to the running application, not the VM. Try
> >
Ben Speakmon wrote:
I think gets passed to the running application, not the VM. Try
instead.
There's an example here:
http://maven.apache.org/plugins/maven-surefire-plugin/examples/system-properties.html
Unfortunately, this doesn't help either:
org.apache.maven.plugins
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=3070&projectId=161
Build statistics:
State: Failed
Previous State: Failed
Started at: Thu 30 Aug 2007 13:30:34 -0700
Finished at: Thu 30 Aug 2007 13:31:15 -0700
Total time: 41s
Build Trigger: Schedule
Build Num
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=2982&projectId=161
Build statistics:
State: Failed
Previous State: Failed
Started at: Thu 30 Aug 2007 08:43:32 -0700
Finished at: Thu 30 Aug 2007 08:44:08 -0700
Total time: 35s
Build Trigger: Forced
Build Numbe
I think gets passed to the running application, not the VM. Try
instead.
There's an example here:
http://maven.apache.org/plugins/maven-surefire-plugin/examples/system-properties.html
On 8/29/07, Oliver Heger <[EMAIL PROTECTED]> wrote:
>
> Hm, the following modifications of the pom did not show
Hm, the following modifications of the pom did not show any effect:
org.apache.maven.plugins
maven-surefire-plugin
once
-Djava.awt.headless=true
Is there anything wrong with this setup? What else could be the pro
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=2892&projectId=161
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 29 Aug 2007 13:30:45 -0700
Finished at: Wed 29 Aug 2007 13:32:28 -0700
Total time: 1m 43s
Build Trigger: Schedule
Build
Junit tests are forked by Maven, so Continuum can't really set that
property itself. I think it's best for the project to configure it if
it requires AWT but doesn't require a display so that anyone that
builds it on a headless machine doesn't need to do so.
I expect that setting -Djava.awt.headle
Maybe Continuum should be running headless, as other projects might
also try to use awt code in the future.
Michiel
On 8/29/07, Jörg Schaible <[EMAIL PROTECTED]> wrote:
> Hi Oliver,
>
> Oliver Heger wrote on Tuesday, August 28, 2007 6:32 PM:
>
> > Henri Yandell wrote:
> >> We can change CI to use
Hi Oliver,
Oliver Heger wrote on Tuesday, August 28, 2007 6:32 PM:
> Henri Yandell wrote:
>> We can change CI to use a JDK 1.6 if that's what Configuration's
>> target is.
>
> This doesn't seem to be the problem. We get errors like the
> one below.
> Is there anything wrong with the JDK on the
Henri Yandell wrote:
We can change CI to use a JDK 1.6 if that's what Configuration's target is.
This doesn't seem to be the problem. We get errors like the one below.
Is there anything wrong with the JDK on the build machine?
Oliver
testGetConfiguration(org.apache.commons.configuration.Tes
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=2781&projectId=161
Build statistics:
State: Failed
Previous State: Failed
Started at: Tue 28 Aug 2007 09:30:22 -0700
Finished at: Tue 28 Aug 2007 09:31:12 -0700
Total time: 50s
Build Trigger: Schedule
Build Num
We can change CI to use a JDK 1.6 if that's what Configuration's target is.
On 8/28/07, Oliver Heger <[EMAIL PROTECTED]> wrote:
> Just an update: the tests should now run on a JDK 1.6. I was able to get
> rid of these dependencies on static fields. I also applied most of the
> improvements to the
Just an update: the tests should now run on a JDK 1.6. I was able to get
rid of these dependencies on static fields. I also applied most of the
improvements to the pom.xml Michiel suggested (thanks again).
However I doubt that CI will be impressed by these changes...
Oliver
Oliver Heger wrote
Ben Speakmon wrote:
> If you find that the JVM required for the test is important, you can specify
> which one to use in the surefire plugin configuration. Never tried it
> myself, though.
This would be an option. But I think in this case the tests are really a
bit bogus if they rely on certain va
If you find that the JVM required for the test is important, you can specify
which one to use in the surefire plugin configuration. Never tried it
myself, though.
On 8/27/07, Oliver Heger <[EMAIL PROTECTED]> wrote:
>
> Hi Michiel,
>
> thanks for this information. Obviously the tests depend on the
Hi Michiel,
thanks for this information. Obviously the tests depend on the JDK
version they are run. For me, using a JDK 1.5.0_09, the tests run fine.
CI also seems to use a JDK 1.5, but here 55 tests are failing, which
seems to be caused by classes from the java.awt package that cannot be
resolve
To me, it seems we should at least be able to run the tests first,
outside of any continuous build systems.
Here's what I had to do to get them running with Maven2 under
jdk1.6.0_02. Maybe this helps ?
1) Get the Commons Parent project using subversion from
http://svn.apache.org/repos/asf/commons
Instead of having nightly builds, couldn't we maybe set it up so that
these projects only build when necessary (svn changes, checked
nightly)? The build number could be synced with the SVN repository's
revision number, maybe? That way, we know how to recreate the build
if need be.
On 8/24/07, [E
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=2383&projectId=161
Build statistics:
State: Failed
Previous State: Failed
Started at: Fri 24 Aug 2007 08:30:28 -0700
Finished at: Fri 24 Aug 2007 08:31:16 -0700
Total time: 48s
Build Trigger: Schedule
Build Num
Looking at the test reports, all test failures seem to be caused by
dependencies to java.awt classes, which cannot be resolved. (For
instance, DataConfiguration supports some data types like
java.awt.Color, and the test class tries to check this).
Is there anything we can do about this?
Olive
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=2359&projectId=161
Build statistics:
State: Failed
Previous State: Failed
Started at: Fri 24 Aug 2007 03:42:49 -0700
Finished at: Fri 24 Aug 2007 03:43:39 -0700
Total time: 50s
Build Trigger: Schedule
Build Num
Online report :
http://vmbuild1.apache.org/continuum/buildResult.action?buildId=2234&projectId=161
Build statistics:
State: Failed
Previous State: Failed
Started at: Thu 23 Aug 2007 07:34:39 -0700
Finished at: Thu 23 Aug 2007 07:35:14 -0700
Total time: 34s
Build Trigger: Schedule
Build Nu
33 matches
Mail list logo
