OpenNMS

tracking sf ticket: dns4java as osgi-bundle depends on junit

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Trivial Trivial
  • Resolution: Unresolved
  • Affects Version/s: 1.11.2
  • Fix Version/s: 1.11.91
  • Component/s: Build/Packaging
  • Security Level: Default (Default Security Scheme)
  • Labels:
    None

Description

to use opennms-util inside an osgi-container you have to bundle org.junit because dns4java bundle information defines org.junit as dependency

opennms-util->dns4java->org.junit

for karaf the workaround command is:
# bundle:install wrap:mvn:junit/junit

i have opened a ticket for dns4java:
https://sourceforge.net/tracker/?func=detail&aid=3556130&group_id=18000&atid=118000

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Simon Walter added a comment -

The issues is explained in depth in the sf ticket.
The upstream maintainer is not interested in resolving the issue himself, because a restructure of the project would be nessecary.
Also he even wasn't the guy who build/uploaded the package to the mvnrepo.

So there are many ways to go:
1. Do a fork just for the maven+osgi packeting and upload this to mvnrepo org opennmsrepo as 2.1.1-1
a. fix the project structure (hard to maintain if upstream doesn't follow)
b. drop the felix plugin and hardcode bundle-infos
This way it would be usable for others.

2. Just rebundle the package by rebundling it with an dependency module? Is this possible?

There is also a new version 2.1.3 with DNSSEC support. It introduces some more dependencies (encryption stuff) and I' not sure if this feature is even relevant for opennms.

Show
Simon Walter added a comment - The issues is explained in depth in the sf ticket. The upstream maintainer is not interested in resolving the issue himself, because a restructure of the project would be nessecary. Also he even wasn't the guy who build/uploaded the package to the mvnrepo. So there are many ways to go: 1. Do a fork just for the maven+osgi packeting and upload this to mvnrepo org opennmsrepo as 2.1.1-1 a. fix the project structure (hard to maintain if upstream doesn't follow) b. drop the felix plugin and hardcode bundle-infos This way it would be usable for others. 2. Just rebundle the package by rebundling it with an dependency module? Is this possible? There is also a new version 2.1.3 with DNSSEC support. It introduces some more dependencies (encryption stuff) and I' not sure if this feature is even relevant for opennms.
Hide
Permalink
Seth Leger added a comment -

I think that installing junit as a wrapped bundle to satisfy this dependency is probably not that big of a problem. We will eventually create a Karaf feature for things like opennms-util and we can just put the dependency in there with a comment noting that junit is only in there to satisfy dns4java.

Show
Seth Leger added a comment - I think that installing junit as a wrapped bundle to satisfy this dependency is probably not that big of a problem. We will eventually create a Karaf feature for things like opennms-util and we can just put the dependency in there with a comment noting that junit is only in there to satisfy dns4java.

People

  • Assignee:
    Benjamin Reed
    Reporter:
    Simon Walter
Vote (0)
Watch (2)

Dates

  • Created:
    Updated: