Re: Launchpad 7 Release?
2014-07-22 23:12 GMT+02:00 Oliver Lietz apa...@oliverlietz.de: +1, I think it's important to have a Sling 7 release soon. Yes, but not a half-baked one. We would have even more users complainig about 7 as we now have with 6. Well, which part do you think would be half-baked if we simply release everything as is. I think most of the bundles (if not all) are in a pretty good shape right now. Carsten I haven't checked the SNAPSHOT bundles, but I think there are some bundles where nothing changed after their latest release so we may use some already released bundles and not release *all* now. there are probaly less than 20 bundles. In theory, the list.xml should only reference snapshots which have actually changes. But I'll check this today to see where we are. Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: Launchpad 7 Release?
On Tue, Jul 22, 2014 at 10:33 PM, Oliver Lietz apa...@oliverlietz.de wrote: On Tuesday 22 July 2014 13:30:59 Bertrand Delacretaz wrote: ...Are you planning to setup integration tests for that Karaf-based launcher? Sure. There are already basic bootstrap tests which check if the required bundles are available and active in org.apache.sling.launchpad.karaf- integration-tests and also some extended tests which check for services and nodes in the repository... Sorry my question was unclear - are you planning to run the launchpad/integration-tests on the Karaf-based launcher? So that the same test suite is used for that and for the launchpad. And there is sling-tests on GitHub. Where exactly? Not sure what that is. -Bertrand
Re: Launchpad 7 Release?
I've updated the bundle list - it was pretty current. For three bundles we still have open issues before we can release: Commons JSON https://issues.apache.org/jira/browse/SLING/fixforversion/12315999 Explorer https://issues.apache.org/jira/browse/SLING/fixforversion/12316190 JCR Jackrabbit Server https://issues.apache.org/jira/browse/SLING/fixforversion/12324840 2014-07-23 8:24 GMT+02:00 Bertrand Delacretaz bdelacre...@apache.org: On Tue, Jul 22, 2014 at 10:33 PM, Oliver Lietz apa...@oliverlietz.de wrote: On Tuesday 22 July 2014 13:30:59 Bertrand Delacretaz wrote: ...Are you planning to setup integration tests for that Karaf-based launcher? Sure. There are already basic bootstrap tests which check if the required bundles are available and active in org.apache.sling.launchpad.karaf- integration-tests and also some extended tests which check for services and nodes in the repository... Sorry my question was unclear - are you planning to run the launchpad/integration-tests on the Karaf-based launcher? So that the same test suite is used for that and for the launchpad. And there is sling-tests on GitHub. Where exactly? Not sure what that is. -Bertrand -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: Launchpad 7 Release?
On Wed, Jul 23, 2014 at 10:21 AM, Carsten Ziegeler cziege...@apache.org wrote: I've updated the bundle list - it was pretty current. For three bundles we still have open issues before we can release: Explorer https://issues.apache.org/jira/browse/SLING/fixforversion/12316190 One open issue, very generic, called 'jQuery JCR Explorer - step 2'. Also no code changes since 2012. I think we can release this one as-is. Robert
Re: Launchpad 7 Release?
On Wed, Jul 23, 2014 at 9:21 AM, Carsten Ziegeler cziege...@apache.org wrote: ...For three bundles we still have open issues before we can release: Commons JSON https://issues.apache.org/jira/browse/SLING/fixforversion/12315999 SLING-3786 does not fix anything, it's just refactoring/testing so it's fine to defer it if convenient. -Bertrand
[VOTE] Release Apache Sling Launchpad Base 4.4.1-2.5.2
Hi, this is a long overdue release with 12 issues fixed https://issues.apache.org/jira/browse/SLING/fixforversion/12321449 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1083 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 1083 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[VOTE] Release Apache Sling Engine 2.3.4
Hi, we fixed 5 issues for this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12326514 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1084 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 1084 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #692
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/692/
Jenkins build is still unstable: sling-trunk-1.7 #692
See https://builds.apache.org/job/sling-trunk-1.7/changes
Re: [VOTE] Release Apache Sling Engine 2.3.4
+1 Robert On Wed, Jul 23, 2014 at 11:27 AM, Carsten Ziegeler cziege...@apache.org wrote: Hi, we fixed 5 issues for this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12326514 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1084 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 1084 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: [VOTE] Release Apache Sling Launchpad Base 4.4.1-2.5.2
+1 Robert On Wed, Jul 23, 2014 at 11:26 AM, Carsten Ziegeler cziege...@apache.org wrote: Hi, this is a long overdue release with 12 issues fixed https://issues.apache.org/jira/browse/SLING/fixforversion/12321449 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1083 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 1083 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Build failed in Jenkins: sling-oak-it-1.6 » Apache Sling Launchpad Testing #39
See https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/39/changes Changes: [cziegeler] Use latest snapshots for release of base and engine -- [...truncated 495 lines...] Downloaded: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.installer.provider.file/1.0.2/org.apache.sling.installer.provider.file-1.0.2.jar (35 KB at 635.0 KB/sec) [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.installer.provider.file/1.0.2/org.apache.sling.installer.provider.file-1.0.2.jar to https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/ws/target/classes/resources/bundles/0/org.apache.sling.installer.provider.file-1.0.2.jar Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.installer.provider.jcr/3.1.5-SNAPSHOT/maven-metadata.xml Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.installer.provider.jcr/3.1.5-SNAPSHOT/maven-metadata.xml (2 KB at 4.8 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.installer.provider.jcr/3.1.5-SNAPSHOT/org.apache.sling.installer.provider.jcr-3.1.5-20121112.104748-164.jar Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.installer.provider.jcr/3.1.5-SNAPSHOT/org.apache.sling.installer.provider.jcr-3.1.5-20121112.104748-164.jar (53 KB at 213.3 KB/sec) [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.installer.provider.jcr/3.1.5-SNAPSHOT/org.apache.sling.installer.provider.jcr-3.1.5-SNAPSHOT.jar to https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/ws/target/classes/resources/bundles/0/org.apache.sling.installer.provider.jcr-3.1.5-SNAPSHOT.jar Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-services/2.0.9-SNAPSHOT/maven-metadata.xml Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-services/2.0.9-SNAPSHOT/maven-metadata.xml (2 KB at 3.4 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-services/2.0.9-SNAPSHOT/org.apache.sling.launchpad.test-services-2.0.9-20121112.105216-533.jar Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-services/2.0.9-SNAPSHOT/org.apache.sling.launchpad.test-services-2.0.9-20121112.105216-533.jar (53 KB at 138.7 KB/sec) [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.launchpad.test-services/2.0.9-SNAPSHOT/org.apache.sling.launchpad.test-services-2.0.9-SNAPSHOT.jar to https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/ws/target/classes/resources/bundles/0/org.apache.sling.launchpad.test-services-2.0.9-SNAPSHOT.jar Downloading: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.launchpad.test-services-war/2.0.8/org.apache.sling.launchpad.test-services-war-2.0.8.war Downloaded: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.launchpad.test-services-war/2.0.8/org.apache.sling.launchpad.test-services-war-2.0.8.war (13 KB at 63.5 KB/sec) [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.launchpad.test-services-war/2.0.8/org.apache.sling.launchpad.test-services-war-2.0.8.war to https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/ws/target/classes/resources/bundles/0/org.apache.sling.launchpad.test-services-war-2.0.8.war [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/slf4j/slf4j-api/1.6.4/slf4j-api-1.6.4.jar to https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/ws/target/classes/resources/bundles/1/slf4j-api-1.6.4.jar Downloading: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.log/3.0.0/org.apache.sling.commons.log-3.0.0.jar Downloaded: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.log/3.0.0/org.apache.sling.commons.log-3.0.0.jar (59 KB at 1063.7 KB/sec) [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.commons.log/3.0.0/org.apache.sling.commons.log-3.0.0.jar to https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/ws/target/classes/resources/bundles/1/org.apache.sling.commons.log-3.0.0.jar Downloading: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.logservice/1.0.0/org.apache.sling.commons.logservice-1.0.0.jar Downloaded:
Build failed in Jenkins: sling-oak-it-1.6 #39
See https://builds.apache.org/job/sling-oak-it-1.6/39/changes Changes: [cziegeler] Use latest snapshots for release of base and engine -- [...truncated 528 lines...] Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.installer.provider.jcr/3.1.5-SNAPSHOT/org.apache.sling.installer.provider.jcr-3.1.5-20121112.104748-164.jar Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.installer.provider.jcr/3.1.5-SNAPSHOT/org.apache.sling.installer.provider.jcr-3.1.5-20121112.104748-164.jar (53 KB at 213.3 KB/sec) [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.installer.provider.jcr/3.1.5-SNAPSHOT/org.apache.sling.installer.provider.jcr-3.1.5-SNAPSHOT.jar to https://builds.apache.org/job/sling-oak-it-1.6/ws/launchpad-testing-oak/target/classes/resources/bundles/0/org.apache.sling.installer.provider.jcr-3.1.5-SNAPSHOT.jar Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-services/2.0.9-SNAPSHOT/maven-metadata.xml Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-services/2.0.9-SNAPSHOT/maven-metadata.xml (2 KB at 3.4 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-services/2.0.9-SNAPSHOT/org.apache.sling.launchpad.test-services-2.0.9-20121112.105216-533.jar Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-services/2.0.9-SNAPSHOT/org.apache.sling.launchpad.test-services-2.0.9-20121112.105216-533.jar (53 KB at 138.7 KB/sec) [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.launchpad.test-services/2.0.9-SNAPSHOT/org.apache.sling.launchpad.test-services-2.0.9-SNAPSHOT.jar to https://builds.apache.org/job/sling-oak-it-1.6/ws/launchpad-testing-oak/target/classes/resources/bundles/0/org.apache.sling.launchpad.test-services-2.0.9-SNAPSHOT.jar Downloading: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.launchpad.test-services-war/2.0.8/org.apache.sling.launchpad.test-services-war-2.0.8.war Downloaded: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.launchpad.test-services-war/2.0.8/org.apache.sling.launchpad.test-services-war-2.0.8.war (13 KB at 63.5 KB/sec) [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.launchpad.test-services-war/2.0.8/org.apache.sling.launchpad.test-services-war-2.0.8.war to https://builds.apache.org/job/sling-oak-it-1.6/ws/launchpad-testing-oak/target/classes/resources/bundles/0/org.apache.sling.launchpad.test-services-war-2.0.8.war [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/slf4j/slf4j-api/1.6.4/slf4j-api-1.6.4.jar to https://builds.apache.org/job/sling-oak-it-1.6/ws/launchpad-testing-oak/target/classes/resources/bundles/1/slf4j-api-1.6.4.jar Downloading: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.log/3.0.0/org.apache.sling.commons.log-3.0.0.jar Downloaded: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.log/3.0.0/org.apache.sling.commons.log-3.0.0.jar (59 KB at 1063.7 KB/sec) [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.commons.log/3.0.0/org.apache.sling.commons.log-3.0.0.jar to https://builds.apache.org/job/sling-oak-it-1.6/ws/launchpad-testing-oak/target/classes/resources/bundles/1/org.apache.sling.commons.log-3.0.0.jar Downloading: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.logservice/1.0.0/org.apache.sling.commons.logservice-1.0.0.jar Downloaded: http://repo.maven.apache.org/maven2/org/apache/sling/org.apache.sling.commons.logservice/1.0.0/org.apache.sling.commons.logservice-1.0.0.jar (25 KB at 76.5 KB/sec) [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.commons.logservice/1.0.0/org.apache.sling.commons.logservice-1.0.0.jar to https://builds.apache.org/job/sling-oak-it-1.6/ws/launchpad-testing-oak/target/classes/resources/bundles/1/org.apache.sling.commons.logservice-1.0.0.jar [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/1/org/slf4j/jcl-over-slf4j/1.6.4/jcl-over-slf4j-1.6.4.jar to https://builds.apache.org/job/sling-oak-it-1.6/ws/launchpad-testing-oak/target/classes/resources/bundles/1/jcl-over-slf4j-1.6.4.jar Downloading: http://repo.maven.apache.org/maven2/org/slf4j/log4j-over-slf4j/1.6.4/log4j-over-slf4j-1.6.4.jar Downloaded: http://repo.maven.apache.org/maven2/org/slf4j/log4j-over-slf4j/1.6.4/log4j-over-slf4j-1.6.4.jar (21 KB at 373.2 KB/sec) [INFO] Copying bundle from
[jira] [Commented] (SLING-3618) Unable to create node at /var/discovery error in sling trunk
[ https://issues.apache.org/jira/browse/SLING-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14071513#comment-14071513 ] Bertrand Delacretaz commented on SLING-3618: [~dekesmith]'s finding confirms my suspicion that /var is created with a different node type depending on which module creates it, depending on startup timing. The mkdir method in ClassLoaderWriterImpl [1] does some (ugly) retries to cope with concurrency issues, it looks like we need a better way to handle the creation of those commonly used nodes a startup - I'll start a discussion on list about that. For now, changing the folders node type to sling:Folder in ClassLoaderWriterImpl should fix this issue, assuming that node type is available when that module starts. [1] https://svn.apache.org/repos/asf/sling/trunk/bundles/jcr/classloader/src/main/java/org/apache/sling/jcr/classloader/internal/ClassLoaderWriterImpl.java Unable to create node at /var/discovery error in sling trunk Key: SLING-3618 URL: https://issues.apache.org/jira/browse/SLING-3618 Project: Sling Issue Type: Bug Components: Extensions Environment: All Reporter: Yogesh Upadhyay Fix For: Discovery Impl 1.0.10 Getting following error after using trunk version of jar 29.05.2014 23:13:15.980 *ERROR* [Apache Sling JCR Resource Event Queue Processor for path '/'] org.apache.sling.discovery.impl [org.apache.sling.discovery.impl.DiscoveryServiceImpl(52)] The activate method has thrown an exception (java.lang.RuntimeException: Exception while talking to repository (org.apache.sling.api.resource.PersistenceException: Unable to create node at /var/discovery)) java.lang.RuntimeException: Exception while talking to repository (org.apache.sling.api.resource.PersistenceException: Unable to create node at /var/discovery) at org.apache.sling.discovery.impl.topology.announcement.AnnouncementRegistryImpl.listAnnouncementsInSameCluster(AnnouncementRegistryImpl.java:204) at org.apache.sling.discovery.impl.topology.announcement.AnnouncementRegistryImpl.listInstances(AnnouncementRegistryImpl.java:487) at org.apache.sling.discovery.impl.DiscoveryServiceImpl.getTopology(DiscoveryServiceImpl.java:423) at org.apache.sling.discovery.impl.DiscoveryServiceImpl.activate(DiscoveryServiceImpl.java:145) at sun.reflect.GeneratedMethodAccessor40.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.felix.scr.impl.helper.BaseMethod.invokeMethod(BaseMethod.java:231) at org.apache.felix.scr.impl.helper.BaseMethod.access$500(BaseMethod.java:39) at org.apache.felix.scr.impl.helper.BaseMethod$Resolved.invoke(BaseMethod.java:624) at org.apache.felix.scr.impl.helper.BaseMethod.invoke(BaseMethod.java:508) at org.apache.felix.scr.impl.helper.ActivateMethod.invoke(ActivateMethod.java:149) at org.apache.felix.scr.impl.manager.SingleComponentManager.createImplementationObject(SingleComponentManager.java:315) at org.apache.felix.scr.impl.manager.SingleComponentManager.createComponent(SingleComponentManager.java:127) at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:871) at org.apache.felix.scr.impl.manager.SingleComponentManager.getServiceInternal(SingleComponentManager.java:838) at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:777) at org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:320) at org.apache.felix.framework.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:231) at org.apache.felix.framework.ServiceRegistry.getService(ServiceRegistry.java:327) at org.apache.felix.framework.Felix.getService(Felix.java:3574) at org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:468) at org.apache.felix.scr.impl.helper.BindMethod.getServiceObject(BindMethod.java:572) at org.apache.felix.scr.impl.manager.DependencyManager.getServiceObject(DependencyManager.java:2012) at org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.prebind(DependencyManager.java:1005) at org.apache.felix.scr.impl.manager.DependencyManager.prebind(DependencyManager.java:1439) at org.apache.felix.scr.impl.manager.AbstractComponentManager.collectDependencies(AbstractComponentManager.java:1119) at org.apache.felix.scr.impl.manager.SingleComponentManager.getServiceInternal(SingleComponentManager.java:807)
[jira] [Updated] (SLING-3750) Delay discovery-service readiness until first vote has finished, to avoid leader being overthrown
[ https://issues.apache.org/jira/browse/SLING-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-3750: --- Fix Version/s: (was: Discovery Impl 1.0.10) Discovery Impl 1.0.12 Delay discovery-service readiness until first vote has finished, to avoid leader being overthrown - Key: SLING-3750 URL: https://issues.apache.org/jira/browse/SLING-3750 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Discovery Impl 1.0.8 Reporter: Stefan Egli Assignee: Stefan Egli Priority: Critical Fix For: Discovery Impl 1.0.12 The current implementation of discovery.impl has a subtle problem at startup. Consider the following problem happening with two simultaneous starts: * two (sling) instances start at roughly the same time * the goal is to write a service which runs on one of the two only, ever * to achieve that, on a TopologyEventListener is used to get hold of the latest TopologyView and derive whether the local instance is leader or not * currently, upon registration of a TopologyEventListener, a TOPOLOGY_INIT event is sent out immediately with the current TopologyView available * right after startup though - hence before the first voting has passed - discovery.impl considers itself to be in so-called isolated mode, creates a topology which contains only itself, and makes itself leader (since every cluster must have a leader) * that means, both instances will receive that isolated view in the TOPOLOGY_INIT and are marked as leader (which is kind of right as they don't know about any other instance yet - but also wrong as it is not yet an established view) * at the same time, they both start voting, then find out about each other and establish a view where one of the two is marked as leader - hence for the other of the two a 'coup d'etat' is happening (the leader is overthrown even though the instance did not crash). This is certainly very problematic and should be avoided. The suggested way to avoid this is to delay both the time when the discovery.impl service is registered with OSGi (by making it a @Component only and registering it as a service explicitly after the first voting) - and by delaying the sending of TOPOLOGY_INIT until again said first voting is finished. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3618) Unable to create node at /var/discovery error in sling trunk
[ https://issues.apache.org/jira/browse/SLING-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-3618: --- Fix Version/s: (was: Discovery Impl 1.0.10) Discovery Impl 1.0.12 Unable to create node at /var/discovery error in sling trunk Key: SLING-3618 URL: https://issues.apache.org/jira/browse/SLING-3618 Project: Sling Issue Type: Bug Components: Extensions Environment: All Reporter: Yogesh Upadhyay Fix For: Discovery Impl 1.0.12 Getting following error after using trunk version of jar 29.05.2014 23:13:15.980 *ERROR* [Apache Sling JCR Resource Event Queue Processor for path '/'] org.apache.sling.discovery.impl [org.apache.sling.discovery.impl.DiscoveryServiceImpl(52)] The activate method has thrown an exception (java.lang.RuntimeException: Exception while talking to repository (org.apache.sling.api.resource.PersistenceException: Unable to create node at /var/discovery)) java.lang.RuntimeException: Exception while talking to repository (org.apache.sling.api.resource.PersistenceException: Unable to create node at /var/discovery) at org.apache.sling.discovery.impl.topology.announcement.AnnouncementRegistryImpl.listAnnouncementsInSameCluster(AnnouncementRegistryImpl.java:204) at org.apache.sling.discovery.impl.topology.announcement.AnnouncementRegistryImpl.listInstances(AnnouncementRegistryImpl.java:487) at org.apache.sling.discovery.impl.DiscoveryServiceImpl.getTopology(DiscoveryServiceImpl.java:423) at org.apache.sling.discovery.impl.DiscoveryServiceImpl.activate(DiscoveryServiceImpl.java:145) at sun.reflect.GeneratedMethodAccessor40.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.felix.scr.impl.helper.BaseMethod.invokeMethod(BaseMethod.java:231) at org.apache.felix.scr.impl.helper.BaseMethod.access$500(BaseMethod.java:39) at org.apache.felix.scr.impl.helper.BaseMethod$Resolved.invoke(BaseMethod.java:624) at org.apache.felix.scr.impl.helper.BaseMethod.invoke(BaseMethod.java:508) at org.apache.felix.scr.impl.helper.ActivateMethod.invoke(ActivateMethod.java:149) at org.apache.felix.scr.impl.manager.SingleComponentManager.createImplementationObject(SingleComponentManager.java:315) at org.apache.felix.scr.impl.manager.SingleComponentManager.createComponent(SingleComponentManager.java:127) at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:871) at org.apache.felix.scr.impl.manager.SingleComponentManager.getServiceInternal(SingleComponentManager.java:838) at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:777) at org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:320) at org.apache.felix.framework.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:231) at org.apache.felix.framework.ServiceRegistry.getService(ServiceRegistry.java:327) at org.apache.felix.framework.Felix.getService(Felix.java:3574) at org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:468) at org.apache.felix.scr.impl.helper.BindMethod.getServiceObject(BindMethod.java:572) at org.apache.felix.scr.impl.manager.DependencyManager.getServiceObject(DependencyManager.java:2012) at org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.prebind(DependencyManager.java:1005) at org.apache.felix.scr.impl.manager.DependencyManager.prebind(DependencyManager.java:1439) at org.apache.felix.scr.impl.manager.AbstractComponentManager.collectDependencies(AbstractComponentManager.java:1119) at org.apache.felix.scr.impl.manager.SingleComponentManager.getServiceInternal(SingleComponentManager.java:807) at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:777) at org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:320) at org.apache.felix.framework.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:231) at org.apache.felix.framework.ServiceRegistry.getService(ServiceRegistry.java:327) at org.apache.felix.framework.Felix.getService(Felix.java:3574) at org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:468) at org.apache.felix.eventadmin.impl.handler.EventHandlerProxy.obtain(EventHandlerProxy.java:283) at
A better way to create commonly used Resources at startup?
Hi, As SLING-3618 shows, there's some non-deterministic behavior in the Sling startup that potentially causes nodes such as /var to be created by different modules depending on startup timing. So potentially with different node types, as seen in that issue. Does someone have a better idea on how to manage the creation of those commonly used nodes? It's probably only about a handful of them such as /var /libs /apps. We might define a CommonResourcesCreator service on which components such as ClassLoaderWriterImpl depend. That service then makes sure the required node types are available, and provides them to its clients. -Bertrand
Re: [VOTE] Release Apache Sling Engine 2.3.4
+1 2014-07-23 10:36 GMT+02:00 Robert Munteanu romb...@apache.org: +1 Robert On Wed, Jul 23, 2014 at 11:27 AM, Carsten Ziegeler cziege...@apache.org wrote: Hi, we fixed 5 issues for this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12326514 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1084 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 1084 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: [VOTE] Release Apache Sling Launchpad Base 4.4.1-2.5.2
+1 2014-07-23 10:40 GMT+02:00 Robert Munteanu romb...@apache.org: +1 Robert On Wed, Jul 23, 2014 at 11:26 AM, Carsten Ziegeler cziege...@apache.org wrote: Hi, this is a long overdue release with 12 issues fixed https://issues.apache.org/jira/browse/SLING/fixforversion/12321449 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1083 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 1083 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: A better way to create commonly used Resources at startup?
Not sure if we really need that. Agreed, we now have a case where this is a problem - but why not just fix this? In the past we didn't have that problem. Now, *if* we want to do something about it, why not have this as a configuration of the resource resolver factory? Before it registers itself it makes sure that the required resources are created/available. No need for additional services or dependencies. Carsten 2014-07-23 10:58 GMT+02:00 Bertrand Delacretaz bdelacre...@apache.org: Hi, As SLING-3618 shows, there's some non-deterministic behavior in the Sling startup that potentially causes nodes such as /var to be created by different modules depending on startup timing. So potentially with different node types, as seen in that issue. Does someone have a better idea on how to manage the creation of those commonly used nodes? It's probably only about a handful of them such as /var /libs /apps. We might define a CommonResourcesCreator service on which components such as ClassLoaderWriterImpl depend. That service then makes sure the required node types are available, and provides them to its clients. -Bertrand -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: A better way to create commonly used Resources at startup?
It sounds like the core issue is that nodes are created before node types are known? Could we tackle that specifically too? (Maybe that resolves the situation) Cheers, Stefan On 7/23/14 10:58 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, As SLING-3618 shows, there's some non-deterministic behavior in the Sling startup that potentially causes nodes such as /var to be created by different modules depending on startup timing. So potentially with different node types, as seen in that issue. Does someone have a better idea on how to manage the creation of those commonly used nodes? It's probably only about a handful of them such as /var /libs /apps. We might define a CommonResourcesCreator service on which components such as ClassLoaderWriterImpl depend. That service then makes sure the required node types are available, and provides them to its clients. -Bertrand
Re: [VOTE] Release Apache Sling Resource-Based Discovery Service 1.0.10
+1 2014-07-23 10:58 GMT+02:00 Stefan Egli stefane...@apache.org: Hi, We solved 1 hotfix-needed issue in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12326797 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1085/ 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 1085 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Cheers, Stefan -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: [VOTE] Release Apache Sling Resource-Based Discovery Service 1.0.10
+1 Robert On Wed, Jul 23, 2014 at 12:09 PM, Carsten Ziegeler cziege...@apache.org wrote: +1 2014-07-23 10:58 GMT+02:00 Stefan Egli stefane...@apache.org: Hi, We solved 1 hotfix-needed issue in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12326797 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1085/ 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 1085 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Cheers, Stefan -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: A better way to create commonly used Resources at startup?
I guess one of the problem's here is that there are parts which are not using the resource resolver and therefore start doing stuff before the resource bundles are active - and in that case the node types have not been added. I guess another solution would be to use the require/provide capabilities in the manifest. Carsten 2014-07-23 11:04 GMT+02:00 Stefan Egli stefane...@apache.org: It sounds like the core issue is that nodes are created before node types are known? Could we tackle that specifically too? (Maybe that resolves the situation) Cheers, Stefan On 7/23/14 10:58 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, As SLING-3618 shows, there's some non-deterministic behavior in the Sling startup that potentially causes nodes such as /var to be created by different modules depending on startup timing. So potentially with different node types, as seen in that issue. Does someone have a better idea on how to manage the creation of those commonly used nodes? It's probably only about a handful of them such as /var /libs /apps. We might define a CommonResourcesCreator service on which components such as ClassLoaderWriterImpl depend. That service then makes sure the required node types are available, and provides them to its clients. -Bertrand -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[jira] [Created] (SLING-3788) Integration test failure regarding vanity paths
Carsten Ziegeler created SLING-3788: --- Summary: Integration test failure regarding vanity paths Key: SLING-3788 URL: https://issues.apache.org/jira/browse/SLING-3788 Project: Sling Issue Type: Bug Components: ResourceResolver Reporter: Carsten Ziegeler Priority: Critical Fix For: Resource Resolver 1.1.2 When running latest trunk, I get this integration test failure: testRedirectOnPathWithExtension(org.apache.sling.launchpad.webapp.integrationtest.VanityPathTest) Time elapsed: 0.039 sec FAILURE! junit.framework.AssertionFailedError: Expecting temporary redirect expected:302 but was:404 at junit.framework.Assert.fail(Assert.java:57) at junit.framework.Assert.failNotEquals(Assert.java:329) at junit.framework.Assert.assertEquals(Assert.java:78) at junit.framework.Assert.assertEquals(Assert.java:234) at junit.framework.TestCase.assertEquals(TestCase.java:401) at org.apache.sling.launchpad.webapp.integrationtest.VanityPathTest.testRedirectOnPathWithExtension(VanityPathTest.java:186) Might be related to the changes of the vanity path handling? -- This message was sent by Atlassian JIRA (v6.2#6252)
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #693
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/changes
Jenkins build is still unstable: sling-trunk-1.7 #693
See https://builds.apache.org/job/sling-trunk-1.7/changes
Re: A better way to create commonly used Resources at startup?
Hi, On Wed, Jul 23, 2014 at 11:04 AM, Carsten Ziegeler cziege...@apache.org wrote: ...we now have a case where this is a problem - but why not just fix this?... We need to fix that case, sure, but the current behavior is not clean - we probably have several similar potential node creation race conditions at startup. ...*if* we want to do something about it, why not have this as a configuration of the resource resolver factory? Before it registers itself it makes sure that the required resources are created/available. No need for additional services or dependencies Good idea, but services which go directly to the repository do not currently have a dependency on that factory. We could add an unused dependency to that, but in the end that's not cleaner than a new service dedicated to the creation of initial resources. As Stefan says, the Sling node types need to be registered before those initial resources are created, so there's a bit more to it. -Bertrand
Re: A better way to create commonly used Resources at startup?
2014-07-23 11:42 GMT+02:00 Bertrand Delacretaz bdelacre...@apache.org: Hi, On Wed, Jul 23, 2014 at 11:04 AM, Carsten Ziegeler cziege...@apache.org wrote: ...we now have a case where this is a problem - but why not just fix this?... We need to fix that case, sure, but the current behavior is not clean - we probably have several similar potential node creation race conditions at startup. Probably, but maybe not :) Can we find this out? ...*if* we want to do something about it, why not have this as a configuration of the resource resolver factory? Before it registers itself it makes sure that the required resources are created/available. No need for additional services or dependencies Good idea, but services which go directly to the repository do not currently have a dependency on that factory. We could add an unused dependency to that, but in the end that's not cleaner than a new service dedicated to the creation of initial resources. Well, I would suggest to change the code to use the resource resolver - that's why we have the abstraction in the first place. As also pointed out, the correct solution is the resource capabilities model of OSGi - which is declarative by using manifest entries and does not require any artifical service. Carsten As Stefan says, the Sling node types need to be registered before those initial resources are created, so there's a bit more to it. -Bertrand -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Jenkins build is unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2317
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2317/changes
Jenkins build is unstable: sling-trunk-1.6 #2317
See https://builds.apache.org/job/sling-trunk-1.6/2317/changes
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2318
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/changes
Jenkins build is still unstable: sling-trunk-1.6 #2318
See https://builds.apache.org/job/sling-trunk-1.6/changes
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #694
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/changes
Jenkins build is still unstable: sling-trunk-1.7 #694
See https://builds.apache.org/job/sling-trunk-1.7/changes
Re: A better way to create commonly used Resources at startup?
On Wed, Jul 23, 2014 at 11:49 AM, Carsten Ziegeler cziege...@apache.org wrote: ...As also pointed out, the correct solution is the resource capabilities model of OSGi - which is declarative by using manifest entries and does not require any artifical service Interesting, do you have pointers as to how this works? -Bertrand
Re: A better way to create commonly used Resources at startup?
On Wednesday 23 July 2014 14:49:57 Bertrand Delacretaz wrote: On Wed, Jul 23, 2014 at 11:49 AM, Carsten Ziegeler cziege...@apache.org wrote: ...As also pointed out, the correct solution is the resource capabilities model of OSGi - which is declarative by using manifest entries and does not require any artifical service Interesting, do you have pointers as to how this works? http://wiki.osgi.org/wiki/Require-Capability http://wiki.osgi.org/wiki/Provide-Capability http://blog.osgi.org/2012/03/requirements-and-capabilities.html O. -Bertrand
Re: A better way to create commonly used Resources at startup?
On Wed, Jul 23, 2014 at 2:59 PM, Oliver Lietz apa...@oliverlietz.de wrote: http://wiki.osgi.org/wiki/Require-Capability http://wiki.osgi.org/wiki/Provide-Capability Cool - is that implemented by the version of the Felix framework that we use? -Bertrand
Re: A better way to create commonly used Resources at startup?
Sure :) Apache Felix implements R5 Carsten 2014-07-23 15:05 GMT+02:00 Bertrand Delacretaz bdelacre...@apache.org: On Wed, Jul 23, 2014 at 2:59 PM, Oliver Lietz apa...@oliverlietz.de wrote: http://wiki.osgi.org/wiki/Require-Capability http://wiki.osgi.org/wiki/Provide-Capability Cool - is that implemented by the version of the Felix framework that we use? -Bertrand -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: [VOTE] Release Apache Sling Launchpad Base 4.4.1-2.5.2
+1 On Wed, Jul 23, 2014 at 5:00 AM, Carsten Ziegeler cziege...@apache.org wrote: +1 2014-07-23 10:40 GMT+02:00 Robert Munteanu romb...@apache.org: +1 Robert On Wed, Jul 23, 2014 at 11:26 AM, Carsten Ziegeler cziege...@apache.org wrote: Hi, this is a long overdue release with 12 issues fixed https://issues.apache.org/jira/browse/SLING/fixforversion/12321449 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1083 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 1083 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: [VOTE] Release Apache Sling Engine 2.3.4
+1 On Wed, Jul 23, 2014 at 5:00 AM, Carsten Ziegeler cziege...@apache.org wrote: +1 2014-07-23 10:36 GMT+02:00 Robert Munteanu romb...@apache.org: +1 Robert On Wed, Jul 23, 2014 at 11:27 AM, Carsten Ziegeler cziege...@apache.org wrote: Hi, we fixed 5 issues for this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12326514 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1084 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 1084 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: [VOTE] Release Apache Sling Resource-Based Discovery Service 1.0.10
+1 On Wed, Jul 23, 2014 at 5:11 AM, Robert Munteanu romb...@apache.org wrote: +1 Robert On Wed, Jul 23, 2014 at 12:09 PM, Carsten Ziegeler cziege...@apache.org wrote: +1 2014-07-23 10:58 GMT+02:00 Stefan Egli stefane...@apache.org: Hi, We solved 1 hotfix-needed issue in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12326797 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1085/ 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 1085 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Cheers, Stefan -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[jira] [Commented] (SLING-3485) Expose JSON Servlet Helpers
[ https://issues.apache.org/jira/browse/SLING-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14071794#comment-14071794 ] Carsten Ziegeler commented on SLING-3485: - I've corrected the package version exports (1.0.0 for the new package) and also added a dynamic import statement - I think this should do the trick and we can close this issue Expose JSON Servlet Helpers --- Key: SLING-3485 URL: https://issues.apache.org/jira/browse/SLING-3485 Project: Sling Issue Type: Improvement Components: Servlets Affects Versions: Servlets Get 2.1.8 Reporter: Dan Klco Assignee: Dan Klco Priority: Minor Labels: easyfix, patch Attachments: SLING-3485.diff Right now the following classes which are used for the JsonRendererServletare not exported from the bundle. From a developer's perspective, I may want to use these classes to remix the Resource - JSON functionality without having to re-write the code. - https://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/get/src/main/java/org/apache/sling/servlets/get/impl/helpers/JsonObjectCreator.java - https://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/get/src/main/java/org/apache/sling/servlets/get/impl/helpers/ResourceTraversor.java I propose we refactor these classes to be in the package org.apache.sling.servlets.get.helpers which will expose them to the OSGi Container. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3485) Expose JSON Servlet Helpers
[ https://issues.apache.org/jira/browse/SLING-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3485: Fix Version/s: Commons JSON 2.0.8 Expose JSON Servlet Helpers --- Key: SLING-3485 URL: https://issues.apache.org/jira/browse/SLING-3485 Project: Sling Issue Type: Improvement Components: Servlets Affects Versions: Servlets Get 2.1.8 Reporter: Dan Klco Assignee: Dan Klco Priority: Minor Labels: easyfix, patch Fix For: Commons JSON 2.0.8 Attachments: SLING-3485.diff Right now the following classes which are used for the JsonRendererServletare not exported from the bundle. From a developer's perspective, I may want to use these classes to remix the Resource - JSON functionality without having to re-write the code. - https://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/get/src/main/java/org/apache/sling/servlets/get/impl/helpers/JsonObjectCreator.java - https://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/get/src/main/java/org/apache/sling/servlets/get/impl/helpers/ResourceTraversor.java I propose we refactor these classes to be in the package org.apache.sling.servlets.get.helpers which will expose them to the OSGi Container. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3788) Integration test failure regarding vanity paths
[ https://issues.apache.org/jira/browse/SLING-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14071811#comment-14071811 ] Carsten Ziegeler commented on SLING-3788: - [~asanso] Can you please have a look? Integration test failure regarding vanity paths --- Key: SLING-3788 URL: https://issues.apache.org/jira/browse/SLING-3788 Project: Sling Issue Type: Bug Components: ResourceResolver Reporter: Carsten Ziegeler Assignee: Antonio Sanso Priority: Critical Fix For: Resource Resolver 1.1.2 When running latest trunk, I get this integration test failure: testRedirectOnPathWithExtension(org.apache.sling.launchpad.webapp.integrationtest.VanityPathTest) Time elapsed: 0.039 sec FAILURE! junit.framework.AssertionFailedError: Expecting temporary redirect expected:302 but was:404 at junit.framework.Assert.fail(Assert.java:57) at junit.framework.Assert.failNotEquals(Assert.java:329) at junit.framework.Assert.assertEquals(Assert.java:78) at junit.framework.Assert.assertEquals(Assert.java:234) at junit.framework.TestCase.assertEquals(TestCase.java:401) at org.apache.sling.launchpad.webapp.integrationtest.VanityPathTest.testRedirectOnPathWithExtension(VanityPathTest.java:186) Might be related to the changes of the vanity path handling? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3788) Integration test failure regarding vanity paths
[ https://issues.apache.org/jira/browse/SLING-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3788: Assignee: Antonio Sanso Integration test failure regarding vanity paths --- Key: SLING-3788 URL: https://issues.apache.org/jira/browse/SLING-3788 Project: Sling Issue Type: Bug Components: ResourceResolver Reporter: Carsten Ziegeler Assignee: Antonio Sanso Priority: Critical Fix For: Resource Resolver 1.1.2 When running latest trunk, I get this integration test failure: testRedirectOnPathWithExtension(org.apache.sling.launchpad.webapp.integrationtest.VanityPathTest) Time elapsed: 0.039 sec FAILURE! junit.framework.AssertionFailedError: Expecting temporary redirect expected:302 but was:404 at junit.framework.Assert.fail(Assert.java:57) at junit.framework.Assert.failNotEquals(Assert.java:329) at junit.framework.Assert.assertEquals(Assert.java:78) at junit.framework.Assert.assertEquals(Assert.java:234) at junit.framework.TestCase.assertEquals(TestCase.java:401) at org.apache.sling.launchpad.webapp.integrationtest.VanityPathTest.testRedirectOnPathWithExtension(VanityPathTest.java:186) Might be related to the changes of the vanity path handling? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3788) Integration test failure regarding vanity paths
[ https://issues.apache.org/jira/browse/SLING-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso resolved SLING-3788. -- Resolution: Duplicate thanks [~cziegeler] but is a duplicate of SLING-3713 Integration test failure regarding vanity paths --- Key: SLING-3788 URL: https://issues.apache.org/jira/browse/SLING-3788 Project: Sling Issue Type: Bug Components: ResourceResolver Reporter: Carsten Ziegeler Assignee: Antonio Sanso Priority: Critical Fix For: Resource Resolver 1.1.2 When running latest trunk, I get this integration test failure: testRedirectOnPathWithExtension(org.apache.sling.launchpad.webapp.integrationtest.VanityPathTest) Time elapsed: 0.039 sec FAILURE! junit.framework.AssertionFailedError: Expecting temporary redirect expected:302 but was:404 at junit.framework.Assert.fail(Assert.java:57) at junit.framework.Assert.failNotEquals(Assert.java:329) at junit.framework.Assert.assertEquals(Assert.java:78) at junit.framework.Assert.assertEquals(Assert.java:234) at junit.framework.TestCase.assertEquals(TestCase.java:401) at org.apache.sling.launchpad.webapp.integrationtest.VanityPathTest.testRedirectOnPathWithExtension(VanityPathTest.java:186) Might be related to the changes of the vanity path handling? -- This message was sent by Atlassian JIRA (v6.2#6252)
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2319
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2319/
Jenkins build is still unstable: sling-trunk-1.6 #2319
See https://builds.apache.org/job/sling-trunk-1.6/changes
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2320
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2320/
Jenkins build is still unstable: sling-trunk-1.6 #2320
See https://builds.apache.org/job/sling-trunk-1.6/changes
Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #695
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.impl/695/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #695
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/695/
Jenkins build is still unstable: sling-trunk-1.7 #695
See https://builds.apache.org/job/sling-trunk-1.7/changes
Re: Launchpad 7 Release?
just my 2c, but before releasing 7 it would be a good idea to make sure all tutorials and samples are correctly working as well. I took a quick look at espblog and was not able to get it to run with launchpad 7 Ruben On 7/22/2014 11:04 PM, Carsten Ziegeler wrote: 2014-07-22 23:12 GMT+02:00 Oliver Lietz apa...@oliverlietz.de: +1, I think it's important to have a Sling 7 release soon. Yes, but not a half-baked one. We would have even more users complainig about 7 as we now have with 6. Well, which part do you think would be half-baked if we simply release everything as is. I think most of the bundles (if not all) are in a pretty good shape right now. Carsten I haven't checked the SNAPSHOT bundles, but I think there are some bundles where nothing changed after their latest release so we may use some already released bundles and not release *all* now. there are probaly less than 20 bundles. In theory, the list.xml should only reference snapshots which have actually changes. But I'll check this today to see where we are. Carsten
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #696
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.impl/696/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #696
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/696/
Jenkins build is still unstable: sling-trunk-1.7 #696
See https://builds.apache.org/job/sling-trunk-1.7/changes
Re: [VOTE] Release Apache Sling Resource-Based Discovery Service 1.0.10
+1 Chetan Mehrotra On Wed, Jul 23, 2014 at 7:55 PM, Daniel Klco dk...@apache.org wrote: +1 On Wed, Jul 23, 2014 at 5:11 AM, Robert Munteanu romb...@apache.org wrote: +1 Robert On Wed, Jul 23, 2014 at 12:09 PM, Carsten Ziegeler cziege...@apache.org wrote: +1 2014-07-23 10:58 GMT+02:00 Stefan Egli stefane...@apache.org: Hi, We solved 1 hotfix-needed issue in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12326797 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1085/ 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 1085 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Cheers, Stefan -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
