No, after doing the blow away and clean checkout it started working again

Rob

On 06/01/2014 17:13, "Andy Seaborne" <[email protected]> wrote:

>Rob - is this still a problem?
>
>On 17/12/13 10:56, Andy Seaborne wrote:
>> On 17/12/13 09:14, Rob Vesse wrote:
>>> Ian/Andy
>>>
>>> I'm still having trouble building from source at the moment with the
>>> schemagen stuff still failing:
>>>
>>> [INFO] --- maven-invoker-plugin:1.7:run (integration-test) @
>>> jena-maven-tools ---
>>> [INFO] Building: schemagen-integration-0/pom.xml
>>> [INFO] ..FAILED (1.9 s)
>>> [INFO]   The build exited with code 1. See
>>> 
>>>/Users/rvesse/Documents/apache-jena/trunk/jena-maven-tools/target/it/sch
>>>emag
>>>
>>> en-integration-0/build.log for details.
>>> [INFO] Building: schemagen-integration-1/pom.xml
>>> [INFO] ..FAILED (1.7 s)
>>> [INFO]   The build exited with code 1. See
>>> 
>>>/Users/rvesse/Documents/apache-jena/trunk/jena-maven-tools/target/it/sch
>>>emag
>>>
>>> en-integration-1/build.log for details.
>>> [INFO] Building: schemagen-integration-2/pom.xml
>>> [INFO] ..FAILED (1.6 s)
>>> [INFO]   The build exited with code 1. See
>>> 
>>>/Users/rvesse/Documents/apache-jena/trunk/jena-maven-tools/target/it/sch
>>>emag
>>>
>>> en-integration-2/build.log for details.
>>> [INFO] Building: schemagen-integration-3/pom.xml
>>> [INFO] ..FAILED (1.6 s)
>>> [INFO]   The build exited with code 1. See
>>> 
>>>/Users/rvesse/Documents/apache-jena/trunk/jena-maven-tools/target/it/sch
>>>emag
>>>
>>> en-integration-3/build.log for details.
>>>
>>> mvn ­version gives:
>>>
>>> Apache Maven 3.0.4 (r1232337; 2012-01-17 08:44:56+0000)
>>> Maven home: /usr/share/maven
>>> Java version: 1.6.0_65, vendor: Apple Inc.
>>> Java home:
>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>> Default locale: en_GB, platform encoding: MacRoman
>>> OS name: "mac os x", version: "10.8.5", arch: "x86_64", family: "mac"
>>>
>>> Any thoughts?
>>>
>>> Rob
>>>
>>>
>>>
>>
>> Rob,
>>
>> Sorry - no clear answer.  Does it build elsewhere for you?
>>
>> Is the code tree absolutely up to date?  Not just the java files?  This
>> looks just like the thing the last changes fixed.  You may have to use a
>> clean checkout of the jena-maven-tools subtree.
>>
>> Jenkins uses maven 3.0.5 (apparently the "latest" tag !=> 3.1.0) and
>> there is a java6 build in Jenkins that is currently happy.
>>
>>      Andy
>




Reply via email to