entire package structure of the
> codebase and recomposing it in a branch? On what basis would packages be
> grouped?
>
> ajs6f
>
> > On Apr 26, 2018, at 2:58 PM, Christopher Johnson <
> chjohnso...@gmail.com> wrote:
> >
> > In ref
r existing
consumers
What I would like to propose is a new branch that just contains modules
compliant with the JPMS and that is tested for JDK9+. Artifacts produced
from this branch could be distinguished from master artifacts with an
appropriate appendix.
Thank you for your consideration,
Github user christopher-johnson commented on the issue:
https://github.com/apache/jena/pull/411
BND reads the import packages from the jar manifest, which would include
the bundle requirements when deployed. The question is whether a resolver
(like Aether[1] ) can locate
Hi Andy and list,
Thank you for the feedback. I have been working on the Jena JPMS
experiment and a rough concept be reviewed here:
https://github.com/christopher-johnson/jena-redux/tree/jpms
These selected modules can be built now and here is a dependency graph of
jena.arq:
https
Github user christopher-johnson commented on the issue:
https://github.com/apache/jena/pull/411
TDB2 depends on dboe-trans-data and transitively on dboe-transaction and
dboe-base. Should these be added to the bundle definition as well? It hinges
on whether the resolver will pull
Github user christopher-johnson commented on the issue:
https://github.com/apache/jena/pull/401
In working with the automatic modules, I have also found a split
with`org.apache.jena.atlas`. This is between `org.apache.jena.arq` and
`org.apache.jena.base`.
Would it make
Github user christopher-johnson commented on a diff in the pull request:
https://github.com/apache/jena/pull/400#discussion_r181829734
--- Diff: jena-db/pom.xml ---
@@ -75,6 +79,13 @@
org.apache.maven.plugins
maven-jar-plugin
Github user christopher-johnson commented on the issue:
https://github.com/apache/jena/pull/399
See https://github.com/apache/jena/pull/401.
If I understood you correctly, the adapter
`jena-arq:org.apache.jena.system.JenaInit` just provides a short cut for using
the renamed
GitHub user christopher-johnson opened a pull request:
https://github.com/apache/jena/pull/399
[JENA-1524] renames jena-arq org.apache.jena.system to org.apache.jena.sys
The changes are superficial, but will break existing implementations. The
thinking pattern here is shallow
GitHub user christopher-johnson opened a pull request:
https://github.com/apache/jena/pull/400
[JENA-1524] Add to for each jar
module
See comments here:
https://github.com/apache/jena/pull/399
It is possible that there are more artifacts that might want
GitHub user christopher-johnson opened a pull request:
https://github.com/apache/jena/pull/401
[JENA-1524] org.apache.jena.system is split by org.apache.jena.arq and
org.apache.jena.core
per @afs
> this renames of "jena-core:org.apache.jena.system&qu
Github user christopher-johnson closed the pull request at:
https://github.com/apache/jena/pull/399
---
Github user christopher-johnson commented on the issue:
https://github.com/apache/jena/pull/401
the module system does not allow two distinct modules (e.g.
`org.apache.jena.arq` and `org.apache.jena.base`) to export the same package
(e.g. `org.apache.jena.atlas
Github user christopher-johnson commented on the issue:
https://github.com/apache/jena/pull/401
re: `org.apache.jena.atlas` dependents in `org.apache.jena.arq` (namely
`org.apache.jena.riot`)
I attach an excerpt from a `jdep`s output looking at `jena-arq-3.7.0.jar`,
sorted
Github user christopher-johnson commented on the issue:
https://github.com/apache/jena/pull/401
Compilation in JPMS requires a `module-info.java` and is distinct from
compiling in JDK 9+.
> What is the issue here? Does anything break?
A quick background of the
Github user christopher-johnson commented on the issue:
https://github.com/apache/jena/pull/401
Indeed, these dependency questions are issues that I need to solve... I
would prefer to simplify the über-jar `jena-osgi` dependency of
`commons.rdf.jena` by creating lean modular jena
Github user christopher-johnson commented on the issue:
https://github.com/apache/jena/pull/401
a quick note here about the prospect of further restructuring to support
jpms. I have learned today that if a module (e.g. `org.apache.jena.arq`) does
not contain a single top level
[
https://issues.apache.org/jira/browse/JENA-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Johnson updated JENA-1536:
--
Attachment: (was: AtlasSinkNonSynchronizedCollectionException.txt)
> unsynchroni
Christopher Johnson created JENA-1536:
-
Summary: unsynchronized collection in
jena.atlas.lib.SinkToCollection causes ArrayIndexOutOfBoundsException
Key: JENA-1536
URL: https://issues.apache.org/jira/browse
Christopher Johnson created JENA-1524:
-
Summary: org.apache.jena.system is split by org.apache.jena.arq
and org.apache.jena.core
Key: JENA-1524
URL: https://issues.apache.org/jira/browse/JENA-1524
[
https://issues.apache.org/jira/browse/JENA-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16438865#comment-16438865
]
Christopher Johnson commented on JENA-1525:
---
PR: [https://github.com/apache/jena/pull/400]
https
21 matches
Mail list logo
