[
https://issues.apache.org/jira/browse/FELIX-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Mayne updated FELIX-5741:
-------------------------------
Description:
{{\[INFO\] \-
org.apache.felix:org.apache.felix.bundlerepository:jar:2.0.10:compile
\[INFO\] +- org.osgi:org.osgi.core:jar:5.0.0:compile
\[INFO\] \- org.easymock:easymock:jar:3.4:compile
\[INFO\] \- org.objenesis:objenesis:jar:2.2:compile}}
Running a mvn dependency:tree on my own bundle projects gives me the above.
This is not causing an issue yet, but it is our prerogative to keep our
deployment complexity to a minimum, and this appears to be an entirely
unnecessary dependency.
I have quickly searched the source for usages of this in runtime code and have
found nothing.
was:
bq. [INFO] \-
org.apache.felix:org.apache.felix.bundlerepository:jar:2.0.10:compile
bq. [INFO] +- org.osgi:org.osgi.core:jar:5.0.0:compile
bq. [INFO] \- org.easymock:easymock:jar:3.4:compile
bq. [INFO] \- org.objenesis:objenesis:jar:2.2:compile
Running a mvn dependency:tree on my own bundle projects gives me the above.
This is not causing an issue yet, but it is our prerogative to keep our
deployment complexity to a minimum, and this appears to be an entirely
unnecessary dependency.
I have quickly searched the source for usages of this in runtime code and have
found nothing.
> bundlerepository declares easymock as a runtime dependency
> ----------------------------------------------------------
>
> Key: FELIX-5741
> URL: https://issues.apache.org/jira/browse/FELIX-5741
> Project: Felix
> Issue Type: Bug
> Components: Bundle Repository (OBR)
> Affects Versions: bundlerepository-2.0.10
> Reporter: Chris Mayne
> Priority: Minor
>
> {{\[INFO\] \-
> org.apache.felix:org.apache.felix.bundlerepository:jar:2.0.10:compile
> \[INFO\] +- org.osgi:org.osgi.core:jar:5.0.0:compile
> \[INFO\] \- org.easymock:easymock:jar:3.4:compile
> \[INFO\] \- org.objenesis:objenesis:jar:2.2:compile}}
> Running a mvn dependency:tree on my own bundle projects gives me the above.
> This is not causing an issue yet, but it is our prerogative to keep our
> deployment complexity to a minimum, and this appears to be an entirely
> unnecessary dependency.
> I have quickly searched the source for usages of this in runtime code and
> have found nothing.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
