Back to Apache License about tnm4j HOT 6 CLOSED

I don't have an objection to dual licensing. However, the Mibble MIB parser on which this library depends uses the GPL license.

If Mibble's author is willing to dual license or change to the more liberal ASL, I'll be happy to follow suit.

from tnm4j.

I see - Mibble is commercially oriented so I doubt the change will happen. Can we replace Mibble with something else?
Do we need direct MIB reading or would converting to JSON in advance e.g. with https://github.com/etingof/pysmi help?
I 'd love to support OID to cleartext handling in http://www.bitplan.com/index.php/SimpleGraph-SNMP

from tnm4j.

MIB support is loaded using the ServiceLoader mechanism that was introduced in JDK 6. The MibFactory singleton is used to find a MibProvider instance. A MibProvider has a method that is used to get a Mib instance. The Mib interface and the interfaces referenced by it constitute the MIB API used by tnm4j.

So using another MIB implementation is essentially a matter of implementing MibProvider, implementing Mib and the various interfaces referenced by it, and then packaging it up as a JAR module with a service metadata file named META-INF/services/org.soulwing.snmp.provider.MibProvider that contains the fully qualified class name of the provider implementation class. At runtime the alternate provider can be specified by name using one of the methods of MibFactory.

from tnm4j.

So yeah, if someone wanted to make an alternative MIB provider, I'll be happy to dual license.

from tnm4j.

FWIW, I've found Per Cederberg of Mibble to be a pretty reasonable guy. I haven't inquired about the terms of his commercial license, because I haven't had need. But if the reason you want ASL for tnm4j is to make a commercial product, you might at least consider inquiring.

from tnm4j.

For inquiry about re-licensing Mibble, perhaps LGPL would be a good request. Currently, it's under GPL 2.0 so he may really want the source code of any distributed code that uses his project. He may go for LGPL which would explicitly allow for dynamic linking in distribution without requiring linked code to be open sourced at all but he'd still have the requirement to have changes (when being distributed) in the mibble project contributed back.
Eg: if mibble used lgpl; maven project lists mibble as a dep, under lgpl you'd have explicit permission to use mibble and not open source your maven project and you could distribute your maven project under your own license. At least that's how I understand it.

from tnm4j.