Return-Path: 
 <dev-return-28618-apmail-mina-dev-archive=mina.apache.org@mina.apache.org>
X-Original-To: apmail-mina-dev-archive@www.apache.org
Delivered-To: apmail-mina-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id C50EE18364
	for <apmail-mina-dev-archive@www.apache.org>;
 Wed,  5 Aug 2015 17:11:06 +0000 (UTC)
Received: (qmail 36019 invoked by uid 500); 5 Aug 2015 17:11:04 -0000
Delivered-To: apmail-mina-dev-archive@mina.apache.org
Received: (qmail 35917 invoked by uid 500); 5 Aug 2015 17:11:04 -0000
Mailing-List: contact dev-help@mina.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@mina.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@mina.apache.org>
List-Post: <mailto:dev@mina.apache.org>
List-Id: <dev.mina.apache.org>
Reply-To: dev@mina.apache.org
Delivered-To: mailing list dev@mina.apache.org
Received: (qmail 35628 invoked by uid 99); 5 Aug 2015 17:11:04 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Aug 2015 17:11:04 +0000
Date: Wed, 5 Aug 2015 17:11:04 +0000 (UTC)
From: "Ed Schaller (JIRA)" <jira@apache.org>
To: dev@mina.apache.org
Message-ID: <JIRA.12665894.1377685282000.379568.1438794664732@Atlassian.JIRA>
In-Reply-To: <JIRA.12665894.1377685282000@Atlassian.JIRA>
References: <JIRA.12665894.1377685282000@Atlassian.JIRA>
 <JIRA.12665894.1377685282101@arcas>
Subject: [jira] [Commented] (FTPSERVER-447) Bad OSGi exports for FTPServer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/FTPSERVER-447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658529#comment-14658529 ] 

Ed Schaller commented on FTPSERVER-447:
---------------------------------------

So the fix for this was committed a couple of years ago now. Are there plans for a release with this fix? 

> Bad OSGi exports for FTPServer 
> -------------------------------
>
>                 Key: FTPSERVER-447
>                 URL: https://issues.apache.org/jira/browse/FTPSERVER-447
>             Project: FtpServer
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 1.0.6
>            Reporter: Ioan Eugen Stan
>
> Pull request and patch available: https://github.com/apache/ftpserver/pull/1
> I noticed that version 1.0.6 does not work well with OSGi because 
> 1. it includes all the classes from ftplet-api 
> 2. it does not export them in the manifests headers. 
> Detailed problem:
> If you wish to implement your own versions of UserManager or other interfaces and use them in OSGi, this requires adding the ftplet-api bundle. This results in two versions of the same classes on the classpath. This makes custom implementation of Ftpserver interfaces impossible.
> I tried to build my own UserManger and User implementation to authenticate against a DB via JPA. I could not do it because I got linkage errors since my implementation depended on the ftplet-api interfaces which are loaded in OSGi via two separate classloaders: one version from the ftpserver-core bundle (but these are private and not exported) and one from ftplet-api.
>         <dependency>
>             <groupId>org.apache.ftpserver</groupId>
>             <artifactId>ftpserver-core</artifactId>
>             <version>1.0.6</version>
>         </dependency>
> The solution: 
> * remove all the custom manifest headers from maven-bundle-plugin - works very well on it's own
> * build jar that does not include the ftplet-api classes
> This requires another release to fix in OSGi.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)