-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
Two problems:
- The code in this (epics-rip/caj) repository actually contains Matej's JCAS pure-Java CA Server implementation, but the README file talks about it being a CA client. If the JCAS is intentionally being abandoned (I don't remember discussing that at all in the core developer meetings, I would prefer that we explicitly state we are doing so) this archive repository should be named epics-rip/jcas and the README should properly reflect what the code actually does.
- The original CAJ and JCA libraries are currently described on this SourceForge page; JCA provided the client API and the JNI implementation, while CAJ provided the pure Java implementation. It is reasonable that we should keep using the JCA name for the client API, but we should also have an archive of the JNI C code, and it should appear under a project named epics-rip/jca or epics-rip/jca-jni — it was never called CAJ so should not use that name.
Metadata
Metadata
Assignees
Labels
No labels