http://blog.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://comments.gmane.org/gmane.comp.apache.sling.devel/26264 <pre> [ https://issues.apache.org/jira/browse/SLING-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1476. ----------------------------------- -- 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> Carsten Ziegeler (JIRA 2012-05-26T14:30:25 http://comments.gmane.org/gmane.comp.apache.sling.devel/26243 <pre>See &lt;https://builds.apache.org/job/sling-trunk-1.6/1331/changes&gt; </pre> Apache Jenkins Server 2012-05-25T19:54:23 http://comments.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://comments.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://comments.gmane.org/gmane.comp.apache.sling.devel/26220 <pre>See &lt;https://builds.apache.org/job/sling-trunk-1.5/1662/changes&gt; </pre> Apache Jenkins Server 2012-05-23T10:28:47 http://comments.gmane.org/gmane.comp.apache.sling.devel/26219 <pre>Nicolas Peltier created SLING-2492: -------------------------------------- Summary: add documentation on SlingPostServlet's post processor Key: SLING-2492 URL: https://issues.apache.org/jira/browse/SLING-2492 Project: Sling Issue Type: Wish Components: Documentation Reporter: Nicolas Peltier Priority: Minor I've started a documentation on https://cwiki.apache.org/confluence/display/SLING/Creating+a+SlingPostServlet+post+processor for integration in http://sling.apache.org/site/manipulating-content-the-slingpostservlet-servletspost.html -- 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> Nicolas Peltier (JIRA 2012-05-23T08:43:41 http://comments.gmane.org/gmane.comp.apache.sling.devel/26215 <pre>Chris Papagrigoriou created SLING-2491: ------------------------------------------ Summary: How can I change the self.registration.enabled property in java? Key: SLING-2491 URL: https://issues.apache.org/jira/browse/SLING-2491 Project: Sling Issue Type: Task Components: JCR Affects Versions: JCR Jackrabbit User Manager 2.1.0 Environment: Xubuntu Reporter: Chris Papagrigoriou Hey I kinda can't find out how to change the the self.registration.enabled property of the CreateUserServlet. I tried it via the ConfigurationAdmin but it doesn't seem to work. Can anyone tell me how to change it? -- 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> Chris Papagrigoriou (JIRA 2012-05-23T00:42:41 http://comments.gmane.org/gmane.comp.apache.sling.devel/26211 <pre>Dear Apache Sling developers and users, after last year's edition (http://adaptto.mixxt.de/) which got very good feedback from attendees, Provision and Adobe would like to organize and invite you to an event focused on our technologies, in Berlin, Germany, on September 26th-28th, called .adaptTo(Berlin) 2012. A brief description of the event follows below; please note that this is kept in a draft fashion to let the communities (Sling, Jackrabbit) shape its final content and organization. So please let us know if you are interested, what suggestions and what questions you would like to post, and, most of all: what you want to present or you would like to see presented at .adaptTo(Berlin) This is a brief description which we also put up on the web site: .adaptTo(Berlin) is a technical meetup focused on the technical stack of Apache Sling including Apache Jackrabbit and Apache Felix and is adressed to all developers using this stack or parts of it. Specific content will be focused on Adobe CQ5, the commerci</pre> Carsten Ziegeler 2012-05-22T15:58:12 http://comments.gmane.org/gmane.comp.apache.sling.devel/26195 <pre>Hi, would like to contribute to sling doc (post processor part of the sling post servlet's "manipulating content" page), but wasn't able to understand where is the info i should patch :-) Could you tell me where to find it? Also, should i create a JIRA then to post the patch? Cheers, Nicolas </pre> Nicolas Peltier 2012-05-21T12:13:17 http://comments.gmane.org/gmane.comp.apache.sling.devel/26189 <pre>Hi all, I have been giving some quality time to the Sling site project [1] (see also SLING-2002 [2]) again and have started a new page just to get the feel for Markdown. Granted we have a few open issues like the confluence to markdown conversion mangling with the {{}} constructs (creating italic instead of code), I think overall the experience for me has been very positive and feedback on the site (well, we just have staging for now) is just great compared to Confluence. I think the biggest open issue is the download page. I think we can solve this with a download page template. The rest we can fix over time. So, I think it is about time to just switch to ASF CMS. What needs to be done ? * Setup the staging to production publishing * Implement a download page template * Make SLINGxSITE space on cwiki read-only * Over time fix the pages WDYT ? Regards Felix </pre> Felix Meschberger 2012-05-19T23:09:04 http://comments.gmane.org/gmane.comp.apache.sling.devel/26180 <pre>Hi all, Until now we have JCR API 1.0 as a managed dependency in the parent POM. If a bundle requires JCR 2.0 API that version is explicitly noted in the bundle's POM. Now, JCR 2.0 has been out for quite a while and I doubt there are still current implementations of JCR 1.0 out there. So, I think, that we might want to update the managed dependency to 2.0 as an exception to our rule stating to only refer to the lowest version providing the required API. WDYT ? Regards Felix </pre> Felix Meschberger 2012-05-19T09:50:14 http://comments.gmane.org/gmane.comp.apache.sling.devel/26177 <pre>Chris Papagrigoriou created SLING-2490: ------------------------------------------ Summary: User can't add Childnodes after receiving jcr:write and jcr:read privileges Key: SLING-2490 URL: https://issues.apache.org/jira/browse/SLING-2490 Project: Sling Issue Type: Bug Components: Authentication, JCR Affects Versions: JCR Jackrabbit Access Manager 2.1.0 Environment: Xubuntu Reporter: Chris Papagrigoriou Priority: Critical Though I granted jcr:read and jcr:write to my user, it is not possible for him to add any Child nodes. He is able to delete knows and to set properties though. Trying curl -X MKCOL -u Odin:Odin http://localhost:8080/content/private/Odin/apps (jcr:write and jcr:read were given for the Odin Folder) gives me an Internal Server error 500. Trying via the sling Explorer gives me: javax.jcr.AccessDeniedException: Access denied. -- This message is automatically generated by </pre> Chris Papagrigoriou (JIRA 2012-05-18T23:45:07 http://comments.gmane.org/gmane.comp.apache.sling.devel/26169 <pre> [ https://issues.apache.org/jira/browse/SLING-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-1338. ------------------------------------ Close after release. -- 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-18T23:15:09 http://comments.gmane.org/gmane.comp.apache.sling.devel/26154 <pre>Felix Meschberger created SLING-2489: ---------------------------------------- Summary: Updating the framework with system bundle update fails Key: SLING-2489 URL: https://issues.apache.org/jira/browse/SLING-2489 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Base 2.4.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Launchpad Base 2.4.2 The Main.Notified.updated(File) method first calls Main.stopSling to properly stop and cleanup after sling's shutdown and the calls Main.startSling to install the new framework and launch it. The problem is that stopSling sets the launcher field to null and thus startSling assuming the launcher field to not be null to fail with a NullPointerException -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.</pre> Felix Meschberger (JIRA 2012-05-18T23:13:06 http://comments.gmane.org/gmane.comp.apache.sling.devel/26149 <pre>Felix Meschberger created SLING-2488: ---------------------------------------- Summary: Update jcr.api dependency Key: SLING-2488 URL: https://issues.apache.org/jira/browse/SLING-2488 Project: Sling Issue Type: Improvement Components: Testing Affects Versions: JUnit Scriptable Tests Provider 1.0.6 Reporter: Felix Meschberger Assignee: Felix Meschberger The bundle depends on the old o.a.s.jcr.api 2.0.2-incubator bundle which exports the JCR API at version 1.0. With the update to the latest bundle plugin this export now causes the JUnit Scriptable Tests Provider bundle to import JCR API at (1.0,2.0] which of course does not work. Updating the dependency to 2.0.4 and adding JCR as an explicit dependency (inheriting the version number from dependency management) works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: htt</pre> Felix Meschberger (JIRA 2012-05-18T17:25:07 http://comments.gmane.org/gmane.comp.apache.sling.devel/26147 <pre>Hi, This vote is about four modules: Installer Configuration Factory 1.0.8 https://issues.apache.org/jira/browse/SLING/fixforversion/12319440 Engine 2.2.6 https://issues.apache.org/jira/browse/SLING/fixforversion/12316841 Scripting Core 2.0.22 https://issues.apache.org/jira/browse/SLING/fixforversion/12319469 i18n 2.2.2 https://issues.apache.org/jira/browse/SLING/fixforversion/12319474 For some reason, the stuff went into two staging repos... Staging repository: https://repository.apache.org/content/repositories/orgapachesling-099/ https://repository.apache.org/content/repositories/orgapachesling-101/ 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 099 /tmp/sling-staging sh check_staged_release.sh 101 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This vote will be open for</pre> Carsten Ziegeler 2012-05-18T15:49:32 http://comments.gmane.org/gmane.comp.apache.sling.devel/26145 <pre>Carsten Ziegeler created SLING-2487: --------------------------------------- Summary: Check / Improve installer logging Key: SLING-2487 URL: https://issues.apache.org/jira/browse/SLING-2487 Project: Sling Issue Type: Bug Components: Installer Affects Versions: Installer Core 3.3.6 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Installer Core 3.3.8 We should check the logging of the installer and its task and see where we might need additional log messages. Especially all tasks should do proper logging. For example the refresh bundle task does not log its action -- 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> Carsten Ziegeler (JIRA 2012-05-18T15:11:07 http://comments.gmane.org/gmane.comp.apache.sling.devel/26136 <pre>Felix Meschberger created SLING-2486: ---------------------------------------- Summary: Log STARTING and STOPPING bundle events Key: SLING-2486 URL: https://issues.apache.org/jira/browse/SLING-2486 Project: Sling Issue Type: Improvement Components: Commons Affects Versions: Commons Log Service 1.0.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Commons Log Service 1.0.2 The LogService specification mandates bundle events to be logged with the exception of the STARTING and STOPPING events. Therefore the Sling implementation does not log either of them and implements a regular bundle listener. To better support troubleshooting, it would be helpful to also have the STARTING and STOPPING events logged and for all events to be synchronously logged. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administr</pre> Felix Meschberger (JIRA 2012-05-18T09:58:07 http://comments.gmane.org/gmane.comp.apache.sling.devel/26132 <pre>Carsten Ziegeler created SLING-2485: --------------------------------------- Summary: AdapterWebConsolePlugin is not synchronized Key: SLING-2485 URL: https://issues.apache.org/jira/browse/SLING-2485 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Adapter 2.0.12 Reporter: Carsten Ziegeler Fix For: Adapter 2.0.14 The web console plugin uses lists and maps which might be accessed concurrently and result in concurrent modification exceptions -- 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> Carsten Ziegeler (JIRA 2012-05-18T09:26:11 http://comments.gmane.org/gmane.comp.apache.sling.devel/26123 <pre>Robert Munteanu created SLING-2484: -------------------------------------- Summary: Sling parent should map various plugin executions to ignore Key: SLING-2484 URL: https://issues.apache.org/jira/browse/SLING-2484 Project: Sling Issue Type: Task Components: General Affects Versions: Parent 13 Reporter: Robert Munteanu Priority: Minor Following the discussion on sling-dev [0] I suggest that the following plugin executions should be mapped to ignore in Eclipse, rather than execute: * maven-dependency-plugin:unpack/copy-dependencies * maven-antrun-plugin:run * maven-scr-plugin:scr [0]: http://mail-archives.apache.org/mod_mbox/sling-dev/201205.mbox/browser -- 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://ww</pre> Robert Munteanu (JIRA 2012-05-18T07:56:01 http://comments.gmane.org/gmane.comp.apache.sling.devel/26101 <pre> [ https://issues.apache.org/jira/browse/SLING-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-1579. ----------------------------------- -- 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> Carsten Ziegeler (JIRA 2012-05-18T07:49:00 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.apache.sling.devel