Hi, Christophe Lombart schrieb: > Hi Felix, > > Oopps, I didn't pay attention to the profile "bundle".
Yes, this is a nasty thing ... > Thanks for the patch. > it works here. Excellent. > > Why not apply your patch ? I can, no problem. I just didn't want to take this off from under your feet ;-) > Another question, why it is necessary to add the version number ? it is not > working without > that org.apache.jackrabbit.core.security.principal;version=1.6.0 ? This is a package which is exported from the jackrabbit-core library, IIRC to enable user and ACL management in other bundles. As it is re-export, it should be tagged with the same version as the original Jackrabbit library version. Regards Felix > > br, > Christophe > > > > 2009/11/26 Felix Meschberger <[email protected]> > >> Hi, >> >> This looks strange. >> >> So you have just updated the jackrabbit library references to 1.6.0 and >> run the build with the bundle profile ? >> >> $ mvn -Pbundle clean package >> >> The bundle profile is used to update the static MANIFEST.MF file which >> is used by the standard build. I created this to prevent >> OutOfMemoryErrors due to the large number of classes to include. >> >> Regards >> Felix >> >> Christophe Lombart schrieb: >>> Hi all, >>> >>> I would like to work on the issue SLING-1190 (Upgrade Jackrabbit >> dependency >>> to 1.6). I don't understand why I got the exception (see more in [1]). >>> I don't see a big difference between J 1.5 & J 1.6 in this area. So, I >> need >>> help :-) >>> >>> thanks, >>> Christophe >>> >>> >>> [1] https://issues.apache.org/jira/browse/SLING-1190 >>> >
