estarted? Perhaps the local maven cache needs to be
> cleared?
>
> Thank you,
> Gary
>
> -- Forwarded message --
> From: Continuum@vmbuild
> Date: Wed, Aug 7, 2013 at 10:20 PM
> Subject: [continuum] BUILD FAILURE: Apache Commons - Commons
Can continuum be restarted? Perhaps the local maven cache needs to be
cleared?
Thank you,
Gary
-- Forwarded message --
From: Continuum@vmbuild
Date: Wed, Aug 7, 2013 at 10:20 PM
Subject: [continuum] BUILD FAILURE: Apache Commons - Commons VFS -
To: d...@commons.apache.org
Thanks, Dennis. I saw that later as I was looking at it and wondered if that
could be at the root of the problem. I added that when I was trying to get
around a problem introduced in the Commons Parent pom. I was going to define a
variable and then forgot to finish it.
As to the problem i
Hi
Sorry, the first part of my mail doesn't apply here.
It seems like the expression ${} is interpreted as ${project} resulting in
the strange reference to the Model object.
On Monday, August 15, 2011, Ralph Goers wrote:
> Do you know what the odd manifest file is? Some of the people building on
Do you know what the odd manifest file is? Some of the people building on
Windows got
Embedded error: Manifest file:
D:\RC\commons-vfs2-distribution-2.0-src-zip\commons-vfs-2.0\core\org.apache.maven.model.Model@718242
does not exist.
even when the directory structure was preserved. My understand
Hi Ralph
The problem is that you are referencing resources from the parent by
using the property:
${basedir}/..
When you build your project on a CI server it is not certain that the
modules of the project are laid out in that way on the file system.
Jenkins puts every module in its own directory
Can anyone here tell me what the problem is?
Ralph
On Aug 14, 2011, at 7:33 AM, sebb wrote:
> Me neither - try asking on builds@a.o
>
> On 14 August 2011 15:29, Ralph Goers wrote:
>> I don't understand this failure. I've run the build with both Maven 2 & 3
>> and it doesn't fail. The message
