[jira] [Commented] (SLING-2818) ErrorHandlingTest often fails

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-2818:


Indeed, thanks for the stack trace:

java.lang.NullPointerException: Specified service reference cannot be null.
at 
org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:458)
at 
org.apache.sling.jcr.classloader.internal.ClassLoaderWriterImpl.getOrCreateClassLoader(ClassLoaderWriterImpl.java:215)
...

Looks like something causes the DynamicClassLoaderManager that the 
ClassLoaderWriterImpl uses to go away before the test runs.


> ErrorHandlingTest often fails
> -
>
> Key: SLING-2818
> URL: https://issues.apache.org/jira/browse/SLING-2818
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Reporter: Bertrand Delacretaz
>Priority: Minor
> Attachments: error-message.txt
>
>
> At least at https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6 
> the 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolver.errorhandler.ErrorHandlingTest
>  often fails, sometimes for unclear reasons (timing?).
> Recent error messages include
> At ErrorHandlingTest.setUp:
> mkdir(http://localhost:42232/apps/servlets/errorhandler) failed, status 
> code=503
> At ErrorHandlingTest.test_500_errorhandling:
> Error 503 AuthenticationSupport service missing. Cannot authenticate request
> It looks like something (maybe the test's setup itself) causes Sling to go 
> 503 just before the test.
> The test that runs just before is 
> org.apache.sling.launchpad.webapp.integrationtest.CreateNodeTest which 
> shouldn't cause a 503 status.

--
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: Moving discovery modules to bundles?

[Felix Meschberger]

Hi

Having the eventing bundle depend on the discovery bundles is enough of a
reason to move them to bundles. IMHO modules in the "bundles" section
should not depend on modules in the "contrib" section Š

Regards
Felix

--
Felix Meschberger | Principal Scientist | Adobe




On 03.05.13 07:02, "Carsten Ziegeler"  wrote:

>Hi,
>
>I think the new discovery modules are very important, especially for the
>cloud and distributed installations. While they're currently only used in
>the eventing, I see more use cases, for example using them in the
>scheduler
>module (to schedule tasks only on a single instance in the cloud etc.)
>
>So I think we should move them to bundles.
>
>WDYT?
>
>Carsten
>
>-- 
>Carsten Ziegeler
>cziege...@apache.org

Re: SLING-1500: JSP Taglib - Resource Access Tags

[Felix Meschberger]

Sounds good for me.

Regards
Felix




On 02.05.13 17:51, "Daniel Klco"  wrote:

>All,
>
>I would like to propose integrating the enhancements for SLING-1500 (
>https://issues.apache.org/jira/browse/SLING-1500) as well as SLING-2648 (
>https://issues.apache.org/jira/browse/SLING-2648) into the main JSP Taglib
>project and creating a new release of the 1.3 version of the taglib with
>all of the Resource Access Tags and EL Functions.
>
>WDYT?
>
>-Dan

Moving discovery modules to bundles?

[Carsten Ziegeler]

Hi,

I think the new discovery modules are very important, especially for the
cloud and distributed installations. While they're currently only used in
the eventing, I see more use cases, for example using them in the scheduler
module (to schedule tasks only on a single instance in the cloud etc.)

So I think we should move them to bundles.

WDYT?

Carsten

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

[jira] [Updated] (SLING-2818) ErrorHandlingTest often fails

[Robert Munteanu (JIRA)]

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

Robert Munteanu updated SLING-2818:
---

Attachment: error-message.txt

> ErrorHandlingTest often fails
> -
>
> Key: SLING-2818
> URL: https://issues.apache.org/jira/browse/SLING-2818
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Reporter: Bertrand Delacretaz
>Priority: Minor
> Attachments: error-message.txt
>
>
> At least at https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6 
> the 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolver.errorhandler.ErrorHandlingTest
>  often fails, sometimes for unclear reasons (timing?).
> Recent error messages include
> At ErrorHandlingTest.setUp:
> mkdir(http://localhost:42232/apps/servlets/errorhandler) failed, status 
> code=503
> At ErrorHandlingTest.test_500_errorhandling:
> Error 503 AuthenticationSupport service missing. Cannot authenticate request
> It looks like something (maybe the test's setup itself) causes Sling to go 
> 503 just before the test.
> The test that runs just before is 
> org.apache.sling.launchpad.webapp.integrationtest.CreateNodeTest which 
> shouldn't cause a 503 status.

--
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-2818) ErrorHandlingTest often fails

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-2818:


The error seems to be that a JSP can't be compiled due to a missing 
ServiceReference.

> ErrorHandlingTest often fails
> -
>
> Key: SLING-2818
> URL: https://issues.apache.org/jira/browse/SLING-2818
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Reporter: Bertrand Delacretaz
>Priority: Minor
> Attachments: error-message.txt
>
>
> At least at https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6 
> the 
> org.apache.sling.launchpad.webapp.integrationtest.servlets.resolver.errorhandler.ErrorHandlingTest
>  often fails, sometimes for unclear reasons (timing?).
> Recent error messages include
> At ErrorHandlingTest.setUp:
> mkdir(http://localhost:42232/apps/servlets/errorhandler) failed, status 
> code=503
> At ErrorHandlingTest.test_500_errorhandling:
> Error 503 AuthenticationSupport service missing. Cannot authenticate request
> It looks like something (maybe the test's setup itself) causes Sling to go 
> 503 just before the test.
> The test that runs just before is 
> org.apache.sling.launchpad.webapp.integrationtest.CreateNodeTest which 
> shouldn't cause a 503 status.

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

[Apache Jenkins Server]

See 

[jira] [Created] (SLING-2852) Sling Launchpad Testing WAR - ClassCircularityError when executed in a reactor

[Robert Munteanu (JIRA)]

Robert Munteanu created SLING-2852:
--

 Summary: Sling Launchpad Testing WAR - ClassCircularityError when 
executed in a reactor
 Key: SLING-2852
 URL: https://issues.apache.org/jira/browse/SLING-2852
 Project: Sling
  Issue Type: Bug
  Components: Testing
Reporter: Robert Munteanu


The the launchpad/testing-war project is executed as part of a reactor build it 
fails with a CCE. However, when run standalone does have this problem. The 
problem can be seen for instance at 
https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/1640/consoleText
 . I don't know about Java 7 tests since they fail earlier.

2013-05-02 14:04:54.986:INFO:/:sling: Starting Apache Sling in 
/home/jenkins/jenkins-slave/workspace/sling-trunk-1.6/trunk/launchpad/testing-war/target/sling-cargo-test/sling
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.apache.felix.framework.util.SecureAction.invoke(SecureAction.java:840)
at 
org.apache.felix.framework.URLHandlers.getFrameworkFromContext(URLHandlers.java:722)
at 
org.apache.felix.framework.URLHandlersStreamHandlerProxy.getStreamHandlerService(URLHandlersStreamHandlerProxy.java:574)
at 
org.apache.felix.framework.URLHandlersStreamHandlerProxy.parseURL(URLHandlersStreamHandlerProxy.java:369)
at java.net.URL.(URL.java:596)
at java.net.URL.(URL.java:464)
at sun.misc.URLClassPath$JarLoader.checkResource(URLClassPath.java:674)
at sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:759)
at sun.misc.URLClassPath.getResource(URLClassPath.java:169)
at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at 
org.apache.sling.launchpad.base.shared.LauncherClassLoader.loadClass(LauncherClassLoader.java:131)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2436)
at java.lang.Class.getDeclaredMethod(Class.java:1937)
at 
org.apache.sling.launchpad.base.impl.SlingFelix.getBundle(SlingFelix.java:114)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.apache.felix.framework.util.SecureAction.invoke(SecureAction.java:840)
at 
org.apache.felix.framework.URLHandlers.getFrameworkFromContext(URLHandlers.java:722)
at 
org.apache.felix.framework.URLHandlersStreamHandlerProxy.getStreamHandlerService(URLHandlersStreamHandlerProxy.java:574)
at 
org.apache.felix.framework.URLHandlersStreamHandlerProxy.parseURL(URLHandlersStreamHandlerProxy.java:369)
at java.net.URL.(URL.java:596)
at java.net.URL.(URL.java:464)
at sun.misc.URLClassPath$JarLoader.checkResource(URLClassPath.java:674)
at sun.misc.URLClassPath$JarLoader.getResource(URLClassPath.java:759)
at sun.misc.URLClassPath.getResource(URLClassPath.java:169)
at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at 
org.apache.sling.launchpad.base.shared.LauncherClassLoader.loadClass(LauncherClassLoader.java:131)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at 
org.apache.felix.framework.BundleWiringImpl.findResourcesByDelegation(BundleWiringImpl.java:1202)
at 
org.apache.felix.framework.BundleWiringImpl.getResourcesByDelegation(BundleWiringImpl.java:1076)
at 
org.apache.felix.framework.BundleWiringImpl.findResourcesByDelegation(BundleWiringImpl.java:1127)
at 
org.apache.felix.framework.BundleWiringImpl.getResourcesByDelegation(BundleWiringImpl.java:1076)
at 
org.apache.felix.framework.BundleWiringImpl$BundleClassLoaderJava5.getResources(BundleWiringImpl.java:1838)
at 
org.slf4j.LoggerFactory.singleImplementationSanityCheck(LoggerFactory.java:219)
at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:107)
at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:279)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.jav

SLING-1500: JSP Taglib - Resource Access Tags

[Daniel Klco]

All,

I would like to propose integrating the enhancements for SLING-1500 (
https://issues.apache.org/jira/browse/SLING-1500) as well as SLING-2648 (
https://issues.apache.org/jira/browse/SLING-2648) into the main JSP Taglib
project and creating a new release of the 1.3 version of the taglib with
all of the Resource Access Tags and EL Functions.

WDYT?

-Dan

[jira] [Commented] (SLING-920) Jenkins continuous integration setup

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-920:
---

Done for all 4 jobs found under https://builds.apache.org/view/S-Z/view/Sling/

> Jenkins continuous integration setup
> 
>
> Key: SLING-920
> URL: https://issues.apache.org/jira/browse/SLING-920
> Project: Sling
>  Issue Type: Task
>  Components: Testing
>Reporter: Bertrand Delacretaz
>
> Use this issue to record changes to the Hudson continuous environment setup 
> at http://hudson.zones.apache.org/hudson/view/Sling/

--
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-920) Jenkins continuous integration setup

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-920:
---

As discussed on http://sling.markmail.org/thread/qc53zsaia2gsurhi , can someone 
please disable artifact archival for the Sling jobs?

> Jenkins continuous integration setup
> 
>
> Key: SLING-920
> URL: https://issues.apache.org/jira/browse/SLING-920
> Project: Sling
>  Issue Type: Task
>  Components: Testing
>Reporter: Bertrand Delacretaz
>
> Use this issue to record changes to the Hudson continuous environment setup 
> at http://hudson.zones.apache.org/hudson/view/Sling/

--
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-1500) Patch Submission: Expression Language (EL) Functions for JSP Taglib

[Dan Klco (JIRA)]

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

Dan Klco reassigned SLING-1500:
---

Assignee: Dan Klco

> Patch Submission: Expression Language (EL) Functions for JSP Taglib
> ---
>
> Key: SLING-1500
> URL: https://issues.apache.org/jira/browse/SLING-1500
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Affects Versions: Scripting JSP-Taglib 2.0.6
>Reporter: Mark Adamcin
>Assignee: Dan Klco
>Priority: Minor
>  Labels: el, function, jsp, scripting, sling, taglib
> Attachments: add-files.zip, SLING-1500.diff, taglib11.tld.patch
>
>
> I've noticed that the Sling Resource API is not very accessible for tag- and 
> EL-focused JSP development. In order to promote readable JSP code, I created 
> a set of static methods to implement commonly-used ResourceResolver methods 
> as well as to expose the rather useful ResourceUtil methods as EL functions. 
> The functions use ResourceWrappers to work around the isse 
> https://issues.apache.org/jira/browse/SLING-1414 where the Resource.getPath() 
> method is inaccessible in EL for JcrNodeResource objects.
> I've found these taglib functions to be very useful for Day CQ5 development, 
> so I thought I'd offer to contribute them to the project.

--
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: Disabling artifact archival on builds.apache.org?

[Dan Klco]

+1

-Original Message-
From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] 
Sent: Thursday, May 02, 2013 10:51 AM
To: dev@sling.apache.org
Subject: Re: Disabling artifact archival on builds.apache.org?

Hi,

On Thu, May 2, 2013 at 4:46 PM, Robert Munteanu  wrote:
> ...I noticed that while the sling-trunk-1.6 job runs reasonably fast (
> ~30 minutes ) , a lot of time is spent archiving artifacts...

+1 for disabling that, it's very slow and probably not useful.

-Bertrand


-
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.3272 / Virus Database: 3162/6287 - Release Date: 04/30/13

Re: Disabling artifact archival on builds.apache.org?

[Bertrand Delacretaz]

Hi,

On Thu, May 2, 2013 at 4:46 PM, Robert Munteanu  wrote:
> ...I noticed that while the sling-trunk-1.6 job runs reasonably fast (
> ~30 minutes ) , a lot of time is spent archiving artifacts...

+1 for disabling that, it's very slow and probably not useful.

-Bertrand

[jira] [Resolved] (SLING-2689) Document SlingServlet

[Dan Klco (JIRA)]

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

Dan Klco resolved SLING-2689.
-

Resolution: Fixed

This was fixed by [~bdelacretaz] in revision 1453820

> Document SlingServlet
> -
>
> Key: SLING-2689
> URL: https://issues.apache.org/jira/browse/SLING-2689
> Project: Sling
>  Issue Type: Bug
>  Components: Documentation, Servlets, Site
>Reporter: Dan Klco
>Assignee: Dan Klco
>Priority: Trivial
> Attachments: SLING-2689.diff
>
>
> The @SlingServlet annotation should have some documentation on the Sling 
> site, it seems like a better way of registering servlets.

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

Disabling artifact archival on builds.apache.org?

[Robert Munteanu]

Hi,

I noticed that while the sling-trunk-1.6 job runs reasonably fast (
~30 minutes ) , a lot of time is spent archiving artifacts. According
to [1] the Maven execution finished at14:08:54 and artifact archival (
+ emails ) finished at 14:41:59 . That's 33 minutes we can shave off
instantly given that we don't use the archived artifacts.

WDYT?

Robert

Jenkins build is back to normal : sling-trunk-1.6 » Apache Sling Launchpad Testing WAR version #1640

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Event Support #1640

[Apache Jenkins Server]

See 

[jira] [Assigned] (SLING-2689) Document SlingServlet

[Dan Klco (JIRA)]

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

Dan Klco reassigned SLING-2689:
---

Assignee: Dan Klco

> Document SlingServlet
> -
>
> Key: SLING-2689
> URL: https://issues.apache.org/jira/browse/SLING-2689
> Project: Sling
>  Issue Type: Bug
>  Components: Documentation, Servlets, Site
>Reporter: Dan Klco
>Assignee: Dan Klco
>Priority: Trivial
> Attachments: SLING-2689.diff
>
>
> The @SlingServlet annotation should have some documentation on the Sling 
> site, it seems like a better way of registering servlets.

--
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 » Apache Sling Launchpad Testing #1640

[Apache Jenkins Server]

See 

[jira] [Commented] (SLING-2850) launchpad/builder bunde list is missing the discovery bundle

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-2850:


I think it's a good think to move them to bundles. Anyway, we have a bundle 
from 'bundles' depending on a bundle from 'contrib' which doesn't seem right.

Anyway, I tried updating the launchpad to include the discovery bundles and I 
got some SCR XML parsing error and did not have time to investigate. I hope to 
do this a bit later.


> launchpad/builder bunde list is missing the discovery bundle
> 
>
> Key: SLING-2850
> URL: https://issues.apache.org/jira/browse/SLING-2850
> Project: Sling
>  Issue Type: Bug
>  Components: Launchpad
>Reporter: Robert Munteanu
> Fix For: Launchpad Builder 7
>
>
> The latest launchpad/builder bundle fails to start
> 01.05.2013 23:16:52.213 *ERROR* [FelixStartLevel] ERROR: Error starting 
> slinginstall:org.apache.sling.event-3.1.5-SNAPSHOT.jar 
> (org.osgi.framework.BundleException: Unresolved constraint in bundle 
> org.apache.sling.event [40]: Unable to resolve 40.0: missing requirement 
> [40.0] osgi.wiring.package; 
> (&(osgi.wiring.package=org.apache.sling.discovery)(version>=1.0.0)(!(version>=2.0.0
> org.osgi.framework.BundleException: Unresolved constraint in bundle 
> org.apache.sling.event [40]: Unable to resolve 40.0: missing requirement 
> [40.0] osgi.wiring.package; 
> (&(osgi.wiring.package=org.apache.sling.discovery)(version>=1.0.0)(!(version>=2.0.0)))

--
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-2851) Topic Round Robin Queue is not correctly marked for removal

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler resolved SLING-2851.
-

Resolution: Fixed

Fixed in revision 1478359 by reverting the boolean test for the waiting flag.

I've also added a check to see whether a queue is already outdated. This avoids 
outdating a queue more than once

> Topic Round Robin Queue is not correctly marked for removal
> ---
>
> Key: SLING-2851
> URL: https://issues.apache.org/jira/browse/SLING-2851
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Extensions Event 3.1.4
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Extensions Event 3.2.0
>
>
> The canBeMarkedForRemoval() method wrongly checks whether the queue is 
> waiting for a new topic to arrive. If it is waiting, it can be marked for 
> removal

--
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: Time to release Sling 7?

[Bertrand Delacretaz]

On Thu, May 2, 2013 at 2:31 PM, Robert Munteanu  wrote:
> ...I'm having a hard time understanding the build summary from jenkins.
> It shows 12 failed tests but apparently no modules were built ...

Yes, it's behaving in a weird way.

> ...I
> went to 
> https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/17/consoleText
> and searched for 'Failed tests:
> testIgnoreQueue:org.apache.sling.event.it.IgnoreQueueTest' . And I
> found it in the console output

ah yes you're right, sorry, I missed that.
-Bertrand

[jira] [Created] (SLING-2851) Topic Round Robin Queue is not correctly marked for removal

[Carsten Ziegeler (JIRA)]

Carsten Ziegeler created SLING-2851:
---

 Summary: Topic Round Robin Queue is not correctly marked for 
removal
 Key: SLING-2851
 URL: https://issues.apache.org/jira/browse/SLING-2851
 Project: Sling
  Issue Type: Bug
  Components: Extensions
Affects Versions: Extensions Event 3.1.4
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
 Fix For: Extensions Event 3.2.0


The canBeMarkedForRemoval() method wrongly checks whether the queue is waiting 
for a new topic to arrive. If it is waiting, it can be marked for removal

--
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-2848) Event integration tests fail due to unresolvable artifacts

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler commented on SLING-2848:
-

I hope the failure is related to statistics caching inside the job manager. I 
changed the test to wait for a fresh statistics, let's see if this helps

> Event integration tests fail due to unresolvable artifacts
> --
>
> Key: SLING-2848
> URL: https://issues.apache.org/jira/browse/SLING-2848
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Robert Munteanu
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> Similar to issue SLING-2847 , just that this time the error is "Could not 
> find artifact 
> org.apache.sling:org.apache.sling.discovery.api:jar:0.1.0-SNAPSHOT in central 
> (http://repo1.maven.org/maven2/)".

--
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: Time to release Sling 7?

[Robert Munteanu]

On Thu, May 2, 2013 at 3:26 PM, Bertrand Delacretaz
 wrote:
> On Thu, May 2, 2013 at 1:43 PM, Robert Munteanu  wrote:
>> ...For Java 7 I get a hard IT failure with the event
>> bundle
>>
>>testIgnoreQueue:org.apache.sling.event.it.IgnoreQueueTest.testIgnoreQueue:NativeContainer:org.apache.felix.framework.FrameworkFactory@ff7bdb6(org.apache.sling.event.it.IgnoreQueueTest):...
>
> That one passed at
> https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/17/
> AFAICS.
>

I'm having a hard time understanding the build summary from jenkins.
It shows 12 failed tests but apparently no modules were built ... So I
went to 
https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/17/consoleText
and searched for 'Failed tests:
testIgnoreQueue:org.apache.sling.event.it.IgnoreQueueTest' . And I
found it in the console output.

Robert

Re: Time to release Sling 7?

[Bertrand Delacretaz]

On Thu, May 2, 2013 at 1:43 PM, Robert Munteanu  wrote:
> ...For Java 7 I get a hard IT failure with the event
> bundle
>
>testIgnoreQueue:org.apache.sling.event.it.IgnoreQueueTest.testIgnoreQueue:NativeContainer:org.apache.felix.framework.FrameworkFactory@ff7bdb6(org.apache.sling.event.it.IgnoreQueueTest):...

That one passed at
https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/17/
AFAICS.

-Bertrand

Re: GSOC 2013 - Test and Fix Apache Oak Integration with Sling

[Bertrand Delacretaz]

Him

On Thu, May 2, 2013 at 1:08 PM, Marcus Santos  wrote:
> ...I'll focus on the tests now... How can I clone and
> build the project?...

Checkout http://svn.apache.org/repos/asf/sling/trunk/ and run Maven >=
3.0.4 on it.

> ...Can you give me an overview of how the test works on Sling?...

There's unit tests under src/test in many places, and the integration
tests are under
https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/
and run by the sibling "testing" module.

-Bertrand

Re: Time to release Sling 7?

[Robert Munteanu]

> While there cannot be a guarantee, but trunk is expected to work with Java
> 8
>
> (The main problem is the Java API exports from the system package. They
> exist but based on the Java 8 packages and not based on what Java 8
> might/will bring)

I think this is good enough for now.

Robert

Re: Time to release Sling 7?

[Robert Munteanu]

On Thu, May 2, 2013 at 9:57 AM, Bertrand Delacretaz
 wrote:
>
> I have setup a Jenkins build a while ago at
> https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/
> Looks like all tests pass (minus Jenkins weirdnesses) except
> ErrorHandlingTest but that's SLING-2818

I've tried to get the Jenkins jobs to green - that's one prerequisite
for a release IMO. For Java 7 I get a hard IT failure with the event
bundle

- 
testIgnoreQueue:org.apache.sling.event.it.IgnoreQueueTest.testIgnoreQueue:NativeContainer:org.apache.felix.framework.FrameworkFactory@ff7bdb6(org.apache.sling.event.it.IgnoreQueueTest):

But then the job halts. Does it make sense to configure the build to
fail-at-end so we get more information on the Java 7 status? Otherwise
it takes a long time to fix a failure, commit, and then wait 3-4 hours
for another Jenkins build to run.

Robert

--
Sent from my (old) computer

Re: GSOC 2013 - Test and Fix Apache Oak Integration with Sling

[Marcus Santos]

Hi Ian,

Thanks for the news. I'll focus on the tests now... How can I clone and
build the project?
Can you give me an overview of how the test works on Sling?

About my proposal I'm in trouble do write something to the topic "a
detailed description / design document". Can you help me with this? I don't
know where to start..

I have been reading about JCR content repository for now because I never
worked with JCR...

Best regards,
Marcus Santos


2013/5/1 Ian Boston 

> Hi Marcus,
> Good news.
>
> Integration test framework.
> The test integration framework runs an instance of Sling on a reserved
> port. It then makes REST calls to that reserved port testing all aspects of
> Sling over HTTP. There are over 100 tests, I dont know the exact figure.
>
> You will need to:
> Work on the pom.xml [1] so that:
> It starts the standalone Sling instance without errors and then
> runs the tests.
>
> Once that is done, where there are test failures, you will need to
> investigate and fix.
>
> The pom.xml [1], almost works but there is more to do and there will
> certainly be test failures to start with.
>
> There isnt any new Java code to write to make this work, just detailed
> investigation and configuration. You may need to write Java code to fix
> issues that are found once the integration tests are running.
>
> Best Regards
> Ian
>
>
> 1
>
> http://svn.apache.org/repos/asf/sling/whiteboard/ieb/oak/launchpad-testing/pom.xml
>
>
>
> On 2 May 2013 03:46, Marcus Santos  wrote:
>
> > Thanks Ian Boston, actually I'm working on it. I have been reading some
> > tutorials about OSGi and doing some examples.
> >
> > I would like to know more about the integration test framework, what I
> > suppose to do and how...
> >
> > Thanks for helping,
> > Marcus Santos
> >
> >
> > 2013/4/30 Ian Boston 
> >
> > > Dont forget, the deadline for proposals is 3rd May (Probably end of day
> > > PST).
> > >
> > >
> > > On 30 April 2013 10:28, Ian Boston  wrote:
> > >
> > > > Hi,
> > > > I put that one up. The need is genuine, here is some background.
> > > >
> > > > Apache Sling uses a content repository to store its content. You can
> > > think
> > > > of it like a file system but its a lot more sophisticated than that.
> > The
> > > > standard content repository is Apache Jackrabbit. Version 1.x and 2.x
> > of
> > > > Apache Jackrabbit were focused on delivering blisteringly fast read
> > > access
> > > > to content in deep content hierarchies where 99% of the activity was
> > read
> > > > and 1% was write. It does that outstandingly well. Time has moved on,
> > the
> > > > web has become more social and applications typically have higher
> > levels
> > > of
> > > > write acces. Content trees have become more user generated and hence
> > are
> > > > often flatter with few levels and millions of children.
> > > >
> > > > Apache Oak is the next generation of Apache Jackrabbit which aims to
> > > > support much higher levels of write, and much wider flatter
> > > > content hierarchies. It has also been designed to support cloud like
> > > > deployments on NoSQL infrastructure  There is support for storage on
> > > > MongoDB already and other backends are almost certainly possible.
> Where
> > > > Jackrabbit 2.x was capable of being deployed in small clusters, Oak
> > > should
> > > > be suitable for large clusters.
> > > >
> > > > For Apache Sling to use Apache Oak the Apache Jackrabbit server
> > component
> > > > has been replaced with an Apache Oak version. Fortunately all the
> > > projects
> > > > mentioned interact constantly and so the basics of this all work.
> What
> > > > hasn't been done yet is to bring up an Sling instance running on Oak
> > and
> > > > run the 100s of Sling integration tests against that instance. If
> that
> > > can
> > > > be achieved it will create a high level of confidence that Sling will
> > run
> > > > on Oak.
> > > >
> > > > As of today, here is what works:
> > > > An instance of Sling running on Oak that starts up and accepts
> requests
> > > > using Basic http authentication.[1]
> > > > An initial attempt at getting the integration testing framework
> > running,
> > > > which almost starts.
> > > >
> > > > The GSoC project will need to:
> > > >
> > > > Make the integration test framework run.
> > > > Identify tests that fail.
> > > > Fix tests that fail by providing patches to Sling or to Apache Oak.
> > > > (Optionally) write some tests that exercise some of the features of
> Oak
> > > > (high levels of write, large numbers of children).
> > > >
> > > > If you want to take up this challenge you are going to need to be
> > willing
> > > > to learn about OSGi and you will have to be prepared on interact with
> > > both
> > > > the Sling and Jackrabbit/Oak communities, as most of the solutions to
> > > > problems you find will be in the community, such is Apache!
> > > >
> > > > Ian
> > > >
> > > > 1 http://svn.apache.org/repos/asf/sling/whiteboard/ieb/oak/
> > > > (there is a commit pending here, withi

Re: [VOTE] Release parent 16

[Carsten Ziegeler]

+1


2013/5/1 Ian Boston 

> +1
> Signatures all good.
> I did notice some Jenkins failures on list, but will guess (since release
> without build is impossible) that these are transitive.
> Ian
>
>
> On 1 May 2013 01:48, Mike Müller  wrote:
>
> > +1
> > Best regards
> > mike
> >
> > > -Original Message-
> > > From: Carsten Ziegeler [mailto:cziege...@apache.org]
> > > Sent: Tuesday, April 30, 2013 11:58 AM
> > > To: dev@sling.apache.org
> > > Subject: [VOTE] Release parent 16
> > >
> > > Please vote for the release of a new parent pom. This contains a single
> > > change, the update to the latest Maven SCR plugin (
> > > https://issues.apache.org/jira/browse/SLING-2846)
> > >
> > > Staging repository:
> > > https://repository.apache.org/content/repositories/orgapachesling-156
> > >
> > >
> > > 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 156 /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

Re: Time to release Sling 7?

[Felix Meschberger]

Hi

While there cannot be a guarantee, but trunk is expected to work with Java
8

(The main problem is the Java API exports from the system package. They
exist but based on the Java 8 packages and not based on what Java 8
might/will bring)

Regards
Felix

--
Felix Meschberger | Principal Scientist | Adobe




On 02.05.13 07:42, "Carsten Ziegeler"  wrote:

>I totally agree that we should try to get Sling 7 out soon; it's been a
>long time since Sling 6...
>I think, current trunk should work with Java 7 - for Java 8, well, while
>it
>would be nice, I don't see this that urgent, especially as Java 8 has been
>delayed.
>
>The best way to tackle this, is to look at the snapshot dependencies in
>our
>builder bundle list, see what needs to be done to release those bundles,
>work on the issues and release them.
>
>Carsten
>
>
>2013/5/1 Robert Munteanu 
>
>> Hi,
>>
>> While trying to fix the ITs which fail only on Java 7 I remembered that
>> the latest release of the Sling application only works on Java 5 and 6.
>>
>> While for me as a contributor it's just a bit inconvenient, for users it
>> may be unpleasant to download it and find out that it's not working and
>> possibly give up. I remember a few queries on the users list related to
>> that.
>>
>> I suggest that we release a Java 7-compatible and - as much as possible
>> - Java 8-friendly version of Sling.
>>
>> However I have no idea what needs to be done :-)
>>
>> Robert
>>
>>
>
>
>-- 
>Carsten Ziegeler
>cziege...@apache.org

Re: GSoC 2013 - Apache Solr backend for Apache Sling

[Bertrand Delacretaz]

Hi,

On Thu, May 2, 2013 at 8:44 AM, Ian Boston  wrote:
> On 2 May 2013 16:34, Ilya Velesevich  wrote:
>> ...about "using DataImportHandler or
>> ManifoldCF to provide search for Sling resources using Solr". Could you
>> share some thoughts about this task? Or you probably think that this task
>> should not be part of GSoC as it seems there could be not enough time to
>> implement such support?...

> I think there might not be enough time.

I tend to agree - it's perfectly fine to leave some components as
optional in the project proposal, I'd rather have something well
written and not full-featured that something ugly that ticks all
boxes.

-Bertrand