Build failed in Jenkins: sling-trunk-1.6 #1757

[Apache Jenkins Server]

See 

Changes:

[cziegeler] Correct queue type, ignore was missing in the list

[cziegeler] Improve log message

--
[...truncated 20182 lines...]
[INFO] Apache Sling JCR Base Bundle .. SUCCESS [5.176s]
[INFO] Apache Sling JCR ClassLoader .. SUCCESS [10.072s]
[INFO] Apache Sling Initial Content Loader ... SUCCESS [6.385s]
[INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [9.517s]
[INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [3.844s]
[INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support  SUCCESS 
[4.359s]
[INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [6.611s]
[INFO] Apache Sling Object Content Mapping ... SUCCESS [5.948s]
[INFO] Apache Sling JCR Resource Resolver  SUCCESS [2:08.433s]
[INFO] Apache Sling JCR Repository Registration .. SUCCESS [5.304s]
[INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [6.313s]
[INFO] Apache Sling DavEx Access to repositories . SUCCESS [6.059s]
[INFO] Apache Sling JCR WebConsole Bundle  SUCCESS [3.282s]
[INFO] Apache Sling Servlet Resolver . SUCCESS [7.271s]
[INFO] Apache Sling Default GET Servlets . SUCCESS [4.219s]
[INFO] Apache Sling Default POST Servlets  SUCCESS [4.988s]
[INFO] Apache Sling Compat Servlets .. SUCCESS [2.952s]
[INFO] Apache Sling Scripting Implementation API . SUCCESS [2.887s]
[INFO] Apache Sling Scripting Core implementation  SUCCESS [3.738s]
[INFO] Apache Sling Scripting JavaScript Support . SUCCESS [26.319s]
[INFO] Apache Sling Scripting JSP Support  SUCCESS [6.986s]
[INFO] Apache Sling JSP Tag Library .. SUCCESS [4.232s]
[INFO] Apache Sling JSP Standard Tag Library . SUCCESS [2.912s]
[INFO] Apache Sling Adapter Manager Implementation ... SUCCESS [3.899s]
[INFO] Apache Sling Bundle Resource Provider . SUCCESS [4.557s]
[INFO] Apache Sling Discovery API  SUCCESS [4.124s]
[INFO] Apache Sling Resource-Based Discovery Service . SUCCESS [3:18.320s]
[INFO] Apache Sling Discovery Support Bundle . SUCCESS [4.479s]
[INFO] Apache Sling Discovery Standalone Implementation .. SUCCESS [6.273s]
[INFO] Apache Sling Event Support  FAILURE [8:34.429s]
[INFO] Apache Sling Filesystem Resource Provider . SKIPPED
[INFO] Apache Sling javax.activation bundle .. SKIPPED
[INFO] Apache Sling Settings . SKIPPED
[INFO] Apache Sling Thread Dumper  SKIPPED
[INFO] Apache Sling Web Console Branding . SKIPPED
[INFO] Apache Sling Web Console Security Provider  SKIPPED
[INFO] Apache Sling Groovy Extensions  SKIPPED
[INFO] Apache Sling Explorer . SKIPPED
[INFO] Apache Sling Test Tools ... SKIPPED
[INFO] Apache Sling JUnit Core ... SKIPPED
[INFO] Apache Sling JUnit Scriptable Tests Provider .. SKIPPED
[INFO] Apache Sling JUnit Remote Tests Runners ... SKIPPED
[INFO] Apache Sling Testing Resource Resolver Mock ... SKIPPED
[INFO] Apache Sling Installer  SKIPPED
[INFO] Apache Sling Installer WebConsole Plugin .. SKIPPED
[INFO] Apache Sling File Installer ... SKIPPED
[INFO] Apache Sling JCR Installer  SKIPPED
[INFO] Apache Sling Installer Configuration Admin Support  SKIPPED
[INFO] Apache Sling Deployment Package Installer . SKIPPED
[INFO] Apache Sling Installer Integration Tests .. SKIPPED
[INFO] Apache Sling Launchpad API  SKIPPED
[INFO] Apache Sling Launchpad Base ... SKIPPED
[INFO] Apache Sling Launchpad Installer .. SKIPPED
[INFO] Apache Sling Launchpad Content  SKIPPED
[INFO] Apache Sling Launchpad Application Builder  SKIPPED
[INFO] Apache Sling Sample Server-Side Tests . SKIPPED
[INFO] Apache Sling Failing Server-Side Tests  SKIPPED
[INFO] Apache Sling Sample Integration Tests . SKIPPED
[INFO] Apache Sling Launchpad Testing Services ... SKIPPED
[INFO] Apache Sling Launchpad Testing Services WAR ... SKIPPED
[INFO] Apache Sling Launchpad Testing Fragment Bundle  SKIPPED
[INFO] Apache Sling Launchpad Test Bundles ... SKIPPED
[INFO] Apache Sling Integration Tests  SKIPPED
[INFO] Apache Sling Launchpad Testing  SKIPPED
[INFO] Apache Sling Launchpad Testing WAR version  SKIPPED
[INFO] Apache Sling (Builder)  SKIPPED
[INFO] --

Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Event Support #1757

[Apache Jenkins Server]

See 


Changes:

[cziegeler] Correct queue type, ignore was missing in the list

--
[...truncated 9315 lines...]
23.07.2013 06:50:21.446 *INFO* [main] 
PAXEXAM-PROBE-8fd34699-3a57-4829-9882-29bf4874c424 Service [90] ServiceEvent 
UNREGISTERING
23.07.2013 06:50:21.446 *INFO* [main] 
PAXEXAM-PROBE-8fd34699-3a57-4829-9882-29bf4874c424 Service [91] ServiceEvent 
UNREGISTERING
23.07.2013 06:50:21.447 *INFO* [main] 
PAXEXAM-PROBE-8fd34699-3a57-4829-9882-29bf4874c424 Service [92] ServiceEvent 
UNREGISTERING
23.07.2013 06:50:21.447 *INFO* [main] 
PAXEXAM-PROBE-8fd34699-3a57-4829-9882-29bf4874c424 Service [93] ServiceEvent 
UNREGISTERING
23.07.2013 06:50:21.447 *INFO* [main] 
PAXEXAM-PROBE-8fd34699-3a57-4829-9882-29bf4874c424 Service [94] ServiceEvent 
UNREGISTERING
23.07.2013 06:50:21.448 *INFO* [main] 
PAXEXAM-PROBE-8fd34699-3a57-4829-9882-29bf4874c424 Service [95] ServiceEvent 
UNREGISTERING
23.07.2013 06:50:21.448 *INFO* [main] 
PAXEXAM-PROBE-8fd34699-3a57-4829-9882-29bf4874c424 Service [96] ServiceEvent 
UNREGISTERING
23.07.2013 06:50:21.448 *INFO* [main] 
PAXEXAM-PROBE-8fd34699-3a57-4829-9882-29bf4874c424 Service [97] ServiceEvent 
UNREGISTERING
23.07.2013 06:50:21.449 *INFO* [main] 
PAXEXAM-PROBE-8fd34699-3a57-4829-9882-29bf4874c424 Service [98] ServiceEvent 
UNREGISTERING
23.07.2013 06:50:21.449 *INFO* [main] 
PAXEXAM-PROBE-8fd34699-3a57-4829-9882-29bf4874c424 BundleEvent STOPPED
23.07.2013 06:50:21.449 *INFO* [main] 
PAXEXAM-PROBE-8fd34699-3a57-4829-9882-29bf4874c424 BundleEvent UNRESOLVED
23.07.2013 06:50:21.451 *INFO* [main] 
PAXEXAM-PROBE-8fd34699-3a57-4829-9882-29bf4874c424 BundleEvent UNINSTALLED
23.07.2013 06:50:21.452 *INFO* [FelixShutdown] org.apache.felix.framework 
BundleEvent STOPPING
23.07.2013 06:50:21.452 *INFO* [FelixDispatchQueue] org.apache.felix.framework 
FrameworkEvent PACKAGES REFRESHED
23.07.2013 06:50:21.453 *INFO* [FelixStartLevel] 
org.ops4j.pax.exam.invoker.junit BundleEvent STOPPING
23.07.2013 06:50:21.453 *INFO* [FelixStartLevel] 
org.ops4j.pax.exam.invoker.junit Service [81] ServiceEvent UNREGISTERING
23.07.2013 06:50:21.453 *INFO* [FelixStartLevel] 
org.ops4j.pax.exam.invoker.junit BundleEvent STOPPED
23.07.2013 06:50:21.454 *INFO* [FelixStartLevel] 
org.ops4j.pax.tipi.hamcrest.core BundleEvent STOPPING
23.07.2013 06:50:21.454 *INFO* [FelixStartLevel] 
org.ops4j.pax.tipi.hamcrest.core BundleEvent STOPPED
23.07.2013 06:50:21.455 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.console.WebConsolePlugin,108] ServiceEvent 
UNREGISTERING
23.07.2013 06:50:21.456 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.console.InventoryPlugin,110] ServiceEvent 
UNREGISTERING
23.07.2013 06:50:21.457 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.deprecated.JobStatusProviderImpl,109] 
ServiceEvent UNREGISTERING
23.07.2013 06:50:21.457 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.jmx.AllJobStatisticsMBean,112] ServiceEvent 
UNREGISTERING
23.07.2013 06:50:21.457 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.JobConsumerManager Updating property provider 
with: 
23.07.2013 06:50:21.458 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.JobManagerImpl Received topology event 
TopologyEvent [type=PROPERTIES_CHANGED, 
oldView=org.apache.sling.discovery.impl.standalone.NoClusterDiscoveryService$3@ea1bc2,
 
newView=org.apache.sling.discovery.impl.standalone.NoClusterDiscoveryService$3@ea1bc2]
23.07.2013 06:50:21.459 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.deprecated.EventAdminBridge,113] ServiceEvent 
UNREGISTERING
23.07.2013 06:50:21.459 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.deprecated.EventAdminBridge Apache Sling Job 
Event Bridge stopped on instance aa5bd2ad-8049-4d7e-a695-9d7da9ba5091
23.07.2013 06:50:21.461 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.jcr.PersistenceHandler,107] ServiceEvent 
UNREGISTERING
23.07.2013 06:50:21.461 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.JobManagerImpl Apache Sling Job Manager 
stopping on instance aa5bd2ad-8049-4d7e-a695-9d7da9ba5091
23.07.2013 06:50:21.461 *INFO* [FelixStartLevel] 
org.apache.sling.event.impl.jobs.JobManagerImpl Apache Sling Job Manager 
stopped on instance aa5bd2ad-8049-4d7e-a695-9d7da9ba5091
23.07.2013 06:50:21.462 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[111] ServiceEvent UNREGISTERING
23.07.2013 06:50:21.463 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.jobs.JobConsumerManager,76] ServiceEvent 
UNREGISTERING
23.07.2013 06:50:21.464 *INFO* [FelixStartLevel] org.apache.sling.event Service 
[org.apache.sling.event.impl.dea.Dis

[jira] [Commented] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13716155#comment-13716155
 ] 

Oliver Lietz commented on SLING-2789:
-

Thanks, Robert. Can you remove empty trunk/contrib/launchpad/karaf/src from SVN?

> deploying Sling 7-SNAPSHOT on Karaf fails
> -
>
> Key: SLING-2789
> URL: https://issues.apache.org/jira/browse/SLING-2789
> Project: Sling
>  Issue Type: Bug
>  Components: Launchpad
>Affects Versions: Launchpad Builder 7
> Environment: Karaf 3.0.0.*
>Reporter: Oliver Lietz
>Assignee: Carsten Ziegeler
> Attachments: SLING-2789.2013-06-04.patch, 
> SLING-2789.2013-07-17.patch, SLING-2789.patch, sling-launchpad-karaf.tar.gz
>
>
> $ ./apache-karaf-3.0.0-SNAPSHOT/bin/start
> $ ssh -p 8101 karaf@localhost
> karaf@root()> feature:install http
> karaf@root()> feature:install webconsole
> karaf@root()> feature:repo-add 
> mvn:org.apache.sling/org.apache.sling.launchpad/7-SNAPSHOT/xml/features
> karaf@root()> feature:install sling
> no errors on startup but JCR is nearly empty
> to prevent errors:
> - add missing org.apache.sling/org.apache.sling.launchpad.api/1.1.0 to 
> features.xml
> - remove org.apache.felix/org.apache.felix.webconsole.plugins.* from 
> features.xml
> - remove management from featuresBoot in org.apache.karaf.features.cfg or 
> remove org.apache.aries.* from features.xml
> setting respectStartLvlDuringFeatureStartup=true and ds.factory.enabled=true 
> does not help

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Build failed in Jenkins: sling-trunk-1.7 #127

[Apache Jenkins Server]

See 

Changes:

[cziegeler] Correct queue type, ignore was missing in the list

[cziegeler] Improve log message

--
[...truncated 5158 lines...]
[INFO] Apache Sling JCR Resource Resolver  SKIPPED
[INFO] Apache Sling JCR Repository Registration .. SKIPPED
[INFO] Apache Sling Simple WebDAV Access to repositories . SKIPPED
[INFO] Apache Sling DavEx Access to repositories . SKIPPED
[INFO] Apache Sling JCR WebConsole Bundle  SKIPPED
[INFO] Apache Sling Servlet Resolver . SKIPPED
[INFO] Apache Sling Default GET Servlets . SKIPPED
[INFO] Apache Sling Default POST Servlets  SKIPPED
[INFO] Apache Sling Compat Servlets .. SKIPPED
[INFO] Apache Sling Scripting Implementation API . SKIPPED
[INFO] Apache Sling Scripting Core implementation  SKIPPED
[INFO] Apache Sling Scripting JavaScript Support . SKIPPED
[INFO] Apache Sling Scripting JSP Support  SKIPPED
[INFO] Apache Sling JSP Tag Library .. SKIPPED
[INFO] Apache Sling JSP Standard Tag Library . SKIPPED
[INFO] Apache Sling Adapter Manager Implementation ... SKIPPED
[INFO] Apache Sling Bundle Resource Provider . SKIPPED
[INFO] Apache Sling Discovery API  SKIPPED
[INFO] Apache Sling Resource-Based Discovery Service . SKIPPED
[INFO] Apache Sling Discovery Support Bundle . SKIPPED
[INFO] Apache Sling Discovery Standalone Implementation .. SKIPPED
[INFO] Apache Sling Event Support  SKIPPED
[INFO] Apache Sling Filesystem Resource Provider . SKIPPED
[INFO] Apache Sling javax.activation bundle .. SKIPPED
[INFO] Apache Sling Settings . SKIPPED
[INFO] Apache Sling Thread Dumper  SKIPPED
[INFO] Apache Sling Web Console Branding . SKIPPED
[INFO] Apache Sling Web Console Security Provider  SKIPPED
[INFO] Apache Sling Groovy Extensions  SKIPPED
[INFO] Apache Sling Explorer . SKIPPED
[INFO] Apache Sling Test Tools ... SKIPPED
[INFO] Apache Sling JUnit Core ... SKIPPED
[INFO] Apache Sling JUnit Scriptable Tests Provider .. SKIPPED
[INFO] Apache Sling JUnit Remote Tests Runners ... SKIPPED
[INFO] Apache Sling Testing Resource Resolver Mock ... SKIPPED
[INFO] Apache Sling Installer  SKIPPED
[INFO] Apache Sling Installer WebConsole Plugin .. SKIPPED
[INFO] Apache Sling File Installer ... SKIPPED
[INFO] Apache Sling JCR Installer  SKIPPED
[INFO] Apache Sling Installer Configuration Admin Support  SKIPPED
[INFO] Apache Sling Deployment Package Installer . SKIPPED
[INFO] Apache Sling Installer Integration Tests .. SKIPPED
[INFO] Apache Sling Launchpad API  SKIPPED
[INFO] Apache Sling Launchpad Base ... SKIPPED
[INFO] Apache Sling Launchpad Installer .. SKIPPED
[INFO] Apache Sling Launchpad Content  SKIPPED
[INFO] Apache Sling Launchpad Application Builder  SKIPPED
[INFO] Apache Sling Sample Server-Side Tests . SKIPPED
[INFO] Apache Sling Failing Server-Side Tests  SKIPPED
[INFO] Apache Sling Sample Integration Tests . SKIPPED
[INFO] Apache Sling Launchpad Testing Services ... SKIPPED
[INFO] Apache Sling Launchpad Testing Services WAR ... SKIPPED
[INFO] Apache Sling Launchpad Testing Fragment Bundle  SKIPPED
[INFO] Apache Sling Launchpad Test Bundles ... SKIPPED
[INFO] Apache Sling Integration Tests  SKIPPED
[INFO] Apache Sling Launchpad Testing  SKIPPED
[INFO] Apache Sling Launchpad Testing WAR version  SKIPPED
[INFO] Apache Sling (Builder)  SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 3:26.934s
[INFO] Finished at: Tue Jul 23 06:20:50 UTC 2013
[INFO] Final Memory: 134M/343M
[INFO] 
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKI

Build failed in Jenkins: sling-trunk-1.7 » Apache Sling Testing Utilities #127

[Apache Jenkins Server]

See 


--
[INFO] 
[INFO] 
[INFO] Building Apache Sling Testing Utilities 2.0.15-SNAPSHOT
[INFO] 
[INFO] [INFO] Deleting 


[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
org.apache.sling.commons.testing ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce-java) @ 
org.apache.sling.commons.testing ---
[INFO] [INFO] Executing tasks

main:
[INFO] Executed tasks

[INFO] --- maven-antrun-plugin:1.7:run 
(set-bundle-required-execution-environment) @ org.apache.sling.commons.testing 
---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.4:process (default) @ 
org.apache.sling.commons.testing ---
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] Copying 3 resources

[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
org.apache.sling.commons.testing ---
[INFO] [INFO] Executing tasks

main:
 [echo]  WARNING (SLING-443/SLING-1782) 
**
 [echo] On most platforms, you'll get OutOfMemoryErrors when building 
unless you set
 [echo] on 32bit platforms: MAVEN_OPTS="-Xmx256M -XX:MaxPermSize=256M", see 
SLING-443
 [echo] on 64bit platforms: MAVEN_OPTS="-Xmx512M -XX:MaxPermSize=512M", see 
SLING-1782
 [echo] 
**
[INFO] Executed tasks

[INFO] --- maven-antrun-plugin:1.7:run (check-memory-task) @ 
org.apache.sling.commons.testing ---
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
org.apache.sling.commons.testing ---
[INFO] Compiling 30 source files to 

[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources

[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
org.apache.sling.commons.testing ---
[INFO] [INFO] Compiling 5 source files to 


[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
org.apache.sling.commons.testing ---
[INFO] [INFO] Surefire report directory: 


---
 T E S T S
---

[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ 
org.apache.sling.commons.testing ---
Running org.apache.sling.commons.testing.jcr.RepositoryTestBaseTest
191 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - Starting 
repository...
196 [main] INFO org.apache.jackrabbit.core.fs.local.LocalFileSystem - 
LocalFileSystem initialized at path 

382 [main] INFO org.apache.jackrabbit.core.nodetype.NodeTypeRegistry - no 
custom node type definitions found
392 [main] INFO org.apache.jackrabbit.core.fs.local.LocalFileSystem - 
LocalFileSystem initialized at path 

10868 [main] INFO org.apache.jackrabbit.core.RepositoryImpl - initializing 
workspace 'default'...
10869 [main] INFO org.apache.jackrabbit.core.fs.local.LocalFileSystem - 
LocalFileSystem initialized at path 

17250 [main] INFO org.apache.jackrabbit.core.query.lucene.MultiIndex - 
indexing... /jcr:system/jcr:nodeTypes/rep:Activities/jcr:childNodeDefinition 
(100)
17424 [main] INFO org.apache.jackrabbit.core.query.lucene.SearchIndex - Index 
initialized: 

 Version: 3
17609 [main] INFO org.apache.jackrabbit.core.query.lucene.SearchIndex - Index 
initialized: 

 Version: 3
17609 [main] INFO org.apache.j

[jira] [Created] (SLING-2976) Add support for instance name and description

[Carsten Ziegeler (JIRA)]

Carsten Ziegeler created SLING-2976:
---

 Summary: Add support for instance name and description
 Key: SLING-2976
 URL: https://issues.apache.org/jira/browse/SLING-2976
 Project: Sling
  Issue Type: Improvement
  Components: Extensions
Affects Versions: Extensions Settings 1.2.2
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
 Fix For: Extensions Settings 1.2.4


With the introduction of the topology API, we added support for two framework 
properties sling.name and sling.description. Right now, these values need 
either be set as system properties or in the sling.properties file.
There are two issues with these:
- we don't have any default values
- they are not changeable at run time

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Build failed in Jenkins: sling-trunk-1.7 #126

[Apache Jenkins Server]

See 

Changes:

[rombert] SLING-2789 - deploying Sling 7-SNAPSHOT on Karaf fails

Applied SLING-2789.2013-07-17.patch from Oliver Lietz:

* corrected various documentation and legal files
* use a released version of the karaf-maven-plugin
* resync the karaf feature list with the launchpad
* remove unneeded dependency on org.apache.karaf.tooling.exam.options

--
[...truncated 10404 lines...]
22.07.2013 21:20:36.940 *INFO* [FelixStartLevel] derby BundleEvent STARTING
22.07.2013 21:20:37.092 *INFO* [FelixStartLevel] derby BundleEvent STARTED
22.07.2013 21:20:37.100 *INFO* [FelixStartLevel] 
org.apache.sling.jcr.jackrabbit.server BundleEvent RESOLVED
22.07.2013 21:20:37.100 *INFO* [FelixStartLevel] 
org.apache.sling.jcr.jackrabbit.server BundleEvent STARTING
22.07.2013 21:20:37.131 *INFO* [FelixStartLevel] 
org.apache.sling.jcr.jackrabbit.server.impl.Activator Creating default config 
for Jackrabbit in jackrabbit
22.07.2013 21:20:37.145 *INFO* [FelixStartLevel] 
org.apache.sling.jcr.jackrabbit.server.impl.Activator verifyConfiguration: 
Created configuration 
org.apache.sling.jcr.jackrabbit.server.SlingServerRepository.b4de208c-f81c-4c5b-a9d1-e248af069b5f
 for org.apache.sling.jcr.jackrabbit.server.SlingServerRepository
22.07.2013 21:20:37.246 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core.RepositoryImpl Starting repository...
22.07.2013 21:20:37.248 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core.fs.local.LocalFileSystem LocalFileSystem initialized 
at path 

22.07.2013 21:20:37.366 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core.nodetype.NodeTypeRegistry no custom node type 
definitions found
22.07.2013 21:20:37.396 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core.fs.local.LocalFileSystem LocalFileSystem initialized 
at path 

22.07.2013 21:20:39.561 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core.RepositoryImpl initializing workspace 'default'...
22.07.2013 21:20:39.561 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core.fs.local.LocalFileSystem LocalFileSystem initialized 
at path 

22.07.2013 21:20:40.708 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core.query.lucene.MultiIndex indexing... 
/jcr:system/jcr:nodeTypes/rep:Activities/jcr:childNodeDefinition (100)
22.07.2013 21:20:41.089 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core.query.lucene.SearchIndex Index initialized: 

 Version: 3
22.07.2013 21:20:41.216 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core.query.lucene.SearchIndex Index initialized: 

 Version: 3
22.07.2013 21:20:41.216 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core.RepositoryImpl workspace 'default' initialized
22.07.2013 21:20:41.220 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core.RepositoryImpl created system workspace: security
22.07.2013 21:20:41.224 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core.RepositoryImpl SecurityManager = class 
org.apache.jackrabbit.core.DefaultSecurityManager
22.07.2013 21:20:41.224 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core.RepositoryImpl initializing workspace 'security'...
22.07.2013 21:20:41.224 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core.fs.local.LocalFileSystem LocalFileSystem initialized 
at path 

22.07.2013 21:20:41.636 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core.query.lucene.SearchIndex Index initialized: 

 Version: 3
22.07.2013 21:20:41.636 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core.RepositoryImpl workspace 'security' initialized
22.07.2013 21:20:41.637 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core.DefaultSecurityManager init: use Repository 
Login-Configuration for Jackrabbit
22.07.2013 21:20:41.655 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core.security.user.UserManagerImpl Admin user does not 
exist.
22.07.2013 21:20:41.813 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core.security.user.UserManagerImpl ... created admin user 
with id 'admin' and default pw.
22.07.2013 21:20:41.846 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core.DefaultSecurityManager ... created anonymous user 
with id 'anonymous' ...
22.07.2013 21:20:41.851 *INFO* [FelixStartLevel] 
org.apache.jackrabbit.core

[jira] [Commented] (SLING-2973) [Tooling] Align Eclipse tooling to proposed structure

[Robert Munteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715651#comment-13715651
 ] 

Robert Munteanu commented on SLING-2973:


* Added a basic Filter API + impl in 
http://svn.apache.org/viewvc?view=revision&revision=1505809
* OSGi service and tracing cleanup in 
http://svn.apache.org/viewvc?view=revision&revision=1505810
* Hooked in filters when importing content in 
http://svn.apache.org/viewvc?view=revision&revision=1505811

> [Tooling] Align Eclipse tooling to proposed structure
> -
>
> Key: SLING-2973
> URL: https://issues.apache.org/jira/browse/SLING-2973
> Project: Sling
>  Issue Type: Sub-task
>  Components: Extensions
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>
> The current IDE tooling needs to be aligned to the structure defined at [1] . 
> We should be careful to preserve existing behaviour, but regressions in the 
> short run are acceptable since we will move to the WST framework, which is a 
> different beast altogether.
> [1]: https://cwiki.apache.org/confluence/display/SLING/Sling+IDE+tooling

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails

[Robert Munteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715595#comment-13715595
 ] 

Robert Munteanu commented on SLING-2789:


Patch applied in http://svn.apache.org/viewvc?view=revision&revision=1505793 .

> deploying Sling 7-SNAPSHOT on Karaf fails
> -
>
> Key: SLING-2789
> URL: https://issues.apache.org/jira/browse/SLING-2789
> Project: Sling
>  Issue Type: Bug
>  Components: Launchpad
>Affects Versions: Launchpad Builder 7
> Environment: Karaf 3.0.0.*
>Reporter: Oliver Lietz
>Assignee: Carsten Ziegeler
> Attachments: SLING-2789.2013-06-04.patch, 
> SLING-2789.2013-07-17.patch, SLING-2789.patch, sling-launchpad-karaf.tar.gz
>
>
> $ ./apache-karaf-3.0.0-SNAPSHOT/bin/start
> $ ssh -p 8101 karaf@localhost
> karaf@root()> feature:install http
> karaf@root()> feature:install webconsole
> karaf@root()> feature:repo-add 
> mvn:org.apache.sling/org.apache.sling.launchpad/7-SNAPSHOT/xml/features
> karaf@root()> feature:install sling
> no errors on startup but JCR is nearly empty
> to prevent errors:
> - add missing org.apache.sling/org.apache.sling.launchpad.api/1.1.0 to 
> features.xml
> - remove org.apache.felix/org.apache.felix.webconsole.plugins.* from 
> features.xml
> - remove management from featuresBoot in org.apache.karaf.features.cfg or 
> remove org.apache.aries.* from features.xml
> setting respectStartLvlDuringFeatureStartup=true and ds.factory.enabled=true 
> does not help

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[GSoc2013 Dishara] Readme

[Ian Boston]

Hi Dishara,

Could you add a README.txt at the same level as the pom.xml to tell someone
what they need to do to build the project. I see its missing and you
obviously need to have setup a cassandra server.

It doesn't need to be targeted at a novice user, just enough information to
allow someone who knows what they are doing to set up the environment.

eg: (this is just and example of what the readme might contain)
"
Setup:
1. You will need to be running a cassandra instance of verison x.x or later
on port 3045, see [1] for details
2. Run ./tools/populate.sh to populate cassandra with sample data.

1 [link to cassandra quick start]
"

Thanks

Best Regards
Ian

Jenkins build is back to stable : sling-trunk-1.6 #1755

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Installer Integration Tests #1755

[Apache Jenkins Server]

See 

[jira] [Commented] (SLING-2968) DiscoveryServiceImpl can make HTTP calls before Sling is properly started up

[Carsten Ziegeler (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715221#comment-13715221
 ] 

Carsten Ziegeler commented on SLING-2968:
-

+1, makes sense

> DiscoveryServiceImpl can make HTTP calls before Sling is properly started up
> 
>
> Key: SLING-2968
> URL: https://issues.apache.org/jira/browse/SLING-2968
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Robert Munteanu
>Assignee: Stefan Egli
>Priority: Minor
>
> If the DiscoveryServiceImpl starts up before the application is completely 
> initalized, the first requests fail:
> {code}03.07.2013 14:24:43.821 *ERROR* [127.0.0.1 [1372850683817] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 503
> 03.07.2013 14:24:43.908 *ERROR* [127.0.0.1 [1372850683908] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 503
> 03.07.2013 14:24:43.996 *ERROR* [127.0.0.1 [1372850683996] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 503
> 03.07.2013 14:24:44.258 *ERROR* [127.0.0.1 [1372850684258] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 
> 503{code}
> The solution would be to call the initialization code from inside a 
> {{StartupListener}}, rather than on component activation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2968) DiscoveryServiceImpl can make HTTP calls before Sling is properly started up

[Stefan Egli (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715201#comment-13715201
 ] 

Stefan Egli commented on SLING-2968:


The suggested solution is to delay the DiscoveryServiceImpl's activate() until 
the StartupListener.startupFinished() has been called. 

This would imply that TOPOLOGY_INIT would also be delayed until the startup has 
been finished. Which might not be a bad idea anyway..

> DiscoveryServiceImpl can make HTTP calls before Sling is properly started up
> 
>
> Key: SLING-2968
> URL: https://issues.apache.org/jira/browse/SLING-2968
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Robert Munteanu
>Assignee: Stefan Egli
>Priority: Minor
>
> If the DiscoveryServiceImpl starts up before the application is completely 
> initalized, the first requests fail:
> {code}03.07.2013 14:24:43.821 *ERROR* [127.0.0.1 [1372850683817] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 503
> 03.07.2013 14:24:43.908 *ERROR* [127.0.0.1 [1372850683908] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 503
> 03.07.2013 14:24:43.996 *ERROR* [127.0.0.1 [1372850683996] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 503
> 03.07.2013 14:24:44.258 *ERROR* [127.0.0.1 [1372850684258] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 
> 503{code}
> The solution would be to call the initialization code from inside a 
> {{StartupListener}}, rather than on component activation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2968) DiscoveryServiceImpl can make HTTP calls before Sling is properly started up

[Stefan Egli (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715219#comment-13715219
 ] 

Stefan Egli commented on SLING-2968:


the main issue is with topology connectors (those that connect two clusters via 
http): those caused the above reported errors when run too early. 

what we could distinguish easiest is to do local heartbeats (inside the 
cluster) right from activate() onwards, the remote once only after startup..

> DiscoveryServiceImpl can make HTTP calls before Sling is properly started up
> 
>
> Key: SLING-2968
> URL: https://issues.apache.org/jira/browse/SLING-2968
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Robert Munteanu
>Assignee: Stefan Egli
>Priority: Minor
>
> If the DiscoveryServiceImpl starts up before the application is completely 
> initalized, the first requests fail:
> {code}03.07.2013 14:24:43.821 *ERROR* [127.0.0.1 [1372850683817] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 503
> 03.07.2013 14:24:43.908 *ERROR* [127.0.0.1 [1372850683908] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 503
> 03.07.2013 14:24:43.996 *ERROR* [127.0.0.1 [1372850683996] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 503
> 03.07.2013 14:24:44.258 *ERROR* [127.0.0.1 [1372850684258] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 
> 503{code}
> The solution would be to call the initialization code from inside a 
> {{StartupListener}}, rather than on component activation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2968) DiscoveryServiceImpl can make HTTP calls before Sling is properly started up

[Carsten Ziegeler (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715213#comment-13715213
 ] 

Carsten Ziegeler commented on SLING-2968:
-

It would be nice if we could come up with a better solution :) startupFinished 
should mark that the instance is ready and can be used - for this, some 
topology should already be established as some services might be based on the 
availability of a topology. So we should try to do this as soon as possible. 
The topology can change after startupFinished of course

> DiscoveryServiceImpl can make HTTP calls before Sling is properly started up
> 
>
> Key: SLING-2968
> URL: https://issues.apache.org/jira/browse/SLING-2968
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Robert Munteanu
>Assignee: Stefan Egli
>Priority: Minor
>
> If the DiscoveryServiceImpl starts up before the application is completely 
> initalized, the first requests fail:
> {code}03.07.2013 14:24:43.821 *ERROR* [127.0.0.1 [1372850683817] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 503
> 03.07.2013 14:24:43.908 *ERROR* [127.0.0.1 [1372850683908] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 503
> 03.07.2013 14:24:43.996 *ERROR* [127.0.0.1 [1372850683996] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 503
> 03.07.2013 14:24:44.258 *ERROR* [127.0.0.1 [1372850684258] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 
> 503{code}
> The solution would be to call the initialization code from inside a 
> {{StartupListener}}, rather than on component activation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Jenkins build is still unstable: sling-trunk-1.6 #1754

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Installer Integration Tests #1754

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #1754

[Apache Jenkins Server]

See 

[jira] [Commented] (SLING-1778) Symlinks

[Stefan Seifert (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715198#comment-13715198
 ] 

Stefan Seifert commented on SLING-1778:
---

no, there is really no magic in this sling symlink feature concerning advanced 
features like jcr queries or observation because the JCR does not "know" 
anything of the symlink.
you have to handle this via code manually. but we added some public methods to 
the OSGI service managing the symlink to query the symlinks that are active 
currently, so you can check for search or observation hits if a symlink mapping 
exists for them in your code.

> Symlinks
> 
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Reporter: Julian Sedding
> Attachments: 130704_symlinks-0.0.4.patch, symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes 
> in the JCR repository. A symlink node has a sling:symlinkTarget property, 
> which should contain a valid JCR path. JCR content from the 
> sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property 
> sling:symlinkTarget and an optional property sling:overlayable. Additionally, 
> there is a convenience node type, sling:SymlinkResource, which extends from 
> sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the 
> bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle 
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Jenkins build is back to stable : sling-trunk-1.7 #124

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #124

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Installer Integration Tests #124

[Apache Jenkins Server]

See 

[jira] [Commented] (SLING-1778) Symlinks

[Dragos Dascalita Haut (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715195#comment-13715195
 ] 

Dragos Dascalita Haut commented on SLING-1778:
--

Sounds cool Stefan, thanks for making it clear. Did you notice any impact in 
the JCR query if symlinks nodes are involved in the query ? Can people query 
symlink nodes transparently (w/o knowing it's actually a symlink) ? 

> Symlinks
> 
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Reporter: Julian Sedding
> Attachments: 130704_symlinks-0.0.4.patch, symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes 
> in the JCR repository. A symlink node has a sling:symlinkTarget property, 
> which should contain a valid JCR path. JCR content from the 
> sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property 
> sling:symlinkTarget and an optional property sling:overlayable. Additionally, 
> there is a convenience node type, sling:SymlinkResource, which extends from 
> sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the 
> bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle 
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715193#comment-13715193
 ] 

Oliver Lietz commented on SLING-2789:
-

Yes, it's a reminder. They are not on Maven Central yet (but in Launchpads' 
list.xml) and I want to keep the number of SNAPSHOT bundles as low a possible.

> deploying Sling 7-SNAPSHOT on Karaf fails
> -
>
> Key: SLING-2789
> URL: https://issues.apache.org/jira/browse/SLING-2789
> Project: Sling
>  Issue Type: Bug
>  Components: Launchpad
>Affects Versions: Launchpad Builder 7
> Environment: Karaf 3.0.0.*
>Reporter: Oliver Lietz
>Assignee: Carsten Ziegeler
> Attachments: SLING-2789.2013-06-04.patch, 
> SLING-2789.2013-07-17.patch, SLING-2789.patch, sling-launchpad-karaf.tar.gz
>
>
> $ ./apache-karaf-3.0.0-SNAPSHOT/bin/start
> $ ssh -p 8101 karaf@localhost
> karaf@root()> feature:install http
> karaf@root()> feature:install webconsole
> karaf@root()> feature:repo-add 
> mvn:org.apache.sling/org.apache.sling.launchpad/7-SNAPSHOT/xml/features
> karaf@root()> feature:install sling
> no errors on startup but JCR is nearly empty
> to prevent errors:
> - add missing org.apache.sling/org.apache.sling.launchpad.api/1.1.0 to 
> features.xml
> - remove org.apache.felix/org.apache.felix.webconsole.plugins.* from 
> features.xml
> - remove management from featuresBoot in org.apache.karaf.features.cfg or 
> remove org.apache.aries.* from features.xml
> setting respectStartLvlDuringFeatureStartup=true and ds.factory.enabled=true 
> does not help

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails

[Robert Munteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715176#comment-13715176
 ] 

Robert Munteanu commented on SLING-2789:


The patch adds the discovery bundles but has them commented out. Is that 
intended?

> deploying Sling 7-SNAPSHOT on Karaf fails
> -
>
> Key: SLING-2789
> URL: https://issues.apache.org/jira/browse/SLING-2789
> Project: Sling
>  Issue Type: Bug
>  Components: Launchpad
>Affects Versions: Launchpad Builder 7
> Environment: Karaf 3.0.0.*
>Reporter: Oliver Lietz
>Assignee: Carsten Ziegeler
> Attachments: SLING-2789.2013-06-04.patch, 
> SLING-2789.2013-07-17.patch, SLING-2789.patch, sling-launchpad-karaf.tar.gz
>
>
> $ ./apache-karaf-3.0.0-SNAPSHOT/bin/start
> $ ssh -p 8101 karaf@localhost
> karaf@root()> feature:install http
> karaf@root()> feature:install webconsole
> karaf@root()> feature:repo-add 
> mvn:org.apache.sling/org.apache.sling.launchpad/7-SNAPSHOT/xml/features
> karaf@root()> feature:install sling
> no errors on startup but JCR is nearly empty
> to prevent errors:
> - add missing org.apache.sling/org.apache.sling.launchpad.api/1.1.0 to 
> features.xml
> - remove org.apache.felix/org.apache.felix.webconsole.plugins.* from 
> features.xml
> - remove management from featuresBoot in org.apache.karaf.features.cfg or 
> remove org.apache.aries.* from features.xml
> setting respectStartLvlDuringFeatureStartup=true and ds.factory.enabled=true 
> does not help

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Jenkins build is unstable: sling-trunk-1.7 #123

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Sample Integration Tests #123

[Apache Jenkins Server]

See 

Jenkins build is back to normal : sling-trunk-1.7 » Apache Sling Launchpad Testing #123

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Installer Integration Tests #123

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #123

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.6 #1753

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Sample Integration Tests #1753

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #1753

[Apache Jenkins Server]

See 

[jira] [Resolved] (SLING-2967) Make topology connectors independent from machine clocks differences

[Stefan Egli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Egli resolved SLING-2967.


Resolution: Fixed

fixed by resetting the created time of a topology announcement before 
persisting it.

persisting a topology announcement happens on both side of a topology 
connector. the 'created' field contained the origin's local machine time. this 
caused issues when the clocks are not in sync. the fix is to redefine 'created' 
as 'receive-time', thus always working with local times only

> Make topology connectors independent from machine clocks differences
> 
>
> Key: SLING-2967
> URL: https://issues.apache.org/jira/browse/SLING-2967
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
>
> In a setup where two machines use discovery.impl to connect the topology 
> between each other - and the two machines's clock have a considerable 
> difference, say 1min - the discovery.impl rejects the incoming announcement, 
> treating it as 'expired'.
> While in theory it is reasonable to assume that server clocks in data centers 
> run fairly in-sync, it is still safer to avoid any dependency on the accuracy 
> of clocks.
> The topology connector should not be dependent on those clocks and not pass 
> times as part of the announcement-json - but rather stamp incoming 
> announcements with local clocks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (SLING-2955) Unnecessary errors "TopologyViewImpl addInstance: cannot add same instance twice"

[Stefan Egli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Egli resolved SLING-2955.


Resolution: Fixed

log.error lowered to info

> Unnecessary errors "TopologyViewImpl addInstance: cannot add same instance 
> twice"
> -
>
> Key: SLING-2955
> URL: https://issues.apache.org/jira/browse/SLING-2955
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
>
> Apparently, adding/removing/adding/removing of instances to/from the cluster 
> cause the following unnecessary (and scary) error - while everything works 
> fine:
> 08.07.2013 17:09:36.513 *ERROR* [Apche Sling JCR Resource Event Queue 
> Processor for path '/'] 
> org.apache.sling.discovery.impl.topology.TopologyViewImpl addInstance: cannot 
> add same instance twice: an 
> InstanceDescription[slindId=23c62a57-2505-410a-9329-7a7f72bdffb4, 
> isLeader=true, isOwn=false, 
> clusterViewId=9249b4de-c6ae-4810-a107-efca0d024a7c, 
> properties={com.adobe.granite.offloading.infrastructure.osgiconsole.path=/system/console,
>  job.consumermanager.whitelist=*, 
> org.apache.sling.instance.endpoints=http://./,http://./}]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (SLING-2962) Increase default heartbeat timeout

[Stefan Egli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Egli resolved SLING-2962.


Resolution: Fixed

increased default heartbeat timeout to 45s (3x interval)

> Increase default heartbeat timeout
> --
>
> Key: SLING-2962
> URL: https://issues.apache.org/jira/browse/SLING-2962
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
>
> The default heartbeat timeout is currently set to 20s - while the interval is 
> 15s. This seems to be too short for load scenarios. Increasing to 30s or 45s 
> seems reasonable.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-1778) Symlinks

[Stefan Seifert (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715109#comment-13715109
 ] 

Stefan Seifert commented on SLING-1778:
---

this symlinks feature is implemented within the sling resource resolver 
infrastructure and can be applied to any resources, not only to JCR resources.
the symlink concept is related but not similar to the shared node concept in 
JCR. the major differences are:
* for JCR shared nodes there is no "master node", but a node can have multiple 
parents which have "equal rights". the symlink concept always has a master tree 
which is referenced by the symlink nodes. this usually matches better to a 
scenario where a dedicated team of editors is responsible for maintaining the 
master tree, while others are responsible only for the inherited tree and are 
not allowed to touch the master tree.
* it is not possible to do things like "overlays" for some subtrees with JCR 
shared nodes, it is always exactly the same subtree that is linked to multiple 
parents. this is possible with this symlink patch (although it has some 
limitations, e.g. no control about the ordering of nodes that are added only in 
a inherited subtree)
* the JCR specification leaves open several details for the implementation of 
the JCR repository, e.g. how to handle observation, JCR queries etc. 
Additionally the shared nodes feature seems to be rarely used and is not 
supported by all JCR-based CMS systems (e.g. Adobe CQ)

> Symlinks
> 
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Reporter: Julian Sedding
> Attachments: 130704_symlinks-0.0.4.patch, symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes 
> in the JCR repository. A symlink node has a sling:symlinkTarget property, 
> which should contain a valid JCR path. JCR content from the 
> sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property 
> sling:symlinkTarget and an optional property sling:overlayable. Additionally, 
> there is a convenience node type, sling:SymlinkResource, which extends from 
> sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the 
> bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle 
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Build failed in Jenkins: sling-trunk-1.7 #122

[Apache Jenkins Server]

See 

Changes:

[rombert] SLING-2929 - Wasted work in ClassDescriptor.validate()

Optimize ClassDescriptor.validate() - applied patch ffrom Adrian Nistor.

--
[...truncated 28498 lines...]
[INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [2.760s]
[INFO] Apache Sling Object Content Mapping ... SUCCESS [7.893s]
[INFO] Apache Sling JCR Resource Resolver  SUCCESS [1:28.043s]
[INFO] Apache Sling JCR Repository Registration .. SUCCESS [5.152s]
[INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [4.733s]
[INFO] Apache Sling DavEx Access to repositories . SUCCESS [5.960s]
[INFO] Apache Sling JCR WebConsole Bundle  SUCCESS [3.336s]
[INFO] Apache Sling Servlet Resolver . SUCCESS [4.636s]
[INFO] Apache Sling Default GET Servlets . SUCCESS [5.318s]
[INFO] Apache Sling Default POST Servlets  SUCCESS [5.185s]
[INFO] Apache Sling Compat Servlets .. SUCCESS [2.692s]
[INFO] Apache Sling Scripting Implementation API . SUCCESS [2.677s]
[INFO] Apache Sling Scripting Core implementation  SUCCESS [4.984s]
[INFO] Apache Sling Scripting JavaScript Support . SUCCESS [22.503s]
[INFO] Apache Sling Scripting JSP Support  SUCCESS [8.735s]
[INFO] Apache Sling JSP Tag Library .. SUCCESS [6.291s]
[INFO] Apache Sling JSP Standard Tag Library . SUCCESS [3.343s]
[INFO] Apache Sling Adapter Manager Implementation ... SUCCESS [3.906s]
[INFO] Apache Sling Bundle Resource Provider . SUCCESS [2.752s]
[INFO] Apache Sling Discovery API  SUCCESS [2.900s]
[INFO] Apache Sling Resource-Based Discovery Service . SUCCESS [2:34.705s]
[INFO] Apache Sling Discovery Support Bundle . SUCCESS [3.685s]
[INFO] Apache Sling Discovery Standalone Implementation .. SUCCESS [4.407s]
[INFO] Apache Sling Event Support  SUCCESS [6:57.799s]
[INFO] Apache Sling Filesystem Resource Provider . SUCCESS [2.999s]
[INFO] Apache Sling javax.activation bundle .. SUCCESS [2.837s]
[INFO] Apache Sling Settings . SUCCESS [3.164s]
[INFO] Apache Sling Thread Dumper  SUCCESS [2.987s]
[INFO] Apache Sling Web Console Branding . SUCCESS [2.405s]
[INFO] Apache Sling Web Console Security Provider  SUCCESS [4.597s]
[INFO] Apache Sling Groovy Extensions  SUCCESS [3.066s]
[INFO] Apache Sling Explorer . SUCCESS [2.472s]
[INFO] Apache Sling Test Tools ... SUCCESS [3.576s]
[INFO] Apache Sling JUnit Core ... SUCCESS [3.900s]
[INFO] Apache Sling JUnit Scriptable Tests Provider .. SUCCESS [3.287s]
[INFO] Apache Sling JUnit Remote Tests Runners ... SUCCESS [2.762s]
[INFO] Apache Sling Testing Resource Resolver Mock ... SUCCESS [3.323s]
[INFO] Apache Sling Installer  SUCCESS [6.898s]
[INFO] Apache Sling Installer WebConsole Plugin .. SUCCESS [3.105s]
[INFO] Apache Sling File Installer ... SUCCESS [2.524s]
[INFO] Apache Sling JCR Installer  SUCCESS [2:13.866s]
[INFO] Apache Sling Installer Configuration Admin Support  SUCCESS [3.130s]
[INFO] Apache Sling Deployment Package Installer . SUCCESS [3.422s]
[INFO] Apache Sling Installer Integration Tests .. SUCCESS [41.639s]
[INFO] Apache Sling Launchpad API  SUCCESS [3.056s]
[INFO] Apache Sling Launchpad Base ... SUCCESS [9.278s]
[INFO] Apache Sling Launchpad Installer .. SUCCESS [2.507s]
[INFO] Apache Sling Launchpad Content  SUCCESS [3.172s]
[INFO] Apache Sling Launchpad Application Builder  SUCCESS [27.103s]
[INFO] Apache Sling Sample Server-Side Tests . SUCCESS [6.197s]
[INFO] Apache Sling Failing Server-Side Tests  SUCCESS [2.723s]
[INFO] Apache Sling Sample Integration Tests . SUCCESS [56.066s]
[INFO] Apache Sling Launchpad Testing Services ... SUCCESS [5.216s]
[INFO] Apache Sling Launchpad Testing Services WAR ... SUCCESS [3.069s]
[INFO] Apache Sling Launchpad Testing Fragment Bundle  SUCCESS [2.619s]
[INFO] Apache Sling Launchpad Test Bundles ... SUCCESS [3.467s]
[INFO] Apache Sling Integration Tests  SUCCESS [7.920s]
[INFO] Apache Sling Launchpad Testing  FAILURE [3:49.344s]
[INFO] Apache Sling Launchpad Testing WAR version  SKIPPED
[INFO] Apache Sling (Builder)  SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] --

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Sample Integration Tests #122

[Apache Jenkins Server]

See 

Build failed in Jenkins: sling-trunk-1.7 » Apache Sling Launchpad Testing #122

[Apache Jenkins Server]

See 


--
[...truncated 789 lines...]
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.GetStarTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.ForwardTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.LaunchpadConfigInstallerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Tests run: 506, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 179.453 sec 
<<< FAILURE!
testRecentRequestsEscape(org.apache.sling.launchpad.webapp.integrationtest.issues.SLING2085Test)
  Time elapsed: 0.096 sec  <<< FAILURE!
junit.framework.AssertionFailedError: Expected status 200 for 
http://localhost:43647/system/console/requests?index=1 (content=


404 No resource found


No resource found (404)
The requested URL /system/console/requests resulted in an error in 
org.apache.sling.servlets.resolver.internal.defaults.DefaultErrorHandlerServlet.
Request Progress:

  0 (2013-07-22 10:01:19) TIMER_START{Request Processing}
  0 (2013-07-22 10:01:19) COMMENT timer_end format is {,} 
  0 (2013-07-22 10:01:19) LOG Method=GET, PathInfo=/system/console/requests
  0 (2013-07-22 10:01:19) TIMER_START{ResourceResolution}
  2 (2013-07-22 10:01:19) TIMER_END{2,ResourceResolution} 
URI=/system/console/requests resolves to Resource=NonExistingResource, 
path=/system/console/requests
  2 (2013-07-22 10:01:19) LOG Resource Path Info: SlingRequestPathInfo: 
path='/system/console/requests', selectorString='null', extension='null', 
suffix='null'
  2 (2013-07-22 10:01:19) TIMER_START{ServletResolution}
  2 (2013-07-22 10:01:19) TIMER_START{resolveServlet(NonExistingResource, 
path=/system/console/requests)}
  4 (2013-07-22 10:01:19) TIMER_END{2,resolveServlet(NonExistingResource, 
path=/system/console/requests)} Using servlet 
org.apache.sling.servlets.get.DefaultGetServlet
  4 (2013-07-22 10:01:19) TIMER_END{2,ServletResolution} 
URI=/system/console/requests handled by 
Servlet=org.apache.sling.servlets.get.DefaultGetServlet
  4 (2013-07-22 10:01:19) LOG Applying Requestfilters
  4 (2013-07-22 10:01:19) LOG Calling filter: 
org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter
  4 (2013-07-22 10:01:19) LOG Calling filter: 
org.apache.sling.launchpad.testservices.filters.SlingFilter
  4 (2013-07-22 10:01:19) LOG Calling filter: 
org.apache.sling.launchpad.testservices.filters.NoPropertyFilter
  4 (2013-07-22 10:01:19) 
TIMER_START{org.apache.sling.servlets.get.DefaultGetServlet#0}
  4 (2013-07-22 10:01:19) 
TIMER_END{0,org.apache.sling.servlets.get.DefaultGetServlet#0}
  4 (2013-07-22 10:01:19) TIMER_START{handleError:status=404}
  6 (2013-07-22 10:01:19) TIMER_END{2,handleError:status=404} Using handler 
org.apache.sling.servlets.resolver.internal.defaults.DefaultErrorHandlerServlet
  7 (2013-07-22 10:01:19) TIMER_END{7,Request Processing} Dumping 
SlingRequestProgressTracker Entries


ApacheSling/2.2 (jetty/6.1.x, Java HotSpot(TM) 64-Bit Server VM 
1.7.0_04, Linux 3.2.0-35-generic amd64)


) expected:<200> but was:<404>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:277)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:195)
at 
org.apache.sling.commons.testing.integration.HttpTestBase.getContent(HttpTestBase.java:380)
at 
org.apache.sling.commons.testing.integration.HttpTestBase.getContent(HttpTestBase.java:355)
at 
org.apache.sling.commons.testing.integration.HttpTestBase.getContent(HttpTestBase.java:347)
at 
org.apache.sling.commons.testing.integration.HttpTestBase.getContent(HttpTestBase.java:342)
at 
org.apache.sling.launchpad.webapp.integrationtest.issues.SLING2085Test.testRecentRequestsEscape(SLING2085Test.java:40)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.r

Jenkins build became unstable: sling-trunk-1.6 #1752

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Sample Integration Tests #1752

[Apache Jenkins Server]

See 

[jira] [Commented] (SLING-1778) Symlinks

[Dragos Dascalita Haut (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715045#comment-13715045
 ] 

Dragos Dascalita Haut commented on SLING-1778:
--

Maybe I'm not following correctly, but this issue made me wonder wether it 
tries to solve the same problem already solved by JCR with Shareable Nodes: 
http://www.day.com/specs/jcr/2.0/14_Shareable_Nodes.html
Aren't shareable nodes working in the same way ?

> Symlinks
> 
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Reporter: Julian Sedding
> Attachments: 130704_symlinks-0.0.4.patch, symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes 
> in the JCR repository. A symlink node has a sling:symlinkTarget property, 
> which should contain a valid JCR path. JCR content from the 
> sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property 
> sling:symlinkTarget and an optional property sling:overlayable. Additionally, 
> there is a convenience node type, sling:SymlinkResource, which extends from 
> sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the 
> bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle 
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2924) Full text extraction issue with Tika v1.0 under OSGi environment

[Robert Munteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715013#comment-13715013
 ] 

Robert Munteanu commented on SLING-2924:


You're perfectly right, that's a much better solution. I've looked at the Tika 
bundles and at version 1.4 they don't provide the metadata we need.

I suggest you file a bug against Tika for this and if they agree file a bug 
here so that we can consume the fix.

> Full text extraction issue with Tika v1.0 under OSGi environment
> 
>
> Key: SLING-2924
> URL: https://issues.apache.org/jira/browse/SLING-2924
> Project: Sling
>  Issue Type: Bug
>  Components: Launchpad
>Reporter: Anjan
>Assignee: Robert Munteanu
>  Labels: tika,text-extraction
> Fix For: Launchpad Builder 7
>
>
> The latest stable build (I checked out revision 1487628) of Sling is using 
> Jackrabbit version 2.4.2 and it uses Tika version 1.0 for extracting 
> metatdata and text for indexing purpose.  Jackrabbit v2.4.2 deployed as a 
> separate web application extracts metadata and text from the uploaded 
> documents perfectly fine, but when deployed in Sling (OSGi environment), full 
> text extraction doesn't work.
> Updating the Tika dependency to Version 1.2 in Sling resolved the above issue.
> Secondly, if the indexes are deleted from the repository and the server is 
> restarted, indexes are not rebuilt for the existing documents.  The Tika 
> bundles were not ready by the time Jackrabbit starts to rebuild the indexes 
> during the Sling server start up.  Updating the startlevel from 15 to 10 for 
> the Tika bundles helps to resolve the issue.
> The changes related to above fixes are in 
> /launchpad/builder/src/main/bundles/list.xml file.
> Currently Tika bundles are at start level 15 as shown below:
> 
> ..
> 
> org.apache.tika
> tika-core
> 1.0
> 
> 
> org.apache.tika
> tika-bundle
> 1.0
> 
> ..
> 
> Moved the above bundles to start level 10 and also the version is changed to 
> 1.2
> 
> ..
> 
> org.apache.tika
> tika-core
> 1.2
> 
> 
> org.apache.tika
> tika-bundle
> 1.2
> 
> ..
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [Status Update] Apache Cassandra backend for Sling

[Ian Boston]

Hi Dishara,

The Unit test coverage sounds great. I will pull the code and review today.


Have you tried loading the bundle into a running Sling instance ?

Once you have built it you can load in 2 ways:

method A

mvn clean install sling:install

The sling:install will post the Jar into the OSGi container over HTTP and
cause it to start.


method B

Goto http://localhost:8080/system/console

select the bundle tab and install the bundle by uploading.

If you monitor the logs you should see no errors, the bundle should
register and you should be able to map cassandra read only to somewhere in
the resource tree.

Best Regards
Ian


On 21 July 2013 13:08, Dishara Wijewardana  wrote:

> On Sun, Jul 21, 2013 at 5:32 PM, Dishara Wijewardana <
> ddwijeward...@gmail.com> wrote:
>
> >
> >
> > On Fri, Jul 19, 2013 at 2:35 PM, Ian Boston  wrote:
> >
> >> Hi,
> >>
> >>
> >> On 19 July 2013 03:20, Dishara Wijewardana 
> >> wrote:
> >>
> >> > Hi Ian
> >> > This is regarding the sub tasks completion  of the project according
> to
> >> the
> >> > time line.
> >> >
> >> > I have my code locally, but yet to do some completion with some
> >> stuff(one
> >> > of them is the ongoing discussion on listChildren).
> >> > After that from API point of view implementation around Cassandra
> >> Resource
> >> > Provider and Resource will be finish. And I have to add some more
> JUnit
> >> > tests(have local code in to some extent already, will commit them once
> >> all
> >> > done around this).
> >> >
> >> > So after that (after mid term)  what I have to do is  enhance the
> >> provider
> >> > implementation  to  do READ operations with access control. My idea is
> >> to
> >> > finish that also before the mid term. I was kind of got stuck in some
> >> OSGi
> >> > stuff last days ;-).  And I will make sure I will have JUnit tests to
> >> cover
> >> > all the implementations before the midterm.
> >> >
> >>
> >> Yes that is fine.
> >> Before adding ACLs I would like to have the code running inside Sling,
> >> inside OSGi connected to a Cassandra instance so that we can do some
> basic
> >> tests over http using Curl.
> >>
> >> Perhaps you are there already? Let me know when you are ready and I'll
> >> give
> >> it a go ?
> >>
> >
> > Hi Ian,
> > That is great and +1. In fact now the code is there and I have completed,
> > rest of the implementation on normal READ and commited.
> >
> > I have added 3 more tests to cover the core implementation.  The tests
> are
> > running which covers add/read nodes, list children,iterate/iterable
> > children and get parent related stuff.
> >
>
> Correction . It should be 4 more tests. Now we have 5 tests all together
> which covers above aspects. We should write more test around Cassandra
> Resource. Will work on that as well.
>
> Please let me know if any issues come across when you run this in the sling
> container. Excited to see whether it works in there :-).
>
>
> > And I have made the changes you mentioned. So now resources will not get
> > loaded unless we do a API call with the resource.
> >
> >
> >>
> >>
> >> > If you would like this approach (or unless please provide your
> feedback
> >> on
> >> > what needs to be done before midterm), please advice me on how to
> >> approach
> >> > on READ with access control. Can I do it and test it with keeping my
> >> code
> >> > in Google Code still ?  And please add if I have missed anything.
> >> >
> >> > On Thu, Jul 4, 2013 at 11:13 PM, Dishara Wijewardana <
> >> > ddwijeward...@gmail.com> wrote:
> >> >
> >> > > Hi Ian,
> >> > > I have refactored almost all the code review changes requested. In
> the
> >> > > process of the rest of the implementation.
> >> > >
> >> > > On Wed, Jul 3, 2013 at 12:52 PM, Bertrand Delacretaz <
> >> > > bdelacre...@apache.org> wrote:
> >> > >
> >> > >> Hi Dishara,
> >> > >>
> >> > >> On Tue, Jul 2, 2013 at 6:51 PM, Dishara Wijewardana
> >> > >>  wrote:
> >> > >> > ...Does each bundle in sling made to run their junit tests
> >> separately
> >> > >> at build
> >> > >> > time...
> >> > >>
> >> > >> Could you start new threads with new subject lines when you start a
> >> > >> new question or discussion?
> >> > >>
> >> > >> Otherwise it's very hard to find things in our mailing list
> archives.
> >> > >>
> >> > >> OK. That's a good idea. I will follow that.
> >> > >
> >> > >
> >> > >> Thanks, and keep up the good work!
> >> > >> -Bertrand
> >> > >>
> >> > >
> >> > >
> >> > >
> >> > > --
> >> > > Thanks
> >> > > /Dishara
> >> > >
> >> >
> >> >
> >> >
> >> > --
> >> > Thanks
> >> > /Dishara
> >> >
> >>
> >
> >
> >
> > --
> > Thanks
> > /Dishara
> >
>
>
>
> --
> Thanks
> /Dishara
>

[jira] [Resolved] (SLING-2929) Wasted work in ClassDescriptor.validate()

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved SLING-2929.


   Resolution: Fixed
Fix Version/s: Maven JCROCM Plugin 2.0.6

Patch applied in http://svn.apache.org/viewvc?view=revision&revision=1505618 , 
thanks!

> Wasted work in ClassDescriptor.validate()
> -
>
> Key: SLING-2929
> URL: https://issues.apache.org/jira/browse/SLING-2929
> Project: Sling
>  Issue Type: Bug
>  Components: Maven Plugins and Archetypes
> Environment: any
>Reporter: Adrian Nistor
>Assignee: Robert Munteanu
>  Labels: patch, perfomance
> Fix For: Maven JCROCM Plugin 2.0.6
>
> Attachments: patch.diff
>
>
> The problem appears in revision 1495454.  I attached a one-line patch
> that fixes it.
> In method "ClassDescriptor.validate", the loop over "children" should
> break immediately after "valid" becomes "false".  All the iterations
> after "valid" becomes "false" do not perform any useful work, at best
> they just set "valid" again to "false".
> Method "isLive" in class "ResourceResolverContext" has a similar loop
> (over "dynamicProviders"), and this loop breaks immediately after
> "result" is set to "false", just like in the proposed patch.  Other
> methods (e.g., "FactoryPreconditions.checkPreconditions",
> "JspUtil.checkAttributes", "EclipseJavaCompiler.compile",
> "SecondPassVisitor.appendPageDirective") also have similar loops with
> similar breaks, just like in the proposed patch.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2929) Wasted work in ClassDescriptor.validate()

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-2929:
---

Assignee: Robert Munteanu

> Wasted work in ClassDescriptor.validate()
> -
>
> Key: SLING-2929
> URL: https://issues.apache.org/jira/browse/SLING-2929
> Project: Sling
>  Issue Type: Bug
>  Components: Maven Plugins and Archetypes
> Environment: any
>Reporter: Adrian Nistor
>Assignee: Robert Munteanu
>  Labels: patch, perfomance
> Attachments: patch.diff
>
>
> The problem appears in revision 1495454.  I attached a one-line patch
> that fixes it.
> In method "ClassDescriptor.validate", the loop over "children" should
> break immediately after "valid" becomes "false".  All the iterations
> after "valid" becomes "false" do not perform any useful work, at best
> they just set "valid" again to "false".
> Method "isLive" in class "ResourceResolverContext" has a similar loop
> (over "dynamicProviders"), and this loop breaks immediately after
> "result" is set to "false", just like in the proposed patch.  Other
> methods (e.g., "FactoryPreconditions.checkPreconditions",
> "JspUtil.checkAttributes", "EclipseJavaCompiler.compile",
> "SecondPassVisitor.appendPageDirective") also have similar loops with
> similar breaks, just like in the proposed patch.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira