Not thinking in through maybe? I just did exactly that and it worked
just fine. I've adjusted our build process and we're good to go with
much shorter builds.
Thanks for pointing that out Alex,
Erik
On Tue, Feb 15, 2011 at 2:54 AM, Alexander Klimetschek
wrote:
> On 15.02.11 01:33, "Erik Froese"
On 15.02.11 01:33, "Erik Froese" wrote:
>I need to copy in the indexes for the default workspace in
>jackrabbit/workspaces/default/index/ as well as in
>jackrabbit/repository/index. I can't do that unless the directory
>exists, which means jackrabbit must have come up already to create it.
What p
Hey Alex,
Thanks for the clarification. I'm not sure how to copy the indexes in
there since Jackrabbit seems to not like the fact that the workspace
folder already exists. It prevents the rest of the application from
coming up.
The culprit is org.apache.jackrabbit.core.config.RepositoryConfig on
On 14.02.11 16:47, "Erik Froese" wrote:
>Is there a way to configure the Lucene that comes with Jackrabbit so
>that it creates the initial indexes in a separate thread when starting
>up?
AFAIK no. I think this is because the JCR spec requires that the index for
queries is up-to-date upon a save()
Hey everyone,
Is there a way to configure the Lucene that comes with Jackrabbit so
that it creates the initial indexes in a separate thread when starting
up?
I found this:
http://wiki.apache.org/jackrabbit/Search
and this:
http://wiki.apache.org/jackrabbit/IndexingConfiguration
But neither prov
