[jira] [Commented] (JENA-380) Migrate core tests to junit4
[ https://issues.apache.org/jira/browse/JENA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750991#comment-13750991 ] ASF subversion and git services commented on JENA-380: -- Commit 1517755 from [~claudenw] [ https://svn.apache.org/r1517755 ] Initial checkin of JENA-380 Migrate core tests to junit4 Key: JENA-380 URL: https://issues.apache.org/jira/browse/JENA-380 Project: Apache Jena Issue Type: Task Components: Jena Affects Versions: Jena 2.10.0 Reporter: Claude Warren Assignee: Claude Warren Priority: Minor Many of the tests for jena core are junit3 suites. I would like to start a process of migrating them to junit 4 and rework them so that when compiling in the Eclipse IDE clicking on the failed test will take you to the failed test while maintaining the current test names. I would expect some test names to change based upon changes in functionality. The goals of this change are : 1) Move to junit 4 2) Ensure that when the entire package is run as a junit test all tests succeed. (i.e. valid default tests) 3) Continue to provide test classes that can be utilized by implementers of interfaces. 4) Extract utility/helper code into utility/helper classes to simplify the test inheritance tree. 5) Move the test classes into the same package name as the classes they test. Currently we have x.foo for the implementation classes and x.foo.test for the test classes. The process would be: 1) build a number of sub tasks under this change to deliver smaller changes. The smaller changes will be based on the package names and that can be delivered incrementally. 2) once all tests are in junit4 perform a sweep across the test code base looking for any junit 3 classes that remain. Verify that their testing functionality has been replaced by other code and remove them. The result will be a complete review of all the core tests and a migration to junit 4 and annotated tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JENA-201) Deliver Fuseki as a WAR file.
[
https://issues.apache.org/jira/browse/JENA-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751088#comment-13751088
]
Andy Seaborne commented on JENA-201:
Rob - yes, that'll get to the same functionality as the standalone server (with
caveats).
At the moment, the {{pages/}} area is mounted as the root static content and
reside on disk. When starting the standalone server you can have them
somewhere else, use your own or editted pages, or arrange for no pages.
If included in the WAR file:
* The pages are always available.
* The pages are fixed.
* request routing needs to be page sensitive.
None of theose are entirely desirable. I guess it's framing what the WAR
version is for; whether it is the standalone server but running in Tomcat or
meeting a deployment need for a SPARQL server, where no pages makes sense.
Re: routing: to make the system generic, there is one uber SPARQL servlet to do
all the routing (it's set as {{/\*}}) so web.xml needs to have {{\*.html}},
{{\*.css}}, {{...}} settings. In the standalone server, servlets are
explicitly added for each service of each dataset, as if web.xml has
{{/ds/query - SPARQL_QueryDataset}}, {{/ds/update - SPARQL_Update}}, ... .
See also JENA-350 (use of session cookies) and JENA-420 (new UI).
This prototype webapp setup is a pure SPARQL server for programmatic access.
Deliver Fuseki as a WAR file.
-
Key: JENA-201
URL: https://issues.apache.org/jira/browse/JENA-201
Project: Apache Jena
Issue Type: Improvement
Components: Fuseki
Reporter: Andy Seaborne
Priority: Minor
Labels: gsoc2013, mentor
Attachments: fuseki-war-proto.zip, GruppoImola_fuseki_war_src.rar
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JENA-201) Deliver Fuseki as a WAR file.
[
https://issues.apache.org/jira/browse/JENA-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751097#comment-13751097
]
Andy Seaborne commented on JENA-201:
Lewis -
Re: NPE and missing counters.
{{GET http://localhost:8080/apache-jena-fuseki/}} is going to the webapp, and
has no dataset nor service. This needs to be graceful caught and make a 400
... or to start yielding the index page.
Clearly, my testing had only covered what should work, not what shouldn't :-)
Re:logging
There is a fight over logging going on - I didn't manage to sort that out and
left it as Fuseki having it's own logging; I only managed to break things in an
attempt to fix that, then I ran out of time.
Probably needs the whole of internal logging converted to using the logger for
the servlet logger (getServletContext().log() which is bad style?) or a
different setup to use java.util.logging, which is I think what Tomcat is
using, or have a separate Fuseki log, not in catalina.out.
Deliver Fuseki as a WAR file.
-
Key: JENA-201
URL: https://issues.apache.org/jira/browse/JENA-201
Project: Apache Jena
Issue Type: Improvement
Components: Fuseki
Reporter: Andy Seaborne
Priority: Minor
Labels: gsoc2013, mentor
Attachments: fuseki-war-proto.zip, GruppoImola_fuseki_war_src.rar
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: New committer: Ying Jiang
Now I have the account to be able to import the jena-spatial code into Apache Jena SVN. Shall I put it in /Experimental first or simply put it straight into trunk? I prefer the latter. When will Jena 2.10.2 be released? Is that possible to include jena-spatial in this release? I don't mind - into trunk is fine my me. Put it there and we can see how it goes. It's pretty trivial to move it (svn mv and edit the master POM). Don't forget the documentation into the website (in svn under /site -- markdown format or HTML). It would be ideal from my point of view to include it in the release. 2.10.2 is going to be 2.11.0 - there are several new things going in and we still have some sorting out to do. It's not going to be in the next few days. I, personally, avoid giving specific dates because we don't have specific resources to do work so dates are always going to be approximate. Aside: In theory, we can release at any time; in an Apache project anyone can call for a release at any time. It does not even have to be a committer or PMC member although (1) the vote needs the necessary PMC majority and 3 +1's and (2) Jena releases via nexus, which you need a log in for, which means a committer. Andy
Re: project components
On 26/08/13 10:15, Claude Warren wrote: I would like to add jena-security to the list of components in JIRA. Is there any objection to my doing so? No objection here. I think the setup on JIRA will let any of us do it, and it is not restricted to the admin (at least, that's what it should be; another system, another configuration UI, ...). There are 3 Claude Warrens in JIRA: claudenw cla...@xenei.org claud...@users.soureforge.net Is 'claudenw' the right, current you? Andy Claude
Re: project components
Yes, claudenw is the right me. :) But I went ahead and added the Security component and placed myself as the component lead and default assignee, Claude On Tue, Aug 27, 2013 at 10:43 AM, Andy Seaborne a...@apache.org wrote: On 26/08/13 10:15, Claude Warren wrote: I would like to add jena-security to the list of components in JIRA. Is there any objection to my doing so? No objection here. I think the setup on JIRA will let any of us do it, and it is not restricted to the admin (at least, that's what it should be; another system, another configuration UI, ...). There are 3 Claude Warrens in JIRA: claudenw cla...@xenei.org claud...@users.soureforge.net Is 'claudenw' the right, current you? Andy Claude -- I like: Like Like - The likeliest place on the webhttp://like-like.xenei.com Identity: https://www.identify.nu/user.php?cla...@xenei.com LinkedIn: http://www.linkedin.com/in/claudewarren
module/component documentation
Greetings, Do we have a simple mechanism for allowing each POM module to add documentation to the Jena web page? I am thinking that providing a point in the documentation tree for module documentation might make maintaining the website easier as each component would be responsible for their section of the tree. Specifically, I want to include documentation specific to the Security module (e.g. example code and how-tos). Thoughts? Claude -- I like: Like Like - The likeliest place on the webhttp://like-like.xenei.com Identity: https://www.identify.nu/user.php?cla...@xenei.com LinkedIn: http://www.linkedin.com/in/claudewarren
Re: Build failed in Jenkins: Jena_Development_Test #871
Jenkins jobs seem to intermittently fail with unexpected JVM termination, no idea why The jobs do have a time limit on them but Jenkins would explicitly state that it was aborting the build due to time limit exceeded if that was the case. e.g. Build timed out (after 20 minutes). Marking the build as aborted. Rob On 8/26/13 10:53 PM, Claude Warren cla...@xenei.com wrote: I am seeing that exit code 143 is the result of a SIGTERM. Anybody have any idea why? Does the Jenkins instance have a limit set that might cause it to abort the build? Claude On Tue, Aug 27, 2013 at 1:14 AM, Apache Jenkins Server jenk...@builds.apache.org wrote: See https://builds.apache.org/job/Jena_Development_Test/871/changes Changes: [rvesse] Regression tests for JENA-522 [rvesse] Switch to using maven profiles in top level POM to select modules to built Default dev profile builds the fast building and most common modules Optional complete profile builds all modules including those like Jena JDBC that are slow Releases will need to use the complete profile [rvesse] Fix for a test clean up bug that was highlighted by the JENA-522 changes [claude] Fixed pom variable names -- [...truncated 209 lines...] Results : Tests run: 8664, Failures: 0, Errors: 0, Skipped: 0 [JENKINS] Recording test results Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Building Apache Jena - ARQ (SPARQL 1.1 Query Engine) 2.10.2-SNAPSHOT Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-clean-plugin:2.5:clean (default-clean) @ jena-arq --- Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-enforcer-plugin:1.2:enforce (enforce) @ jena-arq --- Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-remote-resources-plugin:1.4:process (default) @ jena-arq --- Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-resources-plugin:2.6:resources (default-resources) @ jena-arq --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] Copying 3 resources Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-compiler-plugin:3.1:compile (default-compile) @ jena-arq --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 1444 source files to https://builds.apache.org/job/Jena_Development_Test/ws/trunk/jena-arq/tar get/classes [WARNING] Note: Some input files use or override a deprecated API. [WARNING] Note: Recompile with -Xlint:deprecation for details. Aug 27, 2013 12:11:09 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:11:09 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-resources-plugin:2.6:testResources (default-testResources) @ jena-arq --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] Copying 3 resources Aug 27, 2013 12:11:10 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:11:10 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ jena-arq --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 272 source files to https://builds.apache.org/job/Jena_Development_Test/ws/trunk/jena-arq/tar get/test-classes [WARNING] Note: https://builds.apache.org/job/Jena_Development_Test/ws/trunk/jena-arq/src /test/java/com/hp/hpl/jena/sparql/graph/TestGraphUnionRead.java uses unchecked or unsafe operations. [WARNING] Note: Recompile with -Xlint:unchecked for details. Aug 27, 2013 12:11:14 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:11:14 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
Re: project components
I've done the same for JDBC I also changed the version 2.10.2 = 2.11.0 as we've already decided to do this Rob On 8/27/13 3:08 AM, Claude Warren cla...@xenei.com wrote: Yes, claudenw is the right me. :) But I went ahead and added the Security component and placed myself as the component lead and default assignee, Claude On Tue, Aug 27, 2013 at 10:43 AM, Andy Seaborne a...@apache.org wrote: On 26/08/13 10:15, Claude Warren wrote: I would like to add jena-security to the list of components in JIRA. Is there any objection to my doing so? No objection here. I think the setup on JIRA will let any of us do it, and it is not restricted to the admin (at least, that's what it should be; another system, another configuration UI, ...). There are 3 Claude Warrens in JIRA: claudenw cla...@xenei.org claud...@users.soureforge.net Is 'claudenw' the right, current you? Andy Claude -- I like: Like Like - The likeliest place on the webhttp://like-like.xenei.com Identity: https://www.identify.nu/user.php?cla...@xenei.com LinkedIn: http://www.linkedin.com/in/claudewarren
Re: Build failed in Jenkins: Jena_Development_Test #871
Maybe 143 is secret code for success. I asked on build@ but didn't get any pointers. Please could we all log which specific machine failures occur on in case it's one ubuntu* in particular. The console log says which server is used. Andy On 27/08/13 17:20, Rob Vesse wrote: Jenkins jobs seem to intermittently fail with unexpected JVM termination, no idea why The jobs do have a time limit on them but Jenkins would explicitly state that it was aborting the build due to time limit exceeded if that was the case. e.g. Build timed out (after 20 minutes). Marking the build as aborted. Rob On 8/26/13 10:53 PM, Claude Warren cla...@xenei.com wrote: I am seeing that exit code 143 is the result of a SIGTERM. Anybody have any idea why? Does the Jenkins instance have a limit set that might cause it to abort the build? Claude On Tue, Aug 27, 2013 at 1:14 AM, Apache Jenkins Server jenk...@builds.apache.org wrote: See https://builds.apache.org/job/Jena_Development_Test/871/changes Changes: [rvesse] Regression tests for JENA-522 [rvesse] Switch to using maven profiles in top level POM to select modules to built Default dev profile builds the fast building and most common modules Optional complete profile builds all modules including those like Jena JDBC that are slow Releases will need to use the complete profile [rvesse] Fix for a test clean up bug that was highlighted by the JENA-522 changes [claude] Fixed pom variable names -- [...truncated 209 lines...] Results : Tests run: 8664, Failures: 0, Errors: 0, Skipped: 0 [JENKINS] Recording test results Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Building Apache Jena - ARQ (SPARQL 1.1 Query Engine) 2.10.2-SNAPSHOT Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-clean-plugin:2.5:clean (default-clean) @ jena-arq --- Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-enforcer-plugin:1.2:enforce (enforce) @ jena-arq --- Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-remote-resources-plugin:1.4:process (default) @ jena-arq --- Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-resources-plugin:2.6:resources (default-resources) @ jena-arq --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] Copying 3 resources Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-compiler-plugin:3.1:compile (default-compile) @ jena-arq --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 1444 source files to https://builds.apache.org/job/Jena_Development_Test/ws/trunk/jena-arq/tar get/classes [WARNING] Note: Some input files use or override a deprecated API. [WARNING] Note: Recompile with -Xlint:deprecation for details. Aug 27, 2013 12:11:09 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:11:09 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-resources-plugin:2.6:testResources (default-testResources) @ jena-arq --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] Copying 3 resources Aug 27, 2013 12:11:10 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:11:10 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ jena-arq --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 272 source files to https://builds.apache.org/job/Jena_Development_Test/ws/trunk/jena-arq/tar get/test-classes [WARNING] Note: https://builds.apache.org/job/Jena_Development_Test/ws/trunk/jena-arq/src /test/java/com/hp/hpl/jena/sparql/graph/TestGraphUnionRead.java uses unchecked or unsafe operations. [WARNING] Note: Recompile with
Re: Build failed in Jenkins: Jena_Development_Test #871
Looks like ubuntu4 is the culprit for at least the portion of the history I can see Rob On 8/27/13 9:43 AM, Andy Seaborne a...@apache.org wrote: Maybe 143 is secret code for success. I asked on build@ but didn't get any pointers. Please could we all log which specific machine failures occur on in case it's one ubuntu* in particular. The console log says which server is used. Andy On 27/08/13 17:20, Rob Vesse wrote: Jenkins jobs seem to intermittently fail with unexpected JVM termination, no idea why The jobs do have a time limit on them but Jenkins would explicitly state that it was aborting the build due to time limit exceeded if that was the case. e.g. Build timed out (after 20 minutes). Marking the build as aborted. Rob On 8/26/13 10:53 PM, Claude Warren cla...@xenei.com wrote: I am seeing that exit code 143 is the result of a SIGTERM. Anybody have any idea why? Does the Jenkins instance have a limit set that might cause it to abort the build? Claude On Tue, Aug 27, 2013 at 1:14 AM, Apache Jenkins Server jenk...@builds.apache.org wrote: See https://builds.apache.org/job/Jena_Development_Test/871/changes Changes: [rvesse] Regression tests for JENA-522 [rvesse] Switch to using maven profiles in top level POM to select modules to built Default dev profile builds the fast building and most common modules Optional complete profile builds all modules including those like Jena JDBC that are slow Releases will need to use the complete profile [rvesse] Fix for a test clean up bug that was highlighted by the JENA-522 changes [claude] Fixed pom variable names -- [...truncated 209 lines...] Results : Tests run: 8664, Failures: 0, Errors: 0, Skipped: 0 [JENKINS] Recording test results Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: --- - Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Building Apache Jena - ARQ (SPARQL 1.1 Query Engine) 2.10.2-SNAPSHOT Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: --- - Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-clean-plugin:2.5:clean (default-clean) @ jena-arq --- Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-enforcer-plugin:1.2:enforce (enforce) @ jena-arq --- Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-remote-resources-plugin:1.4:process (default) @ jena-arq --- Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-resources-plugin:2.6:resources (default-resources) @ jena-arq --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] Copying 3 resources Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-compiler-plugin:3.1:compile (default-compile) @ jena-arq --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 1444 source files to https://builds.apache.org/job/Jena_Development_Test/ws/trunk/jena-arq/t ar get/classes [WARNING] Note: Some input files use or override a deprecated API. [WARNING] Note: Recompile with -Xlint:deprecation for details. Aug 27, 2013 12:11:09 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:11:09 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-resources-plugin:2.6:testResources (default-testResources) @ jena-arq --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] Copying 3 resources Aug 27, 2013 12:11:10 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:11:10 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ jena-arq --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 272 source files to https://builds.apache.org/job/Jena_Development_Test/ws/trunk/jena-arq/t ar
Version Bump in POMs?
Since we all seem to be in agreement that the next release will be 2.11.0 rather than 2.10.2 because of all the new stuff we're putting in do we want to go ahead and bump the versions in the POMs? Do we also want to bump versions for components like TDB that don't use 2.10.2 e.g. 0.10.2 = 0.11.0 I will happily volunteer to do this Rob
Re: Version Bump in POMs?
+1 On Tue, Aug 27, 2013 at 6:43 PM, Rob Vesse rve...@yarcdata.com wrote: Since we all seem to be in agreement that the next release will be 2.11.0 rather than 2.10.2 because of all the new stuff we're putting in do we want to go ahead and bump the versions in the POMs? Do we also want to bump versions for components like TDB that don't use 2.10.2 e.g. 0.10.2 = 0.11.0 I will happily volunteer to do this Rob -- I like: Like Like - The likeliest place on the webhttp://like-like.xenei.com Identity: https://www.identify.nu/user.php?cla...@xenei.com LinkedIn: http://www.linkedin.com/in/claudewarren
Re: Build failed in Jenkins: Jena_Development_Test #871
The ubuntu1 executor shows that there is a build stuck and that it has been stuck for quite some time. https://builds.apache.org/computer/ubuntu1/log Perhaps we should delete it or ask for it to be deleted? On Tue, Aug 27, 2013 at 6:42 PM, Rob Vesse rve...@yarcdata.com wrote: Looks like ubuntu4 is the culprit for at least the portion of the history I can see Rob On 8/27/13 9:43 AM, Andy Seaborne a...@apache.org wrote: Maybe 143 is secret code for success. I asked on build@ but didn't get any pointers. Please could we all log which specific machine failures occur on in case it's one ubuntu* in particular. The console log says which server is used. Andy On 27/08/13 17:20, Rob Vesse wrote: Jenkins jobs seem to intermittently fail with unexpected JVM termination, no idea why The jobs do have a time limit on them but Jenkins would explicitly state that it was aborting the build due to time limit exceeded if that was the case. e.g. Build timed out (after 20 minutes). Marking the build as aborted. Rob On 8/26/13 10:53 PM, Claude Warren cla...@xenei.com wrote: I am seeing that exit code 143 is the result of a SIGTERM. Anybody have any idea why? Does the Jenkins instance have a limit set that might cause it to abort the build? Claude On Tue, Aug 27, 2013 at 1:14 AM, Apache Jenkins Server jenk...@builds.apache.org wrote: See https://builds.apache.org/job/Jena_Development_Test/871/changes Changes: [rvesse] Regression tests for JENA-522 [rvesse] Switch to using maven profiles in top level POM to select modules to built Default dev profile builds the fast building and most common modules Optional complete profile builds all modules including those like Jena JDBC that are slow Releases will need to use the complete profile [rvesse] Fix for a test clean up bug that was highlighted by the JENA-522 changes [claude] Fixed pom variable names -- [...truncated 209 lines...] Results : Tests run: 8664, Failures: 0, Errors: 0, Skipped: 0 [JENKINS] Recording test results Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: --- - Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Building Apache Jena - ARQ (SPARQL 1.1 Query Engine) 2.10.2-SNAPSHOT Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: --- - Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-clean-plugin:2.5:clean (default-clean) @ jena-arq --- Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:10:54 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-enforcer-plugin:1.2:enforce (enforce) @ jena-arq --- Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-remote-resources-plugin:1.4:process (default) @ jena-arq --- Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-resources-plugin:2.6:resources (default-resources) @ jena-arq --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] Copying 3 resources Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:10:55 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-compiler-plugin:3.1:compile (default-compile) @ jena-arq --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 1444 source files to https://builds.apache.org/job/Jena_Development_Test/ws/trunk/jena-arq/t ar get/classes [WARNING] Note: Some input files use or override a deprecated API. [WARNING] Note: Recompile with -Xlint:deprecation for details. Aug 27, 2013 12:11:09 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Aug 27, 2013 12:11:09 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-resources-plugin:2.6:testResources (default-testResources) @ jena-arq --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO]
[jira] [Commented] (JENA-201) Deliver Fuseki as a WAR file.
[ https://issues.apache.org/jira/browse/JENA-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751611#comment-13751611 ] Lewis John McGibbney commented on JENA-201: --- bq. The pages are always available. bq. The pages are fixed. For my use case this is exactly what I require Andy :) I am going to work towards obtaining the 400 and presenting the index page upon startup. I think getting a web app (war packaging) which can be dropped in to Tomcat or some other container is certainly a start to overhauling the Fuseki interface. I will work on this anyway. Separate Fuseki logging is certainly useful. A mish mash of Fuseki and Catalina INFO to catalina.out is not going to be particularly helpful as have numerous other applications spewing forth logging on this test server as well. I'll try to work towards separate logging for Fuseki as well. I am not having much joy obtaining any of the static files via my browser yet, even though they are included in the generated war however I should be able to sort this one out. Deliver Fuseki as a WAR file. - Key: JENA-201 URL: https://issues.apache.org/jira/browse/JENA-201 Project: Apache Jena Issue Type: Improvement Components: Fuseki Reporter: Andy Seaborne Priority: Minor Labels: gsoc2013, mentor Attachments: fuseki-war-proto.zip, GruppoImola_fuseki_war_src.rar -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
