Hi, On Jan 24, 2008 3:31 PM, Julian Reschke <[EMAIL PROTECTED]> wrote: > Therefore I'd suggest to either > > - move the query parser into a separate top-level project (with a > dependency on jackrabbit-spi-commons), or to > > - move it into jackrabbit-spi-commons.
+1 to moving it to jackrabbit-spi-commons. > On the other hand, I can think of a few reasons for not doing that now, > such as: > > - with the work on the JCR 2.0 RI, query is a moving target, and > > - exposing the internal query tree as a "public" API may be problematic. I wouldn't worry too much about those. We can label the query parser in spi-commons so that people don't expect the API to be too stable. I don't see any problems in making the query tree public. BR, Jukka Zitting
