[jira] Created: (SLING-949) Upgrade to Felix Framework release 1.6.1
Upgrade to Felix Framework release 1.6.1 Key: SLING-949 URL: https://issues.apache.org/jira/browse/SLING-949 Project: Sling Issue Type: Improvement Components: Launchpad Affects Versions: Launchpad Base 2.0.2 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Launchpad Base 2.0.4 The Apache Felix project is voting on the release of the framework release 1.6.1. If the vote is successfull in time for our release, we should upgrade. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-917) Use repository.apache.org for deployments
[ https://issues.apache.org/jira/browse/SLING-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-917: Component/s: General Summary: Use repository.apache.org for deployments (was: Snapshots of Sling artifacts at repository.apache.org) Changing summary to indicate that we should completely switch to using repository.apache.org for both releases and snapshots. > Use repository.apache.org for deployments > - > > Key: SLING-917 > URL: https://issues.apache.org/jira/browse/SLING-917 > Project: Sling > Issue Type: Task > Components: General >Reporter: Bertrand Delacretaz > > See INFRA-1896 for getting access to repository.apache.org . > Once that's done, we'll need to configure http://vmbuild.apache.org to push > snapshots there. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-950) Remove old ResourceResolver implementation
Remove old ResourceResolver implementation -- Key: SLING-950 URL: https://issues.apache.org/jira/browse/SLING-950 Project: Sling Issue Type: Task Affects Versions: JCR Resource 2.0.4 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: JCR Resource 2.0.4 As of SLING- a new ResourceResolver implementation -- JcrResourceResovler2 -- has been implemented and put into use. The old implementation -- JcrResourceResolver -- still exists and may still be used setting a configuration switch. After having the new resolver in use for some time now, the old one should be removed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Hudson build is still unstable: sling-contrib-1. 5 » Apache Sling Launchpad Contrib Testing #5
On Thu, Apr 30, 2009 at 2:43 AM, Apache Hudson Server wrote: > See > http://hudson.zones.apache.org/hudson/job/sling-contrib-1.5/org.apache.sling$org.apache.sling.launchpad.contrib-testing/5/ FYI, this is due to SLING-946 -Bertrand
Hudson build is still unstable: sling-contrib- 1.5 » Apache Sling Launchpad Contrib Testing #6
See http://hudson.zones.apache.org/hudson/job/sling-contrib-1.5/org.apache.sling$org.apache.sling.launchpad.contrib-testing/6/
Hudson build is still unstable: sling-contrib- 1.5 » Apache Sling Launchpad Contrib Testing #7
See http://hudson.zones.apache.org/hudson/job/sling-contrib-1.5/org.apache.sling$org.apache.sling.launchpad.contrib-testing/7/
[jira] Commented: (SLING-946) jcrinstall integration tests fail on our Hudson build server
[ https://issues.apache.org/jira/browse/SLING-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704694#action_12704694 ] Bertrand Delacretaz commented on SLING-946: --- After my changes of today the error is java.io.IOException: Output file not found after calling bnd.doWrap at org.apache.sling.launchpad.webapp.integrationtest.jcrinstall.util.BundleCloner.cloneBundle(BundleCloner.java:60) so it looks like bnd is not running as it should on this test environment. > jcrinstall integration tests fail on our Hudson build server > > > Key: SLING-946 > URL: https://issues.apache.org/jira/browse/SLING-946 > Project: Sling > Issue Type: Bug > Components: JCR Install >Reporter: Bertrand Delacretaz >Priority: Minor > > The jcrinstall integration tests in the > http://hudson.zones.apache.org/hudson/view/Sling/job/sling-contrib-1.5 build > fail with errors like > java.io.FileNotFoundException: > /home/hudson/hudson-slave/workspace/sling-contrib-1.5/contrib-1.5/launchpad/testing/target/launchpad-bundles/resources/bundles/15/cloned-bundles/observer_clone_1240993668015.jar > For some reason, the tests cannot find the cloned bundles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
JCR2 upgrade plans ?
Hi, With JR trunk having branched 1.x off and now heading for 2.0. What plans, if any does Sling have for moving to 2.0 and 283 support? I am trying to plan where I should be directing internal and community effort in Sakai being just about ready to commit whole heartedly to the JR15/Sling DefaultAccessManager and other core parts. Thanks Ian
Welcome Mike Mueller as Documentation Committer
Hi all, Based on his sustained contributions to the Sling documentation in the last months, the Sling PPMC has decided to give Mike Müller write access to the Sling website content wiki. Thanks again, Mike, for your contributions and keep up the good work. Regards Felix
Hudson build is still unstable: sling-contrib- 1.5 » Apache Sling Launchpad Contrib Testing #8
See http://hudson.zones.apache.org/hudson/job/sling-contrib-1.5/org.apache.sling$org.apache.sling.launchpad.contrib-testing/8/
Re: Welcome Mike Mueller as Documentation Committer
On Thu, Apr 30, 2009 at 7:55 PM, Felix Meschberger wrote: > ...Based on his sustained contributions to the Sling documentation in the > last months, the Sling PPMC has decided to give Mike Müller write access > to the Sling website content wiki... Welcome Mike - this shows that contributions to Sling are not *only* about code! -Bertrand
[VOTE] Update to Community Roles and Processes
Hi all, An update draft of the Sling Community Roles and Processes as been on the site since June 2008 [1]. This draft proposes to separate the roles of Committers and (P)PMC members to lower the entry barrier for committership. Additionally I added an explicit note, that regular contributors of documentation may be elected as Committers just like regular contributors of code. I think it is about time to put this draft on vote and accept or drop it. So lets start a vote on this the current draft for the Sling Community Roles and Processes [1]: [ ] +1 Yes [ ] -1 No, because ... This is a majority vote running until Tuesday, 5. May 2009 (due to long weekend in large parts of Europe). Thanks and Regards Felix [1] http://cwiki.apache.org/SLINGxSITE/apache-sling-community-roles-and-processes.html