-1
The control panel is broken for me in the default install. Steps to reproduce:
wget
https://repository.apache.org/content/repositories/orgapachejena-071/org/apache/jena/jena-fuseki/0.2.1-incubating/jena-fuseki-0.2.1-incubating-distribution.tar.gz
tar xfvz jena-fuseki-0.2.1-incubating-distribution.tar.gz
cd jena-fuseki-0.2.1-incubating
./fuseki-server --update --mem /dataset
I then browse to "http://localhost:3030/control-panel.tpl";. I see
"/dataset" in the combo box and I press the "Select" button. I get
the following results:
Error 400: No query string
Fuseki - version 0.2.1-incubating (Build date: 2012-03-13T09:35:00+0000)
Also, SPARQLer ("http://localhost:3030/sparql.html";) doesn't seem to
work either:
Error 400: No dataset description in protocol request or in the query string
Fuseki - version 0.2.1-incubating (Build date: 2012-03-13T09:35:00+0000)
The command line s-* tools however seem to work fine when I use commands like:
./s-put http://localhost:3030/dataset/data default test.nt
./s-query --service http://localhost:3030/dataset/query 'SELECT * {?s ?p ?o}'
-Stephen
On Thu, Mar 15, 2012 at 10:28 AM, Robert Vesse <[email protected]> wrote:
> Looks good
>
> +1
>
> Rob
>
> On Mar 14, 2012, at 12:11 AM, Paolo Castagna wrote:
>
>> Andy Seaborne wrote:
>>> The module is tagged with the version and "RC-1" to indicate the release
>>> candidate in this release cycle. If voted on successfully, the tag will
>>> be changed ("svn mv") to the same name but minus the RC designation.
>>
>> Not an issue, but I've noticed that doing it this way the pom.xml <scm>
>> element has -RC-1 in it. I normally do not use -RC-1 when I use the
>> maven-release-plugin and the tag is exactly what's there in <scm>.
>>
>> (Indeed, I am not even sure on what's the reason we do it this way. Another
>> option is not to use "RC-1", if a vote is not successful the tag can be
>> deleted. Tagging with "RC-1" allows to have two or more release candidates
>> at the same time, for the same project. Is this the reason?)
>>
>>> Please vote to approve this release:
>>>
>>> [ ] +1 Approve the release
>>> [ ] 0 Don't care
>>> [ ] -1 Don't release, because ...
>>
>> +1
>>
>>
>> Longer answer:
>>
>> 1. is the GPG signature fine?
>>
>> cd /tmp/
>> wget
>> http://people.apache.org/~andy/merge-jena-fuseki-0.2.1-RC-1/jena-fuseki-0.2.1-incubating/jena-fuseki-0.2.1-incubating-source-release.zip
>> wget
>> http://people.apache.org/~andy/merge-jena-fuseki-0.2.1-RC-1/jena-fuseki-0.2.1-incubating/jena-fuseki-0.2.1-incubating-source-release.zip.asc
>> wget http://people.apache.org/~andy/merge-jena-fuseki-0.2.1-RC-1/KEYS
>> gpg --import < KEYS
>> gpg --verify jena-fuseki-0.2.1-incubating-source-release.zip.asc
>>
>> [ok]
>>
>> 2. is there a source archive?
>>
>> http://people.apache.org/~andy/merge-jena-fuseki-0.2.1-RC-1/jena-fuseki-0.2.1-incubating/jena-fuseki-0.2.1-incubating-source-release.zip
>>
>> [ok]
>>
>> 3. can the source archive really be built?
>>
>> cd /tmp
>> wget
>> http://people.apache.org/~andy/merge-jena-fuseki-0.2.1-RC-1/jena-fuseki-0.2.1-incubating/jena-fuseki-0.2.1-incubating-source-release.zip
>> unzip jena-fuseki-0.2.1-incubating-source-release.zip
>> cd jena-fuseki-0.2.1-incubating
>> mvn clean package
>>
>> [ok]
>>
>> 4. is there a correct LICENSE and NOTICE file in each artifact (both source
>> and
>> binary artifacts)?
>>
>> cd /tmp/jena-fuseki-0.2.1-incubating
>> cat NOTICE
>> cat DEPENDENCIES
>> cat LICENSE
>>
>> cd /tmp
>> rm -rf /tmp/jena-fuseki-0.2.1-incubating
>> wget
>> http://people.apache.org/~andy/merge-jena-fuseki-0.2.1-RC-1/jena-fuseki-0.2.1-incubating/jena-fuseki-0.2.1-incubating-distribution.tar.gz
>> tar xvfz jena-fuseki-0.2.1-incubating-distribution.tar.gz
>> cd /tmp/jena-fuseki-0.2.1-incubating
>> cat NOTICE
>> cat DEPENDENCIES
>> cat LICENSE
>> (these have the additional info for the binary release)
>>
>> [ok]
>>
>> cd /tmp
>> wget
>> https://repository.apache.org/content/repositories/orgapachejena-071/org/apache/jena/jena-fuseki/0.2.1-incubating/jena-fuseki-0.2.1-incubating-server.jar
>> jar xvf jena-fuseki-0.2.1-incubating-server.jar
>> cat META-INF/LICENSE
>> cat META-INF/NOTICE
>>
>> [ok]
>>
>> 5. does the NOTICE file contain all necessary attributions?
>>
>> [ok]
>>
>> 6. check the dependencies. We must not have any GPL dependencies and LGPL
>> only
>> if they are optional, etc! See http://www.apache.org/legal/3party.html
>>
>> [ok]
>>
>> 7. do all the tests work?
>>
>> [ok]
>>
>> 8. if there is a TCK to run, does it succeed?
>>
>> [skip]
>>
>> 9. if there is a tag in the SCM, does it contain reproducible sources?
>>
>> cd /tmp
>> svn co
>> https://svn.apache.org/repos/asf/incubator/jena/Jena2/Fuseki/tags/jena-fuseki-0.2.1-incubating-RC-1/
>> jena-fuseki-0.2.1-incubating-RC-1
>> cd jena-fuseki-0.2.1-incubating-RC-1
>> mvn clean package -Papache-release
>> cd target
>> unzip jena-fuseki-0.2.1-incubating-source-release.zip
>> cd jena-fuseki-0.2.1-incubating
>> mvn clean package
>> cat NOTICE
>> cat DEPENDENCIES
>> cat LICENSE
>>
>> [ok]
>>
>> 10. are the Maven artifacts fine?
>>
>> Manual/visual inspection only, I did not tested this (I currently have no
>> projects using Fuseki as a library)
>> https://repository.apache.org/content/repositories/orgapachejena-071
>>
>> [skip]
>>
>>
>> Thanks Andy.
>>
>> Paolo
>>
>
