Would anyone who is using OSGi and Jena be able to test the experimental
jena-osgi bundle? I might have asked about this earlier, but have since
updated the patch.
The ZIP at
https://people.apache.org/~stain/jena-osgi-test-20150112/
includes both
jena-osgi-2.12.2-SNAPSHOT.jar
and the other required bundles (e.g. httpclient-osgi, jackson-core, ++)
Note that this email does not in any way form a release - the above is
based on the unreleased 'master' branch at Jena.
You can build it yourself by checking out my "jena-osgi-bundle" branch:
https://github.com/stain/jena/tree/jena-osgi-bundle
and build the jena-osgi/ module with "mvn clean install". The bundle JAR
would then be in the target/ folder.
See details about the Jena pull request below:
---------- Forwarded message ----------
From: asfbot notifications [ at ] github.com
Date: 12 January 2015 at 00:05
Subject: Re: [jena] Jena OSGi bundle (#10)
To: apache/jena jena [ at ] noreply.github.com
Cc: Stian Soiland-Reyes stian [ at ] mygrid.org.uk
Stian Soiland-Reyes on dev [ at ] jena.apache.org replies:
So I have updated the jena-osgi pull request in
#10 <https://github.com/apache/jena/pull/10>
As commented there - it now includes a new module jena-osgi-test to
test it within Equinox and Apache Felix (two of the leading OSGi
frameworks).
The tests are run as part of the maven build - any failure would be
propagated out. It has to be in a separate module in order to test
calling from 'another' OSGi module.
Note that the test depends on the maven plugin
https://github.com/everit-org/eosgi-maven-plugin
This is licensed under LGPL. This is only used during the test/build
(of jena-osgi-test) - which I believe should be acceptable according
to:
https://www.apache.org/legal/resolved.html#prohibited
Given these brief tests working (which cover jena-core, jena-arq and
jena-tdb), I would be comfortable to put it in, then wait for
feedback. Perhaps wait with promoting it on the website before we know
it works generally?
I tried putting it into Clerezza instead of their
org.apache.clerezza.ext.jena.* modules, but I am not knowledgeable
enough about how to get Clerezza started as an OSGi application..
If you want to copy-paste it into a running OSGi setup, then have a look in
jena/jena-osgi-test/target/eosgi-dist/felix/lib
as it would contain the bundles you need. Namely:
commons-csv-1.0.jar
commons-lang3-3.3.2.jar
httpclient-osgi-4.2.6.jar
httpcore-osgi-4.2.5.jar
jackson-annotations-2.3.0.jar
jackson-core-2.3.3.jar
jackson-databind-2.3.3.jar
jcl-over-slf4j-1.7.6.jar
jena-osgi-2.12.2-SNAPSHOT.jar
jsonld-java-0.5.1.jar
libthrift-0.9.2.jar
log4j-1.2.17.jar
slf4j-api-1.7.6.jar
You might not want this if you do slf4j in another way:
slf4j-log4j12-1.7.6.jar
You should not need these as they are only used for the testing:
org.ops4j.pax.tipi.junit-4.11.0.1.jar
jena-osgi-test-2.12.2-SNAPSHOT.jar
org.everit.osgi.dev.testrunner-4.0.3.jar
org.everit.osgi.dev.testrunner.junit4-3.0.4.jar
org.ops4j.pax.tipi.hamcrest.core-1.3.0.1.jar
—
Reply to this email directly or view it on GitHub
<https://github.com/apache/jena/pull/10#issuecomment-69518840>.
jena-osgi bundle? I might have asked about this earlier, but have since
updated the patch.
The ZIP at
https://people.apache.org/~stain/jena-osgi-test-20150112/
includes both
jena-osgi-2.12.2-SNAPSHOT.jar
and the other required bundles (e.g. httpclient-osgi, jackson-core, ++)
Note that this email does not in any way form a release - the above is
based on the unreleased 'master' branch at Jena.
You can build it yourself by checking out my "jena-osgi-bundle" branch:
https://github.com/stain/jena/tree/jena-osgi-bundle
and build the jena-osgi/ module with "mvn clean install". The bundle JAR
would then be in the target/ folder.
See details about the Jena pull request below:
---------- Forwarded message ----------
From: asfbot notifications [ at ] github.com
Date: 12 January 2015 at 00:05
Subject: Re: [jena] Jena OSGi bundle (#10)
To: apache/jena jena [ at ] noreply.github.com
Cc: Stian Soiland-Reyes stian [ at ] mygrid.org.uk
Stian Soiland-Reyes on dev [ at ] jena.apache.org replies:
So I have updated the jena-osgi pull request in
#10 <https://github.com/apache/jena/pull/10>
As commented there - it now includes a new module jena-osgi-test to
test it within Equinox and Apache Felix (two of the leading OSGi
frameworks).
The tests are run as part of the maven build - any failure would be
propagated out. It has to be in a separate module in order to test
calling from 'another' OSGi module.
Note that the test depends on the maven plugin
https://github.com/everit-org/eosgi-maven-plugin
This is licensed under LGPL. This is only used during the test/build
(of jena-osgi-test) - which I believe should be acceptable according
to:
https://www.apache.org/legal/resolved.html#prohibited
Given these brief tests working (which cover jena-core, jena-arq and
jena-tdb), I would be comfortable to put it in, then wait for
feedback. Perhaps wait with promoting it on the website before we know
it works generally?
I tried putting it into Clerezza instead of their
org.apache.clerezza.ext.jena.* modules, but I am not knowledgeable
enough about how to get Clerezza started as an OSGi application..
If you want to copy-paste it into a running OSGi setup, then have a look in
jena/jena-osgi-test/target/eosgi-dist/felix/lib
as it would contain the bundles you need. Namely:
commons-csv-1.0.jar
commons-lang3-3.3.2.jar
httpclient-osgi-4.2.6.jar
httpcore-osgi-4.2.5.jar
jackson-annotations-2.3.0.jar
jackson-core-2.3.3.jar
jackson-databind-2.3.3.jar
jcl-over-slf4j-1.7.6.jar
jena-osgi-2.12.2-SNAPSHOT.jar
jsonld-java-0.5.1.jar
libthrift-0.9.2.jar
log4j-1.2.17.jar
slf4j-api-1.7.6.jar
You might not want this if you do slf4j in another way:
slf4j-log4j12-1.7.6.jar
You should not need these as they are only used for the testing:
org.ops4j.pax.tipi.junit-4.11.0.1.jar
jena-osgi-test-2.12.2-SNAPSHOT.jar
org.everit.osgi.dev.testrunner-4.0.3.jar
org.everit.osgi.dev.testrunner.junit4-3.0.4.jar
org.ops4j.pax.tipi.hamcrest.core-1.3.0.1.jar
—
Reply to this email directly or view it on GitHub
<https://github.com/apache/jena/pull/10#issuecomment-69518840>.