Hi,
I'm not sure what you mean by used for testing.
I mean used for manual testing. I'm planning to use it for some manual
testing, and I thought others use it as well or plan to use it. I also
want to run some benchmarks to find out if a Lucene index or the property
index is faster.
It has
Hi gang,
I'm wondering about 2 issues that are talking about the same refactoring
task [0] and [1].
There is still a bunch of code there.
Is there any update on the oak-core 'mk' package?
As far as I'm concerned, the index code that references this package is
separated under a package named
Hi,
Isn't the property index (o.a.j.oak.plugins.index.old) still used for
testing?
Regards,
Thomas
On 10/24/12 3:05 PM, Alex Parvulescu alex.parvule...@gmail.com wrote:
Hi gang,
I'm wondering about 2 issues that are talking about the same refactoring
task [0] and [1].
There is still a bunch
Hi,
I'm not sure what you mean by used for testing.
It has some unit tests, but other than that, it has no central role in
testing, removing it doesn't cause a disturbance in the force.
best,
alex
On Wed, Oct 24, 2012 at 4:59 PM, Thomas Mueller muel...@adobe.com wrote:
Hi,
Isn't the
On 24.10.12 17:13, Alex Parvulescu wrote:
Hi,
I'm not sure what you mean by used for testing.
It has some unit tests, but other than that, it has no central role in
testing, removing it doesn't cause a disturbance in the force.
+1 for removing it.
Michael
best,
alex
On Wed, Oct 24,
Hi,
On Wed, Oct 24, 2012 at 6:13 PM, Alex Parvulescu
alex.parvule...@gmail.com wrote:
I'm not sure what you mean by used for testing.
It has some unit tests, but other than that, it has no central role in
testing, removing it doesn't cause a disturbance in the force.
Except hundreds lines of
