Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Follow-on to https://jira.duraspace.org/browse/FCREPO-1667 #890
@awoods it's not that jena.atlas is not OSGi friendly, but rather that there is a transitive dependency clash:
fcrepo-camel depends on clerezza to do some rdf (de-)serialization, and that in turn depends on a wrapped version of jena (version 2.11), which does not contain that particular o.a.jena.atlas class. So, when fcrepo4 is launched for the integration tests, the class loader can't find the jena.atlas class in question, since it doesn't exist in the wrapped clerezza bundles.
That is to say, this proposed change is fine, but perhaps we should address it with a change in the camel component -- though doing so is a bit more complex.