Hi all,
I found the actual problem. The final WAR of sling is built using some
configuration files. In one of those configuration files (list.xml, located
in '\launchpad\builder\src\main\bundles' directory) the sling modules and
their versions are mentioned. In this file the version for
'org.apache.sling.jcr.jacrabbit.server' module was mentioned to an older
version. So though all these time I modified the POM files to set the
current version of the Jackrabbit and Sling modules, still the older
org.apache.sling.jcr.jackrabbit.server was used and as a result the older
Jackrabbit Core was being used.
So now the latest and bug free jackrabbit-core is being used. But now I
found that a framework error is occurring as below:
11.02.2011 21:12:50.569 *ERROR* [FelixDispatchQueue]
org.apache.aries.jmx.core FrameworkEvent ERROR
(org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.aries.jmx.core [7]: Unable to resolve 7.0: missing requirement
[7.0] package;
(&(package=org.apache.aries.util)(version>=0.3.0)(!(version>=1.0.0))))
org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.aries.jmx.core [7]: Unable to resolve 7.0: missing requirement
[7.0] package;
(&(package=org.apache.aries.util)(version>=0.3.0)(!(version>=1.0.0)))
at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3409)
at
org.apache.felix.framework.Felix.startBundle(Felix.java:1719)
at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1148)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:619)
I think it's occurring because of some conflict of this updated module with
some older module of Sling that's still in use. Does anybody have any idea
regarding this?
Thanks & Regards.
On Tue, Feb 8, 2011 at 5:40 PM, Gazi Mushfiqur Rahman <
[email protected]> wrote:
> Hi Stefan,
>
>
> Thanks a lot for your previous reply. But I still failed to fix the issue.
>
>
> I am trying to incorporate the 2.2.3 version of Jackrabbit in Sling, since
> this is the latest stable version of Jackrabbit. Also it has fixed the
> locking issue. I've changed all the POMs in Sling to use the 2.2.3 version
> of Jackrabbit. But still the locking was not working. Then I tried to add
> some logs in the Jackrabbit for debug purpose and modified the version to
> 2.2.3-SNAPSHOT. But I didn't find my logs in the Sling log file. Then I
> tried to logg those messages in the 'System.out' along with the logging. But
> still I am failing to get those logs in the Tomcat's output file
> (catalina.out). So, I think my changes are not used by Sling when I am
> building Sling.
>
>
>
> If I can't push my modifications in the Sling, I think I won't be able to
> fix the issue in Sling in any way. So, can you please help me in building
> Sling properly?
>
>
>
> I followed the following steps for the building:
>
> 1. Modify Some java files in jackrabbit-core (version 2.2.3) for the
> logging
>
> 2. Change all the POMs of Jackrabbit 2.2.3 and set their version to
> '2.2.3-SNAPSHOT'
>
> 3. Build jackrabbit using the following command:
>
> mvn clen
>
> mvn install
>
> 3. Change the all the dependencies of Sling to use 2.2.3-SNAPSHOT
> version of Jackrabbit modules
>
> 4. Change the
> org.apache.sling.jcr.jackrabbit.server.impl.security.PluggableDefaultAccessManager
> and change the signature of 'canRead' method as the modified super class
>
> 5. Build Sling using the following commands:
>
> mvn clean
> mvn install -Dmaven.test.skip=true
>
>
> Am I mistaking anything in the build process? Any help regarding the build
> process will be much appreciated.
>
> Thanks & Regards.
>
> On Mon, Jan 31, 2011 at 4:47 AM, James Stansell <[email protected]>wrote:
>
>> Hi,
>>
>> The jackrabbit core jar version 2.1.1 will be listed in one of the
>> pom.xml files, but I am not sure which one. You need to change it to
>> the 2.2.2 version. Other jar versions may also need to change, but not
>> sure of the details.
>>
>> Regards,
>>
>> -james.
>>
>> On Sunday, January 30, 2011, Gazi Mushfiqur Rahman wrote:
>> ...
>> > Jackrabbit team already resolved this issue on their latest version,
>> i.e.
>> > 2.2.2. So can anyone please update the jackrabbit version for Sling or
>> just
>> > fix this issue or let me know how to build and integrate jackrabbit-core
>> in
>> > Sling?
>>
>
>
