You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jena.apache.org by Andy Seaborne <an...@apache.org> on 2013/02/12 10:12:10 UTC
Jena 2.10.0 : request for pre-release testing
We're gearing up for the Jena 2.10.0 and we'd like to ask for your help
testing it before the release.
This is not an incremental release and so we are especially asking for
feedback to make the transition as smooth a possible.
Key changes are:
* Reification - "Minimal" and "Convenient" styles have been removed.
* New RDF 1.1 Turtle parser tracking the developing standard
* A single maven artifact to include Jena in your maven project
* Changes to the way storage subsystems provide SPARQL Update
The snapshot repository is:
https://repository.apache.org/content/repositories/snapshots/org/apache/jena/
and the download is in directory apache-jena. Please use the latest
2.10.0-SNAPSHOT (there are nightly builds so 'latest' is down the bottom
if is more then one).
You can find out which version have by running the SPARQL script with
--version.
We have undertaken some internal simplification and while we are not
intending to cause change, we also recognize that some applications may
be depending on internal code in ways we don't know about.
We would most grateful for reports in the next 2 weeks of successful use
or any problems arising.
Andy
== apache-jena-libs
There is a new maven artifact to help applications by providing a single
maven artifact that include the main Jena modules.
<dependency>
<groupId>org.apache.jena</groupId>
<artifactId>apache-jena-libs</artifactId>
<type>pom</type>
<version>2.10.0</version>
</dependency>
Note the use of <type>pom</type>
BY using this artifact, applications will not be affected by any future
changes to the internal development module structure of Jena.
See
http://jena.staging.apache.org/download/maven.html
== RIOT Reader
There is a new RDF parser subsystem, which includes
* improved content negotiation
* the ability to register new parsers into Jena
* alignment to RDF 1.1 Turtle
* features apply when applications use model.read
http://jena.apache.org/documentation/io/index.html
The package name org.openjena.riot becomes org.apache.jena.riot.
There is some compatibility code in org.openjena.riot. Operations are
deprecated and will be removed after this release.
Call
org.apache.jena.riot.RIOT.init()
to ensure it is initialized if in doubt but it should automatically be
used by model.read.
Test:
model.read("data.ttl")
will read a local Turtle file.
== Streaming Update
The SPARQL Update engine has been re-architected to make the fundamental
execution of SPARQL Updates streamable.
There is no change to applications using SPARQL Update.
There are changes to the interface for storage systems that make special
provision for SPARQL Update. If you are migrating such a storage system,
do talk to the developers on dev@jena.apache.org if you have any
questions or suggestions for improvements.
== Portuguese Translations of the tutorial
Guilherme Cavalcanti has provided a Portuguese translation of the tutorials.
http://jena.staging.apache.org/tutorials/
== Reification
As part of simplifying Jena, the reification styles Convenient and
Minimal are being removed. These need a significant amount of internal
state management and impede scaling beyond storage in memory.
The only support style is "standard", which as always been the default
style in Jena. Only style "standard" has even been supported by TDB and
SDB.
Use of the constants for these styles is deprecated and will be treated
as "standard".
== Internal simplification
Other simplifications in this release include the removal of the graph
query handler subsystem. This is unrelated to SPARQL and existed in
support of RDQL.
The graph level bulk query handler has been removed - compatibility for
the Model API for all bulk update is maintained.
Re: Jena 2.10.0 : request for pre-release testing
Posted by Stephen Allen <sa...@apache.org>.
On Sun, Feb 17, 2013 at 7:34 AM, Dick & Hannah <da...@gmail.com> wrote:
> Hi. Sorry this is late.
>
> Do you have more details on...
>
> * Changes to the way storage subsystems provide SPARQL Update
>
> ...please?
>
> As we have a heavily modified wrapper around the current code. :-)
>
Hi Dick,
The main change is that UpdateEngine is now geared towards *streaming*
SPARQL Update operations. This means that any custom engines need to
provide an object that can accept update operations as they are being
parsed. Please take a look at UpdateEngineMain for the default ARQ
implementation that is used for in-memory stores, SDB, and TDB. If
you need to continue to receive a fully populated UpdateRequest ahead
of time, please look at UpdateEngineNonStreaming for an example that
is very much like the old style.
Please let me know if you have any more questions as you port your
previous implementation.
-Stephen
Re: Jena 2.10.0 : request for pre-release testing
Posted by Dick & Hannah <da...@gmail.com>.
Hi. Sorry this is late.
Do you have more details on...
* Changes to the way storage subsystems provide SPARQL Update
...please?
As we have a heavily modified wrapper around the current code. :-)
Regards
Dick Murray
Technology Specialist
UNIT4 Business Software
www.unit4.com
+44 1275 377359
+44 7884 111729
On 12 Feb 2013, at 09:12, Andy Seaborne <an...@apache.org> wrote:
> * Changes to the way storage subsystems provide SPARQL Update
Re: Jena 2.10.0 : request for pre-release testing
Posted by Dave Reynolds <da...@gmail.com>.
On 17/02/13 11:44, Andy Seaborne wrote:
> On 16/02/13 22:50, Dave Reynolds wrote:
>> (well, lots of compilation errors due to the Jena changes but at least
>> the artefacts download now.)
>
> What were the compilation errors?
Mostly the openjena -> apache.jena package name change, plus reference
to graph.queryHandler (to use convenience functions like subjectsFor).
> Are they obvious to change?
Yes.
Just took time to work through because I have a small stack of projects
with interdependencies so had to change them all at once. Since I didn't
want to also change Elda that meant removing an Elda dependency out of
one of the projects in the stack.
Now done and the top level project runs successfully with Jena
2.10.0-SNAPSHOT. Phew.
Dave
Re: Jena 2.10.0 : request for pre-release testing
Posted by Andy Seaborne <an...@apache.org>.
On 16/02/13 22:50, Dave Reynolds wrote:
> (well, lots of compilation errors due to the Jena changes but at least
> the artefacts download now.)
What were the compilation errors? Are they obvious to change?
(Because I have a linked set of projects, I don't see the full impact of
the changes so a fresh viewpoint would be helpful.)
Andy
Re: Jena 2.10.0 : request for pre-release testing
Posted by Dave Reynolds <da...@gmail.com>.
Ignore this. Trying again a few hours later and it works (well, lots of
compilation errors due to the Jena changes but at least the artefacts
download now.). Have I said how much I hate Maven?
Dave
On 16/02/13 18:29, Dave Reynolds wrote:
> I realise that the second set of traces shows Maven also trying our
> local Epimorphics repositories. Just to make sure they aren't confusing
> the poor thing I tried again with those remove from the pom. Similar
> results:
>
> [[[
> Downloading:
> https://repository.apache.org/content/repositories/releases/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
>
> Downloading:
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
>
> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
> 53ede9572737d92449809302a82f192cf7870165 for
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
>
> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
> 53ede9572737d92449809302a82f192cf7870165 for
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
>
> Downloaded:
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
> (391 B at 0.0 KB/sec)
> [WARNING] The metadata
> /home/der/.m2/repository/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata-apache-repo-snapshots.xml
> is invalid: end tag name </body> must match start tag name <hr> from
> line 7 (position: TEXT seen ...</address>\n</body>... @9:8)
> [WARNING] The metadata
> /home/der/.m2/repository/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata-apache-repo-snapshots.xml
> is invalid: end tag name </body> must match start tag name <hr> from
> line 7 (position: TEXT seen ...</address>\n</body>... @9:8)
> Downloading:
> https://repository.apache.org/content/repositories/releases/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
>
> Downloading:
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
>
> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
> 90bfca3bbba171909dcef73af4c96a6fad064b48 for
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
>
> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
> 90bfca3bbba171909dcef73af4c96a6fad064b48 for
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
>
> Downloaded:
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
> (401 B at 0.5 KB/sec)
> [WARNING] The POM for org.apache.jena:jena-tdb:jar:0.10.0-SNAPSHOT is
> invalid, transitive dependencies (if any) will not be available, enable
> debug logging for more details
> Downloading:
> https://repository.apache.org/content/repositories/releases/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
>
> Downloading:
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
>
> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
> 7575871f9c161d3792cdff22930ea5f83b52969f for
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
>
> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
> 7575871f9c161d3792cdff22930ea5f83b52969f for
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
>
> Downloaded:
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
> (401 B at 0.5 KB/sec)
> ]]]
>
> Dave
>
> On 16/02/13 18:23, Dave Reynolds wrote:
>> Tried to test against existing projects but failed to get Maven
>> resolution to work. No doubt user error (my inability to ever have Maven
>> work for me is well known) but I've spend some time on this without
>> getting anywhere.
>>
>> Using:
>>
>> <dependency>
>> <groupId>org.apache.jena</groupId>
>> <artifactId>apache-jena-libs</artifactId>
>> <type>pom</type>
>> <version>2.10.0-SNAPSHOT</version>
>> </dependency>
>>
>> and my normal repository entries:
>>
>> <repositories>
>> <repository>
>> <id>apache-repo-releases</id>
>>
>> <url>https://repository.apache.org/content/repositories/releases/</url>
>> <releases>
>> <enabled>true</enabled>
>> </releases>
>> </repository>
>>
>> <repository>
>> <id>apache-repo-snapshots</id>
>>
>> <url>https://repository.apache.org/content/repositories/snapshots/org/apache/jena/</url>
>>
>>
>> <releases>
>> <enabled>false</enabled>
>> </releases>
>> <snapshots>
>> <enabled>true</enabled>
>> </snapshots>
>> </repository>
>> ...
>> </repositories>
>>
>> Then using Maven command line (version 3.0.3, on Ubuntu 13.04) I see:
>>
>> [[[
>> Downloading:
>> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/maven-metadata.xml
>>
>>
>> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
>> 94dbdf66c1bb3a5c799701be99258c04d5b08501 for
>> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/maven-metadata.xml
>>
>>
>> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
>> 94dbdf66c1bb3a5c799701be99258c04d5b08501 for
>> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/maven-metadata.xml
>>
>>
>> Downloaded:
>> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/maven-metadata.xml
>>
>> (399 B at 0.0 KB/sec)
>> [WARNING] The metadata
>> /home/der/.m2/repository/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/maven-metadata-apache-repo-snapshots.xml
>>
>> is invalid: end tag name </body> must match start tag name <hr> from
>> line 7 (position: TEXT seen ...</address>\n</body>... @9:8)
>> Downloading:
>> https://repository.apache.org/content/repositories/releases/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/apache-jena-libs-2.10.0-SNAPSHOT.pom
>>
>>
>> Downloading:
>> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/apache-jena-libs-2.10.0-SNAPSHOT.pom
>>
>>
>> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
>> 130d6e8640395f95842df937e1d43bb33498e44a for
>> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/apache-jena-libs-2.10.0-SNAPSHOT.pom
>>
>>
>> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
>> 130d6e8640395f95842df937e1d43bb33498e44a for
>> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/apache-jena-libs-2.10.0-SNAPSHOT.pom
>>
>>
>> Downloaded:
>> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/apache-jena-libs-2.10.0-SNAPSHOT.pom
>>
>> (417 B at 0.5 KB/sec)
>> [WARNING] The POM for
>> org.apache.jena:apache-jena-libs:pom:2.10.0-SNAPSHOT is invalid,
>> transitive dependencies (if any) will not be available, enable debug
>> logging for more details
>> ]]]
>>
>> Nuking the entire Jena area of my ~/.m2/repository and switching to the
>> dependency:
>>
>> <dependency>
>> <groupId>org.apache.jena</groupId>
>> <artifactId>jena-tdb</artifactId>
>> <version>0.10.0-SNAPSHOT</version>
>> </dependency>
>>
>> Then a clean compile generates:
>>
>> [[[
>> Downloading:
>> http://www.epimorphics.com/maven2/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
>>
>>
>> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
>> 53ede9572737d92449809302a82f192cf7870165 for
>> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
>>
>>
>> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
>> 53ede9572737d92449809302a82f192cf7870165 for
>> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
>>
>>
>> Downloaded:
>> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
>>
>> (391 B at 0.0 KB/sec)
>> [WARNING] Could not transfer metadata
>> org.apache.jena:jena-tdb:0.10.0-SNAPSHOT/maven-metadata.xml from/to
>> repo-epi (http://www.epimorphics.com/maven2): Access denied to:
>> http://www.epimorphics.com/maven2/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
>>
>>
>> [WARNING] The metadata
>> /home/der/.m2/repository/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata-apache-repo-snapshots.xml
>>
>> is invalid: end tag name </body> must match start tag name <hr> from
>> line 7 (position: TEXT seen ...</address>\n</body>... @9:8)
>> Downloading:
>> http://www.epimorphics.com/maven2/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
>>
>>
>> [WARNING] The metadata
>> /home/der/.m2/repository/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata-apache-repo-snapshots.xml
>>
>> is invalid: end tag name </body> must match start tag name <hr> from
>> line 7 (position: TEXT seen ...</address>\n</body>... @9:8)
>> Downloading:
>> https://repository.apache.org/content/repositories/releases/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
>>
>>
>> Downloading:
>> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
>>
>>
>> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
>> 90bfca3bbba171909dcef73af4c96a6fad064b48 for
>> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
>>
>>
>> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
>> 90bfca3bbba171909dcef73af4c96a6fad064b48 for
>> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
>>
>>
>> Downloaded:
>> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
>>
>> (401 B at 0.5 KB/sec)
>> [WARNING] The POM for org.apache.jena:jena-tdb:jar:0.10.0-SNAPSHOT is
>> invalid, transitive dependencies (if any) will not be available, enable
>> debug logging for more details
>> Downloading:
>> https://repository.apache.org/content/repositories/releases/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
>>
>>
>> Downloading:
>> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
>>
>>
>> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
>> 7575871f9c161d3792cdff22930ea5f83b52969f for
>> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
>>
>>
>> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
>> 7575871f9c161d3792cdff22930ea5f83b52969f for
>> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
>>
>>
>> Downloaded:
>> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
>>
>> (401 B at 0.5 KB/sec)
>>
>> ...
>>
>> [INFO] -------------------------------------------------------------
>> [ERROR] COMPILATION ERROR :
>> [INFO] -------------------------------------------------------------
>> [ERROR] error: error reading
>> /home/der/.m2/repository/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar;
>>
>> error in opening zip file
>> [INFO] 1 error
>> ]]]
>>
>> I normally use m2e (v. 1.1.0.20120530-0009) under Eclipse (Juno) which
>> was giving a lot of mysterious errors. Only by wiping (the jena area of)
>> my maven repository and trying the command line could I see the above
>> error messages.
>>
>> Dave
>>
>> On 12/02/13 09:12, Andy Seaborne wrote:
>>> We're gearing up for the Jena 2.10.0 and we'd like to ask for your help
>>> testing it before the release.
>>>
>>> This is not an incremental release and so we are especially asking for
>>> feedback to make the transition as smooth a possible.
>>>
>>> Key changes are:
>>>
>>> * Reification - "Minimal" and "Convenient" styles have been removed.
>>> * New RDF 1.1 Turtle parser tracking the developing standard
>>> * A single maven artifact to include Jena in your maven project
>>> * Changes to the way storage subsystems provide SPARQL Update
>>>
>>> The snapshot repository is:
>>>
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/jena/
>>>
>>>
>>>
>>>
>>> and the download is in directory apache-jena. Please use the latest
>>> 2.10.0-SNAPSHOT (there are nightly builds so 'latest' is down the bottom
>>> if is more then one).
>>>
>>> You can find out which version have by running the SPARQL script with
>>> --version.
>>>
>>> We have undertaken some internal simplification and while we are not
>>> intending to cause change, we also recognize that some applications may
>>> be depending on internal code in ways we don't know about.
>>>
>>> We would most grateful for reports in the next 2 weeks of successful use
>>> or any problems arising.
>>>
>>> Andy
>>>
>>>
>>> == apache-jena-libs
>>>
>>> There is a new maven artifact to help applications by providing a single
>>> maven artifact that include the main Jena modules.
>>>
>>> <dependency>
>>> <groupId>org.apache.jena</groupId>
>>> <artifactId>apache-jena-libs</artifactId>
>>> <type>pom</type>
>>> <version>2.10.0</version>
>>> </dependency>
>>>
>>> Note the use of <type>pom</type>
>>>
>>> BY using this artifact, applications will not be affected by any future
>>> changes to the internal development module structure of Jena.
>>>
>>> See
>>> http://jena.staging.apache.org/download/maven.html
>>>
>>> == RIOT Reader
>>>
>>> There is a new RDF parser subsystem, which includes
>>>
>>> * improved content negotiation
>>> * the ability to register new parsers into Jena
>>> * alignment to RDF 1.1 Turtle
>>> * features apply when applications use model.read
>>>
>>> http://jena.apache.org/documentation/io/index.html
>>>
>>> The package name org.openjena.riot becomes org.apache.jena.riot.
>>>
>>> There is some compatibility code in org.openjena.riot. Operations are
>>> deprecated and will be removed after this release.
>>>
>>> Call
>>>
>>> org.apache.jena.riot.RIOT.init()
>>>
>>> to ensure it is initialized if in doubt but it should automatically be
>>> used by model.read.
>>>
>>> Test:
>>>
>>> model.read("data.ttl")
>>>
>>> will read a local Turtle file.
>>>
>>> == Streaming Update
>>>
>>> The SPARQL Update engine has been re-architected to make the fundamental
>>> execution of SPARQL Updates streamable.
>>>
>>> There is no change to applications using SPARQL Update.
>>>
>>> There are changes to the interface for storage systems that make special
>>> provision for SPARQL Update. If you are migrating such a storage system,
>>> do talk to the developers on dev@jena.apache.org if you have any
>>> questions or suggestions for improvements.
>>>
>>> == Portuguese Translations of the tutorial
>>>
>>> Guilherme Cavalcanti has provided a Portuguese translation of the
>>> tutorials.
>>>
>>> http://jena.staging.apache.org/tutorials/
>>>
>>> == Reification
>>>
>>> As part of simplifying Jena, the reification styles Convenient and
>>> Minimal are being removed. These need a significant amount of internal
>>> state management and impede scaling beyond storage in memory.
>>>
>>> The only support style is "standard", which as always been the default
>>> style in Jena. Only style "standard" has even been supported by TDB and
>>> SDB.
>>>
>>> Use of the constants for these styles is deprecated and will be treated
>>> as "standard".
>>>
>>> == Internal simplification
>>>
>>> Other simplifications in this release include the removal of the graph
>>> query handler subsystem. This is unrelated to SPARQL and existed in
>>> support of RDQL.
>>>
>>> The graph level bulk query handler has been removed - compatibility for
>>> the Model API for all bulk update is maintained.
>>>
>>>
>>>
>>>
>>
>
Re: Jena 2.10.0 : request for pre-release testing
Posted by Dave Reynolds <da...@gmail.com>.
I realise that the second set of traces shows Maven also trying our
local Epimorphics repositories. Just to make sure they aren't confusing
the poor thing I tried again with those remove from the pom. Similar
results:
[[[
Downloading:
https://repository.apache.org/content/repositories/releases/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
Downloading:
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
53ede9572737d92449809302a82f192cf7870165 for
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
53ede9572737d92449809302a82f192cf7870165 for
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
Downloaded:
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
(391 B at 0.0 KB/sec)
[WARNING] The metadata
/home/der/.m2/repository/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata-apache-repo-snapshots.xml
is invalid: end tag name </body> must match start tag name <hr> from
line 7 (position: TEXT seen ...</address>\n</body>... @9:8)
[WARNING] The metadata
/home/der/.m2/repository/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata-apache-repo-snapshots.xml
is invalid: end tag name </body> must match start tag name <hr> from
line 7 (position: TEXT seen ...</address>\n</body>... @9:8)
Downloading:
https://repository.apache.org/content/repositories/releases/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
Downloading:
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
90bfca3bbba171909dcef73af4c96a6fad064b48 for
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
90bfca3bbba171909dcef73af4c96a6fad064b48 for
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
Downloaded:
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
(401 B at 0.5 KB/sec)
[WARNING] The POM for org.apache.jena:jena-tdb:jar:0.10.0-SNAPSHOT is
invalid, transitive dependencies (if any) will not be available, enable
debug logging for more details
Downloading:
https://repository.apache.org/content/repositories/releases/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
Downloading:
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
7575871f9c161d3792cdff22930ea5f83b52969f for
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
7575871f9c161d3792cdff22930ea5f83b52969f for
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
Downloaded:
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
(401 B at 0.5 KB/sec)
]]]
Dave
On 16/02/13 18:23, Dave Reynolds wrote:
> Tried to test against existing projects but failed to get Maven
> resolution to work. No doubt user error (my inability to ever have Maven
> work for me is well known) but I've spend some time on this without
> getting anywhere.
>
> Using:
>
> <dependency>
> <groupId>org.apache.jena</groupId>
> <artifactId>apache-jena-libs</artifactId>
> <type>pom</type>
> <version>2.10.0-SNAPSHOT</version>
> </dependency>
>
> and my normal repository entries:
>
> <repositories>
> <repository>
> <id>apache-repo-releases</id>
>
> <url>https://repository.apache.org/content/repositories/releases/</url>
> <releases>
> <enabled>true</enabled>
> </releases>
> </repository>
>
> <repository>
> <id>apache-repo-snapshots</id>
>
> <url>https://repository.apache.org/content/repositories/snapshots/org/apache/jena/</url>
>
> <releases>
> <enabled>false</enabled>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> </snapshots>
> </repository>
> ...
> </repositories>
>
> Then using Maven command line (version 3.0.3, on Ubuntu 13.04) I see:
>
> [[[
> Downloading:
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/maven-metadata.xml
>
> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
> 94dbdf66c1bb3a5c799701be99258c04d5b08501 for
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/maven-metadata.xml
>
> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
> 94dbdf66c1bb3a5c799701be99258c04d5b08501 for
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/maven-metadata.xml
>
> Downloaded:
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/maven-metadata.xml
> (399 B at 0.0 KB/sec)
> [WARNING] The metadata
> /home/der/.m2/repository/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/maven-metadata-apache-repo-snapshots.xml
> is invalid: end tag name </body> must match start tag name <hr> from
> line 7 (position: TEXT seen ...</address>\n</body>... @9:8)
> Downloading:
> https://repository.apache.org/content/repositories/releases/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/apache-jena-libs-2.10.0-SNAPSHOT.pom
>
> Downloading:
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/apache-jena-libs-2.10.0-SNAPSHOT.pom
>
> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
> 130d6e8640395f95842df937e1d43bb33498e44a for
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/apache-jena-libs-2.10.0-SNAPSHOT.pom
>
> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
> 130d6e8640395f95842df937e1d43bb33498e44a for
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/apache-jena-libs-2.10.0-SNAPSHOT.pom
>
> Downloaded:
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/apache-jena-libs-2.10.0-SNAPSHOT.pom
> (417 B at 0.5 KB/sec)
> [WARNING] The POM for
> org.apache.jena:apache-jena-libs:pom:2.10.0-SNAPSHOT is invalid,
> transitive dependencies (if any) will not be available, enable debug
> logging for more details
> ]]]
>
> Nuking the entire Jena area of my ~/.m2/repository and switching to the
> dependency:
>
> <dependency>
> <groupId>org.apache.jena</groupId>
> <artifactId>jena-tdb</artifactId>
> <version>0.10.0-SNAPSHOT</version>
> </dependency>
>
> Then a clean compile generates:
>
> [[[
> Downloading:
> http://www.epimorphics.com/maven2/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
>
> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
> 53ede9572737d92449809302a82f192cf7870165 for
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
>
> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
> 53ede9572737d92449809302a82f192cf7870165 for
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
>
> Downloaded:
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
> (391 B at 0.0 KB/sec)
> [WARNING] Could not transfer metadata
> org.apache.jena:jena-tdb:0.10.0-SNAPSHOT/maven-metadata.xml from/to
> repo-epi (http://www.epimorphics.com/maven2): Access denied to:
> http://www.epimorphics.com/maven2/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
>
> [WARNING] The metadata
> /home/der/.m2/repository/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata-apache-repo-snapshots.xml
> is invalid: end tag name </body> must match start tag name <hr> from
> line 7 (position: TEXT seen ...</address>\n</body>... @9:8)
> Downloading:
> http://www.epimorphics.com/maven2/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
>
> [WARNING] The metadata
> /home/der/.m2/repository/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata-apache-repo-snapshots.xml
> is invalid: end tag name </body> must match start tag name <hr> from
> line 7 (position: TEXT seen ...</address>\n</body>... @9:8)
> Downloading:
> https://repository.apache.org/content/repositories/releases/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
>
> Downloading:
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
>
> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
> 90bfca3bbba171909dcef73af4c96a6fad064b48 for
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
>
> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
> 90bfca3bbba171909dcef73af4c96a6fad064b48 for
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
>
> Downloaded:
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
> (401 B at 0.5 KB/sec)
> [WARNING] The POM for org.apache.jena:jena-tdb:jar:0.10.0-SNAPSHOT is
> invalid, transitive dependencies (if any) will not be available, enable
> debug logging for more details
> Downloading:
> https://repository.apache.org/content/repositories/releases/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
>
> Downloading:
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
>
> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
> 7575871f9c161d3792cdff22930ea5f83b52969f for
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
>
> [WARNING] Checksum validation failed, expected <!DOCTYPE but is
> 7575871f9c161d3792cdff22930ea5f83b52969f for
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
>
> Downloaded:
> http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
> (401 B at 0.5 KB/sec)
>
> ...
>
> [INFO] -------------------------------------------------------------
> [ERROR] COMPILATION ERROR :
> [INFO] -------------------------------------------------------------
> [ERROR] error: error reading
> /home/der/.m2/repository/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar;
> error in opening zip file
> [INFO] 1 error
> ]]]
>
> I normally use m2e (v. 1.1.0.20120530-0009) under Eclipse (Juno) which
> was giving a lot of mysterious errors. Only by wiping (the jena area of)
> my maven repository and trying the command line could I see the above
> error messages.
>
> Dave
>
> On 12/02/13 09:12, Andy Seaborne wrote:
>> We're gearing up for the Jena 2.10.0 and we'd like to ask for your help
>> testing it before the release.
>>
>> This is not an incremental release and so we are especially asking for
>> feedback to make the transition as smooth a possible.
>>
>> Key changes are:
>>
>> * Reification - "Minimal" and "Convenient" styles have been removed.
>> * New RDF 1.1 Turtle parser tracking the developing standard
>> * A single maven artifact to include Jena in your maven project
>> * Changes to the way storage subsystems provide SPARQL Update
>>
>> The snapshot repository is:
>>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/jena/
>>
>>
>>
>> and the download is in directory apache-jena. Please use the latest
>> 2.10.0-SNAPSHOT (there are nightly builds so 'latest' is down the bottom
>> if is more then one).
>>
>> You can find out which version have by running the SPARQL script with
>> --version.
>>
>> We have undertaken some internal simplification and while we are not
>> intending to cause change, we also recognize that some applications may
>> be depending on internal code in ways we don't know about.
>>
>> We would most grateful for reports in the next 2 weeks of successful use
>> or any problems arising.
>>
>> Andy
>>
>>
>> == apache-jena-libs
>>
>> There is a new maven artifact to help applications by providing a single
>> maven artifact that include the main Jena modules.
>>
>> <dependency>
>> <groupId>org.apache.jena</groupId>
>> <artifactId>apache-jena-libs</artifactId>
>> <type>pom</type>
>> <version>2.10.0</version>
>> </dependency>
>>
>> Note the use of <type>pom</type>
>>
>> BY using this artifact, applications will not be affected by any future
>> changes to the internal development module structure of Jena.
>>
>> See
>> http://jena.staging.apache.org/download/maven.html
>>
>> == RIOT Reader
>>
>> There is a new RDF parser subsystem, which includes
>>
>> * improved content negotiation
>> * the ability to register new parsers into Jena
>> * alignment to RDF 1.1 Turtle
>> * features apply when applications use model.read
>>
>> http://jena.apache.org/documentation/io/index.html
>>
>> The package name org.openjena.riot becomes org.apache.jena.riot.
>>
>> There is some compatibility code in org.openjena.riot. Operations are
>> deprecated and will be removed after this release.
>>
>> Call
>>
>> org.apache.jena.riot.RIOT.init()
>>
>> to ensure it is initialized if in doubt but it should automatically be
>> used by model.read.
>>
>> Test:
>>
>> model.read("data.ttl")
>>
>> will read a local Turtle file.
>>
>> == Streaming Update
>>
>> The SPARQL Update engine has been re-architected to make the fundamental
>> execution of SPARQL Updates streamable.
>>
>> There is no change to applications using SPARQL Update.
>>
>> There are changes to the interface for storage systems that make special
>> provision for SPARQL Update. If you are migrating such a storage system,
>> do talk to the developers on dev@jena.apache.org if you have any
>> questions or suggestions for improvements.
>>
>> == Portuguese Translations of the tutorial
>>
>> Guilherme Cavalcanti has provided a Portuguese translation of the
>> tutorials.
>>
>> http://jena.staging.apache.org/tutorials/
>>
>> == Reification
>>
>> As part of simplifying Jena, the reification styles Convenient and
>> Minimal are being removed. These need a significant amount of internal
>> state management and impede scaling beyond storage in memory.
>>
>> The only support style is "standard", which as always been the default
>> style in Jena. Only style "standard" has even been supported by TDB and
>> SDB.
>>
>> Use of the constants for these styles is deprecated and will be treated
>> as "standard".
>>
>> == Internal simplification
>>
>> Other simplifications in this release include the removal of the graph
>> query handler subsystem. This is unrelated to SPARQL and existed in
>> support of RDQL.
>>
>> The graph level bulk query handler has been removed - compatibility for
>> the Model API for all bulk update is maintained.
>>
>>
>>
>>
>
Re: Jena 2.10.0 : request for pre-release testing
Posted by Dave Reynolds <da...@gmail.com>.
Tried to test against existing projects but failed to get Maven
resolution to work. No doubt user error (my inability to ever have Maven
work for me is well known) but I've spend some time on this without
getting anywhere.
Using:
<dependency>
<groupId>org.apache.jena</groupId>
<artifactId>apache-jena-libs</artifactId>
<type>pom</type>
<version>2.10.0-SNAPSHOT</version>
</dependency>
and my normal repository entries:
<repositories>
<repository>
<id>apache-repo-releases</id>
<url>https://repository.apache.org/content/repositories/releases/</url>
<releases>
<enabled>true</enabled>
</releases>
</repository>
<repository>
<id>apache-repo-snapshots</id>
<url>https://repository.apache.org/content/repositories/snapshots/org/apache/jena/</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
...
</repositories>
Then using Maven command line (version 3.0.3, on Ubuntu 13.04) I see:
[[[
Downloading:
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/maven-metadata.xml
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
94dbdf66c1bb3a5c799701be99258c04d5b08501 for
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/maven-metadata.xml
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
94dbdf66c1bb3a5c799701be99258c04d5b08501 for
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/maven-metadata.xml
Downloaded:
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/maven-metadata.xml
(399 B at 0.0 KB/sec)
[WARNING] The metadata
/home/der/.m2/repository/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/maven-metadata-apache-repo-snapshots.xml
is invalid: end tag name </body> must match start tag name <hr> from
line 7 (position: TEXT seen ...</address>\n</body>... @9:8)
Downloading:
https://repository.apache.org/content/repositories/releases/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/apache-jena-libs-2.10.0-SNAPSHOT.pom
Downloading:
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/apache-jena-libs-2.10.0-SNAPSHOT.pom
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
130d6e8640395f95842df937e1d43bb33498e44a for
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/apache-jena-libs-2.10.0-SNAPSHOT.pom
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
130d6e8640395f95842df937e1d43bb33498e44a for
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/apache-jena-libs-2.10.0-SNAPSHOT.pom
Downloaded:
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-libs/2.10.0-SNAPSHOT/apache-jena-libs-2.10.0-SNAPSHOT.pom
(417 B at 0.5 KB/sec)
[WARNING] The POM for
org.apache.jena:apache-jena-libs:pom:2.10.0-SNAPSHOT is invalid,
transitive dependencies (if any) will not be available, enable debug
logging for more details
]]]
Nuking the entire Jena area of my ~/.m2/repository and switching to the
dependency:
<dependency>
<groupId>org.apache.jena</groupId>
<artifactId>jena-tdb</artifactId>
<version>0.10.0-SNAPSHOT</version>
</dependency>
Then a clean compile generates:
[[[
Downloading:
http://www.epimorphics.com/maven2/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
53ede9572737d92449809302a82f192cf7870165 for
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
53ede9572737d92449809302a82f192cf7870165 for
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
Downloaded:
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
(391 B at 0.0 KB/sec)
[WARNING] Could not transfer metadata
org.apache.jena:jena-tdb:0.10.0-SNAPSHOT/maven-metadata.xml from/to
repo-epi (http://www.epimorphics.com/maven2): Access denied to:
http://www.epimorphics.com/maven2/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
[WARNING] The metadata
/home/der/.m2/repository/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata-apache-repo-snapshots.xml
is invalid: end tag name </body> must match start tag name <hr> from
line 7 (position: TEXT seen ...</address>\n</body>... @9:8)
Downloading:
http://www.epimorphics.com/maven2/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata.xml
[WARNING] The metadata
/home/der/.m2/repository/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/maven-metadata-apache-repo-snapshots.xml
is invalid: end tag name </body> must match start tag name <hr> from
line 7 (position: TEXT seen ...</address>\n</body>... @9:8)
Downloading:
https://repository.apache.org/content/repositories/releases/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
Downloading:
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
90bfca3bbba171909dcef73af4c96a6fad064b48 for
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
90bfca3bbba171909dcef73af4c96a6fad064b48 for
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
Downloaded:
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.pom
(401 B at 0.5 KB/sec)
[WARNING] The POM for org.apache.jena:jena-tdb:jar:0.10.0-SNAPSHOT is
invalid, transitive dependencies (if any) will not be available, enable
debug logging for more details
Downloading:
https://repository.apache.org/content/repositories/releases/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
Downloading:
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
7575871f9c161d3792cdff22930ea5f83b52969f for
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
[WARNING] Checksum validation failed, expected <!DOCTYPE but is
7575871f9c161d3792cdff22930ea5f83b52969f for
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
Downloaded:
http://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar
(401 B at 0.5 KB/sec)
...
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] error: error reading
/home/der/.m2/repository/org/apache/jena/jena-tdb/0.10.0-SNAPSHOT/jena-tdb-0.10.0-SNAPSHOT.jar;
error in opening zip file
[INFO] 1 error
]]]
I normally use m2e (v. 1.1.0.20120530-0009) under Eclipse (Juno) which
was giving a lot of mysterious errors. Only by wiping (the jena area of)
my maven repository and trying the command line could I see the above
error messages.
Dave
On 12/02/13 09:12, Andy Seaborne wrote:
> We're gearing up for the Jena 2.10.0 and we'd like to ask for your help
> testing it before the release.
>
> This is not an incremental release and so we are especially asking for
> feedback to make the transition as smooth a possible.
>
> Key changes are:
>
> * Reification - "Minimal" and "Convenient" styles have been removed.
> * New RDF 1.1 Turtle parser tracking the developing standard
> * A single maven artifact to include Jena in your maven project
> * Changes to the way storage subsystems provide SPARQL Update
>
> The snapshot repository is:
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/jena/
>
>
> and the download is in directory apache-jena. Please use the latest
> 2.10.0-SNAPSHOT (there are nightly builds so 'latest' is down the bottom
> if is more then one).
>
> You can find out which version have by running the SPARQL script with
> --version.
>
> We have undertaken some internal simplification and while we are not
> intending to cause change, we also recognize that some applications may
> be depending on internal code in ways we don't know about.
>
> We would most grateful for reports in the next 2 weeks of successful use
> or any problems arising.
>
> Andy
>
>
> == apache-jena-libs
>
> There is a new maven artifact to help applications by providing a single
> maven artifact that include the main Jena modules.
>
> <dependency>
> <groupId>org.apache.jena</groupId>
> <artifactId>apache-jena-libs</artifactId>
> <type>pom</type>
> <version>2.10.0</version>
> </dependency>
>
> Note the use of <type>pom</type>
>
> BY using this artifact, applications will not be affected by any future
> changes to the internal development module structure of Jena.
>
> See
> http://jena.staging.apache.org/download/maven.html
>
> == RIOT Reader
>
> There is a new RDF parser subsystem, which includes
>
> * improved content negotiation
> * the ability to register new parsers into Jena
> * alignment to RDF 1.1 Turtle
> * features apply when applications use model.read
>
> http://jena.apache.org/documentation/io/index.html
>
> The package name org.openjena.riot becomes org.apache.jena.riot.
>
> There is some compatibility code in org.openjena.riot. Operations are
> deprecated and will be removed after this release.
>
> Call
>
> org.apache.jena.riot.RIOT.init()
>
> to ensure it is initialized if in doubt but it should automatically be
> used by model.read.
>
> Test:
>
> model.read("data.ttl")
>
> will read a local Turtle file.
>
> == Streaming Update
>
> The SPARQL Update engine has been re-architected to make the fundamental
> execution of SPARQL Updates streamable.
>
> There is no change to applications using SPARQL Update.
>
> There are changes to the interface for storage systems that make special
> provision for SPARQL Update. If you are migrating such a storage system,
> do talk to the developers on dev@jena.apache.org if you have any
> questions or suggestions for improvements.
>
> == Portuguese Translations of the tutorial
>
> Guilherme Cavalcanti has provided a Portuguese translation of the
> tutorials.
>
> http://jena.staging.apache.org/tutorials/
>
> == Reification
>
> As part of simplifying Jena, the reification styles Convenient and
> Minimal are being removed. These need a significant amount of internal
> state management and impede scaling beyond storage in memory.
>
> The only support style is "standard", which as always been the default
> style in Jena. Only style "standard" has even been supported by TDB and
> SDB.
>
> Use of the constants for these styles is deprecated and will be treated
> as "standard".
>
> == Internal simplification
>
> Other simplifications in this release include the removal of the graph
> query handler subsystem. This is unrelated to SPARQL and existed in
> support of RDQL.
>
> The graph level bulk query handler has been removed - compatibility for
> the Model API for all bulk update is maintained.
>
>
>
>
Re: Jena 2.10.0 : request for pre-release testing
Posted by Andy Seaborne <an...@apache.org>.
On 15/02/13 17:53, Jeroen Kransen wrote:
> Hi, sorry Andy, a lot of things have been going on here.
No problem - I don't usually ping people (we all busy) but we're in a
release cycle so I wanted to check I understood what's going on.
I think we've established that there hasn't been a step backwards. The
SDB and TDB cases are similar but the fixes would be in SDB or TDB - not
the general framework.
The node table is hard to GC - reference counting on nodes would be much
more expensive than is worth it.
> We switched back to TDB again (at least my code is generic enough now to
> be easy to switch back and forth).
>
> We keep having a problem with growing databases, both in SDB and TDB,
> both recent snapshots (pre-2.10 release). Our typical use case is that
> we fetch triples from sources and store it in a named graph with ID
> equal to the source URL. We delete the old data before we do. I wonder
> if this is a typical use case or that people normally keep their triples
> forever and never overwrite. We do use layout2, but I can't recall if it
> was hashed or indexed at this moment (I'm home now).
>
> I would love to contribute to Jena, but it would cost me some effort to
> dive into it, get up to speed and trace the problem. A problem is that
> the project will come to an end for me soon, but a team member might
> take over. I will keep it in mind. The least I can do is add a failing
> unit test that points out the problem. Not sure if that will be possible
> (or even desirable) in the two-week window you set for the upcoming release.
This isn't going to get addressed in this cycle so a test case would be
great but it's independent of the release cycle from my POV.
>
> You will hear from me when I have anything to contribute. Thanks for now
> and have a nice weekend!
Have a good weekend,
Andy
>
> Jeroen
>
>
> 2013/2/15 Andy Seaborne <andy@apache.org <ma...@apache.org>>
>
> Jeroen - ping?
>
>
>
> -------- Original Message --------
> Subject: Re: Jena 2.10.0 : request for pre-release testing
> Date: Tue, 12 Feb 2013 16:15:45 +0000
> From: Andy Seaborne <andy@apache.org <ma...@apache.org>>
> To: users@jena.apache.org <ma...@jena.apache.org>
>
> On 12/02/13 13:50, Jeroen Kransen wrote:
>
> Is it ok to report bugs here? I just downloaded the release
> candidate to
> try and see if it solves an issue we're having. It does not.
>
>
> The project uses JIRA:
>
> https://issues.apache.org/__jira/browse/JENA
> <https://issues.apache.org/jira/browse/JENA>
>
> If you could provide a complete, minimal example (ideally with Derby or
> H2 for practicality reasons), someone might have a look. Patches
> welcome.
>
> In SDB, when we try to delete a named graph, it does not delete
> it. It
> seems to make a switch from named graph to default graph and try
> to delete
> the triples there. I tried to debug what happened. In the class
> DatasetGraph line 165 it explicitly converts triples to quads
> using the
> default graph uri. I suspect this is wrong, as it tracked the
> graph uri up
> till this point.
>
>
> Even in layout2?
> ...
>
>
Re: Re: Jena 2.10.0 : request for pre-release testing
Posted by Jeroen Kransen <je...@kransen.nl>.
Hi, sorry Andy, a lot of things have been going on here.
We switched back to TDB again (at least my code is generic enough now to be
easy to switch back and forth).
We keep having a problem with growing databases, both in SDB and TDB, both
recent snapshots (pre-2.10 release). Our typical use case is that we fetch
triples from sources and store it in a named graph with ID equal to the
source URL. We delete the old data before we do. I wonder if this is a
typical use case or that people normally keep their triples forever and
never overwrite. We do use layout2, but I can't recall if it was hashed or
indexed at this moment (I'm home now).
I would love to contribute to Jena, but it would cost me some effort to
dive into it, get up to speed and trace the problem. A problem is that the
project will come to an end for me soon, but a team member might take over.
I will keep it in mind. The least I can do is add a failing unit test that
points out the problem. Not sure if that will be possible (or even
desirable) in the two-week window you set for the upcoming release.
You will hear from me when I have anything to contribute. Thanks for now
and have a nice weekend!
Jeroen
2013/2/15 Andy Seaborne <an...@apache.org>
> Jeroen - ping?
>
>
>
> -------- Original Message --------
> Subject: Re: Jena 2.10.0 : request for pre-release testing
> Date: Tue, 12 Feb 2013 16:15:45 +0000
> From: Andy Seaborne <an...@apache.org>
> To: users@jena.apache.org
>
> On 12/02/13 13:50, Jeroen Kransen wrote:
>
>> Is it ok to report bugs here? I just downloaded the release candidate to
>> try and see if it solves an issue we're having. It does not.
>>
>
> The project uses JIRA:
>
> https://issues.apache.org/**jira/browse/JENA<https://issues.apache.org/jira/browse/JENA>
>
> If you could provide a complete, minimal example (ideally with Derby or
> H2 for practicality reasons), someone might have a look. Patches welcome.
>
> In SDB, when we try to delete a named graph, it does not delete it. It
>> seems to make a switch from named graph to default graph and try to delete
>> the triples there. I tried to debug what happened. In the class
>> DatasetGraph line 165 it explicitly converts triples to quads using the
>> default graph uri. I suspect this is wrong, as it tracked the graph uri up
>> till this point.
>>
>
> Even in layout2?
> ...
>
Fwd: Re: Jena 2.10.0 : request for pre-release testing
Posted by Andy Seaborne <an...@apache.org>.
Jeroen - ping?
-------- Original Message --------
Subject: Re: Jena 2.10.0 : request for pre-release testing
Date: Tue, 12 Feb 2013 16:15:45 +0000
From: Andy Seaborne <an...@apache.org>
To: users@jena.apache.org
On 12/02/13 13:50, Jeroen Kransen wrote:
> Is it ok to report bugs here? I just downloaded the release candidate to
> try and see if it solves an issue we're having. It does not.
The project uses JIRA:
https://issues.apache.org/jira/browse/JENA
If you could provide a complete, minimal example (ideally with Derby or
H2 for practicality reasons), someone might have a look. Patches welcome.
> In SDB, when we try to delete a named graph, it does not delete it. It
> seems to make a switch from named graph to default graph and try to delete
> the triples there. I tried to debug what happened. In the class
> DatasetGraph line 165 it explicitly converts triples to quads using the
> default graph uri. I suspect this is wrong, as it tracked the graph uri up
> till this point.
Even in layout2?
...
Re: Jena 2.10.0 : request for pre-release testing
Posted by Andy Seaborne <an...@apache.org>.
On 12/02/13 13:50, Jeroen Kransen wrote:
> Is it ok to report bugs here? I just downloaded the release candidate to
> try and see if it solves an issue we're having. It does not.
The project uses JIRA:
https://issues.apache.org/jira/browse/JENA
If you could provide a complete, minimal example (ideally with Derby or
H2 for practicality reasons), someone might have a look. Patches welcome.
> In SDB, when we try to delete a named graph, it does not delete it. It
> seems to make a switch from named graph to default graph and try to delete
> the triples there. I tried to debug what happened. In the class
> DatasetGraph line 165 it explicitly converts triples to quads using the
> default graph uri. I suspect this is wrong, as it tracked the graph uri up
> till this point.
Even in layout2?
> When debugging I also had a suspicion that in SDB the triples are deleted
> one by one when deleting a whole graph. Is this true? Because I would think
> it is much more efficient to do a "delete where graph = :graph" instead. I
> hope I'm wrong on this.
>
> In a previous version of TDB I recently mentioned a bug where disk space is
> not freed when named graphs are deleted. Is this solved by any chance in
> this release candidate? It is too much work for me to switch back just to
> try it at this moment.
No changes in this area.
The issue is two fold:
1/ across restarts (index blocks should be recycled within a JVM
2/ the node table isn't GC'ed
(but it isn't in SDB either nor various other RDF databases)
I'd like to add a "compact" operation but I have there are higher
priorities.
> Could SDB also be added to the aggregated build?
The testing cycle for SDB is much longer so it would have a major impact
on the rest of Jena.
We have been keeping the SNAPSHOT up to date and it runs the test suite
nightly on Derby (which is quite picky so a good test SQL DB and it also
can execute tree-joins queries, which H2 and friends can't).
I am not comfortable with untested software being released. I used to
have access to a machine with every database installed for SDB testing
but I don't now. I don't use SDB at work currently so my work time
isn't going to go on it.
If people want to join and help systematic regular testing of SDB that
would be ideal. It does not have to be down to the project committers.
The community is everyone interested.
The brutal bottom line is that if there is no help, it does not get
tested. It's as simple as that.
Andy
> Jeroen
>
>
> 2013/2/12 Adrian Gschwend <ml...@netlabs.org>
>
>> On 12.02.13 14:11, Claude Warren wrote:
>>
>>> Is that information on a webpage somewhere? I'd like to be able to point
>>> to it in any posts.
>>
>>
>> https://mail-archives.apache.org/mod_mbox/jena-users/201302.mbox/%3C511A076A.2030907%40apache.org%3E
>>
>> :-D
>>
>> cu
>>
>> Adrian
>>
>
Re: Jena 2.10.0 : request for pre-release testing
Posted by Jeroen Kransen <je...@kransen.nl>.
Is it ok to report bugs here? I just downloaded the release candidate to
try and see if it solves an issue we're having. It does not.
In SDB, when we try to delete a named graph, it does not delete it. It
seems to make a switch from named graph to default graph and try to delete
the triples there. I tried to debug what happened. In the class
DatasetGraph line 165 it explicitly converts triples to quads using the
default graph uri. I suspect this is wrong, as it tracked the graph uri up
till this point.
When debugging I also had a suspicion that in SDB the triples are deleted
one by one when deleting a whole graph. Is this true? Because I would think
it is much more efficient to do a "delete where graph = :graph" instead. I
hope I'm wrong on this.
In a previous version of TDB I recently mentioned a bug where disk space is
not freed when named graphs are deleted. Is this solved by any chance in
this release candidate? It is too much work for me to switch back just to
try it at this moment.
Could SDB also be added to the aggregated build?
Jeroen
2013/2/12 Adrian Gschwend <ml...@netlabs.org>
> On 12.02.13 14:11, Claude Warren wrote:
>
> > Is that information on a webpage somewhere? I'd like to be able to point
> > to it in any posts.
>
>
> https://mail-archives.apache.org/mod_mbox/jena-users/201302.mbox/%3C511A076A.2030907%40apache.org%3E
>
> :-D
>
> cu
>
> Adrian
>
Re: Jena 2.10.0 : request for pre-release testing
Posted by Andy Seaborne <an...@apache.org>.
On 12/02/13 13:15, Adrian Gschwend wrote:
> On 12.02.13 14:11, Claude Warren wrote:
>
>> Is that information on a webpage somewhere? I'd like to be able to point
>> to it in any posts.
>
> https://mail-archives.apache.org/mod_mbox/jena-users/201302.mbox/%3C511A076A.2030907%40apache.org%3E
:-)
also available via:
http://s.apache.org/jena-2.10.0-testing
("s." is the Apache URL shortener - any committer can use it).
Andy
>
> :-D
>
> cu
>
> Adrian
>
Re: Jena 2.10.0 : request for pre-release testing
Posted by Adrian Gschwend <ml...@netlabs.org>.
On 12.02.13 14:11, Claude Warren wrote:
> Is that information on a webpage somewhere? I'd like to be able to point
> to it in any posts.
https://mail-archives.apache.org/mod_mbox/jena-users/201302.mbox/%3C511A076A.2030907%40apache.org%3E
:-D
cu
Adrian
Re: Jena 2.10.0 : request for pre-release testing
Posted by Claude Warren <cl...@xenei.com>.
Andy,
Is that information on a webpage somewhere? I'd like to be able to point
to it in any posts.
thx,
Claude
On Tue, Feb 12, 2013 at 9:12 AM, Andy Seaborne <an...@apache.org> wrote:
> We're gearing up for the Jena 2.10.0 and we'd like to ask for your help
> testing it before the release.
>
> This is not an incremental release and so we are especially asking for
> feedback to make the transition as smooth a possible.
>
> Key changes are:
>
> * Reification - "Minimal" and "Convenient" styles have been removed.
> * New RDF 1.1 Turtle parser tracking the developing standard
> * A single maven artifact to include Jena in your maven project
> * Changes to the way storage subsystems provide SPARQL Update
>
> The snapshot repository is:
>
> https://repository.apache.org/**content/repositories/**
> snapshots/org/apache/jena/<https://repository.apache.org/content/repositories/snapshots/org/apache/jena/>
>
> and the download is in directory apache-jena. Please use the latest
> 2.10.0-SNAPSHOT (there are nightly builds so 'latest' is down the bottom if
> is more then one).
>
> You can find out which version have by running the SPARQL script with
> --version.
>
> We have undertaken some internal simplification and while we are not
> intending to cause change, we also recognize that some applications may be
> depending on internal code in ways we don't know about.
>
> We would most grateful for reports in the next 2 weeks of successful use
> or any problems arising.
>
> Andy
>
>
> == apache-jena-libs
>
> There is a new maven artifact to help applications by providing a single
> maven artifact that include the main Jena modules.
>
> <dependency>
> <groupId>org.apache.jena</**groupId>
> <artifactId>apache-jena-libs</**artifactId>
> <type>pom</type>
> <version>2.10.0</version>
> </dependency>
>
> Note the use of <type>pom</type>
>
> BY using this artifact, applications will not be affected by any future
> changes to the internal development module structure of Jena.
>
> See
> http://jena.staging.apache.**org/download/maven.html<http://jena.staging.apache.org/download/maven.html>
>
> == RIOT Reader
>
> There is a new RDF parser subsystem, which includes
>
> * improved content negotiation
> * the ability to register new parsers into Jena
> * alignment to RDF 1.1 Turtle
> * features apply when applications use model.read
>
> http://jena.apache.org/**documentation/io/index.html<http://jena.apache.org/documentation/io/index.html>
>
> The package name org.openjena.riot becomes org.apache.jena.riot.
>
> There is some compatibility code in org.openjena.riot. Operations are
> deprecated and will be removed after this release.
>
> Call
>
> org.apache.jena.riot.RIOT.**init()
>
> to ensure it is initialized if in doubt but it should automatically be
> used by model.read.
>
> Test:
>
> model.read("data.ttl")
>
> will read a local Turtle file.
>
> == Streaming Update
>
> The SPARQL Update engine has been re-architected to make the fundamental
> execution of SPARQL Updates streamable.
>
> There is no change to applications using SPARQL Update.
>
> There are changes to the interface for storage systems that make special
> provision for SPARQL Update. If you are migrating such a storage system,
> do talk to the developers on dev@jena.apache.org if you have any
> questions or suggestions for improvements.
>
> == Portuguese Translations of the tutorial
>
> Guilherme Cavalcanti has provided a Portuguese translation of the
> tutorials.
>
> http://jena.staging.apache.**org/tutorials/<http://jena.staging.apache.org/tutorials/>
>
> == Reification
>
> As part of simplifying Jena, the reification styles Convenient and
> Minimal are being removed. These need a significant amount of internal
> state management and impede scaling beyond storage in memory.
>
> The only support style is "standard", which as always been the default
> style in Jena. Only style "standard" has even been supported by TDB and
> SDB.
>
> Use of the constants for these styles is deprecated and will be treated
> as "standard".
>
> == Internal simplification
>
> Other simplifications in this release include the removal of the graph
> query handler subsystem. This is unrelated to SPARQL and existed in
> support of RDQL.
>
> The graph level bulk query handler has been removed - compatibility for
> the Model API for all bulk update is maintained.
>
>
>
>
>
--
I like: Like Like - The likeliest place on the web<http://like-like.xenei.com>
Identity: https://www.identify.nu/user.php?claude@xenei.com
LinkedIn: http://www.linkedin.com/in/claudewarren