Re: Build error

On Fri, May 23, 2008 at 12:56 AM, Christophe Lombart [EMAIL PROTECTED] wrote: ...yep, it works after moving my maven repo in a folder without space. Sorry for the noise... Thanks for reporting, added to http://incubator.apache.org/sling/site/maventipsandtricks.html (should be updated in a few

[jira] Created: (SLING-474) Reorder modification operation processing

Reorder modification operation processing - Key: SLING-474 URL: https://issues.apache.org/jira/browse/SLING-474 Project: Sling Issue Type: Improvement Components: Servlets Post

[jira] Commented: (SLING-471) LogService to implement JCL 1.1.1

[ https://issues.apache.org/jira/browse/SLING-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12599303#action_12599303 ] Niklas Gustavsson commented on SLING-471: - A CLIRR diff between 1.0.4 and 1.1.1 does

Re: [jira] Commented: (SLING-471) LogService to implement JCL 1.1.1

Hi, Taking this discussion to the list... Looking at this report, there is one method - objectId(Object) - which is not clearly destined at creating a LogFactory implementation. So my question with respect to JCL is: Do these bundles really require 1.1.1 as per Import-Package:

[jira] Created: (SLING-475) Create Integration tests for the sling:include tag

Create Integration tests for the sling:include tag -- Key: SLING-475 URL: https://issues.apache.org/jira/browse/SLING-475 Project: Sling Issue Type: Sub-task Components: Scripting

Re: [jira] Commented: (SLING-471) LogService to implement JCL 1.1.1

On Fri, May 23, 2008 at 11:41 AM, Felix Meschberger [EMAIL PROTECTED] wrote: Am Freitag, den 23.05.2008, 11:35 +0200 schrieb Niklas Gustavsson: I would also add that the static fields might actually be used by clients who want to configure the JCL behavior. Well, as far as I can tell,

Re: [jira] Commented: (SLING-471) LogService to implement JCL 1.1.1

On Fri, May 23, 2008 at 11:16 AM, Felix Meschberger [EMAIL PROTECTED] wrote: Looking at this report, there is one method - objectId(Object) - which is not clearly destined at creating a LogFactory implementation. So my question with respect to JCL is: Do these bundles really require 1.1.1 as

Re: [jira] Commented: (SLING-471) LogService to implement JCL 1.1.1

Hi, Am Freitag, den 23.05.2008, 11:35 +0200 schrieb Niklas Gustavsson: On Fri, May 23, 2008 at 11:16 AM, Felix Meschberger [EMAIL PROTECTED] wrote: Looking at this report, there is one method - objectId(Object) - which is not clearly destined at creating a LogFactory implementation. So

Re: [jira] Commented: (SLING-471) LogService to implement JCL 1.1.1

Am Freitag, den 23.05.2008, 11:46 +0200 schrieb Niklas Gustavsson: On Fri, May 23, 2008 at 11:41 AM, Felix Meschberger [EMAIL PROTECTED] wrote: Am Freitag, den 23.05.2008, 11:35 +0200 schrieb Niklas Gustavsson: I would also add that the static fields might actually be used by clients who

[jira] Created: (SLING-476) make maven-jspc-plugin configurable to suppress deletion of .java files

make maven-jspc-plugin configurable to suppress deletion of .java files --- Key: SLING-476 URL: https://issues.apache.org/jira/browse/SLING-476 Project: Sling Issue Type:

[jira] Assigned: (SLING-476) make maven-jspc-plugin configurable to suppress deletion of .java files

[ https://issues.apache.org/jira/browse/SLING-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-476: --- Assignee: Felix Meschberger make maven-jspc-plugin configurable to suppress deletion

[jira] Commented: (SLING-476) make maven-jspc-plugin configurable to suppress deletion of .java files

[ https://issues.apache.org/jira/browse/SLING-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12599385#action_12599385 ] Felix Meschberger commented on SLING-476: - How stupid of me ;-) I coded this and

[jira] Resolved: (SLING-476) make maven-jspc-plugin configurable to suppress deletion of .java files

[ https://issues.apache.org/jira/browse/SLING-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-476. - Resolution: Fixed Fix Version/s: 2.0.0 Thanks for finding this. I have removed the

Support for additional content types in SlingPostServlet

Hi, I am planning to add support for additional content types to the SlingPostServlet that would allow processing Web Forms 2.0, JSON (allowing an effective-round-tripping from Sling.js), XML (in JCR document notation), ATOM (in terms of the Atom publishing protocol). To do this I would

[jira] Assigned: (SLING-462) Endless loop in JobEventHandler

[ https://issues.apache.org/jira/browse/SLING-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-462: -- Assignee: Carsten Ziegeler Endless loop in JobEventHandler

Re: Support for additional content types in SlingPostServlet

On Fri, May 23, 2008 at 6:05 PM, Lars Trieloff [EMAIL PROTECTED] wrote: ... and submitting a patch (on Youtube) This is so 2006. All ASF projects switched to RTF printouts of the patch and filming them on Seesmic ;-) Alex -- Alexander Klimetschek [EMAIL PROTECTED]

Re: Support for additional content types in SlingPostServlet

This sounds like a good option. How do I do this? Lars On May 23, 2008, at 15:34 , Tobias Bocanegra wrote: if the code is very different from the default post servlet, i would create individual ones, that decline service if the headers do not match (felix: this is possible, right?)