Re: Creating a user as anonymous (SLING-2465)
It looks like all it needs is the path of the created user. The created user should always be the first Modification in the changes list so you can probably just get the user path from there if the returned user is null. See patch [1]. Regards, Eric 1. http://pastebin.com/0DX4i8fK On Wed, May 16, 2012 at 12:25 PM, Carl Hall c...@hallwaytech.com wrote: SLING-2465 outlines that when creating a user (self-registration=true) as an anonymous user, an NPE is thrown because the anonymous user can't see the newly created user and the User is used to set the path on the response. In talking with Justin, I've created a patch[1] to impersonate a session with the new user but closing the impersonated session in createUser(..) creates a problem of using the returned User (This session has been closed.). Does anyone see a nice way to get around this? I can think of some terrible hacks but no one wants that. :) Thanks, Carl 1 http://pastebin.com/6DMeiih0
Update parent POM to JCR 2.0
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
Jenkins build is still unstable: sling-trunk-1.6 #1327
See https://builds.apache.org/job/sling-trunk-1.6/changes
Re: [VOTE] Four new releases
+1 Carsten 2012/5/18 Carsten Ziegeler cziege...@apache.org: 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 72 hours. Regards -- Carsten Ziegeler cziege...@apache.org -- Carsten Ziegeler cziege...@apache.org
Re: Update parent POM to JCR 2.0
+1 Carsten 2012/5/19 Justin Edelson justinedel...@gmail.com: +1 On May 19, 2012, at 5:50 AM, Felix Meschberger fmesc...@adobe.com wrote: 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 -- Carsten Ziegeler cziege...@apache.org
[jira] [Commented] (SLING-2002) Migrate the Sling website to the ASF CMS
[ https://issues.apache.org/jira/browse/SLING-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279623#comment-13279623 ] Felix Meschberger commented on SLING-2002: -- Some enhancements to the current setup: * Changed the H1 and H2 tag CSS to use a yellow background to structure the pages * Added last modification information to the rendered page (SVN revision, date, committer). This is defined in the skeleton.html template while the actual information is retrieved from SVN and prepared for the template in the view.pm module. * Fixed breadcrumb generation. See also the new sample page. * Started working on a new page (only available in the staging area for now): http://sling.staging.apache.org/the-sling-engine/sling-properties.html Migrate the Sling website to the ASF CMS Key: SLING-2002 URL: https://issues.apache.org/jira/browse/SLING-2002 Project: Sling Issue Type: Task Components: Site Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz As discussed at http://markmail.org/thread/vbdqqnbaghpcxwp5 I'll try the tools mentioned at http://wiki.apache.org/general/ApacheCms2010#Migrating_from_Confluence -- 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
Sling Site and CMS
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
