Hi,
Am 25.01.2012 um 01:37 schrieb Jukka Zitting:
> Hi,
>
> On Wed, Jan 25, 2012 at 1:06 AM, Tobias Bocanegra wrote:
>> how about adding getSelectorJcrNames() and deprecate the other one?
>
> Yes, we can do that. It just feels silly that we have to go through
> hoops like that when AFAICT were
Hi,
On Wed, Jan 25, 2012 at 1:06 AM, Tobias Bocanegra wrote:
> how about adding getSelectorJcrNames() and deprecate the other one?
Yes, we can do that. It just feels silly that we have to go through
hoops like that when AFAICT were the only ones using and implementing
this interface.
And (corre
On 2012-01-25 01:04, Felix Meschberger wrote:
Wanted to upgrade the Sling build to Jacktabbit 2.3.7 bundles .. Due to this
incompatibility this is not possible without updating everything Jackrabbit to
2.3.7...
Regards
Felix
...
Which IMHO is exactly the right thing to do...
I agree with felix,
/**
- * @return an array of Names representing the
selector names of
+ * @return an array of Strings representing the
selector names of
* the query result.
* @see javax.jcr.query.QueryResult#getSelectorNames()
*/
- public Name[] getSele
Wanted to upgrade the Sling build to Jacktabbit 2.3.7 bundles .. Due to this
incompatibility this is not possible without updating everything Jackrabbit to
2.3.7...
Regards
Felix
Jukka Zitting schrieb:
Hi,
On Wed, Jan 25, 2012 at 12:36 AM, Felix Meschberger wrote:
> I got a big problem with
Hi,
On Wed, Jan 25, 2012 at 12:36 AM, Felix Meschberger wrote:
> I got a big problem with Jackrabbit SPI version 2.3.7 just released: This
> increases the
> export version of the org.apache.jackrabit.spi package from 2.4.0 to 3.0.0.
Yes, I changed the SPI in a minor but backwards-incompatible w
Hi
Looks like this came in for JCR-3198, which indeed changes signatures on
methods, which is indeed breaking compatiblity.
This should probably not be done (and may new interfaces defined with new API).
Regards
Felix
Am 25.01.2012 um 00:36 schrieb Felix Meschberger:
> Hi all,
>
> I got a bi
Hi all,
I got a big problem with Jackrabbit SPI version 2.3.7 just released: This
increases the export version of the org.apache.jackrabit.spi package from 2.4.0
to 3.0.0.
The consequence of this is dramatic: It breaks compatibility on all levels !
It looks like this has been done by commit 12
