On 01/30/2018 02:07 AM, Ralph Lange wrote:
> On Tue, Jan 30, 2018 at 12:57 AM, J. Lewis Muir wrote:
>
> I noticed that the EPICS Extensions page at
>
> https://epics.anl.gov/extensions/index.php
>
> links to the SourceForge project pages for CAJ and JCA. Haven't those
> moved to GitHub as JCA:
>
> https://github.com/epics-base/jca
>
> And it seems the projects have been merged into one because I see
>
> https://github.com/epics-rip/caj
>
> is under "epics-rip".
>
> If so, I think those links should be updated. Or am I premature, and
> the GitHub stuff isn't ready yet?
>
> You are perfectly right, Lewis,
>
> The EPICS website is behind the APS firewall, which restricts the people
> who are able to do updates to Andrew.
I was about to update the JCAS, JCA and CAJ links to all point to the
GitHub jca project, although I would rather point to a page that has
links to online documentation and more information about how to use the
libraries. Didn't there used to be some API documentation about the JCA
library API? Is the Javadoc published anywhere?
However, I see that both the extensions index page and the page at
http://epics-jca.sourceforge.net/ list JCA as being the client library
that used JNI to wrap the C++ client library, while CAJ was the name
given to the pure Java implementation of the library, so it seems that
we have switched our names around recently. The maintainers agreed to
abandon the JNI-based code which was supposed to be archived under the
epics-rip project, and all future maintenance will occur on the pure
Java code.
However I can't actually find any C code in the epics-rip/caj project,
which actually contains the code for JCAS, Matej's pure-java CA server
implementation and not the JNI-based client library implementation at
all. I just filed an issue against the epics-rip/caj project about this.
Until all this naming gets cleared up I am reluctant to confuse people
further by changing any links.
> @Andrew: while you're at it, the page about CAS
> (https://epics.anl.gov/extensions/cas/index.php) also needs updating.
Done, but since there is PCAS API reference documentation linked from
that page we need to decide what to do about those documents; at minimum
the README.md should also point to the above page (the CA reference
manual which is linked only covers the CA client API).
- Andrew
--
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon
- References:
- CAJ and JCA links on website point to SourceForge J. Lewis Muir
- Re: CAJ and JCA links on website point to SourceForge Ralph Lange
- Navigate by Date:
- Prev:
Sequencer seem to skip states with EPICS 3.16.1 Simon Reiter
- Next:
Re: Scanning on event number fails with EPICS 3.16 Michael Davidsaver
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
<2018>
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: CAJ and JCA links on website point to SourceForge Ralph Lange
- Next:
Using EPICS PV Gateway with multiple IOCs on the same server Abdalla Ahmad
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
<2018>
2019
2020
2021
2022
2023
2024
|