At first impression it appears that the gnu-crypto library yanked a great portion of code from the jldap library althought I suppose it could have been the other way around. I doubt it since, IIRC jldap has been around for far longer than gnu-crypto. The problem is that the two packages collide in the area of Sasl code because they both contain javax.security.Sasl. I do not know which project should be considered the maintainer and if there is a fork in the development of these classes then different packages should be used for each. As it stands the two libraries collide. I'm trying to get in touch with the maintainers and find out who owns this stuff for the purpose of future development and consolodation of effort. Reproducible: Always Steps to Reproduce: 1.Try to install either package or use either package with the other in the classpath before it. 2. 3.
I've decided to roll a new version of the jldap ebuild since Novell has patched up their stuff to fix the javas.security collision with both gnu-crypto and java 1.5. Use the following command to get the latest version of the ndk for jldap, check it, and then tarball it for the ebuild (as was done with the previous release): cvs -d :pserver:anonymous@cvs.openldap.org:/repo/OpenLDAP -z3 co -r Mar_ndk_2004 openldap-jldap
Created attachment 57882 [details] New proposed ebuild. Just changed the name of the file really, since that's the only relevant change to the new ebuild (new source, new ebuild version).
Need someone to package, deploy and allow sync & test before we can move on and close this bug.
Latest jldap tag committed. Sorry to keep you waiting for this long. It is best to add a comment to a bug if nothing happens for in a month to catch the attention of java developers. We are understaffed so some bugs haven't gotten the attention they deserve.
