http://permalink.gmane.org/gmane.comp.apache.sling.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.apache.sling.devel/26242 <pre> +1 on all four. Checked digests, signatures, builds and that the contents match the respective svn tags. -Bertrand P.S. md5 of archives that I verified: MD5 (org.apache.sling.installer.factory.configuration-1.0.8-source-release.zip) = a35362832e08a4c2750ccb764c8f1465 MD5 (org.apache.sling.engine-2.2.6-source-release.zip) = fa76515695d22492295528567569c8b9 MD5 (org.apache.sling.i18n-2.2.2-source-release.zip) = e66c314ae68deca0f7478f452892ac83 MD5 (org.apache.sling.scripting.core-2.0.22-source-release.zip) = 45fb1cfc7800d0ac33433242ce5562f4 </pre> Bertrand Delacretaz 2012-05-25T12:49:07 http://permalink.gmane.org/gmane.comp.apache.sling.devel/26241 <pre>Sorry, missed it ... +1 Regards Felix Am 25.05.2012 um 09:37 schrieb Carsten Ziegeler: </pre> Felix Meschberger 2012-05-25T10:59:22 http://permalink.gmane.org/gmane.comp.apache.sling.devel/26240 <pre> [ https://issues.apache.org/jira/browse/SLING-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-2494. -------------------------------------- Resolution: Fixed Fix Version/s: JCR Registration 1.0.0 Thanks for reporting. This makes perfect sense. I have changed the configuration policy to REQUIRED in Rev. 1342555 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Felix Meschberger (JIRA 2012-05-25T10:08:23 http://permalink.gmane.org/gmane.comp.apache.sling.devel/26239 <pre> [ https://issues.apache.org/jira/browse/SLING-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-2494: ---------------------------------------- Assignee: Felix Meschberger -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Felix Meschberger (JIRA 2012-05-25T09:57:26 http://permalink.gmane.org/gmane.comp.apache.sling.devel/26238 <pre>+1, All checks out Ok, signatures all Ok, everything unpacks, all poms are valid and legal files all look in place. Issues fixed also look good to me. Nothing less than perfection (state normal) Thanks Ian On 25 May 2012 17:59, Ian Boston &lt;ieb-9NYRByl3pLhaa/9Udqfwiw&lt; at &gt;public.gmane.org&gt; wrote: </pre> Ian Boston 2012-05-25T08:17:41 http://permalink.gmane.org/gmane.comp.apache.sling.devel/26237 <pre>Give me a sec and I'll review. Ian On 25 May 2012 17:37, Carsten Ziegeler &lt;cziegeler-1oDqGaOF3Lkdnm+yROfE0A&lt; at &gt;public.gmane.org&gt; wrote: </pre> Ian Boston 2012-05-25T07:59:59 http://permalink.gmane.org/gmane.comp.apache.sling.devel/26236 <pre>Anyone? 2012/5/19 Carsten Ziegeler &lt;cziegeler-1oDqGaOF3Lkdnm+yROfE0A&lt; at &gt;public.gmane.org&gt;: </pre> Carsten Ziegeler 2012-05-25T07:37:05 http://permalink.gmane.org/gmane.comp.apache.sling.devel/26235 <pre>Chetan Mehrotra created SLING-2494: -------------------------------------- Summary: JCR Registration should be disabled by default Key: SLING-2494 URL: https://issues.apache.org/jira/browse/SLING-2494 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR Registration 1.0.0 Reporter: Chetan Mehrotra Priority: Minor The current set of JCR registration component RmiRegistrationSupport and JndiRegistrationSupport have Component-&gt; immediate set to true which causes them to activate on default startup. This behavior should be changed to false with activation policy set to ConfigurationPolicy.REQUIRE i.e. should be an opt in activation. For both components the default behavior causes issue RmiRegistrationSupport - It causes issue in embedding Sling in an AppServer application as the default RMI port is already in use. JndiRegistrationSupport - The default config refer to org.apache</pre> Chetan Mehrotra (JIRA 2012-05-25T06:16:23 http://permalink.gmane.org/gmane.comp.apache.sling.devel/26234 <pre> [ https://issues.apache.org/jira/browse/SLING-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=13282284#comment-13282284 ] Bertrand Delacretaz commented on SLING-2002: -------------------------------------------- Here's the current status of my tests, I might not have checked all pages but at least the vast majority of them: broken tables: http://sling.staging.apache.org/documentation/the-sling-engine/dispatching-requests.html http://sling.staging.apache.org/documentation/the-sling-engine/authentication/authentication-authenticationhandler.html http://sling.staging.apache.org/documentation/the-sling-engine/request-parameters.html http://sling.staging.apache.org/documentation/bundles/content-loading-jcr-contentloader.html http://sling.staging.apache.org/documentation/bundles/accessing-filesystem-resources-extensions-fsresource.html external links are broken: http://sling.staging.apache.org/documentation/tutorials-how-tos/jackrabbit-persistence.html (links t</pre> Bertrand Delacretaz (JIRA 2012-05-24T11:30:06 http://permalink.gmane.org/gmane.comp.apache.sling.devel/26233 <pre>Hi, Right, next steps should be "fix by hand", which I already started with some pages (e.g. duplicate titles) and structuring the files according today's site. Regards Felix Am 24.05.2012 um 11:33 schrieb Bertrand Delacretaz: </pre> Felix Meschberger 2012-05-24T09:34:58 http://permalink.gmane.org/gmane.comp.apache.sling.devel/26232 <pre> I see tables broken in those four pages (but might not have checked all pages), we can probably fix those by hand: http://sling.staging.apache.org/documentation/the-sling-engine/authentication/authentication-authenticationhandler.html http://sling.staging.apache.org/documentation/the-sling-engine/request-parameters.html http://sling.staging.apache.org/documentation/bundles/content-loading-jcr-contentloader.html http://sling.staging.apache.org/documentation/bundles/accessing-filesystem-resources-extensions-fsresource.html ... Which might also be fix by hand and/or find simpler layouts that work, IMO. -Bertrand </pre> Bertrand Delacretaz 2012-05-24T09:33:01 http://permalink.gmane.org/gmane.comp.apache.sling.devel/26231 <pre>Hi, Am 24.05.2012 um 10:10 schrieb Bertrand Delacretaz: Yes, the idea is to have an .htdocs in the old site folder which statically redirects to the new locations once we are there. Ok, thanks. Right some tables are converted but don't show correctly because apparently the ASF CMS table support requires table headers and those failing tables don't have headers. Then, of course, all {note}, {panel}, etc. macros have not been converted. We need to come with a solution here. Regards Felix </pre> Felix Meschberger 2012-05-24T09:13:03 http://permalink.gmane.org/gmane.comp.apache.sling.devel/26230 <pre>Hi Felix, On Tue, May 22, 2012 at 10:59 AM, Felix Meschberger &lt;fmeschbe-dv/VyGpifdQAvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; wrote: Cool, thanks! Are you planning to redirect the old URLs to the new ones? For example http://sling.apache.org/site/getting-started.html would become http://sling.apache.org/documentation/getting-started.html as it's now at http://sling.staging.apache.org/documentation/getting-started.html I think we need that, as we have such URLs scattered around blogs, articles and product documentations. I've gone though the current http://sling.staging.apache.org and noted a few remaining problems, will report in SLING-2002 (but jira seems to be down right now). -Bertrand </pre> Bertrand Delacretaz 2012-05-24T08:10:22 http://permalink.gmane.org/gmane.comp.apache.sling.devel/26229 <pre> [ https://issues.apache.org/jira/browse/SLING-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-2493: ----------------------------------------- Affects Version/s: JCR Resource 2.1.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Alexander Klimetschek (JIRA 2012-05-23T17:19:41 http://permalink.gmane.org/gmane.comp.apache.sling.devel/26228 <pre> [ https://issues.apache.org/jira/browse/SLING-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-2493: ----------------------------------------- Summary: sling:vanityPaths: observation listener should be registered before initial scan to avoid missing changes (was: sling:vanityPaths: observation listener should be started before initial scan on bundle activation to avoid missing changes) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Alexander Klimetschek (JIRA 2012-05-23T17:17:40 http://permalink.gmane.org/gmane.comp.apache.sling.devel/26227 <pre> [ https://issues.apache.org/jira/browse/SLING-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-2493: ----------------------------------------- Affects Version/s: (was: JCR Resource 2.1.0) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Alexander Klimetschek (JIRA 2012-05-23T17:17:40 http://permalink.gmane.org/gmane.comp.apache.sling.devel/26226 <pre> [ https://issues.apache.org/jira/browse/SLING-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-2493: ----------------------------------------- Attachment: SLING-2493.patch Attached possible patch (untested, as testing this is really difficult). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira </pre> Alexander Klimetschek (JIRA 2012-05-23T17:17:40 http://permalink.gmane.org/gmane.comp.apache.sling.devel/26225 <pre> [ https://issues.apache.org/jira/browse/SLING-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-2493: ----------------------------------------- Description: MapEntries [0] does first a scan in doInit() and then registers the event listener for sling:vanityPath nodes. Now if a observation event comes in between that, it gets lost - the old content was read in the initial scan and is cached. It looks like we had such a case while both bundle and content were updated "at the same time". Possibly the registerService() method could be blocked for a while if many other services are restarted in such a update scenario involving multiple bundles. I think the observation listener for such cases should always be registered *before* the initial scan. [0] http://svn.apache.org/repos/asf/sling/trunk/bundles/jcr/resource/src/main/java/org/apache/sling/jcr/resource/internal/helper/MapEntries.java was: MapEntries [0] does first a scan in doInit() </pre> Alexander Klimetschek (JIRA 2012-05-23T17:15:43 http://permalink.gmane.org/gmane.comp.apache.sling.devel/26224 <pre>Alexander Klimetschek created SLING-2493: -------------------------------------------- Summary: sling:vanityPaths: observation listener should be started before initial scan on bundle activation to avoid missing changes Key: SLING-2493 URL: https://issues.apache.org/jira/browse/SLING-2493 Project: Sling Issue Type: Bug Components: JCR Affects Versions: JCR Resource 2.1.0 Reporter: Alexander Klimetschek Priority: Minor MapEntries [0] does first a scan in doInit() and then starts a thread for getting observation changes for sling:vanityPath nodes. Now if a observation event comes in between that, it gets lost - the old content was read in the initial scan and is cached. It looks like we had such a case while both bundle and content were updated "at the same time". I think the observation listener for such cases should always be registered *before* the initial scan. [0] http://svn.apache.org/repos/as</pre> Alexander Klimetschek (JIRA 2012-05-23T17:09:41 http://permalink.gmane.org/gmane.comp.apache.sling.devel/26223 <pre>See &lt;https://builds.apache.org/job/sling-samples-1.5/325/&gt; ------------------------------------------ [...truncated 1764 lines...] [INFO] --- maven-remote-resources-plugin:1.1:process (default) &lt; at &gt; org.apache.sling.samples.accessmanager.ui --- mojoSucceeded org.apache.maven.plugins:maven-remote-resources-plugin:1.1(default) mojoStarted org.apache.maven.plugins:maven-resources-plugin:2.4.3(default-resources)[INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) &lt; at &gt; org.apache.sling.samples.accessmanager.ui --- [INFO] Copying 14 resources [INFO] Copying 3 resources mojoSucceeded org.apache.maven.plugins:maven-resources-plugin:2.4.3(default-resources) mojoStarted org.apache.maven.plugins:maven-antrun-plugin:1.6(default)[INFO] Executing tasks main: [echo] **************** WARNING (SLING-443/SLING-1782) ****************************** [echo] On most platforms, you'll get OutOfMemoryErrors when building unless you set [ec</pre> Apache Jenkins Server 2012-05-23T11:25:20 http://permalink.gmane.org/gmane.comp.apache.sling.devel/26222 <pre>See &lt;https://builds.apache.org/job/sling-contrib-1.5/876/&gt; ------------------------------------------ [...truncated 3293 lines...] [INFO] [INFO] --- ianal-maven-plugin:1.0-alpha-1:verify-legal-files (default) &lt; at &gt; org.apache.sling.scripting.xproc --- mojoSucceeded org.codehaus.mojo:ianal-maven-plugin:1.0-alpha-1(default) [INFO] Installing &lt;https://builds.apache.org/job/sling-contrib-1.5/ws/contrib-1.5/scripting/xproc/target/org.apache.sling.scripting.xproc-2.0.0-SNAPSHOT.jar&gt; to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.scripting.xproc/2.0.0-SNAPSHOT/org.apache.sling.scripting.xproc-2.0.0-SNAPSHOT.jar mojoStarted org.apache.maven.plugins:maven-install-plugin:2.3.1(default-install)[INFO] Installing &lt;https://builds.apache.org/job/sling-contrib-1.5/ws/contrib-1.5/scripting/xproc/pom.xml&gt; to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/sling/org.apache.sling.scripting.xproc/2.0.0-SNAPSHOT/org.apache.sling.scripting.xproc-2.0.0-SNAPSHOT.pom [INFO] Installing </pre> Apache Jenkins Server 2012-05-23T11:22:47 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.apache.sling.devel