[
https://issues.apache.org/jira/browse/JCR-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783072#action_12783072
]
Felix Meschberger commented on JCR-2412:
----------------------------------------
When defining the bundle, I get an Import-Package statement for this package -
as I said, I can work around this.
The problem is, that the JackrabbitRepositoryStub class uses three classes form
the test package and from the POV of OSGi, this constitutes an required
dependency to said package. Of course I can exclude the import of that package
assuming this class will never be used in a production system.
But then: why including it in a production library in the first place ?
> JackrabbitRepositoryStub in jackrabbit-core library class contains o.a.j.test
> reference
> ---------------------------------------------------------------------------------------
>
> Key: JCR-2412
> URL: https://issues.apache.org/jira/browse/JCR-2412
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.0-beta3
> Reporter: Felix Meschberger
>
> The JackrabbitRepositoryStub added as part of JCR-2055 contains a reference
> to the org.apache.jackrabbit.test package.
> This is IMHO a very bad dependency for a production library and should be
> removed.
> (I stumbled upon it while trying to create an OSGi bundle for an embedded
> Jackrabbit Repository based on 2.0-beta3, so I can work around this.
> Nevertheless, it is IMHO bad practice and not a very good idea)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
