You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@sling.apache.org by "Robert A. Decker" <de...@robdecker.com> on 2014/06/16 12:49:53 UTC

installed sling explorer version buggy (1.0.2) while built version is not

I think what I describe below has been the case for two years now.

When I build sling from scratch (as of a few minutes ago) it comes installed with sling explorer version 1.0.2, but this version is buggy. It’s unable to display nodes that have ‘/‘ characters in their sling:resourceType.

I see that this is fixed in the sling explorer’s source code (node.esp file). And so I uninstall version 1.0.2 and install 1.0.3-SNAPSHOT which I find at:
bundles/extensions/explorer/target/org.apache.sling.extensions.explorer-1.0.3-SNAPSHOT

Robert A. Decker
decker@robdecker.com
http://robdecker.com/about



Re: installed sling explorer version buggy (1.0.2) while built version is not

Posted by "Robert A. Decker" <de...@robdecker.com>.
Here are my current diffs to get a working version of sling, as of this morning.


Index: bundles/jcr/jackrabbit-server/src/main/java/org/apache/sling/jcr/jackrabbit/server/impl/SlingServerRepository.java
===================================================================
--- bundles/jcr/jackrabbit-server/src/main/java/org/apache/sling/jcr/jackrabbit/server/impl/SlingServerRepository.java	(revision 1603357)
+++ bundles/jcr/jackrabbit-server/src/main/java/org/apache/sling/jcr/jackrabbit/server/impl/SlingServerRepository.java	(working copy)
@@ -23,6 +23,7 @@

 import org.apache.jackrabbit.api.management.DataStoreGarbageCollector;
 import org.apache.jackrabbit.api.management.RepositoryManager;
+import org.apache.jackrabbit.core.RepositoryImpl;
 import org.apache.sling.jcr.api.SlingRepository;
 import org.apache.sling.jcr.base.AbstractSlingRepository2;
 import org.apache.sling.jcr.base.AbstractSlingRepositoryManager;
@@ -48,7 +49,9 @@
         final Repository base = this.getRepository();
         if (base instanceof RepositoryManager) {
             return ((RepositoryManager) base).createDataStoreGarbageCollector();
-        }
+        } else if (base instanceof RepositoryImpl) {
+			return ((RepositoryImpl) base).createDataStoreGarbageCollector();
+		}

         return null;
     }
Index: launchpad/builder/src/main/bundles/list.xml
===================================================================
--- launchpad/builder/src/main/bundles/list.xml	(revision 1603357)
+++ launchpad/builder/src/main/bundles/list.xml	(working copy)
@@ -389,7 +389,7 @@
         <bundle>
             <groupId>org.apache.sling</groupId>
             <artifactId>org.apache.sling.commons.json</artifactId>
-            <version>2.0.6</version>
+            <version>2.0.7-SNAPSHOT</version>
         </bundle>
         <bundle>
             <groupId>org.apache.felix</groupId>





Robert A. Decker
decker@robdecker.com
http://robdecker.com/about


On 17 Jun 2014, at 23:35, Robert A. Decker <de...@robdecker.com> wrote:

> Yes, it works, thanks.
> 
> I'm getting a new error that is probably unrelated:
> org.apache.sling.commons.json.sling,version=[2.0,3) -- Cannot be resolved
> For bundle "Apache Sling Default GET Servletsorg.apache.sling.servlets.get” on a brand new build with nothing custom installed.
> 
> In the pom for:
> <artifactId>org.apache.sling.servlets.get</artifactId>
> 
> There’s the dependency:
>        <dependency>
>            <groupId>org.apache.sling</groupId>
>            <artifactId>org.apache.sling.commons.json</artifactId>
>            <version>2.0.7-SNAPSHOT</version>
>            <scope>provided</scope>
>        </dependency>
> 
> But 2.0.6 seems to be the version of org.apache.sling.commons.json that’s installed.
> 
> 
> 
> Robert A. Decker
> decker@robdecker.com
> http://robdecker.com/about
> 
> 
> On 16 Jun 2014, at 15:03, Bertrand Delacretaz <bd...@apache.org> wrote:
> 
>> Hi Rob,
>> 
>> On Mon, Jun 16, 2014 at 12:49 PM, Robert A. Decker <de...@robdecker.com> wrote:
>>> I see that this is fixed in the sling explorer’s source code (node.esp file). And so
>>> I uninstall version 1.0.2 and install 1.0.3-SNAPSHOT...
>> 
>> http://svn.apache.org/r1602859 should fix this, could you confirm?
>> 
>> Ciao,
>> -Bertrand
>> 
> 
> 


Re: installed sling explorer version buggy (1.0.2) while built version is not

Posted by Sandro Boehme <sa...@gmx.de>.
Hi Robert,

if you use it just for reading the current version of the Sling 
JCRBrowser might also be an option worth trying:
http://www.jcrbrowser.org/sling/website/
I'm currently working on an edit version.

Best,

Sandro

Am 17.06.14 23:35, schrieb Robert A. Decker:
> Yes, it works, thanks.
>
> I'm getting a new error that is probably unrelated:
> org.apache.sling.commons.json.sling,version=[2.0,3) -- Cannot be resolved
> For bundle "Apache Sling Default GET Servletsorg.apache.sling.servlets.get” on a brand new build with nothing custom installed.
>
> In the pom for:
> <artifactId>org.apache.sling.servlets.get</artifactId>
>
> There’s the dependency:
>          <dependency>
>              <groupId>org.apache.sling</groupId>
>              <artifactId>org.apache.sling.commons.json</artifactId>
>              <version>2.0.7-SNAPSHOT</version>
>              <scope>provided</scope>
>          </dependency>
>
> But 2.0.6 seems to be the version of org.apache.sling.commons.json that’s installed.
>
>
>
> Robert A. Decker
> decker@robdecker.com
> http://robdecker.com/about
>
>
> On 16 Jun 2014, at 15:03, Bertrand Delacretaz <bd...@apache.org> wrote:
>
>> Hi Rob,
>>
>> On Mon, Jun 16, 2014 at 12:49 PM, Robert A. Decker <de...@robdecker.com> wrote:
>>> I see that this is fixed in the sling explorer’s source code (node.esp file). And so
>>> I uninstall version 1.0.2 and install 1.0.3-SNAPSHOT...
>>
>> http://svn.apache.org/r1602859 should fix this, could you confirm?
>>
>> Ciao,
>> -Bertrand
>>
>
>


Re: installed sling explorer version buggy (1.0.2) while built version is not

Posted by "Robert A. Decker" <de...@robdecker.com>.
Yes, it works, thanks.

I'm getting a new error that is probably unrelated:
org.apache.sling.commons.json.sling,version=[2.0,3) -- Cannot be resolved
For bundle "Apache Sling Default GET Servletsorg.apache.sling.servlets.get” on a brand new build with nothing custom installed.

In the pom for:
<artifactId>org.apache.sling.servlets.get</artifactId>

There’s the dependency:
        <dependency>
            <groupId>org.apache.sling</groupId>
            <artifactId>org.apache.sling.commons.json</artifactId>
            <version>2.0.7-SNAPSHOT</version>
            <scope>provided</scope>
        </dependency>

But 2.0.6 seems to be the version of org.apache.sling.commons.json that’s installed.



Robert A. Decker
decker@robdecker.com
http://robdecker.com/about


On 16 Jun 2014, at 15:03, Bertrand Delacretaz <bd...@apache.org> wrote:

> Hi Rob,
> 
> On Mon, Jun 16, 2014 at 12:49 PM, Robert A. Decker <de...@robdecker.com> wrote:
>> I see that this is fixed in the sling explorer’s source code (node.esp file). And so
>> I uninstall version 1.0.2 and install 1.0.3-SNAPSHOT...
> 
> http://svn.apache.org/r1602859 should fix this, could you confirm?
> 
> Ciao,
> -Bertrand
> 


Re: installed sling explorer version buggy (1.0.2) while built version is not

Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi Rob,

On Mon, Jun 16, 2014 at 12:49 PM, Robert A. Decker <de...@robdecker.com> wrote:
> I see that this is fixed in the sling explorer’s source code (node.esp file). And so
> I uninstall version 1.0.2 and install 1.0.3-SNAPSHOT...

http://svn.apache.org/r1602859 should fix this, could you confirm?

Ciao,
-Bertrand