From: Matej S. <mat...@co...> - 2011-11-28 17:28:54
|
"This package provides support for Channel Access Version 3. The server allows an existing Channel Access client to access a javaIOC database. The client allows the javaIOC to communicate with a Version 3 server, e.g. a javaIOC database can have links to records in a V3 IOC database." - from package.html You are right, they are optional. Matej On Mon, Nov 28, 2011 at 5:39 PM, Greg White <gr...@sl...> wrote: > PS: Also what's the nature of the dependency of pvIOC on caj and jca? I'm assuming it derives from optional use of a pvAccess server in a pvIOC. Does that mean that, if one confined one's use of the core EPICS V4 modules (pvDataJava, pvIOCJava and pvAccessJava) functionally to ChannelRPC, and so did not use a pvAccess server, that one could omit caj and jca from a download (assuming you were downloading the byte-code jars and just running with them in the classpath, as opposed to building from source, in which case you'd need them to resolve compile time symbols). > > Greg > > On 28 Nov 2011, at 17:26, Greg White wrote: > >> Sure, I omitted SWT deliberately, assuming it's not necessary, it's only desirable for developers. >> Basically my mail was driven by the status of this RemoteTea.jar thing - what is that *Marty*? >> >> I understood the interdependencies and got them from the poms (poms should be plural, we don't >> have one pom but I think we should for the objective of making it easier for someone to get started). >> >> Cheers >> Greg >> >> On 28 Nov 2011, at 17:09, Matej Sekoranja wrote: >> >>> Hi, >>>> Can I confirm what files constitute a the minimum runtime install for EPICS V4 in its java binding, necessary to run either a server or a client, of any "type" (ChannelRPC, ChannelPutGet, etc)? I am assuming it's only these 5 jar files. >>>> >>>> jca-2.3.5.jar | >>>> caj-1.1.8.jar | prerequisites >>>> pvData-1.0-SNAPSHOT.jar | >>>> pvAccess-1.0-SNAPSHOT.jar | EPICSV4 >>>> pvIOC-1.0-SNAPSHOT.jar | >>>> >>>> Maven installs 110 jar files into .m2. Of those more than half (64) have maven in their name, so are presumably just maven. That leaves ~40 unaccounted for, so I wanted to check they're all either maven prerequisites or pvService prerequisites. >>>> >>>> If this list of 5 is right, I'll make them available as downloads from sourceforge. >>> >>> pvData is standalone. >>> pvAccess requires pvData. >>> >>> pvIOC requires jca, caj, SWT and RemoteTra oncrpc JAR. I do not know >>> why the last one is used. Marty can provide more info. >>> Note that SWT is tricky, since you need native library also. But it is >>> optional - only if you want see SWTShell GUI for JavaIOC. >>> >>> Matej >>> >>> ps Just look at pom.xml to see the list of dependencies. >>> >>> ------------------------------------------------------------------------------ >>> All the data continuously generated in your IT infrastructure >>> contains a definitive record of customers, application performance, >>> security threats, fraudulent activity, and more. Splunk takes this >>> data and makes sense of it. IT sense. And common sense. >>> http://p.sf.net/sfu/splunk-novd2d >> >> >> ------------------------------------------------------------------------------ >> All the data continuously generated in your IT infrastructure >> contains a definitive record of customers, application performance, >> security threats, fraudulent activity, and more. Splunk takes this >> data and makes sense of it. IT sense. And common sense. >> http://p.sf.net/sfu/splunk-novd2d > > |