You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2011/09/23 15:15:05 UTC
Build failed in Jenkins: Jena_LARQ #194
See <https://builds.apache.org/job/Jena_LARQ/194/>
------------------------------------------
Started by upstream project "Jena_TDB" build number 159
Started by upstream project "Jena_TDB" build number 160
Building remotely on ubuntu1
Updating http://svn.apache.org/repos/asf/incubator/jena/Jena2/LARQ/trunk
At revision 1174735
no change for http://svn.apache.org/repos/asf/incubator/jena/Jena2/LARQ/trunk since the previous build
Parsing POMs
[trunk] $ /home/hudson/tools/java/latest1.6/bin/java -cp /home/jenkins/jenkins-slave/maven3-agent.jar:/home/jenkins/jenkins-slave/tools/Maven_3.0.3/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /home/jenkins/jenkins-slave/tools/Maven_3.0.3 /home/jenkins/jenkins-slave/slave.jar /home/jenkins/jenkins-slave/maven3-interceptor.jar 53387
<===[JENKINS REMOTING CAPACITY]===>channel started
Executing Maven: -B -f <https://builds.apache.org/job/Jena_LARQ/ws/trunk/pom.xml> clean install findbugs:findbugs cobertura:cobertura pmd:pmd
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building LARQ 0.2.2-incubating-SNAPSHOT
[INFO] ------------------------------------------------------------------------
Downloading: http://openjena.org/repo-dev/com/hp/hpl/jena/tdb/0.8.11-SNAPSHOT/maven-metadata.xml
Downloading: http://repository.apache.org/snapshots/com/hp/hpl/jena/tdb/0.8.11-SNAPSHOT/maven-metadata.xml
Downloaded: http://openjena.org/repo-dev/com/hp/hpl/jena/tdb/0.8.11-SNAPSHOT/maven-metadata.xml (355 B at 0.4 KB/sec)
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ larq ---
[INFO] Deleting <https://builds.apache.org/job/Jena_LARQ/ws/trunk/target>
[INFO]
[INFO] --- maven-remote-resources-plugin:1.1:process (default) @ larq ---
[INFO] Setting property: classpath.resource.loader.class => 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ larq ---
[INFO] Copying 0 resource
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ larq ---
[INFO] Compiling 22 source files to <https://builds.apache.org/job/Jena_LARQ/ws/trunk/target/classes>
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] <https://builds.apache.org/job/Jena_LARQ/ws/trunk/src/main/java/org/apache/jena/larq/LuceneSearch.java>:[240,13] cannot find symbol
symbol : method add(com.hp.hpl.jena.sparql.core.Var,com.hp.hpl.jena.graph.Node)
location: interface com.hp.hpl.jena.sparql.engine.binding.Binding
[ERROR] <https://builds.apache.org/job/Jena_LARQ/ws/trunk/src/main/java/org/apache/jena/larq/LuceneSearch.java>:[242,17] cannot find symbol
symbol : method add(com.hp.hpl.jena.sparql.core.Var,com.hp.hpl.jena.graph.Node)
location: interface com.hp.hpl.jena.sparql.engine.binding.Binding
[ERROR] <https://builds.apache.org/job/Jena_LARQ/ws/trunk/src/main/java/org/apache/jena/larq/HitConverter.java>:[46,9] cannot find symbol
symbol : method add(com.hp.hpl.jena.sparql.core.Var,com.hp.hpl.jena.graph.Node)
location: interface com.hp.hpl.jena.sparql.engine.binding.Binding
[ERROR] <https://builds.apache.org/job/Jena_LARQ/ws/trunk/src/main/java/org/apache/jena/larq/HitConverter.java>:[48,13] cannot find symbol
symbol : method add(com.hp.hpl.jena.sparql.core.Var,com.hp.hpl.jena.graph.Node)
location: interface com.hp.hpl.jena.sparql.engine.binding.Binding
[INFO] 4 errors
[INFO] -------------------------------------------------------------
[JENKINS] Archiving <https://builds.apache.org/job/Jena_LARQ/ws/trunk/pom.xml> to /home/hudson/hudson/jobs/Jena_LARQ/modules/org.apache.jena$larq/builds/2011-09-23_13-14-33/archive/org.apache.jena/larq/0.2.2-incubating-SNAPSHOT/larq-0.2.2-incubating-SNAPSHOT.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15.282s
[INFO] Finished at: Fri Sep 23 13:15:03 UTC 2011
[INFO] Final Memory: 17M/148M
[INFO] ------------------------------------------------------------------------
mavenExecutionResult exceptions not empty
message : Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project larq: Compilation failure
cause : Compilation failure
Stack trace :
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project larq: Compilation failure
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:122)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:74)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure
at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:656)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 27 more
Sending e-mails to: jena-commits@incubator.apache.org
channel stopped
Archiving artifacts
Skipping Cobertura coverage report as build was not UNSTABLE or better ...
IRC notifier plugin: Sending notification to: #jena
Jenkins build is back to normal : Jena_LARQ #195
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/Jena_LARQ/195/changes>
Re: Build failed in Jenkins: Jena_LARQ #194
Posted by Paolo Castagna <ca...@googlemail.com>.
Andy Seaborne wrote:
> On 23/09/11 15:16, Paolo Castagna wrote:
>> This is a good example of continuous integration in action.
>>
>> I want to briefly comment on this, since it's in topic with my previous
>> suggestion to remove jar files from the lib and lib-src directories.
>
> Building SDB from the POM file use dependencies.
>
> Jenkins builds via maven so it's picking up changes anyway. Why does the
> JAR files make any difference?
>
> The jars are for Eclipse and which ever way round you do it, there is
> separate step for Eclipse. Its just a question of who has to do it -
> the person making the changes (who is likely to understand the process)
> or all the people who only download from SVN and look at the code in
> Eclipse and now MUST have maven.
Asking people who want to compile or test or develop to use Maven does
not seem to me a bad thing. At the end of the day our CI system is using
Maven (not Eclipse) and when we build releases or artifacts we use Maven
(not Eclipse).
Once you have Maven to manage your project, it is a bad practice IMHO
to have jar files in your lib and lib-src directories.
It creates two views on your software (command line != IDE) and those
two views might diverge for all sort of reasons.
Personally, I prefer the approach followed by ARQ, Fuseki, TxTDB and LARQ.
I am also in favor of a consistent approach across our modules.
Consistency helps people who are new to the project.
I do not know any other open source project who adopt the same approach
of Jena2, IRI, SDB, etc.: jars in the lib directory + use of Maven to
manage dependencies. Do you know any?
Diverging from what people might expect will require explaining them
why we diverged and help them to understand something they might not
have seen elsewhere.
As I said, having two set of jars caused me problems more than once
when I was making changes to two or more modules. The two sets might
diverge.
>
>> I saw this message. The cause is that a method has been removed from
>> the Binding interface (see: JENA-121):
>> http://svn.apache.org/viewvc/incubator/jena/Jena2/ARQ/trunk/src/com/hp/hpl/jena/sparql/engine/binding/Binding.java?r1=1174251&r2=1174250&pathrev=1174251
>>
>>
>> That change is perfectly fine and I was aware of that change because
>> I saw the notifications. When LARQ failed, without nobody working on
>> it, it's was obvious the reason was that change.
>>
>> A quick and easy fix. Done.
>>
>> No communication needed between me and who is doing the change on
>> JENA-121.
>> ARQ (development) and LARQ (development) are back in sync.
>
> I didn't break LARQ - I took the time and uploaded a patch for LARQ
> (JENA-122).
It did (and I think it is a *good* thing, since CI systems are there
for this as well, "continuously" checking different modules work
together): https://builds.apache.org/view/G-L/view/Jena/job/Jena_LARQ/194/
LARQ depends on ARQ-2.8.9-SNAPSHOT.
If a change is made to ARQ which has an effect on LARQ,
LARQ will fail as soon as an ARQ-2.8.9-SNAPSHOT is published.
All this is *good*. I've never said or proposed to change this.
By the way, thanks for the patch (I was faster, this time) for those
small changes it takes more time to write the JIRA issue and submit
the patch than fixing the source code directly. Fixing the code
directly is my favorite option, since I might not involve me and there
should be no boundaries/barriers between modules, nor strict rules
or mapping between "software module" and "person".
>From a point of view of communication, I see (and review) all the
changes anyway, via the notifications via email which we all receive. :-)
Paolo
>
>> We could have delayed or postponed this to a later point in time.
>> What's the difference? We lose the context.
>>
>> Someone can make a change to a module and not even realize his change
>> will break things somewhere else. This is why CI systems such as Jenkins
>> are really helpful and useful.
>
> Is anyone saying they are not?
>
>> For this particular change, which is trivial, losing context is not that
>> important. For other situations I think it's much better spotting
>> problems
>> earlier than later (for example when you need to upgrade dependencies,
>> etc.)
>>
>> My 2 cents,
>> Paolo
>
> Andy
Re: Build failed in Jenkins: Jena_LARQ #194
Posted by Andy Seaborne <an...@apache.org>.
On 23/09/11 15:16, Paolo Castagna wrote:
> This is a good example of continuous integration in action.
>
> I want to briefly comment on this, since it's in topic with my previous
> suggestion to remove jar files from the lib and lib-src directories.
Building SDB from the POM file use dependencies.
Jenkins builds via maven so it's picking up changes anyway. Why does the
JAR files make any difference?
The jars are for Eclipse and which ever way round you do it, there is
separate step for Eclipse. Its just a question of who has to do it -
the person making the changes (who is likely to understand the process)
or all the people who only download from SVN and look at the code in
Eclipse and now MUST have maven.
> I saw this message. The cause is that a method has been removed from
> the Binding interface (see: JENA-121):
> http://svn.apache.org/viewvc/incubator/jena/Jena2/ARQ/trunk/src/com/hp/hpl/jena/sparql/engine/binding/Binding.java?r1=1174251&r2=1174250&pathrev=1174251
>
> That change is perfectly fine and I was aware of that change because
> I saw the notifications. When LARQ failed, without nobody working on
> it, it's was obvious the reason was that change.
>
> A quick and easy fix. Done.
>
> No communication needed between me and who is doing the change on JENA-121.
> ARQ (development) and LARQ (development) are back in sync.
I didn't break LARQ - I took the time and uploaded a patch for LARQ
(JENA-122).
> We could have delayed or postponed this to a later point in time.
> What's the difference? We lose the context.
>
> Someone can make a change to a module and not even realize his change
> will break things somewhere else. This is why CI systems such as Jenkins
> are really helpful and useful.
Is anyone saying they are not?
> For this particular change, which is trivial, losing context is not that
> important. For other situations I think it's much better spotting problems
> earlier than later (for example when you need to upgrade dependencies, etc.)
>
> My 2 cents,
> Paolo
Andy
Re: Build failed in Jenkins: Jena_LARQ #194
Posted by Paolo Castagna <ca...@googlemail.com>.
This is a good example of continuous integration in action.
I want to briefly comment on this, since it's in topic with my previous
suggestion to remove jar files from the lib and lib-src directories.
I saw this message. The cause is that a method has been removed from
the Binding interface (see: JENA-121):
http://svn.apache.org/viewvc/incubator/jena/Jena2/ARQ/trunk/src/com/hp/hpl/jena/sparql/engine/binding/Binding.java?r1=1174251&r2=1174250&pathrev=1174251
That change is perfectly fine and I was aware of that change because
I saw the notifications. When LARQ failed, without nobody working on
it, it's was obvious the reason was that change.
A quick and easy fix. Done.
No communication needed between me and who is doing the change on JENA-121.
ARQ (development) and LARQ (development) are back in sync.
We could have delayed or postponed this to a later point in time.
What's the difference? We lose the context.
Someone can make a change to a module and not even realize his change
will break things somewhere else. This is why CI systems such as Jenkins
are really helpful and useful.
For this particular change, which is trivial, losing context is not that
important. For other situations I think it's much better spotting problems
earlier than later (for example when you need to upgrade dependencies, etc.)
My 2 cents,
Paolo
Apache Jenkins Server wrote:
> See <https://builds.apache.org/job/Jena_LARQ/194/>
>
> ------------------------------------------
> Started by upstream project "Jena_TDB" build number 159
> Started by upstream project "Jena_TDB" build number 160
> Building remotely on ubuntu1
> Updating http://svn.apache.org/repos/asf/incubator/jena/Jena2/LARQ/trunk
> At revision 1174735
> no change for http://svn.apache.org/repos/asf/incubator/jena/Jena2/LARQ/trunk since the previous build
> Parsing POMs
> [trunk] $ /home/hudson/tools/java/latest1.6/bin/java -cp /home/jenkins/jenkins-slave/maven3-agent.jar:/home/jenkins/jenkins-slave/tools/Maven_3.0.3/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /home/jenkins/jenkins-slave/tools/Maven_3.0.3 /home/jenkins/jenkins-slave/slave.jar /home/jenkins/jenkins-slave/maven3-interceptor.jar 53387
> <===[JENKINS REMOTING CAPACITY]===>channel started
> Executing Maven: -B -f <https://builds.apache.org/job/Jena_LARQ/ws/trunk/pom.xml> clean install findbugs:findbugs cobertura:cobertura pmd:pmd
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building LARQ 0.2.2-incubating-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> Downloading: http://openjena.org/repo-dev/com/hp/hpl/jena/tdb/0.8.11-SNAPSHOT/maven-metadata.xml
> Downloading: http://repository.apache.org/snapshots/com/hp/hpl/jena/tdb/0.8.11-SNAPSHOT/maven-metadata.xml
> Downloaded: http://openjena.org/repo-dev/com/hp/hpl/jena/tdb/0.8.11-SNAPSHOT/maven-metadata.xml (355 B at 0.4 KB/sec)
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ larq ---
> [INFO] Deleting <https://builds.apache.org/job/Jena_LARQ/ws/trunk/target>
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ larq ---
> [INFO] Setting property: classpath.resource.loader.class => 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> [INFO] Setting property: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
>
> [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ larq ---
> [INFO] Copying 0 resource
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ larq ---
> [INFO] Compiling 22 source files to <https://builds.apache.org/job/Jena_LARQ/ws/trunk/target/classes>
> [INFO] -------------------------------------------------------------
> [ERROR] COMPILATION ERROR :
> [INFO] -------------------------------------------------------------
> [ERROR] <https://builds.apache.org/job/Jena_LARQ/ws/trunk/src/main/java/org/apache/jena/larq/LuceneSearch.java>:[240,13] cannot find symbol
> symbol : method add(com.hp.hpl.jena.sparql.core.Var,com.hp.hpl.jena.graph.Node)
> location: interface com.hp.hpl.jena.sparql.engine.binding.Binding
> [ERROR] <https://builds.apache.org/job/Jena_LARQ/ws/trunk/src/main/java/org/apache/jena/larq/LuceneSearch.java>:[242,17] cannot find symbol
> symbol : method add(com.hp.hpl.jena.sparql.core.Var,com.hp.hpl.jena.graph.Node)
> location: interface com.hp.hpl.jena.sparql.engine.binding.Binding
> [ERROR] <https://builds.apache.org/job/Jena_LARQ/ws/trunk/src/main/java/org/apache/jena/larq/HitConverter.java>:[46,9] cannot find symbol
> symbol : method add(com.hp.hpl.jena.sparql.core.Var,com.hp.hpl.jena.graph.Node)
> location: interface com.hp.hpl.jena.sparql.engine.binding.Binding
> [ERROR] <https://builds.apache.org/job/Jena_LARQ/ws/trunk/src/main/java/org/apache/jena/larq/HitConverter.java>:[48,13] cannot find symbol
> symbol : method add(com.hp.hpl.jena.sparql.core.Var,com.hp.hpl.jena.graph.Node)
> location: interface com.hp.hpl.jena.sparql.engine.binding.Binding
> [INFO] 4 errors
> [INFO] -------------------------------------------------------------
> [JENKINS] Archiving <https://builds.apache.org/job/Jena_LARQ/ws/trunk/pom.xml> to /home/hudson/hudson/jobs/Jena_LARQ/modules/org.apache.jena$larq/builds/2011-09-23_13-14-33/archive/org.apache.jena/larq/0.2.2-incubating-SNAPSHOT/larq-0.2.2-incubating-SNAPSHOT.pom
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 15.282s
> [INFO] Finished at: Fri Sep 23 13:15:03 UTC 2011
> [INFO] Final Memory: 17M/148M
> [INFO] ------------------------------------------------------------------------
> mavenExecutionResult exceptions not empty
> message : Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project larq: Compilation failure
> cause : Compilation failure
> Stack trace :
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project larq: Compilation failure
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
> at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
> at hudson.maven.Maven3Builder.call(Maven3Builder.java:122)
> at hudson.maven.Maven3Builder.call(Maven3Builder.java:74)
> at hudson.remoting.UserRequest.perform(UserRequest.java:118)
> at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> at hudson.remoting.Request$2.run(Request.java:287)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure
> at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:656)
> at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 27 more
> Sending e-mails to: jena-commits@incubator.apache.org
> channel stopped
> Archiving artifacts
> Skipping Cobertura coverage report as build was not UNSTABLE or better ...
> IRC notifier plugin: Sending notification to: #jena
>