[
https://issues.apache.org/jira/browse/SSHD-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17303221#comment-17303221
]
Grzegorz Grzybek commented on SSHD-1146:
----------------------------------------
With {{osgi-report-maven-plugin}} you'll notice this:
{noformat}
uses :=
org.apache.sshd.client.channel
org.apache.sshd.client.future
@@ -941,35 +941,4 @@
org.apache.sshd.common.util
org.apache.sshd.common.util.closeable
-Import-Package:
- javax.crypto
- javax.crypto.interfaces
- javax.crypto.spec
- javax.management
- javax.security.auth
- javax.security.auth.callback
- javax.security.auth.login
- net.i2p.crypto.eddsa
- version = [0.3,1)
- resolution := optional
- net.i2p.crypto.eddsa.math
- resolution := optional
- net.i2p.crypto.eddsa.spec
- version = [0.3,1)
- resolution := optional
- org.apache.tomcat.jni
- resolution := optional
- org.bouncycastle.crypto.prng
- version = [1.64,2)
- resolution := optional
- org.bouncycastle.openssl
- version = [1.64,2)
- resolution := optional
- org.bouncycastle.openssl.jcajce
- version = [1.64,2)
- resolution := optional
- org.ietf.jgss
- org.slf4j
- version = [1.7,2)
-
{noformat}
But also this:
{noformat}
org.apache.sshd.common.util.security.eddsa
- version = 2.5.1
+ version = 2.6.1
uses :=
- net.i2p.crypto.eddsa
- net.i2p.crypto.eddsa.spec
org.apache.sshd.common
org.apache.sshd.common.config.keys
org.apache.sshd.common.config.keys.impl
{noformat}
where export {{org.apache.sshd.common.util.security.eddsa}} lost their
{{net.i2p.crypto.eddsa.*}} from {{uses}} clause.
> Missing Import-Package header in sshd-osgi-2.6.0
> ------------------------------------------------
>
> Key: SSHD-1146
> URL: https://issues.apache.org/jira/browse/SSHD-1146
> Project: MINA SSHD
> Issue Type: Bug
> Reporter: Grzegorz Grzybek
> Priority: Major
> Attachments: manifest-summary-2.5.1.txt, manifest-summary.txt
>
>
> After SSHD-1092, where sshd-core and sshd-common (and other modules) lost
> their OSGi manifests, sshd-core which repackages them, no longer provides any
> {{Import-Package}} headers. Effectively this makes sshd-osgi-2.6.0 unusable
> in OSGi env.
> Remember that e.g., Karaf's {{ssh}} features contains not only sshd-osgi
> bundles (now at version 2.5.1):
> {code:xml}
> <bundle
> start-level="30">mvn:org.apache.sshd/sshd-osgi/${sshd.version}</bundle>
> <bundle start-level="30">mvn:org.apache.sshd/sshd-scp/${sshd.version}</bundle>
> <bundle
> start-level="30">mvn:org.apache.sshd/sshd-sftp/${sshd.version}</bundle>
> {code}
> To better look and compare OSGi headers, please have a look at
> https://ops4j1.jira.com/wiki/spaces/TOOLS/pages/412549134/OSGi+Report+Maven+Plugin
> - you don't have to create special maven module (as we do with Pax
> projects), you can simply invoke:
> {noformat}
> mvn install
> org.ops4j.tools.maven:osgi-report-maven-plugin:0.1.1:manifest-summary
> {noformat}
> inside {{sshd-osgi}} module and you'll get something like
> [^manifest-summary.txt] - it is easy to compare it with similar summary
> created for different version, like [^manifest-summary-2.5.1.txt].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]