[jira] [Created] (SLING-2971) BackgroundLoader thread dies for invalid paths

2013-07-17 Thread Chetan Mehrotra (JIRA) 
Chetan Mehrotra created SLING-2971:
--

 Summary: BackgroundLoader thread dies for invalid paths
 Key: SLING-2971
 URL: https://issues.apache.org/jira/browse/SLING-2971
 Project: Sling
  Issue Type: Bug
  Components: Extensions
Affects Versions: Extensions Event 3.1.4
Reporter: Chetan Mehrotra
Priority: Minor


BackgroundLoader thread which is used by JobManager to load and process job 
asynchronously dies if any submitted job path is found to be invalid. 

---
14.07.2013 11:14:22.599 *ERROR* [Apache Sling Job Background Loader] 
org.apache.sling.extensions.threaddump.internal.Activator Uncaught exception in 
Thread Thread[Apache Sling Job Background Loader,5,main] 
java.lang.NullPointerException
at 
org.apache.sling.event.impl.jobs.BackgroundLoader.run(BackgroundLoader.java:219)
at java.lang.Thread.run(Thread.java:662)
---

It might not happen in actual scenario always but it would be better if the 
while loop does not end for such cases

--
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-2971) BackgroundLoader thread dies for invalid paths

2013-07-17 Thread Chetan Mehrotra (JIRA) 

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

Chetan Mehrotra updated SLING-2971:
---

Attachment: SLING-2971.patch

Simple patch to check for null resources

 BackgroundLoader thread dies for invalid paths
 --

 Key: SLING-2971
 URL: https://issues.apache.org/jira/browse/SLING-2971
 Project: Sling
  Issue Type: Bug
  Components: Extensions
Affects Versions: Extensions Event 3.1.4
Reporter: Chetan Mehrotra
Priority: Minor
 Attachments: SLING-2971.patch


 BackgroundLoader thread which is used by JobManager to load and process job 
 asynchronously dies if any submitted job path is found to be invalid. 
 ---
 14.07.2013 11:14:22.599 *ERROR* [Apache Sling Job Background Loader] 
 org.apache.sling.extensions.threaddump.internal.Activator Uncaught exception 
 in Thread Thread[Apache Sling Job Background Loader,5,main] 
 java.lang.NullPointerException
   at 
 org.apache.sling.event.impl.jobs.BackgroundLoader.run(BackgroundLoader.java:219)
   at java.lang.Thread.run(Thread.java:662)
 ---
 It might not happen in actual scenario always but it would be better if the 
 while loop does not end for such cases

--
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-2971) BackgroundLoader thread dies for invalid paths

2013-07-17 Thread Carsten Ziegeler (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710812#comment-13710812
 ] 

Carsten Ziegeler commented on SLING-2971:
-

Can you provide more information when this might happen? (I'm not against 
applying the patch, but I would like to know the root cause)

 BackgroundLoader thread dies for invalid paths
 --

 Key: SLING-2971
 URL: https://issues.apache.org/jira/browse/SLING-2971
 Project: Sling
  Issue Type: Bug
  Components: Extensions
Affects Versions: Extensions Event 3.1.4
Reporter: Chetan Mehrotra
Priority: Minor
 Attachments: SLING-2971.patch


 BackgroundLoader thread which is used by JobManager to load and process job 
 asynchronously dies if any submitted job path is found to be invalid. 
 ---
 14.07.2013 11:14:22.599 *ERROR* [Apache Sling Job Background Loader] 
 org.apache.sling.extensions.threaddump.internal.Activator Uncaught exception 
 in Thread Thread[Apache Sling Job Background Loader,5,main] 
 java.lang.NullPointerException
   at 
 org.apache.sling.event.impl.jobs.BackgroundLoader.run(BackgroundLoader.java:219)
   at java.lang.Thread.run(Thread.java:662)
 ---
 It might not happen in actual scenario always but it would be better if the 
 while loop does not end for such cases

--
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] [Assigned] (SLING-2971) BackgroundLoader thread dies for invalid paths

2013-07-17 Thread Carsten Ziegeler (JIRA) 

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

Carsten Ziegeler reassigned SLING-2971:
---

Assignee: Carsten Ziegeler

 BackgroundLoader thread dies for invalid paths
 --

 Key: SLING-2971
 URL: https://issues.apache.org/jira/browse/SLING-2971
 Project: Sling
  Issue Type: Bug
  Components: Extensions
Affects Versions: Extensions Event 3.1.4
Reporter: Chetan Mehrotra
Assignee: Carsten Ziegeler
Priority: Minor
 Attachments: SLING-2971.patch


 BackgroundLoader thread which is used by JobManager to load and process job 
 asynchronously dies if any submitted job path is found to be invalid. 
 ---
 14.07.2013 11:14:22.599 *ERROR* [Apache Sling Job Background Loader] 
 org.apache.sling.extensions.threaddump.internal.Activator Uncaught exception 
 in Thread Thread[Apache Sling Job Background Loader,5,main] 
 java.lang.NullPointerException
   at 
 org.apache.sling.event.impl.jobs.BackgroundLoader.run(BackgroundLoader.java:219)
   at java.lang.Thread.run(Thread.java:662)
 ---
 It might not happen in actual scenario always but it would be better if the 
 while loop does not end for such cases

--
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-2971) BackgroundLoader thread dies for invalid paths

2013-07-17 Thread Carsten Ziegeler (JIRA) 

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

Carsten Ziegeler updated SLING-2971:


Affects Version/s: (was: Extensions Event 3.1.4)

 BackgroundLoader thread dies for invalid paths
 --

 Key: SLING-2971
 URL: https://issues.apache.org/jira/browse/SLING-2971
 Project: Sling
  Issue Type: Bug
  Components: Extensions
Reporter: Chetan Mehrotra
Assignee: Carsten Ziegeler
Priority: Minor
 Attachments: SLING-2971.patch


 BackgroundLoader thread which is used by JobManager to load and process job 
 asynchronously dies if any submitted job path is found to be invalid. 
 ---
 14.07.2013 11:14:22.599 *ERROR* [Apache Sling Job Background Loader] 
 org.apache.sling.extensions.threaddump.internal.Activator Uncaught exception 
 in Thread Thread[Apache Sling Job Background Loader,5,main] 
 java.lang.NullPointerException
   at 
 org.apache.sling.event.impl.jobs.BackgroundLoader.run(BackgroundLoader.java:219)
   at java.lang.Thread.run(Thread.java:662)
 ---
 It might not happen in actual scenario always but it would be better if the 
 while loop does not end for such cases

--
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-2971) BackgroundLoader thread dies for invalid paths

2013-07-17 Thread Carsten Ziegeler (JIRA) 

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

Carsten Ziegeler updated SLING-2971:


Fix Version/s: Extensions Event 3.2.0

 BackgroundLoader thread dies for invalid paths
 --

 Key: SLING-2971
 URL: https://issues.apache.org/jira/browse/SLING-2971
 Project: Sling
  Issue Type: Bug
  Components: Extensions
Reporter: Chetan Mehrotra
Assignee: Carsten Ziegeler
Priority: Minor
 Fix For: Extensions Event 3.2.0

 Attachments: SLING-2971.patch


 BackgroundLoader thread which is used by JobManager to load and process job 
 asynchronously dies if any submitted job path is found to be invalid. 
 ---
 14.07.2013 11:14:22.599 *ERROR* [Apache Sling Job Background Loader] 
 org.apache.sling.extensions.threaddump.internal.Activator Uncaught exception 
 in Thread Thread[Apache Sling Job Background Loader,5,main] 
 java.lang.NullPointerException
   at 
 org.apache.sling.event.impl.jobs.BackgroundLoader.run(BackgroundLoader.java:219)
   at java.lang.Thread.run(Thread.java:662)
 ---
 It might not happen in actual scenario always but it would be better if the 
 while loop does not end for such cases

--
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] [Created] (SLING-2972) Improve processing performance if job is processed locally

2013-07-17 Thread Carsten Ziegeler (JIRA) 
Carsten Ziegeler created SLING-2972:
---

 Summary: Improve processing performance if job is processed locally
 Key: SLING-2972
 URL: https://issues.apache.org/jira/browse/SLING-2972
 Project: Sling
  Issue Type: Improvement
  Components: Extensions
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
 Fix For: Extensions Event 3.2.0


Currently the job processing is completely observation based: even if a job is 
added locally and also processed locally, this is not immediately put into the 
queue. This creates an unnecessary delay between adding a job and processing it 
which can easily be avoided by directly putting the job into the queue.

--
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] [Assigned] (SLING-2923) release org.apache.sling.jcr.jackrabbit.server 2.1.1

2013-07-17 Thread Robert Munteanu (JIRA) 

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

Robert Munteanu reassigned SLING-2923:
--

Assignee: Robert Munteanu

 release org.apache.sling.jcr.jackrabbit.server 2.1.1
 

 Key: SLING-2923
 URL: https://issues.apache.org/jira/browse/SLING-2923
 Project: Sling
  Issue Type: Task
  Components: JCR
Affects Versions: JCR Jackrabbit Server 2.1.0
 Environment: Apache Karaf 3.0.0.RC1
Reporter: Oliver Lietz
Assignee: Robert Munteanu
 Attachments: karaf.log.5, org.apache.sling.jcr.jackrabbit.server.log


 There are problems with Tika and org.apache.sling.jcr.jackrabbit.server 
 (Caused by: java.lang.ClassNotFoundException: 
 org.apache.tika.parser.xml.DcXMLParser not found by org.apache.tika.core) on 
 Karaf which seem to be solved with 2.1.1-SNAPSHOT. Release 2.1.1-SNAPSHOT as 
 2.1.1.

--
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: [VOTE] New Module Releases

2013-07-17 Thread Daniel Klco 
+1


On Tue, Jul 16, 2013 at 11:15 AM, Carsten Ziegeler cziege...@apache.orgwrote:

 Anyone else?


 2013/7/9 Carsten Ziegeler cziege...@apache.org

  Hi,
 
  this vote is about some important bug fix releases.
 
  So please vote for:
  Parent POM 17
  https://issues.apache.org/jira/browse/SLING/fixforversion/12324381
 
  JCR ClassLoader 3.2.0
  https://issues.apache.org/jira/browse/SLING/fixforversion/12324058
 
  Commons FileSystem ClassLoader 1.0.0
  First Release
 
  Servlets Post 2.3.2
  https://issues.apache.org/jira/browse/SLING/fixforversion/12324380
 
  I18n 2.2.6
  https://issues.apache.org/jira/browse/SLING/fixforversion/12323577
 
  Discovery API 1.0.0
  First Release
 
  Staging repository:
  https://repository.apache.org/content/repositories/orgapachesling-119/
 
 
  You can use this UNIX script to download the release and verify the
  signatures:
  http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
 
  Usage:
  sh check_staged_release.sh 119 /tmp/sling-staging
 
 
  Please vote to approve this release:
 
   [ ] +1 Approve the release
   [ ]  0 Don't care
   [ ] -1 Don't release, because ...
 
  This vote will be open for 72 hours.
 
  Regards
 
  --
  Carsten Ziegeler
  cziege...@apache.org
 



 --
 Carsten Ziegeler
 cziege...@apache.org

[jira] [Commented] (SLING-2923) release org.apache.sling.jcr.jackrabbit.server 2.1.1

2013-07-17 Thread Robert Munteanu (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710827#comment-13710827
 ] 

Robert Munteanu commented on SLING-2923:


I'm trying to build this myself and try it on Karaf in order to understand what 
the problem is here. I'm following the README ( I've previously run mvn clean 
install in contrib/launchpad/karaf ) . However, when I try to add the feature 
url to Karaf it always fails:

karaf@root features:addUrl 
mvn:org.apache.sling/org.apache.sling.launchpad.karaf/0.1.0.BUILD-SNAPSHOT/xml/features
Error executing command: Unable to add repositories:
URL 
[mvn:org.apache.sling/org.apache.sling.launchpad.karaf/0.1.0.BUILD-SNAPSHOT/xml/features]
 could not be resolved.
karaf@root features:addUrl 
mvn:org.apache.sling/org.apache.sling.launchpad.karaf/1.0.0-SNAPSHOT/xml/features
Error executing command: Unable to add repositories:
URL 
[mvn:org.apache.sling/org.apache.sling.launchpad.karaf/1.0.0-SNAPSHOT/xml/features]
 could not be resolved.

How do you install the feature in Karaf?

 release org.apache.sling.jcr.jackrabbit.server 2.1.1
 

 Key: SLING-2923
 URL: https://issues.apache.org/jira/browse/SLING-2923
 Project: Sling
  Issue Type: Task
  Components: JCR
Affects Versions: JCR Jackrabbit Server 2.1.0
 Environment: Apache Karaf 3.0.0.RC1
Reporter: Oliver Lietz
Assignee: Robert Munteanu
 Attachments: karaf.log.5, org.apache.sling.jcr.jackrabbit.server.log


 There are problems with Tika and org.apache.sling.jcr.jackrabbit.server 
 (Caused by: java.lang.ClassNotFoundException: 
 org.apache.tika.parser.xml.DcXMLParser not found by org.apache.tika.core) on 
 Karaf which seem to be solved with 2.1.1-SNAPSHOT. Release 2.1.1-SNAPSHOT as 
 2.1.1.

--
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-2971) BackgroundLoader thread dies for invalid paths

2013-07-17 Thread Chetan Mehrotra (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710837#comment-13710837
 ] 

Chetan Mehrotra commented on SLING-2971:


Its coming while trying to run Sling based app on Oak. I am still looking into 
why the resource is not found for created job ... probably a bug in Oak. 

 BackgroundLoader thread dies for invalid paths
 --

 Key: SLING-2971
 URL: https://issues.apache.org/jira/browse/SLING-2971
 Project: Sling
  Issue Type: Bug
  Components: Extensions
Reporter: Chetan Mehrotra
Assignee: Carsten Ziegeler
Priority: Minor
 Fix For: Extensions Event 3.2.0

 Attachments: SLING-2971.patch


 BackgroundLoader thread which is used by JobManager to load and process job 
 asynchronously dies if any submitted job path is found to be invalid. 
 ---
 14.07.2013 11:14:22.599 *ERROR* [Apache Sling Job Background Loader] 
 org.apache.sling.extensions.threaddump.internal.Activator Uncaught exception 
 in Thread Thread[Apache Sling Job Background Loader,5,main] 
 java.lang.NullPointerException
   at 
 org.apache.sling.event.impl.jobs.BackgroundLoader.run(BackgroundLoader.java:219)
   at java.lang.Thread.run(Thread.java:662)
 ---
 It might not happen in actual scenario always but it would be better if the 
 while loop does not end for such cases

--
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-2971) BackgroundLoader thread dies for invalid paths

2013-07-17 Thread Carsten Ziegeler (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710849#comment-13710849
 ] 

Carsten Ziegeler commented on SLING-2971:
-

Ok, I've committed a fix and leave this open for now

 BackgroundLoader thread dies for invalid paths
 --

 Key: SLING-2971
 URL: https://issues.apache.org/jira/browse/SLING-2971
 Project: Sling
  Issue Type: Bug
  Components: Extensions
Reporter: Chetan Mehrotra
Assignee: Carsten Ziegeler
Priority: Minor
 Fix For: Extensions Event 3.2.0

 Attachments: SLING-2971.patch


 BackgroundLoader thread which is used by JobManager to load and process job 
 asynchronously dies if any submitted job path is found to be invalid. 
 ---
 14.07.2013 11:14:22.599 *ERROR* [Apache Sling Job Background Loader] 
 org.apache.sling.extensions.threaddump.internal.Activator Uncaught exception 
 in Thread Thread[Apache Sling Job Background Loader,5,main] 
 java.lang.NullPointerException
   at 
 org.apache.sling.event.impl.jobs.BackgroundLoader.run(BackgroundLoader.java:219)
   at java.lang.Thread.run(Thread.java:662)
 ---
 It might not happen in actual scenario always but it would be better if the 
 while loop does not end for such cases

--
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.6 #1747

2013-07-17 Thread Apache Jenkins Server 
See https://builds.apache.org/job/sling-trunk-1.6/1747/

--
[...truncated 160 lines...]
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387)
at 
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:157)
at 
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:153)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:903)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:884)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:867)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
Caused by: svn: E175002: OPTIONS /repos/asf/sling/trunk failed
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97)
... 36 more
Caused by: org.tmatesoft.svn.core.SVNAuthenticationException: svn: E170001: 
OPTIONS request failed on '/repos/asf/sling/trunk'
svn: E170001: OPTIONS of '/repos/asf/sling/trunk': 403 Forbidden 
(http://svn.apache.org)
at 
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:62)
at 
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:748)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373)
... 35 more
Caused by: svn: E170001: OPTIONS of '/repos/asf/sling/trunk': 403 Forbidden 
(http://svn.apache.org)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:189)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:141)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.createDefaultErrorMessage(HTTPRequest.java:452)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.dispatch(HTTPRequest.java:189)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:460)
... 36 more
ERROR: Subversion update failed
hudson.util.IOException2: remote file operation failed: 
https://builds.apache.org/job/sling-trunk-1.6/ws/ at 
hudson.remoting.Channel@649c9365:ubuntu1
at hudson.FilePath.act(FilePath.java:861)
at hudson.FilePath.act(FilePath.java:838)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:843)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:781)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1331)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:682)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:587)
at hudson.model.Run.execute(Run.java:1568)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)
Caused by: java.io.IOException
at 
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:207)
at 
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:153)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:903)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:884)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:867)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at

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

2013-07-17 Thread Apache Jenkins Server 
See https://builds.apache.org/job/sling-trunk-1.7/118/

--
[...truncated 160 lines...]
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387)
at 
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:157)
at 
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:153)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:903)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:884)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:867)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
Caused by: svn: E175002: OPTIONS /repos/asf/sling/trunk failed
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97)
... 36 more
Caused by: org.tmatesoft.svn.core.SVNAuthenticationException: svn: E170001: 
OPTIONS request failed on '/repos/asf/sling/trunk'
svn: E170001: OPTIONS of '/repos/asf/sling/trunk': 403 Forbidden 
(http://svn.apache.org)
at 
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:62)
at 
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:748)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373)
... 35 more
Caused by: svn: E170001: OPTIONS of '/repos/asf/sling/trunk': 403 Forbidden 
(http://svn.apache.org)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:189)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:141)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.createDefaultErrorMessage(HTTPRequest.java:452)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.dispatch(HTTPRequest.java:189)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:460)
... 36 more
ERROR: Subversion update failed
hudson.util.IOException2: remote file operation failed: 
https://builds.apache.org/job/sling-trunk-1.7/ws/ at 
hudson.remoting.Channel@649c9365:ubuntu1
at hudson.FilePath.act(FilePath.java:861)
at hudson.FilePath.act(FilePath.java:838)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:843)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:781)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1331)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:682)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:587)
at hudson.model.Run.execute(Run.java:1568)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)
Caused by: java.io.IOException
at 
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:207)
at 
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:153)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:903)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:884)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:867)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at

[jira] [Commented] (SLING-2923) release org.apache.sling.jcr.jackrabbit.server 2.1.1

2013-07-17 Thread Robert Munteanu (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710973#comment-13710973
 ] 

Robert Munteanu commented on SLING-2923:


I've tweaked to integration-tests pom to use more stable dependencies in 
http://svn.apache.org/viewvc?view=revisionrevision=1504075 . I plan to use 
this to verify the functionality, once I find out how to actually run the 
project.

 release org.apache.sling.jcr.jackrabbit.server 2.1.1
 

 Key: SLING-2923
 URL: https://issues.apache.org/jira/browse/SLING-2923
 Project: Sling
  Issue Type: Task
  Components: JCR
Affects Versions: JCR Jackrabbit Server 2.1.0
 Environment: Apache Karaf 3.0.0.RC1
Reporter: Oliver Lietz
Assignee: Robert Munteanu
 Attachments: karaf.log.5, org.apache.sling.jcr.jackrabbit.server.log


 There are problems with Tika and org.apache.sling.jcr.jackrabbit.server 
 (Caused by: java.lang.ClassNotFoundException: 
 org.apache.tika.parser.xml.DcXMLParser not found by org.apache.tika.core) on 
 Karaf which seem to be solved with 2.1.1-SNAPSHOT. Release 2.1.1-SNAPSHOT as 
 2.1.1.

--
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-2923) release org.apache.sling.jcr.jackrabbit.server 2.1.1

2013-07-17 Thread Oliver Lietz (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710996#comment-13710996
 ] 

Oliver Lietz commented on SLING-2923:
-

Please see SLING-2789:

karaf@root() feature:repo-add 
mvn:org.apache.sling/org.apache.sling.launchpad.karaf-features/0.1.0.BUILD-SNAPSHOT/xml/features
 
karaf@root() feature:install sling-karaf


 release org.apache.sling.jcr.jackrabbit.server 2.1.1
 

 Key: SLING-2923
 URL: https://issues.apache.org/jira/browse/SLING-2923
 Project: Sling
  Issue Type: Task
  Components: JCR
Affects Versions: JCR Jackrabbit Server 2.1.0
 Environment: Apache Karaf 3.0.0.RC1
Reporter: Oliver Lietz
Assignee: Robert Munteanu
 Attachments: karaf.log.5, org.apache.sling.jcr.jackrabbit.server.log


 There are problems with Tika and org.apache.sling.jcr.jackrabbit.server 
 (Caused by: java.lang.ClassNotFoundException: 
 org.apache.tika.parser.xml.DcXMLParser not found by org.apache.tika.core) on 
 Karaf which seem to be solved with 2.1.1-SNAPSHOT. Release 2.1.1-SNAPSHOT as 
 2.1.1.

--
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

2013-07-17 Thread Oliver Lietz (JIRA) 

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

Oliver Lietz commented on SLING-2924:
-

Please use Provide-Capability and Require-Capability instead of start levels.

http://wiki.osgi.org/wiki/Provide-Capability
http://wiki.osgi.org/wiki/Require-Capability
http://blog.osgi.org/2012/03/requirements-and-capabilities.html



 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 
 sling/launchpad/builder/src/main/bundles/list.xml file.
 Currently Tika bundles are at start level 15 as shown below:
 startLevel level=15
 ..
 bundle
 groupIdorg.apache.tika/groupId
 artifactIdtika-core/artifactId
 version1.0/version
 /bundle
 bundle
 groupIdorg.apache.tika/groupId
 artifactIdtika-bundle/artifactId
 version1.0/version
 /bundle
 ..
 /startLevel
 Moved the above bundles to start level 10 and also the version is changed to 
 1.2
 startLevel level=10
 ..
 bundle
 groupIdorg.apache.tika/groupId
 artifactIdtika-core/artifactId
 version1.2/version
 /bundle
 bundle
 groupIdorg.apache.tika/groupId
 artifactIdtika-bundle/artifactId
 version1.2/version
 /bundle
 ..
 /startLevel

--
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 became unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing WAR version #1748

2013-07-17 Thread Apache Jenkins Server 
See 
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/1748/

Jenkins build is unstable: sling-trunk-1.6 #1748

2013-07-17 Thread Apache Jenkins Server 
See https://builds.apache.org/job/sling-trunk-1.6/1748/changes

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Launchpad Base #119

2013-07-17 Thread Apache Jenkins Server 
See 
https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.base/119/

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

2013-07-17 Thread Apache Jenkins Server 
See https://builds.apache.org/job/sling-trunk-1.7/119/changes

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

2013-07-17 Thread Robert Munteanu (JIRA) 
Robert Munteanu created SLING-2973:
--

 Summary: [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] [Updated] (SLING-2973) [Tooling] Align Eclipse tooling to proposed structure

2013-07-17 Thread Robert Munteanu (JIRA) 

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

Robert Munteanu updated SLING-2973:
---

Due Date: (was: 17/Jul/13)

 [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

Re: [VOTE] New Module Releases

2013-07-17 Thread Justin Edelson 
+1


On Tue, Jul 16, 2013 at 9:05 PM, Daniel Klco daniel.k...@gmail.com wrote:

 +1


 On Tue, Jul 16, 2013 at 11:15 AM, Carsten Ziegeler cziege...@apache.org
 wrote:

  Anyone else?
 
 
  2013/7/9 Carsten Ziegeler cziege...@apache.org
 
   Hi,
  
   this vote is about some important bug fix releases.
  
   So please vote for:
   Parent POM 17
   https://issues.apache.org/jira/browse/SLING/fixforversion/12324381
  
   JCR ClassLoader 3.2.0
   https://issues.apache.org/jira/browse/SLING/fixforversion/12324058
  
   Commons FileSystem ClassLoader 1.0.0
   First Release
  
   Servlets Post 2.3.2
   https://issues.apache.org/jira/browse/SLING/fixforversion/12324380
  
   I18n 2.2.6
   https://issues.apache.org/jira/browse/SLING/fixforversion/12323577
  
   Discovery API 1.0.0
   First Release
  
   Staging repository:
   https://repository.apache.org/content/repositories/orgapachesling-119/
  
  
   You can use this UNIX script to download the release and verify the
   signatures:
   http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
  
   Usage:
   sh check_staged_release.sh 119 /tmp/sling-staging
  
  
   Please vote to approve this release:
  
[ ] +1 Approve the release
[ ]  0 Don't care
[ ] -1 Don't release, because ...
  
   This vote will be open for 72 hours.
  
   Regards
  
   --
   Carsten Ziegeler
   cziege...@apache.org
  
 
 
 
  --
  Carsten Ziegeler
  cziege...@apache.org

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

2013-07-17 Thread Justin Edelson (JIRA) 

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

Justin Edelson commented on SLING-2973:
---

perhaps I'm being daft, but where is the structure defined in the wiki? 

 [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-2973) [Tooling] Align Eclipse tooling to proposed structure

2013-07-17 Thread Robert Munteanu (JIRA) 

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

Robert Munteanu commented on SLING-2973:


I'm referring to the 'high-level-architecture' section:

- server control
- resource serialization format
- transport api
- transport implementation ( http for now )
- eclipse ( core, ui )

This allows us to easily evolve other transport implementations ( vlt is a good 
candidate ) and also plugin in implementations for intellij which reuse 
existing modules.

 [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] [Updated] (SLING-2789) deploying Sling 7-SNAPSHOT on Karaf fails

2013-07-17 Thread Oliver Lietz (JIRA) 

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

Oliver Lietz updated SLING-2789:


Attachment: SLING-2789.2013-07-17.patch

dependencies, plugins, NOTICE and README.txt updated

 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-2973) [Tooling] Align Eclipse tooling to proposed structure

2013-07-17 Thread Robert Munteanu (JIRA) 

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

Robert Munteanu commented on SLING-2973:


Of course, you're welcome to propose a different project structure. I'm happy 
for input, and it can come even after I've created the initial directories ; 
we'll be moving stuff around a lot in the beginning anyway until we find a good 
structure.

 [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

Re: Does Sling has a Resource Resolver for Cassandra already ?

2013-07-17 Thread Dishara Wijewardana 
On Tue, Jul 16, 2013 at 1:58 PM, Ian Boston i...@tfd.co.uk wrote:

 One further thing.

 For testing, use dummies.

OK. got the point. For testing, currently will keep the dummy resolver
impl. And once this is in the sling ogsi environment, will add this.


 When the Component is started within the Sling OSGi container as a real
 bundle the real ResourceResolver will be injected for you.

 Does that clear up my misunderstanding of what you were asking ?

Yes. Thank you very much for the example.


 Ian


 On 16 July 2013 09:26, Ian Boston i...@tfd.co.uk wrote:

  Hi,
 
  There are 2 options.
 
  You can
  use
  org.apache.sling.testing.resourceresolver.MockResourceResolverFactory
 
  which should allow you to do
  this.factory = new MockResourceResolverFactory();
 
  ...
 
 
  ResourceResolver resolver =
  this.factory.getAdministrativeResourceResolver(null);
 
 
  or
 
 
  you can use Mockito and do
 
  public class ResourceProviderTest {
 
  @Mock
  ResourceResolver mockResourceResolver;
 
 
  public ResourceProviderTest() {
 MockitoAnnotation.initMocks(this);
  }
 
 
 @Test
 public void testSomething() {
Resource mockResource = Mockito.mock(Resource.class);
 
 
 Mockito.when(mockResourceResolver.getResource(/test/path)).thenReturn(mockResource);
 
 }
 
  }
 
 
  I prefer using Mockito as it gives greater control and isolation.
 
  Grep the code base for @Mock to see examples of Mockito usage or read the
  Mockito docs.
 
 
  Does that help ?
 
  Best Regards
  Ian
 
 
 
  On 16 July 2013 08:58, Dishara Wijewardana ddwijeward...@gmail.com
 wrote:
 
  On Tue, Jul 16, 2013 at 1:19 PM, Bertrand Delacretaz 
  bdelacre...@apache.org
   wrote:
 
   Hi,
  
   On Tue, Jul 16, 2013 at 9:34 AM, Dishara Wijewardana
   ddwijeward...@gmail.com wrote:
I was got stuck where to find the resolver (according to  my
understanding). To set the resolver through reflection, I need to
 get
  a
real resolver reference instance
  
   Where exactly do you have that problem?
  
   If you can give us the URL of that problematic code, it would be much
   easier for us to suggest solutions.
  
 
  This is a simple Junit test class[1]. And I cannot figure out what needs
  to
  be done to obtain a existing resource resolver reference due to above
  mentioned complicatoins.
   And there currently I am using a dummy resolver implementation to pass
 to
  the provider to obtain a resource.  As Ian mentioned we should pass an
  existing reference of a resolver. Here is the code that does this.
 
 private void readData(CassandraResourceProvider
  cassandraResourceProvider, String cf) {
  Resource resource = cassandraResourceProvider.getResource(new
  CassandraResourceResolver(), /content/cassandra/ + cf + /foo/bar);
 
  }
 
 
  [1] -
 
 
 https://cassandra-backend-for-sling.googlecode.com/svn/trunk/main/cassandra/src/test/java/org/apache/sling/cassandra/test/data/populator/CassandraDataPopulatorTest.java
 
 
   -Bertrand
  
 
 
 
  --
  Thanks
  /Dishara
 
 
 




-- 
Thanks
/Dishara

What should return for Provider.listChildren() ?

2013-07-17 Thread Dishara Wijewardana 
Hi Ian and all,
I am in the process of completing the rest of the implementation.

I would like to know about what is expected to return  from this method.
CAssandraResourceProvider.listChildren(Resource).
Is it all the children inside the resource path ? (then we have to
recursively search all nodes until the leaf node). Or shouldn't we have a
certain depth to return the results.


-- 
Thanks
/Dishara

Re: What should return for Provider.listChildren() ?

2013-07-17 Thread Ian Boston 
Hi,
listChildren is only supposed to return a list of immediate children (ie no
recursion).

If code using listChildren wants the entire structure is should call
listChildren, using ResourceResolver.listChildren(childResource);

Note, ResourceProvider.listChildren will always be called by the
ResourceResolver and never directly by the client code.

also, listChildren should return a true iterator, where the Resources are
not loaded into memory until they are requested. Usually that means having
some form of query to generate pointers to the list of Resources and as the
iterator.hasNext() and iterator.next() are invoked the iterator loads the
resources into memory. That way, if there are millions of children, code
can retrieve the first 10 without having to wait for 1M to be loaded into a
list.


Best Regards
Ian



On 18 July 2013 01:55, Dishara Wijewardana ddwijeward...@gmail.com wrote:

 Hi Ian and all,
 I am in the process of completing the rest of the implementation.

 I would like to know about what is expected to return  from this method.
 CAssandraResourceProvider.listChildren(Resource).
 Is it all the children inside the resource path ? (then we have to
 recursively search all nodes until the leaf node). Or shouldn't we have a
 certain depth to return the results.


 --
 Thanks
 /Dishara

Re: [VOTE] New Module Releases

2013-07-17 Thread Carsten Ziegeler 
We still need one PMC vote...


2013/7/17 Justin Edelson jus...@justinedelson.com

 +1


 On Tue, Jul 16, 2013 at 9:05 PM, Daniel Klco daniel.k...@gmail.com
 wrote:

  +1
 
 
  On Tue, Jul 16, 2013 at 11:15 AM, Carsten Ziegeler cziege...@apache.org
  wrote:
 
   Anyone else?
  
  
   2013/7/9 Carsten Ziegeler cziege...@apache.org
  
Hi,
   
this vote is about some important bug fix releases.
   
So please vote for:
Parent POM 17
https://issues.apache.org/jira/browse/SLING/fixforversion/12324381
   
JCR ClassLoader 3.2.0
https://issues.apache.org/jira/browse/SLING/fixforversion/12324058
   
Commons FileSystem ClassLoader 1.0.0
First Release
   
Servlets Post 2.3.2
https://issues.apache.org/jira/browse/SLING/fixforversion/12324380
   
I18n 2.2.6
https://issues.apache.org/jira/browse/SLING/fixforversion/12323577
   
Discovery API 1.0.0
First Release
   
Staging repository:
   
 https://repository.apache.org/content/repositories/orgapachesling-119/
   
   
You can use this UNIX script to download the release and verify the
signatures:
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
   
Usage:
sh check_staged_release.sh 119 /tmp/sling-staging
   
   
Please vote to approve this release:
   
 [ ] +1 Approve the release
 [ ]  0 Don't care
 [ ] -1 Don't release, because ...
   
This vote will be open for 72 hours.
   
Regards
   
--
Carsten Ziegeler
cziege...@apache.org
   
  
  
  
   --
   Carsten Ziegeler
   cziege...@apache.org
  
 




-- 
Carsten Ziegeler
cziege...@apache.org