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

Colm O hEigeartaigh commented on DIRKRB-738:
--------------------------------------------

[~rfeezel] - I moved this to 2.1.0. I will get 2.0.1 out first and then bump 
the version on master to 2.1.0-SNAPSHOT and look at your patch. I can't apply 
it to 2.0.x as it will break existing clients.

> Package name conflicts between sub-projects create problems with Java modules
> -----------------------------------------------------------------------------
>
>                 Key: DIRKRB-738
>                 URL: https://issues.apache.org/jira/browse/DIRKRB-738
>             Project: Directory Kerberos
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Richard Feezel
>            Priority: Major
>              Labels: patch
>             Fix For: 2.1.0
>
>         Attachments: kerby-package-conflicts.patch
>
>
> Eclipse now flags as errors attempts to access classes contained in a package 
> that is declared in more than one Jar (module). The current Kerby code base 
> has problems with the "org.apache.kerby.kerberos.kerb" and "org.apache.kerby" 
> packages in this regard. The affected projects are kerb-common, kerby-util, 
> kerb-core, kerb-util, and mavibot-backend. My approach to addressing this is 
> to create project-specific packages and moving the classes from these problem 
> package names to the new, project-specific ones. These changes, of course, 
> impact all uses of these moved classes resulting in many changes throughout 
> the Kerby system.
> Also included in the attached patch is a modification to the call to the 
> sun.security.krb5.Credentials constructor in has.client.HasLoginModule() to 
> add values for the new parameters.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to