[
https://issues.apache.org/jira/browse/JENA-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1860.
-
Resolution: Fixed
> Move org.slf4j dependency to jena-b
028643a176675949f3a06e6745e957da0236498d in jena's branch
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=028643a ]
JENA-1860: Move org.slf4j:slf4j-api dependency into jena-base
> Move org.slf4j dependency to jena-b
is the only dependency in /pom.xml.
It would be better in jena-base.
Eventually, /pom.xml will have {{dependencyManagement}} but no dependencies.
was:
Cleaning up logging (JENA-1005) means that the org.slf4j dependency is the only
dependency in /pom.xml.
It would be better in jena-base
Andy Seaborne created JENA-1860:
---
Summary: Move org.slf4j dependency to jena-base
Key: JENA-1860
URL: https://issues.apache.org/jira/browse/JENA-1860
Project: Apache Jena
Issue Type: Task
[
https://issues.apache.org/jira/browse/JENA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1387.
-
Resolution: Fixed
> Add commons-io to jena-base as depende
bbad94844362d06126dc3f171995debb5853b0d9 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=bbad948 ]
JENA-1387: Merge commit 'refs/pull/276/head' of github.com:apache/jena
This closes #276.
> Add commons-io to jena-base as depende
[
https://issues.apache.org/jira/browse/JENA-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1387:
Description:
Apache commons-io is picked up anyway by via jsonld-java so putting into
jena-base
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/276
---
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
Andy Seaborne created JENA-1387:
---
Summary: Add commons-io to jena-base as dependency
Key: JENA-1387
URL: https://issues.apache.org/jira/browse/JENA-1387
Project: Apache Jena
Issue Type: Task
GitHub user afs opened a pull request:
https://github.com/apache/jena/pull/276
Add commons-io to jena-base as dependency.
As a follow-on to JENA-1386 (update jsonld-java), this PR puts
commons:commons-io as a dependency of jena-base. It was being picked up anyway
by via jsonld
:
https://github.com/apache/jena/pull/115#discussion_r48558378
--- Diff:
jena-base/src/main/java/org/apache/jena/atlas/lib/tuple/Tuple.java ---
@@ -0,0 +1,73 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See
://github.com/apache/jena/pull/115
> Improve jena-base lib.Tuple
> ---
>
> Key: JENA-1107
> URL: https://issues.apache.org/jira/browse/JENA-1107
> Project: Apache Jena
> Issue Type: Improvement
>
d3603482019d9bfd0295f96f5a767f4cebc3e71a in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=d360348 ]
JENA-1107: Improve Tuple. Merge commit 'refs/pull/115/head'
This closes #115.
> Improve jena-base lib.Tu
c665f63004fee2d465f2cbcb48d2defd17e12858 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=c665f63 ]
JENA-1107: Changes due to reworking Tuple.
> Improve jena-base lib.Tuple
> ---
>
> Ke
Author: Andy Seaborne <a...@seaborne.org>
Date: 2015-12-28T16:57:39Z
Tuple.asArray
commit b5d593d2d132e23533937924891a6d642afe32f2
Author: Andy Seaborne <a...@seaborne.org>
Date: 2015-12-28T17:34:56Z
Clean up whitespace inconsistencies
--
:
https://github.com/apache/jena/pull/115#discussion_r48498210
--- Diff:
jena-base/src/main/java/org/apache/jena/atlas/lib/tuple/Tuple.java ---
@@ -0,0 +1,73 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See
:
https://github.com/apache/jena/pull/115#discussion_r48498336
--- Diff:
jena-base/src/main/java/org/apache/jena/atlas/lib/tuple/Tuple.java ---
@@ -0,0 +1,73 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See
:
https://github.com/apache/jena/pull/115#discussion_r48498599
--- Diff:
jena-base/src/main/java/org/apache/jena/atlas/lib/tuple/Tuple.java ---
@@ -0,0 +1,73 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See
Andy Seaborne created JENA-1107:
---
Summary: Rework jena-base lib.Tuple
Key: JENA-1107
URL: https://issues.apache.org/jira/browse/JENA-1107
Project: Apache Jena
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/JENA-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1107:
Summary: Improve jena-base lib.Tuple (was: Rework jena-base lib.Tuple)
> Improve jena-b
Triple elements are
accessed by name ({{getSubject}} etc), not index. SPO is just one possible
order in which to think about triples but it has no special status.
> Improve jena-base lib.Tuple
> ---
>
> Key: JENA-1107
>
ements are
accessed by name (`getSubject` etc) not index. SPO is just one possible order
in which to think about triples but it has no special status.
> Improve jena-base lib.Tuple
> ---
>
> Key: JENA-1107
> URL: https://i
d95df6fcd841a713ac041dc1439aff51d99095ca in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=d95df6f ]
JENA-1107: Move ColumnMap into TDB.
> Improve jena-base lib.Tuple
> ---
>
> Key: JENA-1107
>
[
https://issues.apache.org/jira/browse/JENA-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-923.
Resolution: Done
Fix Version/s: Jena 3.0.0
Populate jena-base
I was looking at a couple of modules in Jena and using Eclipse to work
with them.
I could build the projects in maven. Created all the jars using -U to
force rebuilding of snapshot jars.
However, the jena-permissions package would not build without adding
jena-base. That package uses apache
rebuilding of snapshot jars.
However, the jena-permissions package would not build without adding
jena-base. That package uses apache-jena-libs. I think the jena-base is
somehow missing from apache-jena-libs but I am not certain how to add it.
Any ideas?
Claude
--
I like: Like Like
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/56#issuecomment-99403016
I'll look again but the NodeTransform and the Closeable issues seem to be
the main things and after that the size is due to the number of places that
Java8 improves things.
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/56#issuecomment-99466597
Sounds good. After this, wherever goes the conversation about Java 8, the
Streams API, Commons RDF, etc., I will keep PRs much smaller. I felt
comfortable trying to get away
org.apache.jena.atlas in jena-base onto Java 8 types
--
Key: JENA-931
URL: https://issues.apache.org/jira/browse/JENA-931
Project: Apache Jena
Issue Type: Improvement
Components: Jena
at:
https://github.com/apache/jena/pull/56
Shift org.apache.jena.atlas in jena-base onto Java 8 types
--
Key: JENA-931
URL: https://issues.apache.org/jira/browse/JENA-931
Project: Apache Jena
fa3bae848ab63855900627d8745246a1170eff7d in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=fa3bae8 ]
Fix warnings after JENA-931
Shift org.apache.jena.atlas in jena-base onto Java 8 types
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/56#issuecomment-99121831
Okay, I'll plug `NodeTransform` back in at oaj.sparql.graph, since that is
where it was: minimal disruption. I've got the JavaDocs square and re-separated
the two
Github user afs commented on the pull request:
https://github.com/apache/jena/pull/56#issuecomment-99120861
The vast majority of the PR looks good including converting code in
passing. MultiMap?mulitSet are unlikely to have leaked (and can be restored if
need be); I've already
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/56#issuecomment-99085428
I'm definitely up for breaking this down. :)
The major moves here are:
- I replaced any interface inside oaj.atlas for which I could find a
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/56#issuecomment-99100248
Actually, for `NodeTransform`, perhaps it could be even more tightly scoped
to just `org.apache.jena.sparql.algebra.optimize`?
---
If your project is set up for it, you can
these changes, and then we can figure out how to parcel this
stuff out into reasonable commits?
JENA-931
Shift org.apache.jena.atlas in jena-base onto Java 8 types
--
Key: JENA-931
URL: https
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/56#issuecomment-99141455
`NodeTransform` is back-- I think that's all the emendation we wanted, yes?
Did you have thoughts about dividing out this large PR?
---
If your project is set up
GitHub user ajs6f opened a pull request:
https://github.com/apache/jena/pull/56
Jena base to java8
Work for https://issues.apache.org/jira/browse/JENA-931
Using Java 8 types and removing code that duplicates functionality found
inside the current footprint.
You can merge
:
https://github.com/apache/jena/pull/56
Jena base to java8
Work for https://issues.apache.org/jira/browse/JENA-931
Using Java 8 types and removing code that duplicates functionality found
inside the current footprint.
You can merge this pull request into a Git repository by running
org.apache.jena.atlas in jena-base onto Java 8 types
--
Key: JENA-931
URL: https://issues.apache.org/jira/browse/JENA-931
Project: Apache Jena
Issue Type: Improvement
Components: Jena
A. Soroka created JENA-931:
--
Summary: Shift org.apache.jena.atlas in jena-base onto Java 8 types
Key: JENA-931
URL: https://issues.apache.org/jira/browse/JENA-931
Project: Apache Jena
Issue Type
b06ed195677975477d778791d69f041504e2479d in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=b06ed19 ]
JENA-923: jena-base now used in testing
Populate jena-base
--
Key: JENA-923
URL: https
9eedadcd040e036eb58f4191b03b7dacb38060de in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=9eedadc ]
JENA-923: Remove jena-arq files now in jena-base
Populate jena-base
--
Key: JENA-923
URL
57aa6abca72c259c664a30665d5c0c7136d24335 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=57aa6ab ]
JENA-923: Move IRILib to future jena-base code tree.
This is the first step - moving within ARQ, for later migration to
jena-base.
Populate
890c070a4b710b57feb49898f63fab0882441870 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=890c070 ]
JENA-923: (Preparation) Put all string escape processing in one place.
Populate jena-base
--
Key: JENA-923
6790a64f2127eb4f115bf7f7e1ad938468dc2294 in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=6790a64 ]
JENA-923: Move Timer class to oaj.atlas.lib
Populate jena-base
--
Key: JENA-923
URL
d93f238301cec9be8cd07669f8825f1cb1dca1ab in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=d93f238 ]
JENA-923: Move className operations to oaj.atlas.lib.Lib
Populate jena-base
--
Key: JENA-923
So what is then the difference from jena-base and jena-core? The base
is utillity non-RDF stuff, and jena-core basic RDF? Would not
jena-iri fit in jena-base?
I am not too sure about creating a new module which everyone will
ultimately depend on through jena-core anyway.. what benefit
at 3:51 PM, Stian Soiland-Reyes st...@apache.org
wrote:
So what is then the difference from jena-base and jena-core? The base
is utillity non-RDF stuff, and jena-core basic RDF? Would not
jena-iri fit in jena-base?
I am not too sure about creating a new module which everyone will
ultimately
cdb2c9c631b9d54dc7585e42a3d75cd6e14d87be in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=cdb2c9c ]
JENA-923: Import of lib, io, logging and iterator packages
Populate jena-base
--
Key: JENA-923
bac746dfbdde01f80bb12f48b0f681e7471d9d8c in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=bac746d ]
JENA-923: Refactoring in preparation for jena-base
Separate out DateTimeUtils
Remove duplicate OutputUtils
EscapeStr functions into atlas
Andy Seaborne created JENA-923:
--
Summary: Populate jena-base
Key: JENA-923
URL: https://issues.apache.org/jira/browse/JENA-923
Project: Apache Jena
Issue Type: Improvement
Affects Versions
(!) in the path name to use a zipInput stream.
Where would we put code like that?
I think that the ability to read data files from a zip/jar would be a GIBNI
(Gee, i'd be need it).
Claude
On Sun, Apr 26, 2015 at 2:07 PM, Andy Seaborne a...@apache.org wrote:
Makes sense.
jena-base comes before any
So the base test helper code I was talking about yesterday -- do you see
this going into jena-base test branch? If I understand what you are
suggesting, I think I do.
Claude
On Sat, Apr 25, 2015 at 10:32 PM, Andy Seaborne a...@apache.org wrote:
As part of rearranging the code, I'd like
Makes sense.
jena-base comes before any RDF code.
One hazy area I found is some IRI handling for filenames to make
file:/// work. At current approximation, the part of IRILib for file
IRIs should go in jena-base for seemless filename handling. But that's
web not RDF. jena-base shouldn't
07:49, Claude Warren wrote:
So the base test helper code I was talking about yesterday -- do you see
this going into jena-base test branch? If I understand what you are
suggesting, I think I do.
Claude
On Sat, Apr 25, 2015 at 10:32 PM, Andy Seaborne a...@apache.org wrote:
As part
as being?
Andy
On 26/04/15 07:49, Claude Warren wrote:
So the base test helper code I was talking about yesterday -- do you see
this going into jena-base test branch? If I understand what you are
suggesting, I think I do.
Claude
On Sat, Apr 25, 2015 at 10:32 PM, Andy Seaborne
+1 Claude
I liked the idea of having some common testing code in one place, and I'm also
leaning toward having it in base later.
Bruno
From: Claude Warren cla...@xenei.com
To: dev@jena.apache.org
Sent: Monday, April 27, 2015 12:44 AM
Subject: Re: New module : jena-base
I see
As part of rearranging the code, I'd like to propose we have module
jena-base
It would be non-RDF related code, seeded with what is currently
org.apache.jena.atlas which is in jena-arq and is then used by TDB and
SDB and others. RIOT uses it so it is a prequiste for moving RIOT.
Depends
59 matches
Mail list logo
