To support something like this, I'm thinking it would require that during initialization of the pipeline, UIMA would need to "install" the PEAR in some temporary location somewhere, and then use that installation. (The installation is needed because of the possibility that there are resources that are referenced by strings in the PEAR configuration, which need to be resolved relative to where the PEAR was installed.)
Is this what you have in mind? Though, typically, this is not something you'd want to do every time a pipeline was run, I think. -Marshall On 5/25/2011 4:01 AM, Greg Holmberg wrote: >> This is the part I haven't figured out yet. Reading the docs on pear files, >> it appears it is necessary to go through an installation process. I was >> really hoping to be able to just use a pear file as it comes from nexus, no >> unpacking, no modification--just read-only reference. In other words, just >> point to the pear file (unzipped) in my .m2/repository directory from an AAE >> descriptor, with no installation process. > > Sorry, I meant > > just point to the pear file (still zipped) in my .m2/repository directory > from an AAE descriptor, with no installation process. > >> >> Am I dreaming, or is there some way I could make that happen? By managing >> classpath and datapath, somehow? >> >> Or should I proceed directly to OSGI, do not pass pear, do not collect $200? >> :-) >
