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 in commons parent - Commons Parent defines the maven-bundle
plugin to generate an OSGi manifest. This isn't a problem, but it only
generates a manifest for jar and bundle projects. On others it emits a warning.
Recently, the jar plugin was configured to generate a test jar for all
projects. This failed in the parent project because no manifest was being
generated. I created a bogus manifest and now it is generating a completely
worthless jar, but the build succeeds.
Ralph
On Aug 14, 2011, at 10:20 PM, Dennis Lundberg wrote:
> 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 <ralph.go...@dslextreme.com> wrote:
>> 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 understanding is that
> the jar plugin builds the manifest file into the target directory. Commons
> does have the maven-bundle-plugin configured to generate an OSGi manifest.
>>
>> Although I understand the point about the resources, I don't see how it
> would apply to the jar manifest.
>>
>> Ralph
>>
>>
>> On Aug 14, 2011, at 9:58 AM, Dennis Lundberg wrote:
>>
>>> Hi Ralph
>>>
>>> The problem is that you are referencing resources from the parent by
>>> using the property:
>>>
>>> <vfs.parent.dir>${basedir}/..</vfs.parent.dir>
>>>
>>> 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, so the reference to the
>>> parent will not work. But that doesn't seem to be the case for Continuum.
>>>
>>> The Maven way of doing this is to create a module that contains the
>>> resources that needs to be shared, like the MANIFEST.MF in this case.
>>> Then you add a dependency to this "shared-resources" module from the
>>> other modules.
>>>
>>> For an example of this you can look at the docs for Maven Checkstyle
> Plugin:
>>>
>>>
> http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html
>>>
>>>
>>> To me it seems that this commit is the one that made the build fail.
>>>
>>> http://svn.apache.org/viewvc?view=revision&revision=1157461
>>>
>>> Where you are doing this:
>>>
>>> <commons.manifestfile>${}</commons.manifestfile>
>>>
>>> On 2011-08-14 16:46, Ralph Goers wrote:
>>>> 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 <ralph.go...@dslextreme.com>
> wrote:
>>>>>> I don't understand this failure. I've run the build with both Maven 2
> & 3 and it doesn't fail. The message it fails with is
>>>>>>
>>>>>> [INFO] [jar:jar {execution: default-jar}]
>>>>>> [INFO]
> ------------------------------------------------------------------------
>>>>>> [ERROR] BUILD ERROR
>>>>>> [INFO]
> ------------------------------------------------------------------------
>>>>>> [INFO] Error assembling JAR
>>>>>>
>>>>>> Embedded error: Manifest file:
> /home/continuum/continuum-base/data/working-directory/129/core/org.apache.maven.model.Model@a00185does
> not exist.
>>>>>> Ralph
>>>>>>
>>>>>> On Aug 14, 2011, at 1:23 AM, Continuum@vmbuild wrote:
>>>>>>
>>>>>>> Online report :
> http://vmbuild.apache.org/continuum/buildResult.action?buildId=11238&projectId=129
>>>>>>>
>>>>>>> Build statistics:
>>>>>>> State: Failed
>>>>>>> Previous State: Failed
>>>>>>> Started at: Sun 14 Aug 2011 08:20:52 +0000
>>>>>>> Finished at: Sun 14 Aug 2011 08:23:24 +0000
>>>>>>> Total time: 2m 32s
>>>>>>> Build Trigger: Schedule
>>>>>>> Build Number: 78
>>>>>>> Exit code: 1
>>>>>>> Building machine hostname: vmbuild
>>>>>>> Operating system : Linux(unknown)
>>>>>>> Java Home version :
>>>>>>> java version "1.6.0_24"
>>>>>>> Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
>>>>>>> Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed
> mode)
>>>>>>>
>>>>>>> Builder version :
>>>>>>> Apache Maven 2.2.1 (r801777; 2009-08-06 19:16:01+0000)
>>>>>>> Java version: 1.6.0_24
>>>>>>> Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre
>>>>>>> Default locale: en_AU, platform encoding: UTF-8
>>>>>>> OS name: "linux" version: "2.6.32-31-server" arch: "amd64"
> Family: "unix"
>>>>>>>
>>>>>>> *******************************
>
> --
> Dennis Lundberg
