From: Joe W. <jo...@gm...> - 2010-09-13 17:10:47
|
Hi all, In trunk, xprocxq isn't listed in extensions/build.properties, so it doesn't appear there's a way to disable it using a local.build.properties. Is it a required piece of eXist, such that it must be compiled with the distribution? It appears that every other folder in extensions/ has a corresponding entry in build.properties, except for this one. Thanks, Joe |
From: James F. <jam...@ex...> - 2010-09-13 17:21:09
|
On 13 September 2010 19:10, Joe Wicentowski <jo...@gm...> wrote: > Hi all, > > In trunk, xprocxq isn't listed in extensions/build.properties, so it > doesn't appear there's a way to disable it using a > local.build.properties. Is it a required piece of eXist, such that it > must be compiled with the distribution? It appears that every other > folder in extensions/ has a corresponding entry in build.properties, > except for this one. for now its part of the core build, but if you wanted to disable building it, just do so in extensions properties (it should be there) J |
From: Joe W. <jo...@gm...> - 2010-09-13 17:33:00
|
Thanks for your reply, Jim. >> In trunk, xprocxq isn't listed in extensions/build.properties, so it >> doesn't appear there's a way to disable it using a >> local.build.properties. Is it a required piece of eXist, such that it >> must be compiled with the distribution? It appears that every other >> folder in extensions/ has a corresponding entry in build.properties, >> except for this one. > > for now its part of the core build, but if you wanted to disable > building it, just do so in extensions properties (it should be there) But, as far as I can tell, xprocxq isn't an entry in extensions properties (EXIST_HOME/extensions/build.properties). Looking at extensions/xprocxq/build.xml, it appears that the build file references the build.properties and local.build.properties files but doesn't look for a true/false value. I can manually delete the .jar if I don't need it, but I thought I'd mention it since this appears to be the only extension in the extensions directory without an entry in build.properties. Joe |
From: Joe W. <jo...@gm...> - 2010-09-13 17:43:27
|
>> But, as far as I can tell, xprocxq isn't an entry in extensions >> properties (EXIST_HOME/extensions/build.properties). Looking at >> extensions/xprocxq/build.xml, it appears that the build file >> references the build.properties and local.build.properties files but >> doesn't look for a true/false value. > > hmm, that looks like it was changed/disabled by someone > >> I can manually delete the .jar if I don't need it, but I thought I'd >> mention it since this appears to be the only extension in the >> extensions directory without an entry in build.properties. > > in any event, xproc is core and I will be doing more work on it to > bring it up to compliance now that I have scratched other itches. Cool, thanks, Jim. (Expathrepo and XSGI were some pretty productive itches! Neat stuff!) Joe |