[jira] [Commented] (SLING-6194) Release Sling 9

[Karl Pauls (JIRA)]

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

Karl Pauls commented on SLING-6194:
---

I updated the launchpad to use base-5.6.4-2.6.17-SNAPSHOT for now to get the 
latest Felix framework 5.6.4.

> Release Sling 9
> ---
>
> Key: SLING-6194
> URL: https://issues.apache.org/jira/browse/SLING-6194
> Project: Sling
>  Issue Type: Task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>
> Time to release Sling 9.
> Documentation at 
> https://cwiki.apache.org/confluence/display/SLING/Releasing+a+new+version+of+the+Sling+Launchpad



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (SLING-6857) Include latest version of the Felix framework in the Launchpad

[Karl Pauls (JIRA)]

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

Karl Pauls resolved SLING-6857.
---
Resolution: Fixed

Done in r1796101.

> Include latest version of the Felix framework in the Launchpad
> --
>
> Key: SLING-6857
> URL: https://issues.apache.org/jira/browse/SLING-6857
> Project: Sling
>  Issue Type: Sub-task
>  Components: Launchpad
>Reporter: Robert Munteanu
>Assignee: Karl Pauls
> Fix For: Launchpad Base 2.6.18
>
>
> Update to the upcomming Felix framework 5.6.4.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SLING-6857) Include latest version of the Felix framework in the Launchpad

[Karl Pauls (JIRA)]

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

Karl Pauls updated SLING-6857:
--
Fix Version/s: Launchpad Base 2.6.18

> Include latest version of the Felix framework in the Launchpad
> --
>
> Key: SLING-6857
> URL: https://issues.apache.org/jira/browse/SLING-6857
> Project: Sling
>  Issue Type: Sub-task
>  Components: Launchpad
>Reporter: Robert Munteanu
>Assignee: Karl Pauls
> Fix For: Launchpad Base 2.6.18
>
>
> Update to the upcomming Felix framework 5.6.4.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (SLING-6883) CAConfig: Respect service ranking in ordering context path/config ref proposals

[Stefan Seifert (JIRA)]

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

Stefan Seifert resolved SLING-6883.
---
Resolution: Fixed

Completed: At revision: 1796079  


> CAConfig: Respect service ranking in ordering context path/config ref 
> proposals
> ---
>
> Key: SLING-6883
> URL: https://issues.apache.org/jira/browse/SLING-6883
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: Context-Aware Configuration Impl 1.4.0
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>  Labels: contextaware-config
> Fix For: Context-Aware Configuration SPI 1.3.2, Context-Aware 
> Configuration Impl 1.4.2
>
>
> when multiple context path strategies are registered with provide different 
> config refs for the same context paths, their proposals should be sorted 
> descending by service ranking, so the order can be controlled.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6883) CAConfig: Respect service ranking in ordering context path/config ref proposals

[Stefan Seifert (JIRA)]

Stefan Seifert created SLING-6883:
-

 Summary: CAConfig: Respect service ranking in ordering context 
path/config ref proposals
 Key: SLING-6883
 URL: https://issues.apache.org/jira/browse/SLING-6883
 Project: Sling
  Issue Type: Improvement
  Components: Extensions
Affects Versions: Context-Aware Configuration Impl 1.4.0
Reporter: Stefan Seifert
Assignee: Stefan Seifert
 Fix For: Context-Aware Configuration SPI 1.3.2, Context-Aware 
Configuration Impl 1.4.2


when multiple context path strategies are registered with provide different 
config refs for the same context paths, their proposals should be sorted 
descending by service ranking, so the order can be controlled.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (SLING-6882) CAConfig Impl: Display context paths and config refs in web console

[Stefan Seifert (JIRA)]

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

Stefan Seifert resolved SLING-6882.
---
Resolution: Fixed

Completed: At revision: 1796075  


> CAConfig Impl: Display context paths and config refs in web console
> ---
>
> Key: SLING-6882
> URL: https://issues.apache.org/jira/browse/SLING-6882
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: Context-Aware Configuration Impl 1.4.0
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Minor
> Fix For: Context-Aware Configuration Impl 1.4.2
>
>
> for debugging purpose it is usefull to list all context paths and the 
> associated config references for a given content resource in the web console 
> plugin.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6882) CAConfig Impl: Display context paths and config refs in web console

[Stefan Seifert (JIRA)]

Stefan Seifert created SLING-6882:
-

 Summary: CAConfig Impl: Display context paths and config refs in 
web console
 Key: SLING-6882
 URL: https://issues.apache.org/jira/browse/SLING-6882
 Project: Sling
  Issue Type: Improvement
  Components: Extensions
Affects Versions: Context-Aware Configuration Impl 1.4.0
Reporter: Stefan Seifert
Assignee: Stefan Seifert
Priority: Minor
 Fix For: Context-Aware Configuration Impl 1.4.2


for debugging purpose it is usefull to list all context paths and the 
associated config references for a given content resource in the web console 
plugin.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SLING-6879) [Rewriter] mvn clean install generates empty files under empty files under target/classes/OSGI-INF

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-6879:


Moving to the new annotations is fine, we're gradually doing that for all 
modules.

> [Rewriter] mvn clean install generates empty files under empty files under 
> target/classes/OSGI-INF
> --
>
> Key: SLING-6879
> URL: https://issues.apache.org/jira/browse/SLING-6879
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
> Environment: Windows 10, Ubuntu 16.04, Java 8, Maven 3.5.0
>Reporter: Amrit Verma
>
> Building the {{org.apache.sling.rewriter}} module using mvn clean install 
> (Maven 3.5.0 and Java 8) generates empty files under 
> {{target/classes/OSGI-INF}} eg the generated file
> org.apache.sling.rewriter.impl.components.HtmlGeneratorFactory.xml is empty
> If I change the annotations on those components to osgi annotations instead 
> of felix scr annotations eg 
> {{org.osgi.service.component.annotations.Component}} instead of 
> {{org.apache.felix.scr.annotations.Component}}, the files are generated 
> properly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (SLING-6881) CAConfig Mock Plugin: Register configuration classes via package name

[Stefan Seifert (JIRA)]

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

Stefan Seifert resolved SLING-6881.
---
Resolution: Fixed

Completed: At revision: 1796055  


> CAConfig Mock Plugin: Register configuration classes via package name
> -
>
> Key: SLING-6881
> URL: https://issues.apache.org/jira/browse/SLING-6881
> Project: Sling
>  Issue Type: New Feature
>  Components: Testing
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>  Labels: mocks
> Fix For: Context-Aware Configuration Mock Plugin 1.3.0
>
>
> add methods for registring configuration classes in the current project via 
> their package name:
> * {{MockContextAwareConfig.registerAnnotationPackages}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6881) CAConfig Mock Plugin: Register configuration classes via package name

[Stefan Seifert (JIRA)]

Stefan Seifert created SLING-6881:
-

 Summary: CAConfig Mock Plugin: Register configuration classes via 
package name
 Key: SLING-6881
 URL: https://issues.apache.org/jira/browse/SLING-6881
 Project: Sling
  Issue Type: New Feature
  Components: Testing
Reporter: Stefan Seifert
Assignee: Stefan Seifert
 Fix For: Context-Aware Configuration Mock Plugin 1.3.0


add methods for registring configuration classes in the current project via 
their package name:
* {{MockContextAwareConfig.registerAnnotationPackages}}




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (SLING-6880) CAConfig Mock Plugin: Add helper methods for writing configurations

[Stefan Seifert (JIRA)]

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

Stefan Seifert resolved SLING-6880.
---
Resolution: Fixed

Completed: At revision: 1796051  

i've also dropped support for the old 1.x versions of CAConfig SPI/Impl.
1.2, 1.3 and 1.4 supported.

> CAConfig Mock Plugin: Add helper methods for writing configurations
> ---
>
> Key: SLING-6880
> URL: https://issues.apache.org/jira/browse/SLING-6880
> Project: Sling
>  Issue Type: New Feature
>  Components: Testing
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>  Labels: mocks
> Fix For: Context-Aware Configuration Mock Plugin 1.3.0
>
>
> add methods for writing configuration and configuration collections:
> * {{MockContextAwareConfig.writeConfiguration}}
> * {{MockContextAwareConfig.writeConfigurationCollection}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6880) CAConfig Mock Plugin: Add helper methods for writing configurations

[Stefan Seifert (JIRA)]

Stefan Seifert created SLING-6880:
-

 Summary: CAConfig Mock Plugin: Add helper methods for writing 
configurations
 Key: SLING-6880
 URL: https://issues.apache.org/jira/browse/SLING-6880
 Project: Sling
  Issue Type: New Feature
  Components: Testing
Reporter: Stefan Seifert
Assignee: Stefan Seifert
 Fix For: Context-Aware Configuration Mock Plugin 1.3.0


add methods for writing configuration and configuration collections:
* {{MockContextAwareConfig.writeConfiguration}}
* {{MockContextAwareConfig.writeConfigurationCollection}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SLING-6879) [Rewriter] mvn clean install generates empty files under empty files under target/classes/OSGI-INF

[Amrit Verma (JIRA)]

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

Amrit Verma commented on SLING-6879:


[~rombert], Yes, I am willing to do that :)
I was just wondering if moving to new annotations is fine or should the old 
annotations generate proper results as well?

> [Rewriter] mvn clean install generates empty files under empty files under 
> target/classes/OSGI-INF
> --
>
> Key: SLING-6879
> URL: https://issues.apache.org/jira/browse/SLING-6879
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
> Environment: Windows 10, Ubuntu 16.04, Java 8, Maven 3.5.0
>Reporter: Amrit Verma
>
> Building the {{org.apache.sling.rewriter}} module using mvn clean install 
> (Maven 3.5.0 and Java 8) generates empty files under 
> {{target/classes/OSGI-INF}} eg the generated file
> org.apache.sling.rewriter.impl.components.HtmlGeneratorFactory.xml is empty
> If I change the annotations on those components to osgi annotations instead 
> of felix scr annotations eg 
> {{org.osgi.service.component.annotations.Component}} instead of 
> {{org.apache.felix.scr.annotations.Component}}, the files are generated 
> properly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [VOTE] Release Apache Sling JCR Content Parser 1.2.0, File System Resource Provider 2.1.2, File System Resource Provider 1.4.2, Maven Sling Plugin 2.2.2

[Karl Pauls]

+1

regards,

Karl

On Wed, May 24, 2017 at 11:50 AM, Carsten Ziegeler  wrote:
> +1
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org



-- 
Karl Pauls
karlpa...@gmail.com

Re: [VOTE] Release Apache Sling JCR Content Parser 1.2.0, File System Resource Provider 2.1.2, File System Resource Provider 1.4.2, Maven Sling Plugin 2.2.2

[Carsten Ziegeler]

+1
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

RE: [VOTE] Release Apache Sling JCR Content Parser 1.2.0, File System Resource Provider 2.1.2, File System Resource Provider 1.4.2, Maven Sling Plugin 2.2.2

[Stefan Seifert]

+1

[VOTE] Release Apache Sling JCR Content Parser 1.2.0, File System Resource Provider 2.1.2, File System Resource Provider 1.4.2, Maven Sling Plugin 2.2.2

[Stefan Seifert]

Hi,

Apache Sling Apache Sling JCR Content Parser 1.2.0  (1 issue)
https://issues.apache.org/jira/browse/SLING/fixforversion/12340510

Apache Sling File System Resource Provider 2.1.2  (3 issues)
https://issues.apache.org/jira/browse/SLING/fixforversion/12340512

Apache Sling File System Resource Provider 1.4.2  (3 issues)
https://issues.apache.org/jira/browse/SLING/fixforversion/12340511

Apache Sling Maven Sling Plugin 2.2.2  (1 issue)
https://issues.apache.org/jira/browse/SLING/fixforversion/12340254

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1729/

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 1729 /tmp/sling-staging

Please vote to approve this release:

  [ ] +1 Approve the release
  [ ]  0 Don't care
  [ ] -1 Don't release, because ...

This majority vote is open for at least 72 hours.

stefan

[jira] [Commented] (SLING-6879) [Rewriter] mvn clean install generates empty files under empty files under target/classes/OSGI-INF

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-6879:


Thanks for the report [~amrverma] . Would you be willing to submit a patch or a 
pull request?

> [Rewriter] mvn clean install generates empty files under empty files under 
> target/classes/OSGI-INF
> --
>
> Key: SLING-6879
> URL: https://issues.apache.org/jira/browse/SLING-6879
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
> Environment: Windows 10, Ubuntu 16.04, Java 8, Maven 3.5.0
>Reporter: Amrit Verma
>
> Building the {{org.apache.sling.rewriter}} module using mvn clean install 
> (Maven 3.5.0 and Java 8) generates empty files under 
> {{target/classes/OSGI-INF}} eg the generated file
> org.apache.sling.rewriter.impl.components.HtmlGeneratorFactory.xml is empty
> If I change the annotations on those components to osgi annotations instead 
> of felix scr annotations eg 
> {{org.osgi.service.component.annotations.Component}} instead of 
> {{org.apache.felix.scr.annotations.Component}}, the files are generated 
> properly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6879) [Rewriter] mvn clean install generates empty files under empty files under target/classes/OSGI-INF

[Amrit Verma (JIRA)]

Amrit Verma created SLING-6879:
--

 Summary: [Rewriter] mvn clean install generates empty files under 
empty files under target/classes/OSGI-INF
 Key: SLING-6879
 URL: https://issues.apache.org/jira/browse/SLING-6879
 Project: Sling
  Issue Type: Bug
  Components: Extensions
 Environment: Windows 10, Ubuntu 16.04, Java 8, Maven 3.5.0
Reporter: Amrit Verma


Building the {{org.apache.sling.rewriter}} module using mvn clean install 
(Maven 3.5.0 and Java 8) generates empty files under 
{{target/classes/OSGI-INF}} eg the generated file
org.apache.sling.rewriter.impl.components.HtmlGeneratorFactory.xml is empty

If I change the annotations on those components to osgi annotations instead of 
felix scr annotations eg {{org.osgi.service.component.annotations.Component}} 
instead of {{org.apache.felix.scr.annotations.Component}}, the files are 
generated properly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SLING-6860) Sling pipes has a dependency on unstable Jackrabbit release (2.7.5)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SLING-6860:
---

Github user asfgit closed the pull request at:

https://github.com/apache/sling/pull/230


> Sling pipes has a dependency on unstable Jackrabbit release (2.7.5)
> ---
>
> Key: SLING-6860
> URL: https://issues.apache.org/jira/browse/SLING-6860
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Pipes 0.0.10
>Reporter: Julian Reschke
>Assignee: Robert Munteanu
> Fix For: Pipes 0.0.12
>
>
> (FWIW, it also uses the unmaintained HTTPClient 3.*)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (SLING-6860) Sling pipes has a dependency on unstable Jackrabbit release (2.7.5)

[Robert Munteanu (JIRA)]

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

Robert Munteanu resolved SLING-6860.

Resolution: Fixed

Fixed in [r1796006|https://svn.apache.org/r1796006], thanks [~npeltier] for the 
patch!

> Sling pipes has a dependency on unstable Jackrabbit release (2.7.5)
> ---
>
> Key: SLING-6860
> URL: https://issues.apache.org/jira/browse/SLING-6860
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Pipes 0.0.10
>Reporter: Julian Reschke
>Assignee: Robert Munteanu
> Fix For: Pipes 0.0.12
>
>
> (FWIW, it also uses the unmaintained HTTPClient 3.*)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] sling pull request #230: SLING-6860 bump jackrabbit api version

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/sling/pull/230


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (SLING-6860) Sling pipes has a dependency on unstable Jackrabbit release (2.7.5)

[Robert Munteanu (JIRA)]

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

Robert Munteanu updated SLING-6860:
---
Fix Version/s: Pipes 0.0.12

> Sling pipes has a dependency on unstable Jackrabbit release (2.7.5)
> ---
>
> Key: SLING-6860
> URL: https://issues.apache.org/jira/browse/SLING-6860
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Pipes 0.0.10
>Reporter: Julian Reschke
>Assignee: Robert Munteanu
> Fix For: Pipes 0.0.12
>
>
> (FWIW, it also uses the unmaintained HTTPClient 3.*)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (SLING-6860) Sling pipes has a dependency on unstable Jackrabbit release (2.7.5)

[Robert Munteanu (JIRA)]

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

Robert Munteanu reassigned SLING-6860:
--

Assignee: Robert Munteanu

> Sling pipes has a dependency on unstable Jackrabbit release (2.7.5)
> ---
>
> Key: SLING-6860
> URL: https://issues.apache.org/jira/browse/SLING-6860
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Pipes 0.0.10
>Reporter: Julian Reschke
>Assignee: Robert Munteanu
> Fix For: Pipes 0.0.12
>
>
> (FWIW, it also uses the unmaintained HTTPClient 3.*)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SLING-6623) Add the possibility to execute sling pipes in a background thread

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SLING-6623:
---

Github user asfgit closed the pull request at:

https://github.com/apache/sling/pull/229


> Add the possibility to execute sling pipes in a background thread
> -
>
> Key: SLING-6623
> URL: https://issues.apache.org/jira/browse/SLING-6623
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Affects Versions: Pipes 0.0.10
>Reporter: Nicolas Peltier
>Assignee: Robert Munteanu
> Fix For: Pipes 0.0.12
>
>
> For now the only way to execute a pipe through HTTP is to wait for servlet's 
> response to end.
> For very long pipes this is an issue (as well as for the fact all pending 
> changes might impact memory), as well as it is error prone in case the same 
> pipe is executed several times.
> this ticket is for adding a new execution mode, that write the running status 
> of the pipe configuration, and makes the pipe executed in a separate thread 
> than the servlet thread.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (SLING-6623) Add the possibility to execute sling pipes in a background thread

[Robert Munteanu (JIRA)]

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

Robert Munteanu resolved SLING-6623.

Resolution: Fixed

Applied in [r1796004|https://svn.apache.org/r1796004], thanks for the patch!

> Add the possibility to execute sling pipes in a background thread
> -
>
> Key: SLING-6623
> URL: https://issues.apache.org/jira/browse/SLING-6623
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Affects Versions: Pipes 0.0.10
>Reporter: Nicolas Peltier
>Assignee: Robert Munteanu
> Fix For: Pipes 0.0.12
>
>
> For now the only way to execute a pipe through HTTP is to wait for servlet's 
> response to end.
> For very long pipes this is an issue (as well as for the fact all pending 
> changes might impact memory), as well as it is error prone in case the same 
> pipe is executed several times.
> this ticket is for adding a new execution mode, that write the running status 
> of the pipe configuration, and makes the pipe executed in a separate thread 
> than the servlet thread.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] sling pull request #229: SLING-6623 allow async execution of pipes

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/sling/pull/229


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (SLING-6623) Add the possibility to execute sling pipes in a background thread

[Robert Munteanu (JIRA)]

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

Robert Munteanu updated SLING-6623:
---
Fix Version/s: Pipes 0.0.12

> Add the possibility to execute sling pipes in a background thread
> -
>
> Key: SLING-6623
> URL: https://issues.apache.org/jira/browse/SLING-6623
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Affects Versions: Pipes 0.0.10
>Reporter: Nicolas Peltier
>Assignee: Robert Munteanu
> Fix For: Pipes 0.0.12
>
>
> For now the only way to execute a pipe through HTTP is to wait for servlet's 
> response to end.
> For very long pipes this is an issue (as well as for the fact all pending 
> changes might impact memory), as well as it is error prone in case the same 
> pipe is executed several times.
> this ticket is for adding a new execution mode, that write the running status 
> of the pipe configuration, and makes the pipe executed in a separate thread 
> than the servlet thread.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (SLING-6623) Add the possibility to execute sling pipes in a background thread

[Robert Munteanu (JIRA)]

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

Robert Munteanu reassigned SLING-6623:
--

Assignee: Robert Munteanu

> Add the possibility to execute sling pipes in a background thread
> -
>
> Key: SLING-6623
> URL: https://issues.apache.org/jira/browse/SLING-6623
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Affects Versions: Pipes 0.0.10
>Reporter: Nicolas Peltier
>Assignee: Robert Munteanu
>
> For now the only way to execute a pipe through HTTP is to wait for servlet's 
> response to end.
> For very long pipes this is an issue (as well as for the fact all pending 
> changes might impact memory), as well as it is error prone in case the same 
> pipe is executed several times.
> this ticket is for adding a new execution mode, that write the running status 
> of the pipe configuration, and makes the pipe executed in a separate thread 
> than the servlet thread.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6878) Bundle resource provider: support mounting of JSON files

[Carsten Ziegeler (JIRA)]

Carsten Ziegeler created SLING-6878:
---

 Summary: Bundle resource provider: support mounting of JSON files
 Key: SLING-6878
 URL: https://issues.apache.org/jira/browse/SLING-6878
 Project: Sling
  Issue Type: Improvement
  Components: Extensions
Reporter: Carsten Ziegeler
 Fix For: Bundle Resource 2.2.2


I think similar to SLING-6440 we should support mounting of JSON files through 
the bundle resource provider (we don't need to support other file formats as 
xml or vault)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[RT] Reducing configuration magic through sling.properties

[Carsten Ziegeler]

Hi,

atm we have at least two places for configuration of a Sling
application: the provisioning model and sling.properties. I think we
should try to reduce this to a single place, the provisioning model.

Looking at what we have in sling.properties atm I see basically four
categories:

- OSGi framework properties - these can easily be moved in the
provisioning model
- definition of core packages. This includes the jre packages as well as
the packages provided by the OSGi framework. This is usually already
defined by the OSGi framework and there is actually no need to redefine
this. So we can drop these completely. We just have to make sure to
provide the launchpad api in case launchpad is used to start the
instance. But this can easily be done within launchpad.
- the more magic part for bootdelegation which checks for a
class/package and if that is available from the environment, packages
are added to bootdelegation. Not sure how to handle this yet.
- includes like the default of sling_install.properties. If we consider
that the provisioning model is the source of truth I don't think this is
needed

So overall, getting rid of sling.properties reduces the places of
configuration and simplifies things

WDYT?

PS: I don't think this is something for Sling 9 :)

Regards
Carsten
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Re: [VOTE] Apache Sling JCR Contentloader 2.2.2

[Carsten Ziegeler]

+1

 

-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org