Github user afs commented on a diff in the pull request:
https://github.com/apache/jena/pull/76#discussion_r32211834
--- Diff: jena-core/src/main/java/jena/RuleMap.java ---
@@ -50,7 +53,7 @@
* /p
*/
public class RuleMap {
-static { setLog4jConfiguration() ;
[
https://issues.apache.org/jira/browse/JENA-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14581842#comment-14581842
]
Andy Seaborne commented on JENA-962:
Jena2 is RDF 1.0 and Jena3 is RDF 1.1 -- rdfcat
Github user afs commented on a diff in the pull request:
https://github.com/apache/jena/pull/76#discussion_r32212217
--- Diff: jena-core/src/test/java/org/apache/jena/test/TestPackage.java ---
@@ -32,7 +33,7 @@
public class TestPackage extends TestCase {
--- End diff
On 20/05/15 18:48, Claude Warren wrote:
parallel for now, but I expect we would move a fair number of tests to it
as a replacement.
I'm not so sure replacement is the right thing to do and I'd welcome
veryone's thoughts. It would introduce a signifcant dependency on
On 19/05/15 20:25, Claude Warren wrote:
There is a set of contract tests (and test helpers) on the
add-contract-tests branch. That branch works and has minimal change from
the current tests. Those changes are adding the junit-contract runner and
plugins.
It makes no change to the execution.
Github user afs commented on a diff in the pull request:
https://github.com/apache/jena/pull/76#discussion_r32212133
--- Diff: jena-core/pom.xml ---
@@ -56,12 +56,24 @@
groupIdxerces/groupId
artifactIdxercesImpl/artifactId
Hi Qihong,
Have you modified any files? If the grammar file is identical, the
checksum of each generated java class should be the same.
Best regards,
Ying Jiang
On Mon, Jun 8, 2015 at 5:27 PM, Qihong Lin confidence@gmail.com wrote:
Hi,
The grammar has been modified for the problems you
In the PR I submitted a day or two ago, I added a DEPRECATED: Please use riot
instead message to the help of rdfcat, but I didn't have it emit that message
to stderr on all runs. That seems like a good move to me. I'll add that, and we
can then decide whether to go all the way to having that be
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/76#issuecomment-111221573
Thanks for clearing it up. I've just pulled it into the codebase.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/76
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
[
https://issues.apache.org/jira/browse/JENA-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14582276#comment-14582276
]
ASF GitHub Bot commented on JENA-962:
-
Github user asfgit closed the pull request at:
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/commit/21b37d1b8a4359de8f69786a57aa7d4283f3b779#commitcomment-11639466
Those warnings were there because without them, those inner class throw new
deprecation warnings that don't really tell us anything--
[
https://issues.apache.org/jira/browse/JENA-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-962:
---
Assignee: A. Soroka
Remove jena-core's jena.cmdline
---
[
https://issues.apache.org/jira/browse/JENA-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14582292#comment-14582292
]
Andy Seaborne commented on JENA-962:
I think I have solved the assign issue without
[
https://issues.apache.org/jira/browse/JENA-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-962.
Resolution: Fixed
Fix Version/s: Jena 3.0.0
[PR#76|https://github.com/apache/jena/pull/76]
[
https://issues.apache.org/jira/browse/JENA-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Soroka reopened JENA-962:
Remove jena-core's jena.cmdline
---
Key: JENA-962
[
https://issues.apache.org/jira/browse/JENA-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Soroka closed JENA-962.
--
Resolution: Fixed
Remove jena-core's jena.cmdline
---
Key:
[
https://issues.apache.org/jira/browse/JENA-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14582300#comment-14582300
]
A. Soroka commented on JENA-962:
Well, I just monkeyed about with it a bit to see if I could
[
https://issues.apache.org/jira/browse/JENA-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14582306#comment-14582306
]
A. Soroka commented on JENA-962:
Nope, can't self-assign. DO you think it matters? Should I
Github user afs commented on the pull request:
https://github.com/apache/jena/commit/21b37d1b8a4359de8f69786a57aa7d4283f3b779#commitcomment-11639747
I'll go look in my Eclipse settings though I thought I had the defaults in
this area. Paradoxically, I get the opposite effect - the
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/commit/21b37d1b8a4359de8f69786a57aa7d4283f3b779#commitcomment-11639777
It's so good that Java is so deterministic. I really don't know-- maybe
it's better to not have them. Maybe we should take a vote
[
https://issues.apache.org/jira/browse/JENA-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14582317#comment-14582317
]
Andy Seaborne commented on JENA-962:
If it needs a change in the JIRA project
[
https://issues.apache.org/jira/browse/JENA-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14582335#comment-14582335
]
A. Soroka commented on JENA-962:
Okay, let's play it this way for now, and if it gets to be
[
https://issues.apache.org/jira/browse/JENA-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Soroka updated JENA-960:
---
Epic Name: jena-cmd (was: jena-cli)
The construction of jena-cli
[
https://issues.apache.org/jira/browse/JENA-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Soroka updated JENA-960:
---
Description: The current machinery supporting Jena's CLI tools is too
sophisticated to be replaced entirely by
[
https://issues.apache.org/jira/browse/JENA-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14582341#comment-14582341
]
A. Soroka commented on JENA-960:
I understood your comment on the email list to be
Github user ajs6f commented on a diff in the pull request:
https://github.com/apache/jena/pull/76#discussion_r32220648
--- Diff: jena-core/src/main/java/jena/RuleMap.java ---
@@ -50,7 +53,7 @@
* /p
*/
public class RuleMap {
-static { setLog4jConfiguration()
I'll have to go back and review the dependency tree.
The contract tests should only introduce:
1) a junit runner and associated annotations.
2) a maven mojo to report on the testing structure.
I think the client requirement comes in becaue there is a command line
version of the mojo. I'll see
[
https://issues.apache.org/jira/browse/JENA-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14581935#comment-14581935
]
A. Soroka commented on JENA-962:
Good. Do you think that the warning text in this PR is too
[
https://issues.apache.org/jira/browse/JENA-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14581940#comment-14581940
]
A. Soroka commented on JENA-962:
[~andy.seaborne], I've made the requested changes in the
Github user ajs6f commented on a diff in the pull request:
https://github.com/apache/jena/pull/76#discussion_r32220860
--- Diff: jena-core/src/test/java/org/apache/jena/test/TestPackage.java ---
@@ -32,7 +33,7 @@
public class TestPackage extends TestCase {
--- End
Github user ajs6f commented on a diff in the pull request:
https://github.com/apache/jena/pull/76#discussion_r32220786
--- Diff: jena-core/pom.xml ---
@@ -56,12 +56,24 @@
groupIdxerces/groupId
artifactIdxercesImpl/artifactId
Clone URL (Committers only):
https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://jena.apache.org/tutorials%2Frdf_api.mdtext
bibithink
Index: trunk/content/tutorials/rdf_api.mdtext
===
---
I work on other projects for which we separate the lifecycles of the main
product and ancillary or supporting products (e.g. configuration for
Checkstyles) and it works well so long as:
1) The sidecar artifacts are available from Maven Central or an appropriate
more specific repository. This
Hi,
If the checksum and grammar script is OK, I'd like to continue coding.
However, the grammar script only generates ARQ and SPARQL_11, without
touching SPARQL_10. If I change the code of, e.g. Template [1], it
will affect SPARQL_10. Shall I modify the code of SPARQL_10 manually,
change the
On 11/06/15 14:35, Claude Warren wrote:
I'll have to go back and review the dependency tree.
The contract tests should only introduce:
1) a junit runner and associated annotations.
2) a maven mojo to report on the testing structure.
I think the client requirement comes in becaue there is a
36 matches
Mail list logo
