You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2005/05/21 22:14:51 UTC

[jira] Created: (DIRKERBEROS-24) compilation pb with MINA 0.7.1

compilation pb with MINA 0.7.1
------------------------------

         Key: DIRKERBEROS-24
         URL: http://issues.apache.org/jira/browse/DIRKERBEROS-24
     Project: Directory Kerberos
        Type: Bug
    Reporter: Emmanuel Lecharny


As many improvement and changes has been done in MINA, many pieces of cade are now not compiling anymore. For instance, 
Kerberos protocol provider is still depending on org.apache.mina.protocol.ProtocolProvider, which does not exist anymore.

May I suggest that if a class is renamed, then at least the old one still remain, deprecated? If not, don't we have to change user code in  the project to be sure that it compiles? The pb with Maven, her, is that Kerberos protocol provider depends on an older version of MINA. I'm not sure that it's a good thing to have two pieces of code dependng on two different versions of the same code (MINA) in the same project...

wdyt?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Re: [jira] Created: (DIRKERBEROS-24) compilation pb with MINA 0.7.1

Posted by Alex Karasulu <ao...@bellsouth.net>.
Yeah +1 over and over.  This happens a lot not just with MINA but other 
things.  Let's try to at least keep the trunk compiling.

Alex


Emmanuel Lecharny (JIRA) wrote:

>compilation pb with MINA 0.7.1
>------------------------------
>
>         Key: DIRKERBEROS-24
>         URL: http://issues.apache.org/jira/browse/DIRKERBEROS-24
>     Project: Directory Kerberos
>        Type: Bug
>    Reporter: Emmanuel Lecharny
>
>
>As many improvement and changes has been done in MINA, many pieces of cade are now not compiling anymore. For instance, 
>Kerberos protocol provider is still depending on org.apache.mina.protocol.ProtocolProvider, which does not exist anymore.
>
>May I suggest that if a class is renamed, then at least the old one still remain, deprecated? If not, don't we have to change user code in  the project to be sure that it compiles? The pb with Maven, her, is that Kerberos protocol provider depends on an older version of MINA. I'm not sure that it's a good thing to have two pieces of code dependng on two different versions of the same code (MINA) in the same project...
>  
>


[jira] Closed: (DIRKERBEROS-24) compilation pb with MINA 0.7.1

Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/DIRKERBEROS-24?page=all ]
     
Emmanuel Lecharny closed DIRKERBEROS-24:
----------------------------------------


Trustin is right, I'm wrong...

This issue occurs only with the 0.9-SNAPSHOT version of MINA

> compilation pb with MINA 0.7.1
> ------------------------------
>
>          Key: DIRKERBEROS-24
>          URL: http://issues.apache.org/jira/browse/DIRKERBEROS-24
>      Project: Directory Kerberos
>         Type: Bug
>     Reporter: Emmanuel Lecharny
>     Assignee: Trustin Lee

>
> As many improvement and changes has been done in MINA, many pieces of cade are now not compiling anymore. For instance, 
> Kerberos protocol provider is still depending on org.apache.mina.protocol.ProtocolProvider, which does not exist anymore.
> May I suggest that if a class is renamed, then at least the old one still remain, deprecated? If not, don't we have to change user code in  the project to be sure that it compiles? The pb with Maven, her, is that Kerberos protocol provider depends on an older version of MINA. I'm not sure that it's a good thing to have two pieces of code dependng on two different versions of the same code (MINA) in the same project...
> wdyt?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Resolved: (DIRKERBEROS-24) compilation pb with MINA 0.7.1

Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/DIRKERBEROS-24?page=all ]
     
Trustin Lee resolved DIRKERBEROS-24:
------------------------------------

     Assign To: Trustin Lee
    Resolution: Invalid

mina-0.7.1.jar does contain ProtocolProvider.class.  I downloaded it just now and confirmed it is there.  You seemed to have used mina-0.9-SNAPSHOT.jar.

Thanks,
Trustin

> compilation pb with MINA 0.7.1
> ------------------------------
>
>          Key: DIRKERBEROS-24
>          URL: http://issues.apache.org/jira/browse/DIRKERBEROS-24
>      Project: Directory Kerberos
>         Type: Bug
>     Reporter: Emmanuel Lecharny
>     Assignee: Trustin Lee

>
> As many improvement and changes has been done in MINA, many pieces of cade are now not compiling anymore. For instance, 
> Kerberos protocol provider is still depending on org.apache.mina.protocol.ProtocolProvider, which does not exist anymore.
> May I suggest that if a class is renamed, then at least the old one still remain, deprecated? If not, don't we have to change user code in  the project to be sure that it compiles? The pb with Maven, her, is that Kerberos protocol provider depends on an older version of MINA. I'm not sure that it's a good thing to have two pieces of code dependng on two different versions of the same code (MINA) in the same project...
> wdyt?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira