Hello snmp4j community,

I'm using Apache Maven as build tool and to obtain snmp4j binaries I'm
using https://server.oosnmp.net/dist/release as a repository. There is
a problem with server certificate, it's not signed directly by a
common Java trusted certificate authority CA, there is a additional
certificate in the chain which is not trusted. To have Maven to be
able to access snmp4j repo, this certificate needs to be added to
trusted ones, on every developers machine.

Also, having additional repository in list of repositories slows down
a build since it will be consulted if it contains build dependencies,
and it contains only one, snmp4j.

It is great that there is snmp4j Maven repository, thanks for
providing it and publishing Maven artifacts at all, but IMO it would
be much better if artifacts from snmp4j repository would be synced to
Maven central. Then snmp4j users which use Maven as build tool would
not have to configure any additional repository in their build
scripts, also no certificate issues, and it would improve build time.

AFAIK it's enough to create a ticket on either
https://issues.sonatype.org/browse/OSSRH or
https://issues.sonatype.org/browse/MVNCENTRAL JIRA, and Sonatype will
configure syncing. I read now that they prefer using (publishing
project artifacts to) approved repositories (see
http://maven.apache.org/guides/mini/guide-central-repository-upload.html#Approved_Repository_Hosting)
instead of syncing project specific repositories to Central, but I
syncing is still an option.

Have snmp4j developers thought about having snmp4j repository synced
to Maven central?

Regards,
Stevo.
_______________________________________________
SNMP4J mailing list
SNMP4J@agentpp.org
http://lists.agentpp.org/mailman/listinfo/snmp4j

Reply via email to