Make our first release available on central Maven repo? (was: Problems with dependency paths)

Hi Ian, On Thu, Jun 11, 2009 at 11:59 PM, Ian Bostoni...@tfd.co.uk wrote: ...I have a jar that depends on  org.apache.sling:org.apache.sling.engine:jar:2.0.4-incubator, which since its released I think is a reasonable thing to do... Of course. . But if you clean out your maven repo (rm -rf

Re: load root node from a bundle

Hi Andreas, On Fri, Jun 12, 2009 at 6:08 AM, Andreas Kolleggerandr...@kollegger.name wrote: The content loading web page [1] is pretty helpful for getting initial content for directories below root. But, is it possible to use a content definition file for the root node? ... Yes, see

Re: Make our first release available on central Maven repo? (was: Problems with dependency paths)

Hi, Yes at the time of our first release poddlings had to deploy to the incubator repository at http://people.apache.org/repo/m2-incubating-repository And, yes, I agree we should probably deploy this to central, now. Central being managed through the Nexus repository nowadays, it would

Re: Make our first release available on central Maven repo? (was: Problems with dependency paths)

Felix Meschberger wrote: Hi, Yes at the time of our first release poddlings had to deploy to the incubator repository at http://people.apache.org/repo/m2-incubating-repository And, yes, I agree we should probably deploy this to central, now. Central being managed through the Nexus

Re: Make our first release available on central Maven repo? (was: Problems with dependency paths)

On 12 Jun 2009, at 07:37, Bertrand Delacretaz wrote: That's correct, the artifacts of the first Sling release are in http://people.apache.org/repo/m2-incubating-repository/org/apache/sling/org.apache.sling.commons.osgi/ Ahh, ok thanks, Ian

Re: Make our first release available on central Maven repo? (was: Problems with dependency paths)

Hi, On Fri, Jun 12, 2009 at 8:46 AM, Felix Meschbergerfmesc...@gmail.com wrote: My first try to would be to checkout the Sling 3 tag and deploy it to repository.apache.org setting the altDeploymentRepository property appropriately. I'd rather not do that, as then we'd have separate copies of

Re: Make our first release available on central Maven repo? (was: Problems with dependency paths)

Hi, Jukka Zitting schrieb: Hi, On Fri, Jun 12, 2009 at 8:46 AM, Felix Meschbergerfmesc...@gmail.com wrote: My first try to would be to checkout the Sling 3 tag and deploy it to repository.apache.org setting the altDeploymentRepository property appropriately. I'd rather not do that, as

Sling Artifacts from incubator repository

Hi all, In the incubating Sling project we deployed the initial release to the incubator maven 2 repository instead of the central mirror as it was custom until a few months ago. Now that we use repository.a.o it would be cool and good for our users to have the artifacts available from

[jira] Created: (SLING-1004) The folder where Sling servlets store their configuration should be configurable at deployment

The folder where Sling servlets store their configuration should be configurable at deployment -- Key: SLING-1004 URL: https://issues.apache.org/jira/browse/SLING-1004

Re: Sling configuration

Salut B. Just created SLING-1004 I did not bother reading any guideline for issue creation but I hope you'll like it :) Cheers, Claude On Thu, Jun 11, 2009 at 2:36 PM, Bertrand Delacretazbdelacre...@apache.org wrote: Salut Claude, On Thu, Jun 11, 2009 at 2:07 PM, Claude

[jira] Commented: (SLING-1004) The folder where Sling servlets store their configuration should be configurable at deployment

[ https://issues.apache.org/jira/browse/SLING-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12718849#action_12718849 ] Felix Meschberger commented on SLING-1004: -- Actually, the default Sling web app

Re: Sling configuration

Thanks for reporting. I added the findings of the mail thread as implementation notes. Regards Felix Claude Vedovini schrieb: Salut B. Just created SLING-1004 I did not bother reading any guideline for issue creation but I hope you'll like it :) Cheers, Claude On Thu, Jun 11, 2009

[jira] Assigned: (SLING-1003) Integration of 3rd party servlet filters problematic

[ https://issues.apache.org/jira/browse/SLING-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-1003: Assignee: Felix Meschberger Integration of 3rd party servlet filters problematic

[jira] Resolved: (SLING-1003) Integration of 3rd party servlet filters problematic

[ https://issues.apache.org/jira/browse/SLING-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-1003. -- Resolution: Fixed Fix Version/s: Engine 2.0.6 Thanks for reporting the bug.

Re: Integrate a Servlet Filter: init-params

Hi, Christian Sprecher schrieb: Felix Meschberger schrieb: Hi, Yes. And if you have the scr plugin generate the Metatype data (not setting metatype=no on the @scr.component tag) you will be able to configure the properties on the Configuration page of the Web Console. Wow, it works.

[jira] Created: (SLING-1005) JcrResourceResolver2.map should consider request path info for mapping

JcrResourceResolver2.map should consider request path info for mapping -- Key: SLING-1005 URL: https://issues.apache.org/jira/browse/SLING-1005 Project: Sling Issue Type:

[jira] Commented: (SLING-1005) JcrResourceResolver2.map should consider request path info for mapping

[ https://issues.apache.org/jira/browse/SLING-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12718864#action_12718864 ] Felix Meschberger commented on SLING-1005: -- Fixed this as described above in Rev.

[jira] Commented: (SLING-490) SlingStatusServlet - find out whether a Sling application is ready after startup

[ https://issues.apache.org/jira/browse/SLING-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12718894#action_12718894 ] Bertrand Delacretaz commented on SLING-490: --- Added a new extensions/systemstatus

JSONQueryServlet questions

I'm trying to get back a multivalued property from the JSON Query Servlet, but it appears that that doesn't work. Here's what I did: curl -Ftitle=some title text -Ftext=some body text content \ -Ftest=1 -Ftest=2 http://admin:ad...@localhost:8080/some/new/content That posts successfully, and I

[jira] Commented: (SLING-490) SlingStatusServlet - find out whether a Sling application is ready after startup

[ https://issues.apache.org/jira/browse/SLING-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12718923#action_12718923 ] Felix Meschberger commented on SLING-490: - Thanks for taking a stab at this. Here

Versions of new modules

Hi all, It seems to be custom to add new modules with versions like 2.0.5-incubator-SNAPSHOT. I think this is not very sexy and might even be misleading. I suggest we add new modules at version 0.9.0-incubator-SNAPSHOT such that we can release the first version as 1.0.0-incubator. Historical

Re: JSONQueryServlet questions

Hi Stuart, D. Stuart Freeman schrieb: I'm trying to get back a multivalued property from the JSON Query Servlet, but it appears that that doesn't work. Here's what I did: curl -Ftitle=some title text -Ftext=some body text content \ -Ftest=1 -Ftest=2

Re: JSONQueryServlet questions

On Fri, Jun 12, 2009 at 08:18:01PM +0200, Felix Meschberger wrote: Hi Stuart, D. Stuart Freeman schrieb: I'm trying to get back a multivalued property from the JSON Query Servlet, but it appears that that doesn't work. Here's what I did: curl -Ftitle=some title text -Ftext=some

[jira] Created: (SLING-1006) JsonQueryServlet does not return multi-value properties

JsonQueryServlet does not return multi-value properties --- Key: SLING-1006 URL: https://issues.apache.org/jira/browse/SLING-1006 Project: Sling Issue Type: Bug Components:

Re: JSONQueryServlet questions

Hi Stuart, After re-reading the JsonQueryServlet, I saw the bug. It is not related to any JCR query stuff but to how we add properties to the result as per the property parameters. This is done by only accessing the property value as a single value which fails for multi-value properties ... I

[jira] Resolved: (SLING-1006) JsonQueryServlet does not return multi-value properties

[ https://issues.apache.org/jira/browse/SLING-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-1006. -- Resolution: Fixed I have committed a fix in Rev. 784278. The JsonQueryServlet now

Re: JSONQueryServlet questions

I have committed a fix in Rev. 784278. You might want to update the servlets/get bundle and crosscheck. Thanks. Regards Felix Felix Meschberger schrieb: Hi Stuart, After re-reading the JsonQueryServlet, I saw the bug. It is not related to any JCR query stuff but to how we add properties to