[jira] [Commented] (SLING-3993) Avoiding loops when syncing via coordinate agents
[ https://issues.apache.org/jira/browse/SLING-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14160063#comment-14160063 ] Tommaso Teofili commented on SLING-3993: bq. how does OAK support userData see http://markmail.org/message/i2qy6ck22muwe4oc Avoiding loops when syncing via coordinate agents - Key: SLING-3993 URL: https://issues.apache.org/jira/browse/SLING-3993 Project: Sling Issue Type: Bug Components: Replication Reporter: Tommaso Teofili Assignee: Tommaso Teofili In the case of a 'coordinate agent', sitting on 'author' instance, responsible for synchronizing 2+ 'publish' instances the simplest setup would consist of a 'queueing agent' (local exporter, no importer) sitting on each of the 'publish' instances with a trigger responsible of signaling changes of resources under a certain path so that when, for example, a resource 'bar' gets created under '/foo' the trigger will cause the creation of a package for '/foo/bar' which will be queued locally, the 'coordinate agent' will remotely fetch such a package from the queue of e.g. 'pub1' instance and remotely import it into 'pub2' instance. If both 'pub1' and 'pub2' have the same trigger this may result into a looping scenario when instances keep exchanging packages for the same changed content. Possible solutions to this can be, conceptually, based on: 1. identifying the source of the event that generates the replication so that events on changed resources generated by the package builder (upon package installation) are filtered and do not trigger a replication request. 2. filtering packages before they get transported if a same/similar package has been already sent by the target instance, keeping something a cache-like structure for the communication (in the coordinate agent). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-3511) Support selectors for pipeline configuration
[ https://issues.apache.org/jira/browse/SLING-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14160066#comment-14160066 ] Dirk Rudolph commented on SLING-3511: - We should not forget to update the documentation at http://sling.apache.org/site/output-rewriting-pipelines-orgapacheslingrewriter.html. ... Good chance to move the page to the CMS :-) Support selectors for pipeline configuration Key: SLING-3511 URL: https://issues.apache.org/jira/browse/SLING-3511 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Rewriter 1.0.4 Reporter: Dirk Rudolph Assignee: Stefan Seifert Priority: Minor Fix For: Extensions Rewriter 1.0.6 Attachments: rewriter-selectors-support.patch Currently paths, contentTypes, extensions and resourceTypes are available for filtering pipeline configurations. I would be appreciated when filtering by selector would also be possible. We have an intranet/internet application that sends newsletters to different groups of users. Some of the users have to access the links provided in the generated mails trough a portal application. Due to some other rewriting we apply to the links it is necessary to append a prefix to the links in the last step of output rewriting but only for a special selector (we use someresource.mail.html as representation of the this is a mail view). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-3511) Support selectors for pipeline configuration
[ https://issues.apache.org/jira/browse/SLING-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14160116#comment-14160116 ] Robert Munteanu commented on SLING-3511: [~diru] - the page is already moved see - https://sling.apache.org/documentation/bundles/output-rewriting-pipelines-org-apache-sling-rewriter.html . Support selectors for pipeline configuration Key: SLING-3511 URL: https://issues.apache.org/jira/browse/SLING-3511 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Rewriter 1.0.4 Reporter: Dirk Rudolph Assignee: Stefan Seifert Priority: Minor Fix For: Extensions Rewriter 1.0.6 Attachments: rewriter-selectors-support.patch Currently paths, contentTypes, extensions and resourceTypes are available for filtering pipeline configurations. I would be appreciated when filtering by selector would also be possible. We have an intranet/internet application that sends newsletters to different groups of users. Some of the users have to access the links provided in the generated mails trough a portal application. Due to some other rewriting we apply to the links it is necessary to append a prefix to the links in the last step of output rewriting but only for a special selector (we use someresource.mail.html as representation of the this is a mail view). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-3511) Support selectors for pipeline configuration
[ https://issues.apache.org/jira/browse/SLING-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14160121#comment-14160121 ] Dirk Rudolph commented on SLING-3511: - Ok, thanks. However we should not forget to update the documentation after 1.0.6 has been released. Support selectors for pipeline configuration Key: SLING-3511 URL: https://issues.apache.org/jira/browse/SLING-3511 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Rewriter 1.0.4 Reporter: Dirk Rudolph Assignee: Stefan Seifert Priority: Minor Fix For: Extensions Rewriter 1.0.6 Attachments: rewriter-selectors-support.patch Currently paths, contentTypes, extensions and resourceTypes are available for filtering pipeline configurations. I would be appreciated when filtering by selector would also be possible. We have an intranet/internet application that sends newsletters to different groups of users. Some of the users have to access the links provided in the generated mails trough a portal application. Due to some other rewriting we apply to the links it is necessary to append a prefix to the links in the last step of output rewriting but only for a special selector (we use someresource.mail.html as representation of the this is a mail view). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-4006) [HtmlRendererServlet] Must setStatus(204) instead of sendError(204)
Felix Meschberger created SLING-4006: Summary: [HtmlRendererServlet] Must setStatus(204) instead of sendError(204) Key: SLING-4006 URL: https://issues.apache.org/jira/browse/SLING-4006 Project: Sling Issue Type: Bug Components: Servlets Affects Versions: Servlets Get 2.1.10 Reporter: Felix Meschberger Assignee: Felix Meschberger The HtmlRendererServlet of the Default GET Servlets bundle sets the response status if no content can be rendered to 204/NO CONTENT using the HttpServletResponse.sendError method. This is wrong sind sendError does not directly set the status. Instead it causes the error handler to be called with the status set as a response attribute. In addition, at least in Jetty 8, this causes an IllegalStateException since it looks like Jetty 8 does not like any response data once 204/NO CONTENT is set (which IMHO makes sense). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-4006) [HtmlRendererServlet] Must setStatus(204) instead of sendError(204)
[ https://issues.apache.org/jira/browse/SLING-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4006. -- Resolution: Fixed Fix Version/s: Servlets GET 2.1.12 Fixed in Rev. 1629607 [HtmlRendererServlet] Must setStatus(204) instead of sendError(204) --- Key: SLING-4006 URL: https://issues.apache.org/jira/browse/SLING-4006 Project: Sling Issue Type: Bug Components: Servlets Affects Versions: Servlets Get 2.1.10 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Servlets GET 2.1.12 The HtmlRendererServlet of the Default GET Servlets bundle sets the response status if no content can be rendered to 204/NO CONTENT using the HttpServletResponse.sendError method. This is wrong sind sendError does not directly set the status. Instead it causes the error handler to be called with the status set as a response attribute. In addition, at least in Jetty 8, this causes an IllegalStateException since it looks like Jetty 8 does not like any response data once 204/NO CONTENT is set (which IMHO makes sense). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLING-4007) [POST] Prevent NPE if no Session is available
Felix Meschberger created SLING-4007: Summary: [POST] Prevent NPE if no Session is available Key: SLING-4007 URL: https://issues.apache.org/jira/browse/SLING-4007 Project: Sling Issue Type: Bug Components: Servlets Affects Versions: Servlets Post 2.3.6 Reporter: Felix Meschberger Assignee: Felix Meschberger If the request has no Session available, a NullPointerException is thrown on line 285 of the SlingPropertyValueHandler class since ResourceResolver.adaptTo(Session.class) returns null which is not checked. (There is a TODO comment already, sigh...) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-4007) [POST] Prevent NPE if no Session is available
[ https://issues.apache.org/jira/browse/SLING-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4007. -- Resolution: Fixed Fix Version/s: Servlets POST 2.3.8 Fixed in Rev. 1629608 [POST] Prevent NPE if no Session is available - Key: SLING-4007 URL: https://issues.apache.org/jira/browse/SLING-4007 Project: Sling Issue Type: Bug Components: Servlets Affects Versions: Servlets Post 2.3.6 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Servlets POST 2.3.8 If the request has no Session available, a NullPointerException is thrown on line 285 of the SlingPropertyValueHandler class since ResourceResolver.adaptTo(Session.class) returns null which is not checked. (There is a TODO comment already, sigh...) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [PROPOSAL] Sightly donation to Apache Sling
Hello Carsten, The official Sightly specification has been published at [2]. The TCK should be ready by the end of next week. Regards, Radu [2] - https://github.com/Adobe-Marketing-Cloud/sightly-spec On Tue, Sep 23, 2014 at 8:07 AM, Carsten Ziegeler cziege...@apache.org wrote: thanks for the offering. This definitely looks very interesting for Sling. Is the spec downloadable from somewhere? When do you think the test suite will be available?
Re: [PROPOSAL] Sightly donation to Apache Sling
Thanks Radu, I think it's strange that the spec defines something in the Apache Sling namespace (Java Use-API). A spec defined outside of Apache should not define anything in an Apache space. In addition I think for a general purpose templating language this isn't appropriate anyway. Carsten 2014-10-06 12:43 GMT+02:00 Radu Cotescu r...@apache.org: Hello Carsten, The official Sightly specification has been published at [2]. The TCK should be ready by the end of next week. Regards, Radu [2] - https://github.com/Adobe-Marketing-Cloud/sightly-spec On Tue, Sep 23, 2014 at 8:07 AM, Carsten Ziegeler cziege...@apache.org wrote: thanks for the offering. This definitely looks very interesting for Sling. Is the spec downloadable from somewhere? When do you think the test suite will be available? -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[jira] [Commented] (SLING-3511) Support selectors for pipeline configuration
[ https://issues.apache.org/jira/browse/SLING-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14160193#comment-14160193 ] Robert Munteanu commented on SLING-3511: Feel free to add a patch ;-) , you're probably the best suited to do this anyway Support selectors for pipeline configuration Key: SLING-3511 URL: https://issues.apache.org/jira/browse/SLING-3511 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Rewriter 1.0.4 Reporter: Dirk Rudolph Assignee: Stefan Seifert Priority: Minor Fix For: Extensions Rewriter 1.0.6 Attachments: rewriter-selectors-support.patch Currently paths, contentTypes, extensions and resourceTypes are available for filtering pipeline configurations. I would be appreciated when filtering by selector would also be possible. We have an intranet/internet application that sends newsletters to different groups of users. Some of the users have to access the links provided in the generated mails trough a portal application. Due to some other rewriting we apply to the links it is necessary to append a prefix to the links in the last step of output rewriting but only for a special selector (we use someresource.mail.html as representation of the this is a mail view). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-3511) Support selectors for pipeline configuration
[ https://issues.apache.org/jira/browse/SLING-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14160195#comment-14160195 ] Stefan Seifert commented on SLING-3511: --- the source of this documentation page is at https://svn.apache.org/repos/asf/sling/site/trunk/content/documentation/bundles/output-rewriting-pipelines-org-apache-sling-rewriter.mdtext Support selectors for pipeline configuration Key: SLING-3511 URL: https://issues.apache.org/jira/browse/SLING-3511 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Rewriter 1.0.4 Reporter: Dirk Rudolph Assignee: Stefan Seifert Priority: Minor Fix For: Extensions Rewriter 1.0.6 Attachments: rewriter-selectors-support.patch Currently paths, contentTypes, extensions and resourceTypes are available for filtering pipeline configurations. I would be appreciated when filtering by selector would also be possible. We have an intranet/internet application that sends newsletters to different groups of users. Some of the users have to access the links provided in the generated mails trough a portal application. Due to some other rewriting we apply to the links it is necessary to append a prefix to the links in the last step of output rewriting but only for a special selector (we use someresource.mail.html as representation of the this is a mail view). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-3511) Support selectors for pipeline configuration
[ https://issues.apache.org/jira/browse/SLING-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14160196#comment-14160196 ] Dirk Rudolph commented on SLING-3511: - A patch against the current HTML-page wouldn't be that hard but I think the wrong way to provide those changes right? Support selectors for pipeline configuration Key: SLING-3511 URL: https://issues.apache.org/jira/browse/SLING-3511 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Rewriter 1.0.4 Reporter: Dirk Rudolph Assignee: Stefan Seifert Priority: Minor Fix For: Extensions Rewriter 1.0.6 Attachments: rewriter-selectors-support.patch Currently paths, contentTypes, extensions and resourceTypes are available for filtering pipeline configurations. I would be appreciated when filtering by selector would also be possible. We have an intranet/internet application that sends newsletters to different groups of users. Some of the users have to access the links provided in the generated mails trough a portal application. Due to some other rewriting we apply to the links it is necessary to append a prefix to the links in the last step of output rewriting but only for a special selector (we use someresource.mail.html as representation of the this is a mail view). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (SLING-3511) Support selectors for pipeline configuration
[ https://issues.apache.org/jira/browse/SLING-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dirk Rudolph updated SLING-3511: Comment: was deleted (was: A patch against the current HTML-page wouldn't be that hard but I think the wrong way to provide those changes right? ) Support selectors for pipeline configuration Key: SLING-3511 URL: https://issues.apache.org/jira/browse/SLING-3511 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Rewriter 1.0.4 Reporter: Dirk Rudolph Assignee: Stefan Seifert Priority: Minor Fix For: Extensions Rewriter 1.0.6 Attachments: rewriter-selectors-support.patch Currently paths, contentTypes, extensions and resourceTypes are available for filtering pipeline configurations. I would be appreciated when filtering by selector would also be possible. We have an intranet/internet application that sends newsletters to different groups of users. Some of the users have to access the links provided in the generated mails trough a portal application. Due to some other rewriting we apply to the links it is necessary to append a prefix to the links in the last step of output rewriting but only for a special selector (we use someresource.mail.html as representation of the this is a mail view). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build is still unstable: sling-trunk-1.8 » Apache Sling Launchpad Testing #250
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.launchpad.testing/250/
Jenkins build is back to stable : sling-trunk-1.8 » Apache Sling Event Support #250
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/250/
Jenkins build is still unstable: sling-trunk-1.8 #250
See https://builds.apache.org/job/sling-trunk-1.8/changes
Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #962
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/962/
Jenkins build became unstable: sling-trunk-1.7 #962
See https://builds.apache.org/job/sling-trunk-1.7/962/changes
Build failed in Jenkins: sling-oak-it-1.6 » Apache Sling Launchpad Testing #157
See https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/157/ -- maven3-agent.jar already up to date maven3-interceptor.jar already up to date maven3-interceptor-commons.jar already up to date ===[JENKINS REMchannel started OTING CAPACITY]=== log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter). log4j:WARN Please initialize the log4j system properly. Executing Maven: -B -f https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/ws/pom.xml -Dmaven.repo.local=/home/jenkins/jenkins-slave/maven-repositories/0 clean install -Dsling.run.modes=oak [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Apache Sling Launchpad Testing 7-SNAPSHOT [INFO] Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.integration-tests/1.0.1-SNAPSHOT/maven-metadata.xml Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.integration-tests/1.0.1-SNAPSHOT/maven-metadata.xml (2 KB at 2.1 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.commons.testing/2.0.15-SNAPSHOT/maven-metadata.xml Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.commons.testing/2.0.15-SNAPSHOT/maven-metadata.xml (1016 B at 21.6 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.junit.remote/1.0.9-SNAPSHOT/maven-metadata.xml Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.junit.remote/1.0.9-SNAPSHOT/maven-metadata.xml (2 KB at 32.0 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-bundles/0.0.1-SNAPSHOT/maven-metadata.xml Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-bundles/0.0.1-SNAPSHOT/maven-metadata.xml (2 KB at 4.8 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad/7-SNAPSHOT/maven-metadata.xml [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ org.apache.sling.launchpad.testing --- [INFO] Deleting https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/ws/target [INFO] Deleting https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/ws/ (includes = [derby.log, cachedir, sling/**, jackrabbit, coverage.ec], excludes = []) [INFO] [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java) @ org.apache.sling.launchpad.testing --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (set-bundle-required-execution-environment) @ org.apache.sling.launchpad.testing --- [INFO] Executing tasks main: [INFO] Executed tasks [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ org.apache.sling.launchpad.testing --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ org.apache.sling.launchpad.testing --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] [INFO] --- maven-antrun-plugin:1.7:run (check-memory-task) @ org.apache.sling.launchpad.testing --- [INFO] Executing tasks main: [echo] WARNING (SLING-443/SLING-1782) ** [echo] On most platforms, you'll get OutOfMemoryErrors when building unless you set [echo] on 32bit platforms: MAVEN_OPTS=-Xmx256M -XX:MaxPermSize=256M, see SLING-443 [echo] on 64bit platforms: MAVEN_OPTS=-Xmx512M -XX:MaxPermSize=512M, see SLING-1782 [echo] ** [INFO] Executed tasks [INFO] [INFO] --- build-helper-maven-plugin:1.8:reserve-network-port (reserve-network-port) @ org.apache.sling.launchpad.testing --- [INFO] Reserved port 59845 for http.port [INFO] Reserved port 44233 for sling.control.port [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ org.apache.sling.launchpad.testing --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ org.apache.sling.launchpad.testing --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ org.apache.sling.launchpad.testing --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ org.apache.sling.launchpad.testing --- [JENKINS] Recording test
Build failed in Jenkins: sling-oak-it-1.6 #157
See https://builds.apache.org/job/sling-oak-it-1.6/157/ -- Started by upstream project sling-trunk-1.6 build number 2591 originally caused by: Started by an SCM change Building remotely on ubuntu-6 (Ubuntu ubuntu) in workspace https://builds.apache.org/job/sling-oak-it-1.6/ws/ Updating http://svn.apache.org/repos/asf/sling/trunk/launchpad/testing at revision '2014-10-06T11:45:28.405 +' At revision 1629618 no change for http://svn.apache.org/repos/asf/sling/trunk/launchpad/testing since the previous build Parsing POMs maven3-agent.jar already up to date maven3-interceptor.jar already up to date maven3-interceptor-commons.jar already up to date [launchpad-testing-oak] $ /home/jenkins/tools/java/latest1.6/bin/java -Xmx512M -XX:MaxPermSize=256M -enableassertions -cp /home/jenkins/jenkins-slave/maven3-agent.jar:/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.5/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.5 /home/jenkins/jenkins-slave/slave.jar /home/jenkins/jenkins-slave/maven3-interceptor.jar /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 38256 ===[JENKINS REMchannel started OTING CAPACITY]=== log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter). log4j:WARN Please initialize the log4j system properly. Executing Maven: -B -f https://builds.apache.org/job/sling-oak-it-1.6/ws/launchpad-testing-oak/pom.xml -Dmaven.repo.local=/home/jenkins/jenkins-slave/maven-repositories/0 clean install -Dsling.run.modes=oak [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Apache Sling Launchpad Testing 7-SNAPSHOT [INFO] Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.integration-tests/1.0.1-SNAPSHOT/maven-metadata.xml Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.integration-tests/1.0.1-SNAPSHOT/maven-metadata.xml (2 KB at 2.1 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.commons.testing/2.0.15-SNAPSHOT/maven-metadata.xml Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.commons.testing/2.0.15-SNAPSHOT/maven-metadata.xml (1016 B at 21.6 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.junit.remote/1.0.9-SNAPSHOT/maven-metadata.xml Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.junit.remote/1.0.9-SNAPSHOT/maven-metadata.xml (2 KB at 32.0 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-bundles/0.0.1-SNAPSHOT/maven-metadata.xml Downloaded: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-bundles/0.0.1-SNAPSHOT/maven-metadata.xml (2 KB at 4.8 KB/sec) Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad/7-SNAPSHOT/maven-metadata.xml [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ org.apache.sling.launchpad.testing --- [INFO] Deleting https://builds.apache.org/job/sling-oak-it-1.6/ws/launchpad-testing-oak/target [INFO] Deleting https://builds.apache.org/job/sling-oak-it-1.6/ws/launchpad-testing-oak (includes = [derby.log, cachedir, sling/**, jackrabbit, coverage.ec], excludes = []) [INFO] [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java) @ org.apache.sling.launchpad.testing --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (set-bundle-required-execution-environment) @ org.apache.sling.launchpad.testing --- [INFO] Executing tasks main: [INFO] Executed tasks [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ org.apache.sling.launchpad.testing --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ org.apache.sling.launchpad.testing --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] [INFO] --- maven-antrun-plugin:1.7:run (check-memory-task) @ org.apache.sling.launchpad.testing --- [INFO] Executing tasks main: [echo] WARNING (SLING-443/SLING-1782) ** [echo] On most platforms, you'll get OutOfMemoryErrors when building unless you set [echo] on 32bit platforms: MAVEN_OPTS=-Xmx256M -XX:MaxPermSize=256M, see SLING-443 [echo] on 64bit platforms: MAVEN_OPTS=-Xmx512M -XX:MaxPermSize=512M, see SLING-1782 [echo] ** [INFO] Executed
Re: [PROPOSAL] Sightly donation to Apache Sling
Hi, You are right. It leaks implementation details which have not been abstracted enough. I've reformatted that section to provide a more generic description for Use-API objects. Thanks for your feedback! Regards, Radu On Mon, Oct 6, 2014 at 2:00 PM, Carsten Ziegeler cziege...@apache.org wrote: Thanks Radu, I think it's strange that the spec defines something in the Apache Sling namespace (Java Use-API). A spec defined outside of Apache should not define anything in an Apache space. In addition I think for a general purpose templating language this isn't appropriate anyway. Carsten 2014-10-06 12:43 GMT+02:00 Radu Cotescu r...@apache.org: Hello Carsten, The official Sightly specification has been published at [2]. The TCK should be ready by the end of next week. Regards, Radu [2] - https://github.com/Adobe-Marketing-Cloud/sightly-spec On Tue, Sep 23, 2014 at 8:07 AM, Carsten Ziegeler cziege...@apache.org wrote: thanks for the offering. This definitely looks very interesting for Sling. Is the spec downloadable from somewhere? When do you think the test suite will be available? -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Building the launchpad, snapshot bundles (was: [jira] [Created] (SLING-3987) move from Subversion to Git)
Hi, On Fri, Oct 3, 2014 at 3:43 AM, Justin Edelson jus...@justinedelson.com wrote: Hi Radu, I agree. But this is an orthogonal problem to the question of what SCM system we use. I actually thought that we did deploy snapshots via CI. I see some artifacts under https://repository.apache.org/content/repositories/snapshots/org/apache/sling/ but it is inconsistent. Anyone know what is going on with the snapshot deployment? And what we can do to re-enable it? Not sure why, but the Jenkins jobs seem to use mvn clean install I can switch the sling-trunk-1.6 job to deploy the build results, so we are compatible with as many setups as possible. However, this will only work if the Apache snapshots repository is declared either in ~/.m2/settings.xml or in one of our poms ( which it is not ). For the contributor setup, what I think is simplest is building a subset of the reactor, e.g. mvn -am -pl launchpad/builder/pom.xml clean package This should build the launchpad and any dependencies that I can resolve from the reactor. Unfortuntely that used to work with Maven 3.0.5 but does not work anymore with Maven 3.2.1 . I'm not sure why it broke and had no time to look into it. FWIW, I don't think we should (or really could) following a launchpad-only-contains-releases rule. But I'm willing to be convinced otherwise if the snapshot thing is really impossible. Same here, it takes too long to propagate a fix into the launchpad with releases only and the integration tests will run against old code, therefore we will only catch regressions after the release. Robert Justin On Thu, Oct 2, 2014 at 3:46 PM, Radu Cotescu r...@apache.org wrote: Hi, I know that I'm just an occasional contributor to Sling and I noticed that this talk is mostly between PMC members. However, here's my big +1 for what Robert proposed. Currently if somebody wants to contribute a new module to Sling they have to build the full project to get a running launchpad, which (assuming that they didn't use -DskipTests) takes a while. Just my €0.02. Cheers, Radu On Thu, Oct 2, 2014 at 4:14 PM, Robert Munteanu romb...@apache.org wrote: Or do we we guarantee that the Launchpad is always buildable outside the reactor by banning SNAPSHOT dependencies
[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 ] Carsten Ziegeler updated SLING-3750: Fix Version/s: (was: Discovery Impl 1.0.12) Discovery Impl 1.0.14 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.14 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.3.4#6332)
[jira] [Assigned] (SLING-3977) org.apache.sling.discovery.impl bundle gets deactivated
[ https://issues.apache.org/jira/browse/SLING-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-3977: --- Assignee: Carsten Ziegeler org.apache.sling.discovery.impl bundle gets deactivated --- Key: SLING-3977 URL: https://issues.apache.org/jira/browse/SLING-3977 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Discovery Impl 1.0.10 Reporter: Timothee Maret Assignee: Carsten Ziegeler Fix For: Discovery Impl 1.0.12 When removing the content under /var/discovery/impl, the org.apache.sling.discovery.impl bundle will be deactivated. Looking at the code, the org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler does deactivate the bundle when it detects two instances using the same sling.id in the same topology. This mechanism was implemented in SLING-2892, SLING-2901. When removing the content under /var/discovery/impl, the code will detect this as a having two instances with the same id and thus disable the bundle. Those two cases, should be differentiated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-3977) org.apache.sling.discovery.impl bundle gets deactivated
[ https://issues.apache.org/jira/browse/SLING-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3977. - Resolution: Fixed Fixed in rev 1629638 org.apache.sling.discovery.impl bundle gets deactivated --- Key: SLING-3977 URL: https://issues.apache.org/jira/browse/SLING-3977 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Discovery Impl 1.0.10 Reporter: Timothee Maret Assignee: Carsten Ziegeler Fix For: Discovery Impl 1.0.12 When removing the content under /var/discovery/impl, the org.apache.sling.discovery.impl bundle will be deactivated. Looking at the code, the org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler does deactivate the bundle when it detects two instances using the same sling.id in the same topology. This mechanism was implemented in SLING-2892, SLING-2901. When removing the content under /var/discovery/impl, the code will detect this as a having two instances with the same id and thus disable the bundle. Those two cases, should be differentiated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-3832) on 'discovery bindTopologyEventListener' an INIT event can be sent after CHANGING/CHANGED
[ https://issues.apache.org/jira/browse/SLING-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3832: Fix Version/s: (was: Discovery Impl 1.0.12) Discovery Impl 1.0.14 on 'discovery bindTopologyEventListener' an INIT event can be sent after CHANGING/CHANGED - Key: SLING-3832 URL: https://issues.apache.org/jira/browse/SLING-3832 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Discovery Impl 1.0.10 Reporter: Stefan Egli Fix For: Discovery Impl 1.0.14 [DiscoveryServiceImpl|http://svn.apache.org/viewvc/sling/trunk/bundles/extensions/discovery/impl/src/main/java/org/apache/sling/discovery/impl/DiscoveryServiceImpl.java?view=markup], in bindTopologyEventListener, does not correctly synchronize sending the INIT event - the INIT event is sent outside of synchronized(lock) - opening up the possibility of a race condition where bindTopologyEventListener happens while a CHANGING or CHANGED event is just being sent (which would hold the lock object), and an INIT could be sent *after* CHANGING and/or CHANGED. Basically: * even though the API guarantees that the order of events is always: INIT-CHANGING-CHANGED * it can happen, due to this bug, that you can first get CHANGING and/or CHANGED and then afterwards an INIT. * nevertheless, INIT is never called twice To fix this, bindTopologyEventListener needs to send the INIT event in the synchronized(lock) block -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-3434) Make intra-cluster discovery-heartbeats independent from machine clock differences
[ https://issues.apache.org/jira/browse/SLING-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3434: Fix Version/s: (was: Discovery Impl 1.0.12) Discovery Impl 1.0.14 Make intra-cluster discovery-heartbeats independent from machine clock differences -- Key: SLING-3434 URL: https://issues.apache.org/jira/browse/SLING-3434 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Discovery Impl 1.0.2 Reporter: Stefan Egli Fix For: Discovery Impl 1.0.14 SLING-2967 fixed an issue where topology connectors were dependent on having machine clocks in sync - so inter-cluster we're no longer dependent on NTP-synching. Inside a cluster though, this problem is still there. Since heartbeats are written as absolute time - based on the originator's machine clock - it still only works fine the whole cluster is NTP-synched. In general I think this is not a problem as it is best-practice to make sure machines have NTP set up. Nevertheless, it would help if discovery.impl could become independent from this. Also, if clocks are off by too much, pseudo-network-partitions can occur, with the result of having multiple leaders in a cluster (also see SLING-3432) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-3726) Topology contains duplicated instances
[
https://issues.apache.org/jira/browse/SLING-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-3726:
Fix Version/s: (was: Discovery Impl 1.0.12)
Discovery Impl 1.0.14
Topology contains duplicated instances
--
Key: SLING-3726
URL: https://issues.apache.org/jira/browse/SLING-3726
Project: Sling
Issue Type: Bug
Components: Extensions
Affects Versions: Discovery Impl 1.0.4
Reporter: Timothee Maret
Labels: discovery
Fix For: Discovery Impl 1.0.14
In our setup, we experience duplicated instances reported in the topology.
The duplicated instance is reported in two different clusters.
One of the duplicated instance contains no properties (when accessing via the
Discovery APIs).
This block us from relying on the properties announced by the instances.
Our setup is composed of a set of CRX active/passive clusters as in the diag.
below
{noformat}
- ELB - CRX active/passive cluster
|
Dispatcher - |- ELB - CRX active/passive cluster
.
.
.
|
- ELB - CRX active/passive cluster
{noformat}
The discovery service is configured to create a star topology, connecting all
instances to a central instance.
All clusters run the same code which embeds org.apache.sling.discovery.impl
1.0.8
The issue may have been introduced in org.apache.sling.discovery.impl 1.0.4
since we did not experience it with previous releases.
In one occurence of the issue, the duplicated instance identifier was:
10b323d0-b59e-4f87-8370-a15aab1bdc24
The server logs contains the trace [0]
we noticed that all clusters contained the structure [1] which seems to be
the cause of the duplicate.
The workaround consisting of removing [1] from the repository of all
instances removed the duplicated instance from the topology.
We checked that all instances in the topology have a unique sling identifiers
(looking in sling.id.file)
We also checked that the structure [1] was not created by a mechanism
external to the Sling discovery (e.g. content package or initial content)
[0] (IP, path and properties are edited)
{noformat}
21.05.2014 07:43:06.756 *INFO* [192.168.0.1 [1400658186712] POST
/some/service.json HTTP/1.1]
org.apache.sling.discovery.impl.topology.TopologyViewImpl addInstance: cannot
add same instance twice: an
InstanceDescription[slindId=10b323d0-b59e-4f87-8370-a15aab1bdc24,
isLeader=false, isOwn=false,
clusterViewId=e5df113c-03a8-48bb-9fee-63cf2a8a6ab3, properties={ ... }]
{noformat}
[1] /var/discovery/impl/clusterInstances/10b323d0-b59e-4f87-8370-a15aab1bdc24
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Jenkins build became unstable: sling-trunk-1.8 » Apache Sling Event Support #251
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/251/
Jenkins build is still unstable: sling-trunk-1.8 #251
See https://builds.apache.org/job/sling-trunk-1.8/changes
Jenkins build is still unstable: sling-trunk-1.8 » Apache Sling Launchpad Testing #251
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.launchpad.testing/251/
Jenkins build is back to stable : sling-trunk-1.7 #963
See https://builds.apache.org/job/sling-trunk-1.7/963/changes
Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Launchpad Testing #963
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/963/
Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2592
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2592/
Jenkins build became unstable: sling-trunk-1.6 #2592
See https://builds.apache.org/job/sling-trunk-1.6/2592/changes
[jira] [Created] (SLING-4008) Create a JcrEventTrigger
Tommaso Teofili created SLING-4008: -- Summary: Create a JcrEventTrigger Key: SLING-4008 URL: https://issues.apache.org/jira/browse/SLING-4008 Project: Sling Issue Type: Improvement Components: Replication Reporter: Tommaso Teofili Assignee: Tommaso Teofili In the context of SLING-3993 a trigger which is able to reuse userData in order to avoid the loops in content sync would be helpful. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-4008) Create a JcrEventTrigger
[ https://issues.apache.org/jira/browse/SLING-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved SLING-4008. Resolution: Fixed fixed in r1629691 Create a JcrEventTrigger Key: SLING-4008 URL: https://issues.apache.org/jira/browse/SLING-4008 Project: Sling Issue Type: Improvement Components: Replication Reporter: Tommaso Teofili Assignee: Tommaso Teofili In the context of SLING-3993 a trigger which is able to reuse userData in order to avoid the loops in content sync would be helpful. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Launchpad Testing #2593
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2593/
Build failed in Jenkins: sling-oak-it-1.6 » Apache Sling Launchpad Testing #158
See https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/158/ -- maven3-agent.jar already up to date maven3-interceptor.jar already up to date maven3-interceptor-commons.jar already up to date ===[JENKINchannel started S REMOTING CAPACITY]=== log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter). log4j:WARN Please initialize the log4j system properly. Executing Maven: -B -f https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/ws/pom.xml -Dmaven.repo.local=/home/jenkins/jenkins-slave/maven-repositories/0 clean install -Dsling.run.modes=oak [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Apache Sling Launchpad Testing 7-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ org.apache.sling.launchpad.testing --- [INFO] Deleting https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/ws/target [INFO] Deleting https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/ws/ (includes = [derby.log, cachedir, sling/**, jackrabbit, coverage.ec], excludes = []) [INFO] [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java) @ org.apache.sling.launchpad.testing --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (set-bundle-required-execution-environment) @ org.apache.sling.launchpad.testing --- [INFO] Executing tasks main: [INFO] Executed tasks [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ org.apache.sling.launchpad.testing --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ org.apache.sling.launchpad.testing --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] [INFO] --- maven-antrun-plugin:1.7:run (check-memory-task) @ org.apache.sling.launchpad.testing --- [INFO] Executing tasks main: [echo] WARNING (SLING-443/SLING-1782) ** [echo] On most platforms, you'll get OutOfMemoryErrors when building unless you set [echo] on 32bit platforms: MAVEN_OPTS=-Xmx256M -XX:MaxPermSize=256M, see SLING-443 [echo] on 64bit platforms: MAVEN_OPTS=-Xmx512M -XX:MaxPermSize=512M, see SLING-1782 [echo] ** [INFO] Executed tasks [INFO] [INFO] --- build-helper-maven-plugin:1.8:reserve-network-port (reserve-network-port) @ org.apache.sling.launchpad.testing --- [INFO] Reserved port 49195 for http.port [INFO] Reserved port 50701 for sling.control.port [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ org.apache.sling.launchpad.testing --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ org.apache.sling.launchpad.testing --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ org.apache.sling.launchpad.testing --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ org.apache.sling.launchpad.testing --- [JENKINS] Recording test results[INFO] [INFO] --- animal-sniffer-maven-plugin:1.11:check (default) @ org.apache.sling.launchpad.testing --- [INFO] Checking unresolved references to org.codehaus.mojo.signature:java15:1.0 [INFO] [INFO] --- maven-launchpad-plugin:2.3.0:prepare-package (prepare-package) @ org.apache.sling.launchpad.testing --- [INFO] Using bundle list file from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.launchpad/7-SNAPSHOT/org.apache.sling.launchpad-7-SNAPSHOT-bundlelist.xml [INFO] Merging partial bundle list org.apache.sling:org.apache.sling.launchpad.test-bundles:0.0.1-SNAPSHOT Downloading: http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.launchpad.test-bundles/0.0.1-SNAPSHOT/org.apache.sling.launchpad.test-bundles-0.0.1-SNAPSHOT-bundlelistconfig.zip [INFO] Copying base artifact from /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.launchpad.base/4.4.1-2.5.2/org.apache.sling.launchpad.base-4.4.1-2.5.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/org.apache.sling.launchpad.base.jar. [INFO] Copying bundle from /home/jenkins/jenkins-slave/maven-repositories/0/org/slf4j/slf4j-api/1.7.6/slf4j-api-1.7.6.jar to
Build failed in Jenkins: sling-oak-it-1.6 #158
See https://builds.apache.org/job/sling-oak-it-1.6/158/ -- Started by upstream project sling-trunk-1.6 build number 2593 originally caused by: Started by an SCM change Building remotely on ubuntu-6 (Ubuntu ubuntu) in workspace https://builds.apache.org/job/sling-oak-it-1.6/ws/ Updating http://svn.apache.org/repos/asf/sling/trunk/launchpad/testing at revision '2014-10-06T16:46:46.653 +' At revision 1629707 no change for http://svn.apache.org/repos/asf/sling/trunk/launchpad/testing since the previous build Parsing POMs maven3-agent.jar already up to date maven3-interceptor.jar already up to date maven3-interceptor-commons.jar already up to date [launchpad-testing-oak] $ /home/jenkins/tools/java/latest1.6/bin/java -Xmx512M -XX:MaxPermSize=256M -enableassertions -cp /home/jenkins/jenkins-slave/maven3-agent.jar:/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.5/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.5 /home/jenkins/jenkins-slave/slave.jar /home/jenkins/jenkins-slave/maven3-interceptor.jar /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 46422 ===[JENKINchannel started S REMOTING CAPACITY]=== log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter). log4j:WARN Please initialize the log4j system properly. Executing Maven: -B -f https://builds.apache.org/job/sling-oak-it-1.6/ws/launchpad-testing-oak/pom.xml -Dmaven.repo.local=/home/jenkins/jenkins-slave/maven-repositories/0 clean install -Dsling.run.modes=oak [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Apache Sling Launchpad Testing 7-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ org.apache.sling.launchpad.testing --- [INFO] Deleting https://builds.apache.org/job/sling-oak-it-1.6/ws/launchpad-testing-oak/target [INFO] Deleting https://builds.apache.org/job/sling-oak-it-1.6/ws/launchpad-testing-oak (includes = [derby.log, cachedir, sling/**, jackrabbit, coverage.ec], excludes = []) [INFO] [INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java) @ org.apache.sling.launchpad.testing --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (set-bundle-required-execution-environment) @ org.apache.sling.launchpad.testing --- [INFO] Executing tasks main: [INFO] Executed tasks [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ org.apache.sling.launchpad.testing --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ org.apache.sling.launchpad.testing --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] [INFO] --- maven-antrun-plugin:1.7:run (check-memory-task) @ org.apache.sling.launchpad.testing --- [INFO] Executing tasks main: [echo] WARNING (SLING-443/SLING-1782) ** [echo] On most platforms, you'll get OutOfMemoryErrors when building unless you set [echo] on 32bit platforms: MAVEN_OPTS=-Xmx256M -XX:MaxPermSize=256M, see SLING-443 [echo] on 64bit platforms: MAVEN_OPTS=-Xmx512M -XX:MaxPermSize=512M, see SLING-1782 [echo] ** [INFO] Executed tasks [INFO] [INFO] --- build-helper-maven-plugin:1.8:reserve-network-port (reserve-network-port) @ org.apache.sling.launchpad.testing --- [INFO] Reserved port 49195 for http.port [INFO] Reserved port 50701 for sling.control.port [INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ org.apache.sling.launchpad.testing --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ org.apache.sling.launchpad.testing --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ org.apache.sling.launchpad.testing --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.17:test (default-test) @ org.apache.sling.launchpad.testing --- [JENKINS] Recording test results[INFO] [INFO] --- animal-sniffer-maven-plugin:1.11:check (default) @ org.apache.sling.launchpad.testing --- [INFO] Checking unresolved references to org.codehaus.mojo.signature:java15:1.0 [INFO] [INFO] --- maven-launchpad-plugin:2.3.0:prepare-package (prepare-package) @ org.apache.sling.launchpad.testing --- [INFO] Using bundle list file from
Jenkins build is back to stable : sling-trunk-1.6 #2593
See https://builds.apache.org/job/sling-trunk-1.6/2593/changes
Jenkins build is back to stable : sling-contrib-1.6 » Apache Sling Replication Integration Tests #1286
See https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.it/1286/changes
Jenkins build is still unstable: sling-trunk-1.8 » Apache Sling Event Support #252
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/252/
Jenkins build is back to stable : sling-trunk-1.8 » Apache Sling Launchpad Testing #252
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.launchpad.testing/252/
Jenkins build is still unstable: sling-trunk-1.8 #252
See https://builds.apache.org/job/sling-trunk-1.8/changes
Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Installer Integration Tests #2594
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.installer.it/2594/
Jenkins build became unstable: sling-trunk-1.6 #2594
See https://builds.apache.org/job/sling-trunk-1.6/2594/changes
[VOTE] Release Apache Sling Discovery API 1.0.2 and Discovery Impl 1.0.12
Hi, We solved 1 issue for the API https://issues.apache.org/jira/browse/SLING/fixforversion/12324748 and solved 4 issues for Impl https://issues.apache.org/jira/browse/SLING/fixforversion/12327459 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1136 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 1136 /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
[VOTE] Release Apache Sling Settings 1.3.4
Hi, We solved 1 issue for the API https://issues.apache.org/jira/browse/SLING/fixforversion/12327370 https://issues.apache.org/jira/browse/SLING/fixforversion/12324748 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1137 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 1137 /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
[jira] [Updated] (SLING-4001) Apache Sling Content Editor contribution
[ https://issues.apache.org/jira/browse/SLING-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandro Boehme updated SLING-4001: - Attachment: apache _sling_resource_editor.zip Apache Sling Content Editor contribution Key: SLING-4001 URL: https://issues.apache.org/jira/browse/SLING-4001 Project: Sling Issue Type: New Feature Reporter: Sandro Boehme Attachments: apache _sling_resource_editor.zip, apache_sling_content_editor.zip Based on the discussion at the dev list [1, 2] I would like to contribute the Apache Sling Content Editor (previously named JCRBrowser). ++ Features ++ Currently it can be used to rename and delete nodes. Rename works by double clicking the node and you can multi select nodes for the deletion with the 'del' key. The node names are HTML and URL escaped and it provides stateless deep links to the nodes. ++ Further development ++ In the months to come I can work more intensely on the Sling Content Editor and I might add commercial add ons separately. This is why I would like to be able to point users to such an add on from Sling. But judging from other Apache projects [6] I assume this is probably not a problem. I will continue the development at GitHub[7] and send patch files to Sling when new features are implemented. ++ Implementation ++ It uses the Sling API. For the tree on the left the JSTree library is used. It wants a URL to a JSON that contains the data for the child nodes. This URL points to a Sling resource with a 'contenteditor.nodes' selector and a 'json' extension. This way the JSPs [3] render the JSON for the resource that is consumed by the JSTree library. For the deletion and renaming of nodes I use jQuery Ajax calls to the Sling POST servlet. The properties list on the right is rendered [4] using JSTL and the currentNode variable of Sling. The html.jsp is registered for the 'contenteditor' selector relatively to the default servlet. And for not getting overruled by servlets registered by paths and by other resources that are using the 'contenteditor' selector I use a ResourceDecorator [5]. I understand from Dominik Süß that I should use a ResourceProvider instead. I will work on changing that. I'm looking forward to your feedback! [1] - http://comments.gmane.org/gmane.comp.apache.sling.devel/47292 [2] - http://comments.gmane.org/gmane.comp.apache.sling.devel/47517 [3] - https://github.com/sandroboehme/contenteditor/tree/master/src/main/resources/SLING-INF/libs/sling/servlet/default/contenteditor [4] - https://github.com/sandroboehme/contenteditor/blob/master/src/main/resources/SLING-INF/libs/sling/servlet/default/contenteditor/html.jsp line 176 [5] - https://github.com/sandroboehme/contenteditor/blob/master/src/main/java/org/apache/sling/contenteditor/SelectorBasedResourceDecorator.java [6] - https://www.google.de/search?q=site%3Aapache.org+commercial [7] - https://github.com/sandroboehme/contenteditor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4001) Apache Sling Content Editor contribution
[ https://issues.apache.org/jira/browse/SLING-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandro Boehme updated SLING-4001: - Attachment: (was: apache_sling_content_editor.zip) Apache Sling Content Editor contribution Key: SLING-4001 URL: https://issues.apache.org/jira/browse/SLING-4001 Project: Sling Issue Type: New Feature Reporter: Sandro Boehme Attachments: apache _sling_resource_editor.zip Based on the discussion at the dev list [1, 2] I would like to contribute the Apache Sling Content Editor (previously named JCRBrowser). ++ Features ++ Currently it can be used to rename and delete nodes. Rename works by double clicking the node and you can multi select nodes for the deletion with the 'del' key. The node names are HTML and URL escaped and it provides stateless deep links to the nodes. ++ Further development ++ In the months to come I can work more intensely on the Sling Content Editor and I might add commercial add ons separately. This is why I would like to be able to point users to such an add on from Sling. But judging from other Apache projects [6] I assume this is probably not a problem. I will continue the development at GitHub[7] and send patch files to Sling when new features are implemented. ++ Implementation ++ It uses the Sling API. For the tree on the left the JSTree library is used. It wants a URL to a JSON that contains the data for the child nodes. This URL points to a Sling resource with a 'contenteditor.nodes' selector and a 'json' extension. This way the JSPs [3] render the JSON for the resource that is consumed by the JSTree library. For the deletion and renaming of nodes I use jQuery Ajax calls to the Sling POST servlet. The properties list on the right is rendered [4] using JSTL and the currentNode variable of Sling. The html.jsp is registered for the 'contenteditor' selector relatively to the default servlet. And for not getting overruled by servlets registered by paths and by other resources that are using the 'contenteditor' selector I use a ResourceDecorator [5]. I understand from Dominik Süß that I should use a ResourceProvider instead. I will work on changing that. I'm looking forward to your feedback! [1] - http://comments.gmane.org/gmane.comp.apache.sling.devel/47292 [2] - http://comments.gmane.org/gmane.comp.apache.sling.devel/47517 [3] - https://github.com/sandroboehme/contenteditor/tree/master/src/main/resources/SLING-INF/libs/sling/servlet/default/contenteditor [4] - https://github.com/sandroboehme/contenteditor/blob/master/src/main/resources/SLING-INF/libs/sling/servlet/default/contenteditor/html.jsp line 176 [5] - https://github.com/sandroboehme/contenteditor/blob/master/src/main/java/org/apache/sling/contenteditor/SelectorBasedResourceDecorator.java [6] - https://www.google.de/search?q=site%3Aapache.org+commercial [7] - https://github.com/sandroboehme/contenteditor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4001) Apache Sling Resource Editor contribution
[ https://issues.apache.org/jira/browse/SLING-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandro Boehme updated SLING-4001: - Description: Based on the discussion at the dev list [1, 2] I would like to contribute the Apache Sling Resource Editor (previously named JCRBrowser and Apache Sling Content Editor). ++ Features ++ Currently it can be used to rename and delete nodes. Rename works by double clicking the node and you can multi select nodes for the deletion with the 'del' key. The node names are HTML and URL escaped and it provides stateless deep links to the nodes. ++ Further development ++ In the months to come I can work more intensely on the Sling Resource Editor and I might add commercial add-ons separately. This is why I would like to be able to point users to such an add-on from Sling. But judging from other Apache projects [6] I assume this is probably not a problem. I will continue the development at GitHub[7] and send patch files to Sling when new features are implemented. ++ Implementation ++ It uses the Sling API. For the tree on the left the JSTree library is used. It expects a URL to a JSON that contains the data for the child nodes. This URL points to a Sling resource with a 'reseditor.nodes' selector and a 'json' extension. This way the JSPs [3] render the JSON for the resource that is consumed by the JSTree library. For the deletion and renaming of nodes I use jQuery Ajax calls to the Sling POST servlet. The properties list on the right is rendered [4] using JSTL and the currentNode variable of Sling. The html.jsp is registered for the 'reseditor' selector relatively to the default servlet. And for not getting overruled by servlets registered by paths and by other resources that are using the 'reseditor' selector I use a ResourceDecorator [5]. After a hint from Dominik Süß I work on using a ResourceProvider instead. I'm looking forward to your feedback! [1] - http://comments.gmane.org/gmane.comp.apache.sling.devel/47292 [2] - http://comments.gmane.org/gmane.comp.apache.sling.devel/47517 [3] - https://github.com/sandroboehme/resourceeditor/tree/master/src/main/resources/SLING-INF/libs/sling/servlet/default/reseditor [4] - https://github.com/sandroboehme/resourceeditor/blob/master/src/main/resources/SLING-INF/libs/sling/servlet/default/reseditor/html.jsp line 174 [5] - https://github.com/sandroboehme/resourceeditor/blob/master/src/main/java/org/apache/sling/reseditor/SelectorBasedResourceDecorator.java [6] - https://www.google.de/search?q=site%3Aapache.org+commercial [7] - https://github.com/sandroboehme/resourceeditor was: Based on the discussion at the dev list [1, 2] I would like to contribute the Apache Sling Content Editor (previously named JCRBrowser). ++ Features ++ Currently it can be used to rename and delete nodes. Rename works by double clicking the node and you can multi select nodes for the deletion with the 'del' key. The node names are HTML and URL escaped and it provides stateless deep links to the nodes. ++ Further development ++ In the months to come I can work more intensely on the Sling Content Editor and I might add commercial add ons separately. This is why I would like to be able to point users to such an add on from Sling. But judging from other Apache projects [6] I assume this is probably not a problem. I will continue the development at GitHub[7] and send patch files to Sling when new features are implemented. ++ Implementation ++ It uses the Sling API. For the tree on the left the JSTree library is used. It wants a URL to a JSON that contains the data for the child nodes. This URL points to a Sling resource with a 'contenteditor.nodes' selector and a 'json' extension. This way the JSPs [3] render the JSON for the resource that is consumed by the JSTree library. For the deletion and renaming of nodes I use jQuery Ajax calls to the Sling POST servlet. The properties list on the right is rendered [4] using JSTL and the currentNode variable of Sling. The html.jsp is registered for the 'contenteditor' selector relatively to the default servlet. And for not getting overruled by servlets registered by paths and by other resources that are using the 'contenteditor' selector I use a ResourceDecorator [5]. I understand from Dominik Süß that I should use a ResourceProvider instead. I will work on changing that. I'm looking forward to your feedback! [1] - http://comments.gmane.org/gmane.comp.apache.sling.devel/47292 [2] - http://comments.gmane.org/gmane.comp.apache.sling.devel/47517 [3] - https://github.com/sandroboehme/contenteditor/tree/master/src/main/resources/SLING-INF/libs/sling/servlet/default/contenteditor [4] - https://github.com/sandroboehme/contenteditor/blob/master/src/main/resources/SLING-INF/libs/sling/servlet/default/contenteditor/html.jsp line 176 [5] -
[jira] [Comment Edited] (SLING-4001) Apache Sling Resource Editor contribution
[ https://issues.apache.org/jira/browse/SLING-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14160694#comment-14160694 ] Sandro Boehme edited comment on SLING-4001 at 10/6/14 6:51 PM: --- Renamed the contribution from Content Editor to Resource Editor. The issue is ready for comments and votings now. was (Author: sandro): renamed the contribution from Content Editor to Resource Editor Apache Sling Resource Editor contribution - Key: SLING-4001 URL: https://issues.apache.org/jira/browse/SLING-4001 Project: Sling Issue Type: New Feature Reporter: Sandro Boehme Attachments: apache _sling_resource_editor.zip Based on the discussion at the dev list [1, 2] I would like to contribute the Apache Sling Resource Editor (previously named JCRBrowser and Apache Sling Content Editor). ++ Features ++ Currently it can be used to rename and delete nodes. Rename works by double clicking the node and you can multi select nodes for the deletion with the 'del' key. The node names are HTML and URL escaped and it provides stateless deep links to the nodes. ++ Further development ++ In the months to come I can work more intensely on the Sling Resource Editor and I might add commercial add-ons separately. This is why I would like to be able to point users to such an add-on from Sling. But judging from other Apache projects [6] I assume this is probably not a problem. I will continue the development at GitHub[7] and send patch files to Sling when new features are implemented. ++ Implementation ++ It uses the Sling API. For the tree on the left the JSTree library is used. It expects a URL to a JSON that contains the data for the child nodes. This URL points to a Sling resource with a 'reseditor.nodes' selector and a 'json' extension. This way the JSPs [3] render the JSON for the resource that is consumed by the JSTree library. For the deletion and renaming of nodes I use jQuery Ajax calls to the Sling POST servlet. The properties list on the right is rendered [4] using JSTL and the currentNode variable of Sling. The html.jsp is registered for the 'reseditor' selector relatively to the default servlet. And for not getting overruled by servlets registered by paths and by other resources that are using the 'reseditor' selector I use a ResourceDecorator [5]. After a hint from Dominik Süß I work on using a ResourceProvider instead. I'm looking forward to your feedback! [1] - http://comments.gmane.org/gmane.comp.apache.sling.devel/47292 [2] - http://comments.gmane.org/gmane.comp.apache.sling.devel/47517 [3] - https://github.com/sandroboehme/resourceeditor/tree/master/src/main/resources/SLING-INF/libs/sling/servlet/default/reseditor [4] - https://github.com/sandroboehme/resourceeditor/blob/master/src/main/resources/SLING-INF/libs/sling/servlet/default/reseditor/html.jsp line 174 [5] - https://github.com/sandroboehme/resourceeditor/blob/master/src/main/java/org/apache/sling/reseditor/SelectorBasedResourceDecorator.java [6] - https://www.google.de/search?q=site%3Aapache.org+commercial [7] - https://github.com/sandroboehme/resourceeditor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (SLING-4001) Apache Sling Resource Editor contribution
[ https://issues.apache.org/jira/browse/SLING-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandro Boehme reopened SLING-4001: -- renamed the contribution from Content Editor to Resource Editor Apache Sling Resource Editor contribution - Key: SLING-4001 URL: https://issues.apache.org/jira/browse/SLING-4001 Project: Sling Issue Type: New Feature Reporter: Sandro Boehme Attachments: apache _sling_resource_editor.zip Based on the discussion at the dev list [1, 2] I would like to contribute the Apache Sling Resource Editor (previously named JCRBrowser and Apache Sling Content Editor). ++ Features ++ Currently it can be used to rename and delete nodes. Rename works by double clicking the node and you can multi select nodes for the deletion with the 'del' key. The node names are HTML and URL escaped and it provides stateless deep links to the nodes. ++ Further development ++ In the months to come I can work more intensely on the Sling Resource Editor and I might add commercial add-ons separately. This is why I would like to be able to point users to such an add-on from Sling. But judging from other Apache projects [6] I assume this is probably not a problem. I will continue the development at GitHub[7] and send patch files to Sling when new features are implemented. ++ Implementation ++ It uses the Sling API. For the tree on the left the JSTree library is used. It expects a URL to a JSON that contains the data for the child nodes. This URL points to a Sling resource with a 'reseditor.nodes' selector and a 'json' extension. This way the JSPs [3] render the JSON for the resource that is consumed by the JSTree library. For the deletion and renaming of nodes I use jQuery Ajax calls to the Sling POST servlet. The properties list on the right is rendered [4] using JSTL and the currentNode variable of Sling. The html.jsp is registered for the 'reseditor' selector relatively to the default servlet. And for not getting overruled by servlets registered by paths and by other resources that are using the 'reseditor' selector I use a ResourceDecorator [5]. After a hint from Dominik Süß I work on using a ResourceProvider instead. I'm looking forward to your feedback! [1] - http://comments.gmane.org/gmane.comp.apache.sling.devel/47292 [2] - http://comments.gmane.org/gmane.comp.apache.sling.devel/47517 [3] - https://github.com/sandroboehme/resourceeditor/tree/master/src/main/resources/SLING-INF/libs/sling/servlet/default/reseditor [4] - https://github.com/sandroboehme/resourceeditor/blob/master/src/main/resources/SLING-INF/libs/sling/servlet/default/reseditor/html.jsp line 174 [5] - https://github.com/sandroboehme/resourceeditor/blob/master/src/main/java/org/apache/sling/reseditor/SelectorBasedResourceDecorator.java [6] - https://www.google.de/search?q=site%3Aapache.org+commercial [7] - https://github.com/sandroboehme/resourceeditor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #965
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/965/
Jenkins build became unstable: sling-trunk-1.7 #965
See https://builds.apache.org/job/sling-trunk-1.7/965/changes
Jenkins build is back to stable : sling-trunk-1.6 #2595
See https://builds.apache.org/job/sling-trunk-1.6/2595/changes
Jenkins build is back to stable : sling-trunk-1.8 » Apache Sling Event Support #253
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/253/
Re: Please review Sling 7 Javadocs
Hi Robert, thanks for the great work - I had a brief look at the javadocs and they seem to be good. So +1 Carsten 2014-10-05 23:06 GMT+02:00 Robert Munteanu romb...@apache.org: Hi, I've generated a first draft of the Sling 7 API docs, which we should publish soon. They are temporarily placed at [1], if someone would like to review them before publishing. If no one find any issue with them, I'll do that in a couple of days. The scripts used to generate the Javadocs are at [2] . I would add them to the main Sling repo, but I'm not sure where - tooling/release is maybe a candidate, but I'd welcome other suggestions. Cheers, Robert [1]: https://people.apache.org/~rombert/sling-7-apidocs/ [2]: https://github.com/rombert/sling-releng -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Jenkins build is unstable: sling-oak-it-1.6 » Apache Sling Launchpad Testing #159
See https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/159/
Jenkins build is unstable: sling-oak-it-1.6 #159
See https://builds.apache.org/job/sling-oak-it-1.6/159/
Re: Please review Sling 7 Javadocs
Cool :) Would it be possible to use the old javadoc css? Because IMO the new one by Oracle (since Java 7 IIRC) is really bad, tiny fonts, really bad contrast, hard to browse read... Cheers, Alex On 05.10.2014, at 14:06, Robert Munteanu romb...@apache.org wrote: Hi, I've generated a first draft of the Sling 7 API docs, which we should publish soon. They are temporarily placed at [1], if someone would like to review them before publishing. If no one find any issue with them, I'll do that in a couple of days. The scripts used to generate the Javadocs are at [2] . I would add them to the main Sling repo, but I'm not sure where - tooling/release is maybe a candidate, but I'd welcome other suggestions. Cheers, Robert [1]: https://people.apache.org/~rombert/sling-7-apidocs/ [2]: https://github.com/rombert/sling-releng
