[jira] [Created] (SLING-2351) Catch potential exception in query

2012-01-04 Thread Carsten Ziegeler (Created) (JIRA) 
Catch potential exception in query
--

 Key: SLING-2351
 URL: https://issues.apache.org/jira/browse/SLING-2351
 Project: Sling
  Issue Type: Bug
  Components: Extensions
Affects Versions: I18n 2.1.2
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
 Fix For:  i18n 2.2.0


We should catch the SlingException in the loadFully method to avoid breakage of 
the whole i18n component if something in the search goes wrong

--
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

[jira] [Issue Comment Edited] (SLING-2350) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects

2012-01-04 Thread David Gonzalez (Issue Comment Edited) (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179771#comment-13179771
 ] 

David Gonzalez edited comment on SLING-2350 at 1/5/12 4:47 AM:
---

Hi Carsten, thanks!

Appreciate your patience - in more of a ruby/git person :)

Will this change immediately propagate to the main maven repos? I'm
alittle fuzzy on how to force my maven project to use the committed
changes.

I'm using the default repos exposed on netbeans and archiva servlet
under Felix to turn my jcr into a maven repo.

Thanks again

Update: I added the apache snapshots repo to my pom.xml and updated the plugin 
to look for version 2.0.5-incubator thought it doesnt seem to find the change. 
I looked through the pom's at:
https://repository.apache.org/content/groups/snapshots/org/apache/sling/maven-jspc-plugin/2.0.5-SNAPSHOT/
  and didnt see the changes there either.

  was (Author: empire29):
Hi Carsten, thanks!

Appreciate your patience - in more of a ruby/git person :)

Will this change immediately propagate to the main maven repos? I'm
alittle fuzzy on how to force my maven project to use the committed
changes.

I'm using the default repos exposed on netbeans and archiva servlet
under Felix to turn my jcr into a maven repo.

Thanks again

On Jan 4, 2012, at 12:39 PM, "Carsten Ziegeler (Commented) (JIRA)"


  
> Sling Maven JSPC Plugin depends on legacy Sling API lib which does not 
> support adaptable SlingHttpServletRequest objects
> 
>
> Key: SLING-2350
> URL: https://issues.apache.org/jira/browse/SLING-2350
> Project: Sling
>  Issue Type: Improvement
>  Components: Maven Plugins and Archetypes
>Affects Versions:  Maven JSPC Plugin 2.0.4
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
> Maven home: /usr/share/maven
> Java version: 1.6.0_29, vendor: Apple Inc.
> Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.7.2", arch: "x86_64", family: "mac"
>Reporter: David Gonzalez
>Assignee: Carsten Ziegeler
>  Labels: maven-bundle-plugin
> Attachments: pom.xml, pom.xml.diff
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> Buiding Sling-based project using the Maven JSPC Plugin but am getting 
> compilation errors because SlingHttpServletRequest object doesn't have 
> .adaptTo(...) defined.
> Latest Sling API docs state:
>   Starting with Sling API 2.0.6, this [SlingHttpServletRequest] interface 
> also extends the Adaptable interface.
> Sling Maven JSPC Plugin 2.0.4-incubator plugin [1] depends on  "Sling 
> Scripting 2.0.2-incubator" [2] which in turn depends on "Sling API  
> 2.0.2-incubator" which is older than 2.0.6 thus no Adaptable support.
> [1] 
> http://svn.apache.org/repos/asf/sling/tags/maven-jspc-plugin-2.0.4-incubator/pom.xml
> [2] 
> http://svn.apache.org/viewvc/sling/tags/org.apache.sling.scripting.jsp-2.0.2-incubator/pom.xml?view=markup

--
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

Build failed in Jenkins: sling-contrib-1.5 #790

2012-01-04 Thread Apache Jenkins Server 
See 

Changes:

[bdelacretaz] SLING-2347 - startup filter disabler bundle added

[bdelacretaz] SLING-2347 - use whiteboard pattern with StartupInfoProvider 
services

--
[...truncated 3028 lines...]
[INFO] Copying bundle from 
/home/jenkins/.m2/repository/org/apache/sling/org.apache.sling.scripting.scala.forum/0.9.0-SNAPSHOT/org.apache.sling.scripting.scala.forum-0.9.0-SNAPSHOT.jar
 to 

[INFO] Copying bundle from 
/home/jenkins/.m2/repository/org/apache/servicemix/bundles/org.apache.servicemix.bundles.scala-library/2.8.1_1/org.apache.servicemix.bundles.scala-library-2.8.1_1.jar
 to 

[INFO] Copying bundle from 
/home/jenkins/.m2/repository/org/apache/servicemix/bundles/org.apache.servicemix.bundles.scala-compiler/2.8.1_1/org.apache.servicemix.bundles.scala-compiler-2.8.1_1.jar
 to 

[INFO] snapshot 
org.apache.sling:org.apache.sling.scripting.xproc:2.0.0-SNAPSHOT: checking for 
updates from apache.snapshots
[INFO] Copying bundle from 
/home/jenkins/.m2/repository/org/apache/sling/org.apache.sling.scripting.xproc/2.0.0-SNAPSHOT/org.apache.sling.scripting.xproc-2.0.0-SNAPSHOT.jar
 to 

[INFO] snapshot 
org.apache.sling:org.apache.sling.extensions.apt.servlet:2.0.3-SNAPSHOT: 
checking for updates from apache.snapshots
[INFO] Copying bundle from 
/home/jenkins/.m2/repository/org/apache/sling/org.apache.sling.extensions.apt.servlet/2.0.3-SNAPSHOT/org.apache.sling.extensions.apt.servlet-2.0.3-SNAPSHOT.jar
 to 

[INFO] snapshot 
org.apache.sling:org.apache.sling.extensions.apt.parser:2.0.3-SNAPSHOT: 
checking for updates from apache.snapshots
[INFO] Copying bundle from 
/home/jenkins/.m2/repository/org/apache/sling/org.apache.sling.extensions.apt.parser/2.0.3-SNAPSHOT/org.apache.sling.extensions.apt.parser-2.0.3-SNAPSHOT.jar
 to 

[INFO] snapshot 
org.apache.sling.samples:org.apache.sling.samples.path-based.rtp:2.0.5-SNAPSHOT:
 checking for updates from apache.snapshots
Downloading: 
http://repository.apache.org/snapshots/org/apache/sling/samples/org.apache.sling.samples.path-based.rtp/2.0.5-SNAPSHOT/org.apache.sling.samples.path-based.rtp-2.0.5-SNAPSHOT.jar
[INFO] Copying bundle from 
/home/jenkins/.m2/repository/org/apache/sling/samples/org.apache.sling.samples.path-based.rtp/2.0.5-SNAPSHOT/org.apache.sling.samples.path-based.rtp-2.0.5-SNAPSHOT.jar
 to 

[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO] Copying 3 resources
[INFO] [build-helper:reserve-network-port {execution: reserve-network-port}]
[INFO] Reserved port 50812 for http.port
[WARNING] DEPRECATED [tasks]: Use target instead
[INFO] [antrun:run {execution: default}]
[WARNING] Parameter tasks is deprecated, use target instead
[INFO] Executing tasks

main:
 [echo]  WARNING (SLING-443/SLING-1782) 
**
 [echo] On most platforms, you'll get OutOfMemoryErrors when building 
unless you set
 [echo] on 32bit platforms: MAVEN_OPTS="-Xmx256M -XX:MaxPermSize=256M", see 
SLING-443
 [echo] on 64bit platforms: MAVEN_OPTS="-Xmx512M -XX:MaxPermSize=512M", see 
SLING-1782
 [echo] 
**
[INFO] Executed tasks
[INFO] [compiler:compile {execution: default-compile}]
[INFO] No sources to compile
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 50 resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: def

[jira] [Commented] (SLING-2350) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects

2012-01-04 Thread David Gonzalez (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179771#comment-13179771
 ] 

David Gonzalez commented on SLING-2350:
---

Hi Carsten, thanks!

Appreciate your patience - in more of a ruby/git person :)

Will this change immediately propagate to the main maven repos? I'm
alittle fuzzy on how to force my maven project to use the committed
changes.

I'm using the default repos exposed on netbeans and archiva servlet
under Felix to turn my jcr into a maven repo.

Thanks again

On Jan 4, 2012, at 12:39 PM, "Carsten Ziegeler (Commented) (JIRA)"



> Sling Maven JSPC Plugin depends on legacy Sling API lib which does not 
> support adaptable SlingHttpServletRequest objects
> 
>
> Key: SLING-2350
> URL: https://issues.apache.org/jira/browse/SLING-2350
> Project: Sling
>  Issue Type: Improvement
>  Components: Maven Plugins and Archetypes
>Affects Versions:  Maven JSPC Plugin 2.0.4
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
> Maven home: /usr/share/maven
> Java version: 1.6.0_29, vendor: Apple Inc.
> Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.7.2", arch: "x86_64", family: "mac"
>Reporter: David Gonzalez
>Assignee: Carsten Ziegeler
>  Labels: maven-bundle-plugin
> Attachments: pom.xml, pom.xml.diff
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> Buiding Sling-based project using the Maven JSPC Plugin but am getting 
> compilation errors because SlingHttpServletRequest object doesn't have 
> .adaptTo(...) defined.
> Latest Sling API docs state:
>   Starting with Sling API 2.0.6, this [SlingHttpServletRequest] interface 
> also extends the Adaptable interface.
> Sling Maven JSPC Plugin 2.0.4-incubator plugin [1] depends on  "Sling 
> Scripting 2.0.2-incubator" [2] which in turn depends on "Sling API  
> 2.0.2-incubator" which is older than 2.0.6 thus no Adaptable support.
> [1] 
> http://svn.apache.org/repos/asf/sling/tags/maven-jspc-plugin-2.0.4-incubator/pom.xml
> [2] 
> http://svn.apache.org/viewvc/sling/tags/org.apache.sling.scripting.jsp-2.0.2-incubator/pom.xml?view=markup

--
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

[jira] [Commented] (SLING-2350) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects

2012-01-04 Thread Carsten Ziegeler (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179671#comment-13179671
 ] 

Carsten Ziegeler commented on SLING-2350:
-

Many thanks for your patch David. I've committed a slightly modified version in 
revision 1227233 which updates the plugin to the latest Sling API and Scripting 
JSP. Could you please test if that works for you? Thanks!

> Sling Maven JSPC Plugin depends on legacy Sling API lib which does not 
> support adaptable SlingHttpServletRequest objects
> 
>
> Key: SLING-2350
> URL: https://issues.apache.org/jira/browse/SLING-2350
> Project: Sling
>  Issue Type: Improvement
>  Components: Maven Plugins and Archetypes
>Affects Versions:  Maven JSPC Plugin 2.0.4
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
> Maven home: /usr/share/maven
> Java version: 1.6.0_29, vendor: Apple Inc.
> Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.7.2", arch: "x86_64", family: "mac"
>Reporter: David Gonzalez
>Assignee: Carsten Ziegeler
>  Labels: maven-bundle-plugin
> Attachments: pom.xml, pom.xml.diff
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> Buiding Sling-based project using the Maven JSPC Plugin but am getting 
> compilation errors because SlingHttpServletRequest object doesn't have 
> .adaptTo(...) defined.
> Latest Sling API docs state:
>   Starting with Sling API 2.0.6, this [SlingHttpServletRequest] interface 
> also extends the Adaptable interface.
> Sling Maven JSPC Plugin 2.0.4-incubator plugin [1] depends on  "Sling 
> Scripting 2.0.2-incubator" [2] which in turn depends on "Sling API  
> 2.0.2-incubator" which is older than 2.0.6 thus no Adaptable support.
> [1] 
> http://svn.apache.org/repos/asf/sling/tags/maven-jspc-plugin-2.0.4-incubator/pom.xml
> [2] 
> http://svn.apache.org/viewvc/sling/tags/org.apache.sling.scripting.jsp-2.0.2-incubator/pom.xml?view=markup

--
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

[jira] [Updated] (SLING-2350) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects

2012-01-04 Thread David Gonzalez (Updated) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Gonzalez updated SLING-2350:
--

Attachment: pom.xml.diff

Patched pom.xml from trunk.

Updated "org.apache.sling.scripting.jsp" dependency to rely on version 2.0.8)


> Sling Maven JSPC Plugin depends on legacy Sling API lib which does not 
> support adaptable SlingHttpServletRequest objects
> 
>
> Key: SLING-2350
> URL: https://issues.apache.org/jira/browse/SLING-2350
> Project: Sling
>  Issue Type: Improvement
>  Components: Maven Plugins and Archetypes
>Affects Versions:  Maven JSPC Plugin 2.0.4
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
> Maven home: /usr/share/maven
> Java version: 1.6.0_29, vendor: Apple Inc.
> Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.7.2", arch: "x86_64", family: "mac"
>Reporter: David Gonzalez
>Assignee: Carsten Ziegeler
>  Labels: maven-bundle-plugin
> Attachments: pom.xml, pom.xml.diff
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> Buiding Sling-based project using the Maven JSPC Plugin but am getting 
> compilation errors because SlingHttpServletRequest object doesn't have 
> .adaptTo(...) defined.
> Latest Sling API docs state:
>   Starting with Sling API 2.0.6, this [SlingHttpServletRequest] interface 
> also extends the Adaptable interface.
> Sling Maven JSPC Plugin 2.0.4-incubator plugin [1] depends on  "Sling 
> Scripting 2.0.2-incubator" [2] which in turn depends on "Sling API  
> 2.0.2-incubator" which is older than 2.0.6 thus no Adaptable support.
> [1] 
> http://svn.apache.org/repos/asf/sling/tags/maven-jspc-plugin-2.0.4-incubator/pom.xml
> [2] 
> http://svn.apache.org/viewvc/sling/tags/org.apache.sling.scripting.jsp-2.0.2-incubator/pom.xml?view=markup

--
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

[jira] [Updated] (SLING-2350) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects

2012-01-04 Thread David Gonzalez (Updated) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Gonzalez updated SLING-2350:
--

Attachment: (was: pom.xml.diff)

> Sling Maven JSPC Plugin depends on legacy Sling API lib which does not 
> support adaptable SlingHttpServletRequest objects
> 
>
> Key: SLING-2350
> URL: https://issues.apache.org/jira/browse/SLING-2350
> Project: Sling
>  Issue Type: Improvement
>  Components: Maven Plugins and Archetypes
>Affects Versions:  Maven JSPC Plugin 2.0.4
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
> Maven home: /usr/share/maven
> Java version: 1.6.0_29, vendor: Apple Inc.
> Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.7.2", arch: "x86_64", family: "mac"
>Reporter: David Gonzalez
>Assignee: Carsten Ziegeler
>  Labels: maven-bundle-plugin
> Attachments: pom.xml
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> Buiding Sling-based project using the Maven JSPC Plugin but am getting 
> compilation errors because SlingHttpServletRequest object doesn't have 
> .adaptTo(...) defined.
> Latest Sling API docs state:
>   Starting with Sling API 2.0.6, this [SlingHttpServletRequest] interface 
> also extends the Adaptable interface.
> Sling Maven JSPC Plugin 2.0.4-incubator plugin [1] depends on  "Sling 
> Scripting 2.0.2-incubator" [2] which in turn depends on "Sling API  
> 2.0.2-incubator" which is older than 2.0.6 thus no Adaptable support.
> [1] 
> http://svn.apache.org/repos/asf/sling/tags/maven-jspc-plugin-2.0.4-incubator/pom.xml
> [2] 
> http://svn.apache.org/viewvc/sling/tags/org.apache.sling.scripting.jsp-2.0.2-incubator/pom.xml?view=markup

--
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

[jira] [Updated] (SLING-2350) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects

2012-01-04 Thread David Gonzalez (Updated) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Gonzalez updated SLING-2350:
--

Comment: was deleted

(was: SVN Patch for udpates to pom.xml

Updated "org.apache.sling.scripting.jsp" dependency to rely on version 2.0.8)

> Sling Maven JSPC Plugin depends on legacy Sling API lib which does not 
> support adaptable SlingHttpServletRequest objects
> 
>
> Key: SLING-2350
> URL: https://issues.apache.org/jira/browse/SLING-2350
> Project: Sling
>  Issue Type: Improvement
>  Components: Maven Plugins and Archetypes
>Affects Versions:  Maven JSPC Plugin 2.0.4
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
> Maven home: /usr/share/maven
> Java version: 1.6.0_29, vendor: Apple Inc.
> Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.7.2", arch: "x86_64", family: "mac"
>Reporter: David Gonzalez
>Assignee: Carsten Ziegeler
>  Labels: maven-bundle-plugin
> Attachments: pom.xml
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> Buiding Sling-based project using the Maven JSPC Plugin but am getting 
> compilation errors because SlingHttpServletRequest object doesn't have 
> .adaptTo(...) defined.
> Latest Sling API docs state:
>   Starting with Sling API 2.0.6, this [SlingHttpServletRequest] interface 
> also extends the Adaptable interface.
> Sling Maven JSPC Plugin 2.0.4-incubator plugin [1] depends on  "Sling 
> Scripting 2.0.2-incubator" [2] which in turn depends on "Sling API  
> 2.0.2-incubator" which is older than 2.0.6 thus no Adaptable support.
> [1] 
> http://svn.apache.org/repos/asf/sling/tags/maven-jspc-plugin-2.0.4-incubator/pom.xml
> [2] 
> http://svn.apache.org/viewvc/sling/tags/org.apache.sling.scripting.jsp-2.0.2-incubator/pom.xml?view=markup

--
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

[jira] [Updated] (SLING-2350) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects

2012-01-04 Thread David Gonzalez (Updated) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Gonzalez updated SLING-2350:
--

Attachment: pom.xml.diff

SVN Patch for udpates to pom.xml

Updated "org.apache.sling.scripting.jsp" dependency to rely on version 2.0.8

> Sling Maven JSPC Plugin depends on legacy Sling API lib which does not 
> support adaptable SlingHttpServletRequest objects
> 
>
> Key: SLING-2350
> URL: https://issues.apache.org/jira/browse/SLING-2350
> Project: Sling
>  Issue Type: Improvement
>  Components: Maven Plugins and Archetypes
>Affects Versions:  Maven JSPC Plugin 2.0.4
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
> Maven home: /usr/share/maven
> Java version: 1.6.0_29, vendor: Apple Inc.
> Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.7.2", arch: "x86_64", family: "mac"
>Reporter: David Gonzalez
>Assignee: Carsten Ziegeler
>  Labels: maven-bundle-plugin
> Attachments: pom.xml, pom.xml.diff
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> Buiding Sling-based project using the Maven JSPC Plugin but am getting 
> compilation errors because SlingHttpServletRequest object doesn't have 
> .adaptTo(...) defined.
> Latest Sling API docs state:
>   Starting with Sling API 2.0.6, this [SlingHttpServletRequest] interface 
> also extends the Adaptable interface.
> Sling Maven JSPC Plugin 2.0.4-incubator plugin [1] depends on  "Sling 
> Scripting 2.0.2-incubator" [2] which in turn depends on "Sling API  
> 2.0.2-incubator" which is older than 2.0.6 thus no Adaptable support.
> [1] 
> http://svn.apache.org/repos/asf/sling/tags/maven-jspc-plugin-2.0.4-incubator/pom.xml
> [2] 
> http://svn.apache.org/viewvc/sling/tags/org.apache.sling.scripting.jsp-2.0.2-incubator/pom.xml?view=markup

--
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

[jira] [Issue Comment Edited] (SLING-2347) Startup filter: allow requests to be rejected with a 503 during startup

2012-01-04 Thread Bertrand Delacretaz (Issue Comment Edited) (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179623#comment-13179623
 ] 

Bertrand Delacretaz edited comment on SLING-2347 at 1/4/12 4:48 PM:


Startup filter disabler bundle added in revision 1227218 - its Activator 
disables the StartupFilter if found.

With this, the use case is as follows:

1. Start the startupfilter bundle at a low run level, ideally before the Sling 
servlet

2. Any requests return a 503 status until the filter is disabled

3. StartupInfoProvider services can be registered to provide additional 
information about startup progress, returned with the 503 response

4. Start the startupfilter.disabler bundle at a higher run level, when the 
system is ready to accept requests. This disables the startupfilter bundle's 
Filter service, so there's no performance hit once that's done.

  was (Author: bdelacretaz):
Startup filter disabler bundle added in revision 1227218.

With this, the use case is as follows:

1. Start the startupfilter bundle at a low run level, ideally before the Sling 
servlet

2. Any requests return a 503 status until the filter is disabled

3. StartupInfoProvider services can be registered to provide additional 
information about startup progress, returned with the 503 response

4. Start the startupfilter.disabler bundle at a higher run level, when the 
system is ready to accept requests. This disables the startupfilter bundle's 
Filter service, so there's no performance hit once that's done.
  
> Startup filter: allow requests to be rejected with a 503 during startup
> ---
>
> Key: SLING-2347
> URL: https://issues.apache.org/jira/browse/SLING-2347
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
>
> To provide a clear status during startup, especially when that implies 
> automatic application or content upgrades, I have implemented a simple filter 
> that causes all Sling requests to return a 503 status until another component 
> decides that Sling is ready to accept requests.
> The use case is to start the bundle that contains this filter at start level 
> lower than that of the Sling engine, so that the 503 filter kicks in as soon 
> as the Sling servlet starts, with a simple API to provide progress 
> information (returned in the body of the 503 response) and remove the filter 
> when the system is ready.
> I'll add that filter as a new bundle under contrib/extensions.

--
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

[jira] [Resolved] (SLING-2347) Startup filter: allow requests to be rejected with a 503 during startup

2012-01-04 Thread Bertrand Delacretaz (Resolved) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bertrand Delacretaz resolved SLING-2347.


Resolution: Fixed

Startup filter disabler bundle added in revision 1227218.

With this, the use case is as follows:

1. Start the startupfilter bundle at a low run level, ideally before the Sling 
servlet

2. Any requests return a 503 status until the filter is disabled

3. StartupInfoProvider services can be registered to provide additional 
information about startup progress, returned with the 503 response

4. Start the startupfilter.disabler bundle at a higher run level, when the 
system is ready to accept requests. This disables the startupfilter bundle's 
Filter service, so there's no performance hit once that's done.

> Startup filter: allow requests to be rejected with a 503 during startup
> ---
>
> Key: SLING-2347
> URL: https://issues.apache.org/jira/browse/SLING-2347
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
>
> To provide a clear status during startup, especially when that implies 
> automatic application or content upgrades, I have implemented a simple filter 
> that causes all Sling requests to return a 503 status until another component 
> decides that Sling is ready to accept requests.
> The use case is to start the bundle that contains this filter at start level 
> lower than that of the Sling engine, so that the 503 filter kicks in as soon 
> as the Sling servlet starts, with a simple API to provide progress 
> information (returned in the body of the 503 response) and remove the filter 
> when the system is ready.
> I'll add that filter as a new bundle under contrib/extensions.

--
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

[jira] [Commented] (SLING-2347) Startup filter: allow requests to be rejected with a 503 during startup

2012-01-04 Thread Bertrand Delacretaz (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179608#comment-13179608
 ] 

Bertrand Delacretaz commented on SLING-2347:


Whiteboard pattern implemented in revision 1227210

> Startup filter: allow requests to be rejected with a 503 during startup
> ---
>
> Key: SLING-2347
> URL: https://issues.apache.org/jira/browse/SLING-2347
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
>
> To provide a clear status during startup, especially when that implies 
> automatic application or content upgrades, I have implemented a simple filter 
> that causes all Sling requests to return a 503 status until another component 
> decides that Sling is ready to accept requests.
> The use case is to start the bundle that contains this filter at start level 
> lower than that of the Sling engine, so that the 503 filter kicks in as soon 
> as the Sling servlet starts, with a simple API to provide progress 
> information (returned in the body of the 503 response) and remove the filter 
> when the system is ready.
> I'll add that filter as a new bundle under contrib/extensions.

--
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

[jira] [Reopened] (SLING-2347) Startup filter: allow requests to be rejected with a 503 during startup

2012-01-04 Thread Bertrand Delacretaz (Reopened) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bertrand Delacretaz reopened SLING-2347:



Using services for the info providers makes sense, I'll implement that, and 
return the aggregated progress info from all active services in the 503 
response,

> Startup filter: allow requests to be rejected with a 503 during startup
> ---
>
> Key: SLING-2347
> URL: https://issues.apache.org/jira/browse/SLING-2347
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
>
> To provide a clear status during startup, especially when that implies 
> automatic application or content upgrades, I have implemented a simple filter 
> that causes all Sling requests to return a 503 status until another component 
> decides that Sling is ready to accept requests.
> The use case is to start the bundle that contains this filter at start level 
> lower than that of the Sling engine, so that the 503 filter kicks in as soon 
> as the Sling servlet starts, with a simple API to provide progress 
> information (returned in the body of the 503 response) and remove the filter 
> when the system is ready.
> I'll add that filter as a new bundle under contrib/extensions.

--
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

Re: Releases plans for Scripting JSP 2.0.20 and Scripting Core 2.0.20?

2012-01-04 Thread Julian Sedding 
Hi Carsten

Thanks a lot, I much appreciate it!

Regards
Julian



On Tue, Jan 3, 2012 at 3:14 PM, Carsten Ziegeler  wrote:
> Hi Julian,
>
> yes, I have those on my agenda as well. I plan to have them in the
> third "release wave" (the first just started)
>
> Regards
> Carsten
>
> 2012/1/3 Julian Sedding :
>> Hello
>>
>> Are there any plans for releasing Scripting JSP 2.0.20 and Scripting
>> Core 2.0.20?
>>
>> The project I'm working on depends on fixes for SLING-2218 and
>> SLING-2341. It would be great to get these two bundles released by the
>> beginning of February, so we don't need to depend on and manage
>> internal releases of these bundles. Thank you very much in advance.
>>
>> Regards
>> Julian
>
>
>
> --
> Carsten Ziegeler
> cziege...@apache.org

[jira] [Resolved] (SLING-2215) DavEx servlet creates a jackrabbit/tmp directory

2012-01-04 Thread Carsten Ziegeler (Resolved) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler resolved SLING-2215.
-

   Resolution: Fixed
Fix Version/s: JCR DavEx 1.1.0

This has been fixed by SLING-2301

> DavEx servlet creates a jackrabbit/tmp directory
> 
>
> Key: SLING-2215
> URL: https://issues.apache.org/jira/browse/SLING-2215
> Project: Sling
>  Issue Type: Bug
>Affects Versions: JCR DavEx 1.0.0
>Reporter: Jukka Zitting
>Priority: Minor
> Fix For: JCR DavEx 1.1.0
>
> Attachments: 
> 0001-SLING-2215-DavEx-servlet-creates-a-jackrabbit-tmp-di.patch
>
>
> The DavEx servlet bundle added in SLING-1393 doesn't set the "home" and 
> "temp-directory" init parameters of the JcrRemotingServlet base class it uses 
> from Jackrabbit. As a result Jackrabbit defaults to "jackrabbit/tmp" as the 
> location
> for temporary files, and creates such a directory under the current working 
> directory.
> This problem is solved in the latest Jackrabbit trunk as of JCR-3029 where 
> the default location for temporary files was set
> to the standard one defined by the java.io.tmpdir system property, so I guess 
> the easiest way to solve this is simply to
> upgrade the dependency in Sling once the Jackrabbit 2.3.0 release is 
> available.

--
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

[jira] [Resolved] (SLING-1081) fsresource: allow to adapt to ValueMap

2012-01-04 Thread Carsten Ziegeler (Resolved) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler resolved SLING-1081.
-

Resolution: Fixed

Thanks for your patch Stefan - I've applied it in revision 1227076

> fsresource: allow to adapt to ValueMap
> --
>
> Key: SLING-1081
> URL: https://issues.apache.org/jira/browse/SLING-1081
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: File System Resource Provider 1.0.2
>Reporter: Stefan Seifert
>Assignee: Carsten Ziegeler
> Fix For: File System Resource Provider 1.0.4
>
> Attachments: 090812_SLING-1081_fsresource_valuemap.patch, 
> 111202_SLING-1081_fsresource_valuemap.patch
>
>
> the fsresource provider is used often to map a maven bundle project in the 
> sling instance allowing to see changes in file without redeployment of the 
> bundle.
> some sling applications accessing such resources always assume they are 
> reading from JCR and try to adapt the resource to a ValueMap, which returns 
> null for fsresources.
> this is of course a bug in this "some applications", but because fsresource 
> is often used in such a scenario it would be helpful to support a simple 
> adapting to ValueMap in the FsResource class.
> patch attached.

--
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

[jira] [Resolved] (SLING-2051) Sling does not shut down cleanly on Windows Server 2008

2012-01-04 Thread Carsten Ziegeler (Resolved) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler resolved SLING-2051.
-

   Resolution: Fixed
Fix Version/s: Launchpad Builder 6

So this is fixed with a newer event admin release

> Sling does not shut down cleanly on Windows Server 2008
> ---
>
> Key: SLING-2051
> URL: https://issues.apache.org/jira/browse/SLING-2051
> Project: Sling
>  Issue Type: Bug
> Environment: Windows Server 2008 SP2 (Enterprise), JRE 1.6.0_24-b07, 
> Sling 6
>Reporter: Matt Banner
>Assignee: Carsten Ziegeler
> Fix For: Launchpad Builder 6
>
> Attachments: org.apache.felix.eventadmin-1.2.11-SNAPSHOT.jar, 
> sling6.thread_dump.01.txt, sling6.thread_dump.02.txt
>
>
> Sling 6 does not shut down cleanly on Windows Server 2008 and the process 
> must be killed manually.
> The problem was discovered when we upgraded our Tomcat-based application to 
> Sling 6, but it also occurs using an unmodified copy of the Sling Standalone 
> Application.  We consistently see the problem on all Windows Server 2008 
> machines.
> After coming across [#SLING-2020] Update to latest Apache Felix Event Admin 
> 1.2.10, I tried replacing the Apache Felix EventAdmin 1.2.10 bundle with the 
> Knopflerfish Event-Admin 3.0.4 bundle (you will also need their Log Service 
> bundle).  Using the Knopflerfish bundle, the issue no longer occurred.

--
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

[jira] [Commented] (SLING-2350) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects

2012-01-04 Thread Carsten Ziegeler (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179340#comment-13179340
 ] 

Carsten Ziegeler commented on SLING-2350:
-

Thanks David for the issue - could you please create patch against current 
trunk?



> Sling Maven JSPC Plugin depends on legacy Sling API lib which does not 
> support adaptable SlingHttpServletRequest objects
> 
>
> Key: SLING-2350
> URL: https://issues.apache.org/jira/browse/SLING-2350
> Project: Sling
>  Issue Type: Improvement
>  Components: Maven Plugins and Archetypes
>Affects Versions:  Maven JSPC Plugin 2.0.4
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
> Maven home: /usr/share/maven
> Java version: 1.6.0_29, vendor: Apple Inc.
> Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.7.2", arch: "x86_64", family: "mac"
>Reporter: David Gonzalez
>  Labels: maven-bundle-plugin
> Attachments: pom.xml
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> Buiding Sling-based project using the Maven JSPC Plugin but am getting 
> compilation errors because SlingHttpServletRequest object doesn't have 
> .adaptTo(...) defined.
> Latest Sling API docs state:
>   Starting with Sling API 2.0.6, this [SlingHttpServletRequest] interface 
> also extends the Adaptable interface.
> Sling Maven JSPC Plugin 2.0.4-incubator plugin [1] depends on  "Sling 
> Scripting 2.0.2-incubator" [2] which in turn depends on "Sling API  
> 2.0.2-incubator" which is older than 2.0.6 thus no Adaptable support.
> [1] 
> http://svn.apache.org/repos/asf/sling/tags/maven-jspc-plugin-2.0.4-incubator/pom.xml
> [2] 
> http://svn.apache.org/viewvc/sling/tags/org.apache.sling.scripting.jsp-2.0.2-incubator/pom.xml?view=markup

--
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

[jira] [Assigned] (SLING-2350) Sling Maven JSPC Plugin depends on legacy Sling API lib which does not support adaptable SlingHttpServletRequest objects

2012-01-04 Thread Carsten Ziegeler (Assigned) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler reassigned SLING-2350:
---

Assignee: Carsten Ziegeler

> Sling Maven JSPC Plugin depends on legacy Sling API lib which does not 
> support adaptable SlingHttpServletRequest objects
> 
>
> Key: SLING-2350
> URL: https://issues.apache.org/jira/browse/SLING-2350
> Project: Sling
>  Issue Type: Improvement
>  Components: Maven Plugins and Archetypes
>Affects Versions:  Maven JSPC Plugin 2.0.4
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
> Maven home: /usr/share/maven
> Java version: 1.6.0_29, vendor: Apple Inc.
> Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.7.2", arch: "x86_64", family: "mac"
>Reporter: David Gonzalez
>Assignee: Carsten Ziegeler
>  Labels: maven-bundle-plugin
> Attachments: pom.xml
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> Buiding Sling-based project using the Maven JSPC Plugin but am getting 
> compilation errors because SlingHttpServletRequest object doesn't have 
> .adaptTo(...) defined.
> Latest Sling API docs state:
>   Starting with Sling API 2.0.6, this [SlingHttpServletRequest] interface 
> also extends the Adaptable interface.
> Sling Maven JSPC Plugin 2.0.4-incubator plugin [1] depends on  "Sling 
> Scripting 2.0.2-incubator" [2] which in turn depends on "Sling API  
> 2.0.2-incubator" which is older than 2.0.6 thus no Adaptable support.
> [1] 
> http://svn.apache.org/repos/asf/sling/tags/maven-jspc-plugin-2.0.4-incubator/pom.xml
> [2] 
> http://svn.apache.org/viewvc/sling/tags/org.apache.sling.scripting.jsp-2.0.2-incubator/pom.xml?view=markup

--
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