date:20161027

Re: [VOTE] Release Apache Sling Provisioning Model 1.5.0

2016-10-27 Thread Carsten Ziegeler

+1

 

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

[VOTE] Release Apache Sling Provisioning Model 1.5.0

2016-10-27 Thread Carsten Ziegeler

Hi,

We solved 1 issue in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12336074

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

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 1554 /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.

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

[jira] [Created] (SLING-6206) Set feature version to pom version

2016-10-27 Thread Carsten Ziegeler (JIRA)

Carsten Ziegeler created SLING-6206:
---

 Summary: Set feature version to pom version
 Key: SLING-6206
 URL: https://issues.apache.org/jira/browse/SLING-6206
 Project: Sling
  Issue Type: Improvement
  Components: Tooling
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
 Fix For: Slingstart Maven Plugin 1.4.6


The latest provisioning model allows to set a version for a feature.
If there is no version defined in the provisioning model, we should set the 
feature version to the version of the pom



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

2016-10-27 Thread Alexander Klimetschek (JIRA)


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

Alexander Klimetschek edited comment on SLING-6187 at 10/27/16 9:17 PM:


Could this check be based on the resource type? Then you'd configure the 
required post processors based on the RT (or node type), and it's completely 
server side.

This lets me think however, that whatever the @suffix triggers in the first 
place (say an encryption of a property), which you want to guarantee, should 
probably also be defined purely server side.

I.e. if the client forgets/omits the suffix, the requiredPostProcessor check 
would not help and you still get an undesired result.


was (Author: alexander.klimetschek):
Could this check be based on the resource type? Then you'd configure the 
required post processors based on the RT (or node type), and it's completely 
server side.

This lets me think however, that whatever the @suffix triggers in the first 
place (say an encryption of a property), which you want to guarantee, should 
probably also be defined purely server side.

> Provide a way for a POST request to assert a set of required 
> SlingPostProcessors
> 
>
> Key: SLING-6187
> URL: https://issues.apache.org/jira/browse/SLING-6187
> Project: Sling
>  Issue Type: Improvement
>  Components: Servlets
>Reporter: Justin Edelson
>Assignee: Justin Edelson
> Fix For: Servlets Post 2.3.16
>
>
> I would like to add support for a new "special" request parameter understood 
> by the Sling Post Servlet named {{:requiredPostProcessors}}. This parameter 
> may contain a comma-delimited list of names (see below) which *must* be 
> available *at the time the request is processed* in order for the request to 
> be handled. Whether or not those processors _do_ anything or whether the 
> request succeeds or not is a separate question; this is just a preflight 
> check if you will.
> If any of the required SlingPostProcessors are not available, the request 
> will fail with a 501 error.
> The name of a SlingPostProcessor will be defined by a newly defined service 
> registration property {{postProcessor.name}} and default to the simple name 
> of the SlingPostProcessor's implementation class if that property is not 
> defined.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

2016-10-27 Thread Alexander Klimetschek (JIRA)


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

Alexander Klimetschek commented on SLING-6187:
--

Could this check be based on the resource type? Then you'd configure the 
required post processors based on the RT (or node type), and it's completely 
server side.

This lets me think however, that whatever the @suffix triggers in the first 
place (say an encryption of a property), which you want to guarantee, should 
probably also be defined purely server side.

> Provide a way for a POST request to assert a set of required 
> SlingPostProcessors
> 
>
> Key: SLING-6187
> URL: https://issues.apache.org/jira/browse/SLING-6187
> Project: Sling
>  Issue Type: Improvement
>  Components: Servlets
>Reporter: Justin Edelson
>Assignee: Justin Edelson
> Fix For: Servlets Post 2.3.16
>
>
> I would like to add support for a new "special" request parameter understood 
> by the Sling Post Servlet named {{:requiredPostProcessors}}. This parameter 
> may contain a comma-delimited list of names (see below) which *must* be 
> available *at the time the request is processed* in order for the request to 
> be handled. Whether or not those processors _do_ anything or whether the 
> request succeeds or not is a separate question; this is just a preflight 
> check if you will.
> If any of the required SlingPostProcessors are not available, the request 
> will fail with a 501 error.
> The name of a SlingPostProcessor will be defined by a newly defined service 
> registration property {{postProcessor.name}} and default to the simple name 
> of the SlingPostProcessor's implementation class if that property is not 
> defined.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-6187) Provide a way for a POST request to assert a set of required SlingPostProcessors

2016-10-27 Thread Justin Edelson (JIRA)


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

Justin Edelson commented on SLING-6187:
---

Regarding

bq. The name of the post processor is a server implementation detail and with a 
new request parameter existing clients would have to be changed. Maybe there is 
a other way to ensure it...

I'd be happy to remove the use of the implementation class's simple name as a 
fallback and require that assertable post processors have the new service 
registration property mentioned above if that would help with your concerns.

> Provide a way for a POST request to assert a set of required 
> SlingPostProcessors
> 
>
> Key: SLING-6187
> URL: https://issues.apache.org/jira/browse/SLING-6187
> Project: Sling
>  Issue Type: Improvement
>  Components: Servlets
>Reporter: Justin Edelson
>Assignee: Justin Edelson
> Fix For: Servlets Post 2.3.16
>
>
> I would like to add support for a new "special" request parameter understood 
> by the Sling Post Servlet named {{:requiredPostProcessors}}. This parameter 
> may contain a comma-delimited list of names (see below) which *must* be 
> available *at the time the request is processed* in order for the request to 
> be handled. Whether or not those processors _do_ anything or whether the 
> request succeeds or not is a separate question; this is just a preflight 
> check if you will.
> If any of the required SlingPostProcessors are not available, the request 
> will fail with a 501 error.
> The name of a SlingPostProcessor will be defined by a newly defined service 
> registration property {{postProcessor.name}} and default to the simple name 
> of the SlingPostProcessor's implementation class if that property is not 
> defined.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-6175) Sling IDE: Don't configure WTP natures by default for content-package projects

2016-10-27 Thread Robert Munteanu (JIRA)


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

Robert Munteanu commented on SLING-6175:


I see your points but don't necessarily agree. There are two issues, AFAIU

# spurious creation of a MANIFEST.MF
# poor performance/quality of Javascript validators

I think that we can

# automatically configure [a resource 
filter|http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.platform.doc.user%2Fconcepts%2Fresourcefilters.htm]
 to hide away the unneeded manifest file
# automatically disable the Javascript validators. AFAIR we already meddle with 
the default validators for the Sightly nature so we could do the same and 
remove the javascript validators by default, guarded by a pom.xml property ( 
although I'm not a big fan of this - maybe we disable it on-demand and enable 
by default )

Would that address the concerns that you have?

Besides the enhanced JSP support, which still has value IMO, we also get proper 
entries for HTML/CSS/JS files in folders with the WTP natures, and that's 
something which I think is still useful. 

> Sling IDE: Don't configure WTP natures by default for content-package projects
> --
>
> Key: SLING-6175
> URL: https://issues.apache.org/jira/browse/SLING-6175
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.1.0
>Reporter: Konrad Windszus
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.1.2
>
> Attachments: SLING-6175_v01.patch
>
>
> With the configurator being added in SLING-3100 there is always WTP natures 
> and according facets added for {{content-package}} projects. This is not 
> always desired.
> It e.g. leads to the fact that a META-INF/MANIFEST.MF is automatically 
> generated below the jcr_root folder 
> (https://wiki.eclipse.org/M2E-WTP_FAQ#What_is_this_web_resources_folder.3F & 
> http://stackoverflow.com/questions/14659891/m2e-wtp-error-path-target-m2e-wtp-web-resources-meta-inf-manifest-mf-no-such).
> Another drawback is that some validators (e.g. for javascript) are not 
> working reliably (because one package is not an autonomous piece of code and 
> often references code from outside the content package which is invisible to 
> Eclipse).
> Since {{content-packages}} are quite different from {{war}} projects I would 
> propose to only add those natures/facets if this is explicitly 
> configured/requested. Instead we should only add the native Sling IDE 
> natures/facets.
> The original idea behind making a {{content-package}} similar to a {{war}} 
> was to support code assist in JSPs better (i.e. for tag libraries). This 
> never reliably worked and therefore we should rather get rid of that approach.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-6175) Sling IDE: Don't configure WTP natures by default for content-package projects

2016-10-27 Thread Robert Munteanu (JIRA)


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

Robert Munteanu updated SLING-6175:
---
Issue Type: Improvement  (was: Bug)

> Sling IDE: Don't configure WTP natures by default for content-package projects
> --
>
> Key: SLING-6175
> URL: https://issues.apache.org/jira/browse/SLING-6175
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.1.0
>Reporter: Konrad Windszus
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.1.2
>
> Attachments: SLING-6175_v01.patch
>
>
> With the configurator being added in SLING-3100 there is always WTP natures 
> and according facets added for {{content-package}} projects. This is not 
> always desired.
> It e.g. leads to the fact that a META-INF/MANIFEST.MF is automatically 
> generated below the jcr_root folder 
> (https://wiki.eclipse.org/M2E-WTP_FAQ#What_is_this_web_resources_folder.3F & 
> http://stackoverflow.com/questions/14659891/m2e-wtp-error-path-target-m2e-wtp-web-resources-meta-inf-manifest-mf-no-such).
> Another drawback is that some validators (e.g. for javascript) are not 
> working reliably (because one package is not an autonomous piece of code and 
> often references code from outside the content package which is invisible to 
> Eclipse).
> Since {{content-packages}} are quite different from {{war}} projects I would 
> propose to only add those natures/facets if this is explicitly 
> configured/requested. Instead we should only add the native Sling IDE 
> natures/facets.
> The original idea behind making a {{content-package}} similar to a {{war}} 
> was to support code assist in JSPs better (i.e. for tag libraries). This 
> never reliably worked and therefore we should rather get rid of that approach.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-3014) [build] Generate SCR descriptors using the maven-scr-plugin

2016-10-27 Thread Robert Munteanu (JIRA)


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

Robert Munteanu commented on SLING-3014:


In theory, I agree. In practice, non-tycho plugins don't work all that well. 
But I'll give it a shot when I have the time.

> [build] Generate SCR descriptors using the maven-scr-plugin
> ---
>
> Key: SLING-3014
> URL: https://issues.apache.org/jira/browse/SLING-3014
> Project: Sling
>  Issue Type: Task
>  Components: IDE
>Reporter: Robert Munteanu
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.1.2
>
> Attachments: SLING-3014-1.patch
>
>
> Since we're starting to use SCR descriptors when building the Sling IDE tools 
> it would be nice to generate them using the maven-scr-plugin. I have the 
> build working in the CLI, but not yet in the IDE ( see 
> http://dev.eclipse.org/mhonarc/lists/tycho-user/msg04764.html ). Once that is 
> done I'll commit my changes to trunk.
> Note that plain Maven projects work just fine, this is about Tycho-driven 
> builds.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-3014) [build] Generate SCR descriptors using the maven-scr-plugin

2016-10-27 Thread Konrad Windszus (JIRA)


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

Konrad Windszus commented on SLING-3014:


Tycho is a regular Maven build. The only difference is that usually a different 
packaging is used. That is a problem for the maven-bundle-plugin (which 
supports only {{jar}} and {{bundle}}) but should be possible with the 
bnd-maven-plugin.

> [build] Generate SCR descriptors using the maven-scr-plugin
> ---
>
> Key: SLING-3014
> URL: https://issues.apache.org/jira/browse/SLING-3014
> Project: Sling
>  Issue Type: Task
>  Components: IDE
>Reporter: Robert Munteanu
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.1.2
>
> Attachments: SLING-3014-1.patch
>
>
> Since we're starting to use SCR descriptors when building the Sling IDE tools 
> it would be nice to generate them using the maven-scr-plugin. I have the 
> build working in the CLI, but not yet in the IDE ( see 
> http://dev.eclipse.org/mhonarc/lists/tycho-user/msg04764.html ). Once that is 
> done I'll commit my changes to trunk.
> Note that plain Maven projects work just fine, this is about Tycho-driven 
> builds.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-3629) Provide an XML formatter for content.xml files

2016-10-27 Thread Robert Munteanu (JIRA)


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

Robert Munteanu commented on SLING-3629:


What I was considering when I reported this bug was to delegate the formatting 
to FileVault, optionally enhancing it to expose such a formatter if it's needed.

> Provide an XML formatter for content.xml files
> --
>
> Key: SLING-3629
> URL: https://issues.apache.org/jira/browse/SLING-3629
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Reporter: Robert Munteanu
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.1.2
>
>
> When editing resource properties through the JCR properties view, we format 
> the corresponding XML according to the vault canonical format. At the same 
> time, there is no such provision for working with content.xml files directly 
> in the editor.
> While I don't think that we should format them automatically, it would be 
> useful to have a formatter which can be manually invoked.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-4031) Missing MANIFEST.MF should be a validation error

2016-10-27 Thread Robert Munteanu (JIRA)


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

Robert Munteanu commented on SLING-4031:


I am not sure exactly what the best way is, but the current one is sub-optimal. 
Checking the pom.xml for configuration is a very good step, but it doesn't 
guarantee that we have a MANIFEST.MF file generated. So we probably want to 
create this validation error after the build is complete, or even when trying 
to publish a bundle

> Missing MANIFEST.MF should be a validation error
> 
>
> Key: SLING-4031
> URL: https://issues.apache.org/jira/browse/SLING-4031
> Project: Sling
>  Issue Type: Test
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.2
>Reporter: Robert Munteanu
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.1.2
>
>
> I just noticed a warning on the Sling console when a bundle was rebuilt
> {quote}[October 11, 2014 2:09:53 AM EEST] InstallBundle -> 
> /home/ADOBENET/rmuntean/Downloads/import/myproject/components/target/classes 
> : Project P/myproject.components does not have a META-INF/MANIFEST.MF (yet) - 
> not publishing this time (0 ms)
> {quote}
> This should be a validation error and block publishing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-3014) [build] Generate SCR descriptors using the maven-scr-plugin

2016-10-27 Thread Robert Munteanu (JIRA)


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

Robert Munteanu commented on SLING-3014:


Can bnd be used in tycho builds? Note that this is about building the plug-ins, 
not using them.

> [build] Generate SCR descriptors using the maven-scr-plugin
> ---
>
> Key: SLING-3014
> URL: https://issues.apache.org/jira/browse/SLING-3014
> Project: Sling
>  Issue Type: Task
>  Components: IDE
>Reporter: Robert Munteanu
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.1.2
>
> Attachments: SLING-3014-1.patch
>
>
> Since we're starting to use SCR descriptors when building the Sling IDE tools 
> it would be nice to generate them using the maven-scr-plugin. I have the 
> build working in the CLI, but not yet in the IDE ( see 
> http://dev.eclipse.org/mhonarc/lists/tycho-user/msg04764.html ). Once that is 
> done I'll commit my changes to trunk.
> Note that plain Maven projects work just fine, this is about Tycho-driven 
> builds.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-6130) Restrict access for principal everyone and move configuration to repoinit

2016-10-27 Thread Oliver Lietz (JIRA)


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

Oliver Lietz commented on SLING-6130:
-

{{anonymous}} (which should be ok), when trying to access {{/server/content}} I 
do get {{412 Precondition Failed}} for {{admin}} and {{anonymous}}

> Restrict access for principal everyone and move configuration to repoinit
> -
>
> Key: SLING-6130
> URL: https://issues.apache.org/jira/browse/SLING-6130
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR, Oak
>Affects Versions: JCR Oak Server 1.1.0
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>  Labels: security
> Fix For: JCR Oak Server 1.1.2
>
> Attachments: error.log
>
>
> Currently {{everyone}} can {{read}} from {{/}} (configured in 
> {{OakSlingRepositoryManager}}).
> Access for {{everyone}} should be restricted:
> * {{read}} should be restricted to {{/content}}
> * configuration of principals and ACLs should be done with _repoinit_
> # -Change path from {{/}} to {{/content}} in {{OakSlingRepositoryManager}}- 
> (/) (-[r1764259|https://svn.apache.org/r1764259]-)
> # Fix modules (samples) relying on _unrestricted_ {{read}} access
> # Move configuration of ACLs to _repoinit_ (/)
> discussion on 
> [dev@|https://lists.apache.org/thread.html/36908ed62ac93c63cad594a897f8abceb93f08da5bcea30dbce98e58@%3Cdev.sling.apache.org%3E]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-6130) Restrict access for principal everyone and move configuration to repoinit

2016-10-27 Thread Oliver Lietz (JIRA)


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

Oliver Lietz commented on SLING-6130:
-

The attached [^error.log] from build doesn't contain any failures and probably 
I'm hitting an issue (vanity path?) when {{/}} is not _readable_ by 
{{everyone}}.

> Restrict access for principal everyone and move configuration to repoinit
> -
>
> Key: SLING-6130
> URL: https://issues.apache.org/jira/browse/SLING-6130
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR, Oak
>Affects Versions: JCR Oak Server 1.1.0
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>  Labels: security
> Fix For: JCR Oak Server 1.1.2
>
> Attachments: error.log
>
>
> Currently {{everyone}} can {{read}} from {{/}} (configured in 
> {{OakSlingRepositoryManager}}).
> Access for {{everyone}} should be restricted:
> * {{read}} should be restricted to {{/content}}
> * configuration of principals and ACLs should be done with _repoinit_
> # -Change path from {{/}} to {{/content}} in {{OakSlingRepositoryManager}}- 
> (/) (-[r1764259|https://svn.apache.org/r1764259]-)
> # Fix modules (samples) relying on _unrestricted_ {{read}} access
> # Move configuration of ACLs to _repoinit_ (/)
> discussion on 
> [dev@|https://lists.apache.org/thread.html/36908ed62ac93c63cad594a897f8abceb93f08da5bcea30dbce98e58@%3Cdev.sling.apache.org%3E]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-6130) Restrict access for principal everyone and move configuration to repoinit

2016-10-27 Thread Robert Munteanu (JIRA)


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

Robert Munteanu commented on SLING-6130:


Is the WebDAV connection done with the anonymous user or with an admin user?

> Restrict access for principal everyone and move configuration to repoinit
> -
>
> Key: SLING-6130
> URL: https://issues.apache.org/jira/browse/SLING-6130
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR, Oak
>Affects Versions: JCR Oak Server 1.1.0
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>  Labels: security
> Fix For: JCR Oak Server 1.1.2
>
> Attachments: error.log
>
>
> Currently {{everyone}} can {{read}} from {{/}} (configured in 
> {{OakSlingRepositoryManager}}).
> Access for {{everyone}} should be restricted:
> * {{read}} should be restricted to {{/content}}
> * configuration of principals and ACLs should be done with _repoinit_
> # -Change path from {{/}} to {{/content}} in {{OakSlingRepositoryManager}}- 
> (/) (-[r1764259|https://svn.apache.org/r1764259]-)
> # Fix modules (samples) relying on _unrestricted_ {{read}} access
> # Move configuration of ACLs to _repoinit_ (/)
> discussion on 
> [dev@|https://lists.apache.org/thread.html/36908ed62ac93c63cad594a897f8abceb93f08da5bcea30dbce98e58@%3Cdev.sling.apache.org%3E]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-6130) Restrict access for principal everyone and move configuration to repoinit

2016-10-27 Thread Oliver Lietz (JIRA)


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

Oliver Lietz commented on SLING-6130:
-

When trying to access the instance over WebDAV an exception is thrown:
{noformat}
27.10.2016 19:48:56.442 *ERROR* [qtp1622793849-193] 
org.apache.jackrabbit.webdav.jcr.WorkspaceResourceImpl Internal error while 
building resource for the root node.
javax.jcr.AccessDeniedException: Root node is not accessible.
at 
org.apache.jackrabbit.oak.jcr.session.SessionImpl$4.perform(SessionImpl.java:294)
at 
org.apache.jackrabbit.oak.jcr.session.SessionImpl$4.perform(SessionImpl.java:288)
at 
org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:208)
at 
org.apache.jackrabbit.oak.jcr.session.SessionImpl.getRootNode(SessionImpl.java:288)
at 
org.apache.sling.jcr.oak.server.internal.TcclWrappingJackrabbitSession.getRootNode(TcclWrappingJackrabbitSession.java:125)
at 
org.apache.jackrabbit.webdav.jcr.WorkspaceResourceImpl.getMembers(WorkspaceResourceImpl.java:310)
at 
org.apache.jackrabbit.webdav.MultiStatus.addResourceProperties(MultiStatus.java:63)
at 
org.apache.jackrabbit.webdav.server.AbstractWebdavServlet.doPropFind(AbstractWebdavServlet.java:560)
at 
org.apache.jackrabbit.webdav.server.AbstractWebdavServlet.execute(AbstractWebdavServlet.java:348)
at 
org.apache.jackrabbit.webdav.server.AbstractWebdavServlet.service(AbstractWebdavServlet.java:291)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
at 
org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:85)
at 
org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:79)
at 
org.apache.felix.http.sslfilter.internal.SslFilter.doFilter(SslFilter.java:89)
at 
org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:135)
at 
org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:74)
at org.apache.sling.i18n.impl.I18NFilter.doFilter(I18NFilter.java:133)
at 
org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:135)
at 
org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:74)
at 
org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:128)
at 
org.apache.felix.http.base.internal.dispatch.DispatcherServlet.service(DispatcherServlet.java:49)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:224)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at 
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
at org.eclipse.jetty.server.Server.handle(Server.java:523)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320)
at 
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)
at 
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
at 
org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
at 
org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
at 
org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
at 
org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)
at java.lang.Thread.run(Thread.java:745)
{noformat}

> Restrict access for principal everyone and move configuration to repoinit
> -
>
> Key: SLING-6130
> URL:

[jira] [Commented] (SLING-6130) Restrict access for principal everyone and move configuration to repoinit

2016-10-27 Thread Oliver Lietz (JIRA)


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

Oliver Lietz commented on SLING-6130:
-

Requesting the manually started instance at http://localhost:8080 results in:
{noformat}
Forbidden (403)

The requested URL / resulted in an error in 
org.apache.sling.servlets.get.DefaultGetServlet.

Request Progress:

  0 TIMER_START{Request Processing}
  3 COMMENT timer_end format is {,} 

 12 LOG Method=GET, PathInfo=null
 24 TIMER_START{handleSecurity}
   1634 TIMER_END{1607,handleSecurity} authenticator 
org.apache.sling.auth.core.impl.SlingAuthenticator@781504be returns true
   1862 TIMER_START{ResourceResolution}
   2217 TIMER_END{353,ResourceResolution} URI=/ resolves to 
Resource=JcrNodeResource, type=sling:OrderedFolder, superType=null, 
path=/content
   2228 LOG Resource Path Info: SlingRequestPathInfo: path='/content', 
selectorString='null', extension='null', suffix='/'
   2228 TIMER_START{ServletResolution}
   2233 TIMER_START{resolveServlet(/content)}
   2255 TIMER_END{21,resolveServlet(/content)} Using servlet 
org.apache.sling.servlets.get.DefaultGetServlet
   2260 TIMER_END{31,ServletResolution} URI=/ handled by 
Servlet=org.apache.sling.servlets.get.DefaultGetServlet
   2265 LOG Applying Requestfilters
   2273 LOG Calling filter: org.apache.sling.i18n.impl.I18NFilter
   2279 LOG Calling filter: 
org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter
   2283 LOG Applying Componentfilters
   2293 TIMER_START{org.apache.sling.servlets.get.DefaultGetServlet#0}
   2320 LOG Using 
org.apache.sling.servlets.get.impl.helpers.StreamRendererServlet to render for 
extension=null
   2358 LOG Applying Error filters
   2364 LOG Calling filter: org.apache.sling.i18n.impl.I18NFilter
   2369 TIMER_START{handleError:status=403}
   2541 TIMER_END{171,handleError:status=403} Using handler 
org.apache.sling.servlets.resolver.internal.defaults.DefaultErrorHandlerServlet
   3066 TIMER_END{3064,Request Processing} Dumping SlingRequestProgressTracker 
Entries
{noformat}

> Restrict access for principal everyone and move configuration to repoinit
> -
>
> Key: SLING-6130
> URL: https://issues.apache.org/jira/browse/SLING-6130
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR, Oak
>Affects Versions: JCR Oak Server 1.1.0
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>  Labels: security
> Fix For: JCR Oak Server 1.1.2
>
> Attachments: error.log
>
>
> Currently {{everyone}} can {{read}} from {{/}} (configured in 
> {{OakSlingRepositoryManager}}).
> Access for {{everyone}} should be restricted:
> * {{read}} should be restricted to {{/content}}
> * configuration of principals and ACLs should be done with _repoinit_
> # -Change path from {{/}} to {{/content}} in {{OakSlingRepositoryManager}}- 
> (/) (-[r1764259|https://svn.apache.org/r1764259]-)
> # Fix modules (samples) relying on _unrestricted_ {{read}} access
> # Move configuration of ACLs to _repoinit_ (/)
> discussion on 
> [dev@|https://lists.apache.org/thread.html/36908ed62ac93c63cad594a897f8abceb93f08da5bcea30dbce98e58@%3Cdev.sling.apache.org%3E]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-6130) Restrict access for principal everyone and move configuration to repoinit

2016-10-27 Thread Robert Munteanu (JIRA)


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

Robert Munteanu commented on SLING-6130:


If you manually start the instance do you notice anything wrong?

> Restrict access for principal everyone and move configuration to repoinit
> -
>
> Key: SLING-6130
> URL: https://issues.apache.org/jira/browse/SLING-6130
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR, Oak
>Affects Versions: JCR Oak Server 1.1.0
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>  Labels: security
> Fix For: JCR Oak Server 1.1.2
>
> Attachments: error.log
>
>
> Currently {{everyone}} can {{read}} from {{/}} (configured in 
> {{OakSlingRepositoryManager}}).
> Access for {{everyone}} should be restricted:
> * {{read}} should be restricted to {{/content}}
> * configuration of principals and ACLs should be done with _repoinit_
> # -Change path from {{/}} to {{/content}} in {{OakSlingRepositoryManager}}- 
> (/) (-[r1764259|https://svn.apache.org/r1764259]-)
> # Fix modules (samples) relying on _unrestricted_ {{read}} access
> # Move configuration of ACLs to _repoinit_ (/)
> discussion on 
> [dev@|https://lists.apache.org/thread.html/36908ed62ac93c63cad594a897f8abceb93f08da5bcea30dbce98e58@%3Cdev.sling.apache.org%3E]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (SLING-6130) Restrict access for principal everyone and move configuration to repoinit

2016-10-27 Thread Oliver Lietz (JIRA)


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

Oliver Lietz edited comment on SLING-6130 at 10/27/16 5:27 PM:
---

bq. Looks like the repository is not started. You'll have to check the error 
log file and see why, or launch Sling yourself and inspect the instance.

[~rombert], no failures in {{error.log}} (see my comment above)


was (Author: olli):
bq. Looks like the repository is not started. You'll have to check the error 
log file and see why, or launch Sling yourself and inspect the instance.

[~rombert], no failures in !{{error.log}}! (see my comment above)

> Restrict access for principal everyone and move configuration to repoinit
> -
>
> Key: SLING-6130
> URL: https://issues.apache.org/jira/browse/SLING-6130
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR, Oak
>Affects Versions: JCR Oak Server 1.1.0
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>  Labels: security
> Fix For: JCR Oak Server 1.1.2
>
> Attachments: error.log
>
>
> Currently {{everyone}} can {{read}} from {{/}} (configured in 
> {{OakSlingRepositoryManager}}).
> Access for {{everyone}} should be restricted:
> * {{read}} should be restricted to {{/content}}
> * configuration of principals and ACLs should be done with _repoinit_
> # -Change path from {{/}} to {{/content}} in {{OakSlingRepositoryManager}}- 
> (/) (-[r1764259|https://svn.apache.org/r1764259]-)
> # Fix modules (samples) relying on _unrestricted_ {{read}} access
> # Move configuration of ACLs to _repoinit_ (/)
> discussion on 
> [dev@|https://lists.apache.org/thread.html/36908ed62ac93c63cad594a897f8abceb93f08da5bcea30dbce98e58@%3Cdev.sling.apache.org%3E]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-6130) Restrict access for principal everyone and move configuration to repoinit

2016-10-27 Thread Oliver Lietz (JIRA)


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

Oliver Lietz updated SLING-6130:

Attachment: error.log

bq. Looks like the repository is not started. You'll have to check the error 
log file and see why, or launch Sling yourself and inspect the instance.

[~rombert], no failures in !{{error.log}}! (see my comment above)

> Restrict access for principal everyone and move configuration to repoinit
> -
>
> Key: SLING-6130
> URL: https://issues.apache.org/jira/browse/SLING-6130
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR, Oak
>Affects Versions: JCR Oak Server 1.1.0
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>  Labels: security
> Fix For: JCR Oak Server 1.1.2
>
> Attachments: error.log
>
>
> Currently {{everyone}} can {{read}} from {{/}} (configured in 
> {{OakSlingRepositoryManager}}).
> Access for {{everyone}} should be restricted:
> * {{read}} should be restricted to {{/content}}
> * configuration of principals and ACLs should be done with _repoinit_
> # -Change path from {{/}} to {{/content}} in {{OakSlingRepositoryManager}}- 
> (/) (-[r1764259|https://svn.apache.org/r1764259]-)
> # Fix modules (samples) relying on _unrestricted_ {{read}} access
> # Move configuration of ACLs to _repoinit_ (/)
> discussion on 
> [dev@|https://lists.apache.org/thread.html/36908ed62ac93c63cad594a897f8abceb93f08da5bcea30dbce98e58@%3Cdev.sling.apache.org%3E]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Launchpad stable and launchpad unstable

2016-10-27 Thread Robert Munteanu

On Fri, 2016-10-14 at 15:38 +0200, Bertrand Delacretaz wrote:
> I've committed an experimental script [1] which modifies the
> launchpad/builder provisioning model files to remove the version
> numbers for all Sling artifacts. See comments in the script for
> details (and enjoy the sed regexp ;-)
> 
> When doing so, the Slingstart plugin uses the latest snapshot instead
> of a specified version, IIUC.
> 
> The script doesn't fully work yet (see comments in the script -
> patches or hints welcome) but once it does the process for running
> our
> integration tests on this all-snapshots launchpad would be:

For the record, it doesn't work for me either, but misses more SNAPSHOT
versions:

$ mvn dependency:resolve | grep org.apache.sling | grep -v SNAPSHOT
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
support was removed in 8.0
[INFO] --- maven-dependency-plugin:2.10:resolve (default-cli) @
org.apache.sling.launchpad ---
[INFO]org.apache.sling:org.apache.sling.servlets.resolver:jar:2.4.6
:provided
[INFO]org.apache.sling:org.apache.sling.launchpad.base:war:webapp:5
.6.0-2.6.12:provided
[INFO]org.apache.sling:org.apache.sling.commons.scheduler:jar:2.5.2
:provided
[INFO]org.apache.sling:org.apache.sling.commons.log.webconsole:jar:
1.0.0:provided
[INFO]org.apache.sling:org.apache.sling.commons.log:jar:5.0.0:provi
ded
[INFO]org.apache.sling:org.apache.sling.resourceresolver:jar:1.5.0:
provided
[INFO]org.apache.sling:org.apache.sling.launchpad.base:jar:5.6.0-
2.6.12:provided
[INFO]org.apache.sling:org.apache.sling.launchpad.base:jar:app:5.6.
0-2.6.12:provided
[INFO]org.apache.sling:org.apache.sling.event.dea:jar:1.1.0:provide
d
[INFO]org.apache.sling:org.apache.sling.api:jar:2.15.0:provided
[INFO]org.apache.sling:org.apache.sling.installer.core:jar:3.7.0:pr
ovided

Robert

[jira] [Commented] (SLING-6130) Restrict access for principal everyone and move configuration to repoinit

2016-10-27 Thread Robert Munteanu (JIRA)


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

Robert Munteanu commented on SLING-6130:


Looks like the repository is not started. You'll have to check the error log 
file and see why, or launch Sling yourself and inspect the instance.

> Restrict access for principal everyone and move configuration to repoinit
> -
>
> Key: SLING-6130
> URL: https://issues.apache.org/jira/browse/SLING-6130
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR, Oak
>Affects Versions: JCR Oak Server 1.1.0
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>  Labels: security
> Fix For: JCR Oak Server 1.1.2
>
>
> Currently {{everyone}} can {{read}} from {{/}} (configured in 
> {{OakSlingRepositoryManager}}).
> Access for {{everyone}} should be restricted:
> * {{read}} should be restricted to {{/content}}
> * configuration of principals and ACLs should be done with _repoinit_
> # -Change path from {{/}} to {{/content}} in {{OakSlingRepositoryManager}}- 
> (/) (-[r1764259|https://svn.apache.org/r1764259]-)
> # Fix modules (samples) relying on _unrestricted_ {{read}} access
> # Move configuration of ACLs to _repoinit_ (/)
> discussion on 
> [dev@|https://lists.apache.org/thread.html/36908ed62ac93c63cad594a897f8abceb93f08da5bcea30dbce98e58@%3Cdev.sling.apache.org%3E]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Time to release Sling 9

2016-10-27 Thread Robert Munteanu

Hi,

2016 is almost done and Sling 9 is not yet out. Given that we're now
aiming for quarterly Sling releases, it's time to start practicing :-)

I've outlined a list of tasks which should be done for the release, see

  https://issues.apache.org/jira/browse/SLING-6194

It's just a beginning, and if you think that there are more things
which need to be included for the release just include a sub-task.

Call to action
--

- if you think that there are changes to be done for the release, go
ahead and create a sub-task and "just do it"
- if you see any task that might be interesting for you to pick up,
"just do it" :-)
- if you've worked on something cool for the next release of the
Launchpad and think we should let the world know about it, add it to
[1] or just tag the Jira issue with 'Sling-9-ReleaseNotes'

We may or may not switch to the 'stable' Launchpad model for this
release, but in the meantime it's good to keep the releases rolling. We
currently have 15 -SNAPSHOT bundles in the main launchpad, so that's
quite some work in progress.

My aim is to have the launchpad out in November, as I have a feeling
December is not a very productive time of the year. Also, not very
fruitful for making noise about a new release.

Thanks,

Robert


[1]: https://cwiki.apache.org/confluence/display/SLING/Sling+9+Release+
Notes

[jira] [Commented] (SLING-6193) Integrate .mht with AEM

2016-10-27 Thread Robert Munteanu (JIRA)


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

Robert Munteanu commented on SLING-6193:


Do you have a way to reproduce this with just the Sling launchpad?

> Integrate .mht with AEM
> ---
>
> Key: SLING-6193
> URL: https://issues.apache.org/jira/browse/SLING-6193
> Project: Sling
>  Issue Type: Task
>Reporter: Akash
>
> We have seen issues with .mht files not getting rendered in pages.
>  Server performance issue when a huge volume of .mht files saved in AEM which 
> is using SLING at the backend to render pages.
>  would like to know the feasibility in displaying page using .mht.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-6205) Send announcement to u...@sling.apache.org and annou...@apache.org

2016-10-27 Thread Robert Munteanu (JIRA)

Robert Munteanu created SLING-6205:
--

 Summary: Send announcement to u...@sling.apache.org and 
annou...@apache.org
 Key: SLING-6205
 URL: https://issues.apache.org/jira/browse/SLING-6205
 Project: Sling
  Issue Type: Sub-task
Reporter: Robert Munteanu






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-6202) Create 'New and Noteworthy' page for Sling 9

2016-10-27 Thread Robert Munteanu (JIRA)


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

Robert Munteanu updated SLING-6202:
---
Description: This should be similar to 
http://sling.apache.org/news/sling-launchpad-8-released.html . Staging page is 
at https://cwiki.apache.org/confluence/display/SLING/Sling+9+Release+Notes  
(was: This should be similar to 
http://sling.apache.org/news/sling-launchpad-8-released.html . Staging)

> Create 'New and Noteworthy' page for Sling 9
> 
>
> Key: SLING-6202
> URL: https://issues.apache.org/jira/browse/SLING-6202
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>
> This should be similar to 
> http://sling.apache.org/news/sling-launchpad-8-released.html . Staging page 
> is at https://cwiki.apache.org/confluence/display/SLING/Sling+9+Release+Notes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-6204) Use launchpad version 9 in the Maven archetypes

2016-10-27 Thread Robert Munteanu (JIRA)

Robert Munteanu created SLING-6204:
--

 Summary: Use launchpad version 9 in the Maven archetypes
 Key: SLING-6204
 URL: https://issues.apache.org/jira/browse/SLING-6204
 Project: Sling
  Issue Type: Sub-task
Reporter: Robert Munteanu






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-6203) Create a Maven archetype for content packages

2016-10-27 Thread Robert Munteanu (JIRA)

Robert Munteanu created SLING-6203:
--

 Summary: Create a Maven archetype for content packages
 Key: SLING-6203
 URL: https://issues.apache.org/jira/browse/SLING-6203
 Project: Sling
  Issue Type: Sub-task
Reporter: Robert Munteanu






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-6202) Create 'New and Noteworthy' page for Sling 9

2016-10-27 Thread Robert Munteanu (JIRA)

Robert Munteanu created SLING-6202:
--

 Summary: Create 'New and Noteworthy' page for Sling 9
 Key: SLING-6202
 URL: https://issues.apache.org/jira/browse/SLING-6202
 Project: Sling
  Issue Type: Sub-task
Reporter: Robert Munteanu


This should be similar to 
http://sling.apache.org/news/sling-launchpad-8-released.html . Staging



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-6201) Deploy Sling 9 docker image to Docker Hub

2016-10-27 Thread Robert Munteanu (JIRA)

Robert Munteanu created SLING-6201:
--

 Summary: Deploy Sling 9 docker image to Docker Hub
 Key: SLING-6201
 URL: https://issues.apache.org/jira/browse/SLING-6201
 Project: Sling
  Issue Type: Sub-task
Reporter: Robert Munteanu


Note - we should switch to the apache account instead of the apachesling one.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-6200) Deploy API documentation for Sling 9

2016-10-27 Thread Robert Munteanu (JIRA)

Robert Munteanu created SLING-6200:
--

 Summary: Deploy API documentation for Sling 9
 Key: SLING-6200
 URL: https://issues.apache.org/jira/browse/SLING-6200
 Project: Sling
  Issue Type: Sub-task
Reporter: Robert Munteanu






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-6199) Update local launchpad references to 9 or 10-SNAPSHOT

2016-10-27 Thread Robert Munteanu (JIRA)

Robert Munteanu created SLING-6199:
--

 Summary: Update local launchpad references to 9 or 10-SNAPSHOT
 Key: SLING-6199
 URL: https://issues.apache.org/jira/browse/SLING-6199
 Project: Sling
  Issue Type: Sub-task
Reporter: Robert Munteanu






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Deleted] (SLING-6197) Initial release of the content package support for the Installer

2016-10-27 Thread Robert Munteanu (JIRA)


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

Robert Munteanu deleted SLING-6197:
---


> Initial release of the content package support for the Installer
> 
>
> Key: SLING-6197
> URL: https://issues.apache.org/jira/browse/SLING-6197
> Project: Sling
>  Issue Type: Sub-task
>Reporter: Robert Munteanu
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-6198) Deploy the Launchpad 9 artifact to the dist site and Maven central

2016-10-27 Thread Robert Munteanu (JIRA)

Robert Munteanu created SLING-6198:
--

 Summary: Deploy the Launchpad 9 artifact to the dist site and 
Maven central
 Key: SLING-6198
 URL: https://issues.apache.org/jira/browse/SLING-6198
 Project: Sling
  Issue Type: Sub-task
Reporter: Robert Munteanu






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-6197) Initial release of the content package support for the Installer

2016-10-27 Thread Robert Munteanu (JIRA)

Robert Munteanu created SLING-6197:
--

 Summary: Initial release of the content package support for the 
Installer
 Key: SLING-6197
 URL: https://issues.apache.org/jira/browse/SLING-6197
 Project: Sling
  Issue Type: Sub-task
Reporter: Robert Munteanu






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-6196) Initial release of the content package support for the Installer

2016-10-27 Thread Robert Munteanu (JIRA)

Robert Munteanu created SLING-6196:
--

 Summary: Initial release of the content package support for the 
Installer
 Key: SLING-6196
 URL: https://issues.apache.org/jira/browse/SLING-6196
 Project: Sling
  Issue Type: Sub-task
Reporter: Robert Munteanu






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-6195) Initial release of the Content-Package Maven Plugin

2016-10-27 Thread Robert Munteanu (JIRA)

Robert Munteanu created SLING-6195:
--

 Summary: Initial release of the Content-Package Maven Plugin
 Key: SLING-6195
 URL: https://issues.apache.org/jira/browse/SLING-6195
 Project: Sling
  Issue Type: Sub-task
Reporter: Robert Munteanu






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

2016-10-27 Thread Robert Munteanu (JIRA)

Robert Munteanu created SLING-6194:
--

 Summary: 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.4#6332)

[jira] [Resolved] (SLING-2192) Support JAX-RS resource classes

2016-10-27 Thread Robert Munteanu (JIRA)


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

Robert Munteanu resolved SLING-2192.

Resolution: Won't Fix

With OSGi RFC 217 bringing official support to JAX-RS in the Enterprise 
Specification I don't think we need to anything special in Sling.

  https://github.com/osgi/design/tree/master/rfcs/rfc0217

I am resolving this as "Won't Fix", but please reopen if you think there is 
still something to do for us. AFAIK the official implementation will live under 
Apache Aries, but I did not yet find any sign of it.

> Support JAX-RS resource classes
> ---
>
> Key: SLING-2192
> URL: https://issues.apache.org/jira/browse/SLING-2192
> Project: Sling
>  Issue Type: New Feature
>Reporter: Reto Gmür
> Attachments: SLING-2192-20110310.patch, SLING-2192-20111004.patch, 
> SLING-2192-20111013.patch, SLING-2192-new-jax-rs-bundle.patch, 
> SLING-2192-new-jax-rs-bundle.patch, 
> SLING-2192-with-sling-style-style-registration.patch, 
> SLING-2192-with-tests.patch, jaxrs-in-contrib.patch, slingr-on-wink-osgi.patch
>
>
> It should be possible to register jax resource classes and providers as 
> services. As they don't implement a specific interface services that expose 
> java.lang.Object should be considered as javx-rs services iff they have the 
> service property "javax.ws.rs" set to true.
> _Edit, December 2015: the discussions below suggest 
> https://github.com/wcm-io-caravan/caravan-jaxrs as a good and Sling-friendly 
> way of doing that._



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-3317) Concurrent access to WeakHashMap in ConcurrentCache causes infinite loop, 100% CPU usage

2016-10-27 Thread Robert Munteanu (JIRA)


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

Robert Munteanu commented on SLING-3317:


Sorry, this seems to have slipped for some reason. Lots of fixes have been 
applied to the scripting bundles, including one related to concurrency - 
SLING-3984 . Can I ask you to retry with version scripting.jsp version 2.1.6 or 
later and see if the problem still appears?

> Concurrent access to WeakHashMap in ConcurrentCache causes infinite loop, 
> 100% CPU usage
> 
>
> Key: SLING-3317
> URL: https://issues.apache.org/jira/browse/SLING-3317
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Reporter: Takahito Kikuchi
>
> On a web application with Apache Sling Scripting JSP 2.0.24, 100% CPU usage 
> problem happened as following. It looks similar to the tomcat problem, 
> https://issues.apache.org/bugzilla/show_bug.cgi?id=50078
> 
>java.lang.Thread.State: RUNNABLE
>   at java.util.WeakHashMap.get(WeakHashMap.java:470)
>   at org.apache.el.util.ConcurrentCache.get(ConcurrentCache.java:24)
>   at 
> org.apache.el.lang.ExpressionBuilder.createNodeInternal(ExpressionBuilder.java:90)
>   at 
> org.apache.el.lang.ExpressionBuilder.build(ExpressionBuilder.java:146)
>   at 
> org.apache.el.lang.ExpressionBuilder.createValueExpression(ExpressionBuilder.java:190)
>   at 
> org.apache.el.ExpressionFactoryImpl.createValueExpression(ExpressionFactoryImpl.java:68)
>   at 
> org.apache.sling.scripting.jsp.jasper.el.ExpressionEvaluatorImpl.parseExpression(ExpressionEvaluatorImpl.java:45)
>   at 
> org.apache.sling.scripting.jsp.jasper.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:55)
> 
>java.lang.Thread.State: RUNNABLE
>   at java.util.WeakHashMap.eq(WeakHashMap.java:343)
>   at java.util.WeakHashMap.put(WeakHashMap.java:521)
>   at java.util.WeakHashMap.putAll(WeakHashMap.java:640)
>   at org.apache.el.util.ConcurrentCache.put(ConcurrentCache.java:34)
>   at 
> org.apache.el.lang.ExpressionBuilder.createNodeInternal(ExpressionBuilder.java:123)
>   at 
> org.apache.el.lang.ExpressionBuilder.build(ExpressionBuilder.java:146)
>   at 
> org.apache.el.lang.ExpressionBuilder.createValueExpression(ExpressionBuilder.java:190)
>   at 
> org.apache.el.ExpressionFactoryImpl.createValueExpression(ExpressionFactoryImpl.java:68)
>   at 
> org.apache.sling.scripting.jsp.jasper.el.ExpressionEvaluatorImpl.parseExpression(ExpressionEvaluatorImpl.java:45)
>   at 
> org.apache.sling.scripting.jsp.jasper.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:55)
> 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Stuff to work on (Was: sling attic / cleanup)

2016-10-27 Thread Robert Munteanu

On Thu, 2016-10-20 at 17:08 +, Jason Bailey wrote:
> I'm able and willing to work on just about all of that. If I had the
> option I would probably focus on bug fixes, since I get a lot of
> satisfaction out of those.
>  My problem with contributing is more of knowing where to focus than
> anything else, which is why it struck me when it was mentioned that
> some of the items that were going into the attic were going through
> lack of attention.


If you like tweaking builds and figuring out broken CI jobs you might
want to take a look at

  https://builds.apache.org/view/S-Z/view/Sling-Dashboard/

I think in particular the cache extension would need some attention.
Other than that, I would start at the open issue list [1] and drill
down based on the area that interests me, whether this is:

- Maven plug-ins and tooling
- Launchpad ( the general sling launchpad setup )
- Testing ( tools and actual tests )
- IDE ( Eclipse tooling )
- Scripting/JCR/Extensions/etc for actual Sling bundles

Hope this clears up the contribution 'story' a bit. Feel free to ask if
it does not :-)

Robert


[1]: https://issues.apache.org/jira/issues/?jql=project%20%3D%20SLING%2
0AND%20type%20%3D%20%27Bug%27%20AND%20resolution%20%3D%20Unresolved%20a
nd%20assignee%20is%20empty%20ORDER%20BY%20priority%20DESC

> 
> -Original Message-
> From: Robert Munteanu [mailto:romb...@apache.org] 
> Sent: Tuesday, October 18, 2016 4:48 PM
> To: dev@sling.apache.org
> Subject: Stuff to work on (Was: sling attic / cleanup)
> 
> On Tue, 2016-10-18 at 14:32 +, Jason Bailey wrote:
> > Is there a list or something of modules that the sling developers 
> > would like to have someone work on?
> 
> Well :-) What would you like to work on? Top of my head I can think
> of things that need work on
> 
> - automated testing
> - performance checks/improvements
> - bug fixes
> - documentation
> - design
> - IDE Tooling
> - CI setup
> - Maven tooling
> - migration to new parent pom
> 
> (and the list can go on)
> 
> What kind of things do you enjoy working on?
> 
> Robert
> 
> 
> > 
> > 
> > 
> > 
> > -Original Message-
> > From: Bertrand Delacretaz [mailto:bdelacre...@apache.org]
> > Sent: Tuesday, October 18, 2016 10:04 AM
> > To: dev 
> > Subject: Re: sling attic / cleanup
> > 
> > Hi,
> > 
> > On Tue, Oct 18, 2016 at 3:53 PM, Robert Munteanu  > g>
> > wrote:
> > > ...1) There are modules where we have people who think should
> > > move 
> > > to the attic, but also others think the modules should be kept.
> > > 
> > > - contrib/auth/xing
> > > - contrib/commons/html
> > > - contrib/scripting/freemarker ..
> > 
> > 
> > I don't have strong opinions on those but suggest moving at list
> > the 
> > first two to attic.
> > 
> > > ...2) We scheduled contrib/jcr/js for removal, but it's
> > > indirectly 
> > > referenced from contrib/explorers/resourceeditor.
> > > So we either keep both or move both to the attic. ...
> > 
> > 
> > contrib/explorers/resourceeditor has changed very little since
> > r1696091 from 2015-08-15 and the vast majority of commits are from 
> > Sandro who hasn't been present here since January this year AFAICS.
> > 
> > So I suggest moving both modules to attic, it's easy to move back
> > if 
> > needed.
> > 
> > -Bertrand
> > 
> 
>

Re: How to access the requesting resource in the ResourceDecorator

2016-10-27 Thread Carsten Ziegeler

Feike Visser wrote
> hi there,
> 
> Question about the ResourceDecorator [1], since the method with the request 
> is deprecated I am looking to see how to retrieve the requesting resource.
> This mainly in the case of script-resources.
> 
> Like /apps/x was it requested in the context of /content/a or /content/b?
> 
> Any hints/tips?
> 

It seems we don't have any OOTB mechanism for this, you can get to the
resource resolve associated with the thread, but that doesn't really
help as that one has no knowledge of the first request.

But you can register a
org.apache.sling.auth.core.spi.AuthenticationInfoPostProcessor and store
the request path or the tenant name as an attribute into the auth info.
This auth info is then later on available through the getAttribute
method of the resource resolver.

 Regards

Carsten

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

[jira] [Resolved] (SLING-6176) Installer: Persist optional error text per resource

2016-10-27 Thread Konrad Windszus (JIRA)


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

Konrad Windszus resolved SLING-6176.

Resolution: Fixed

I assume this is fixed with all the previous commits. Any more missing error 
texts from some InstallTasks can be tracked in individual JIRA issues.

> Installer: Persist optional error text per resource
> ---
>
> Key: SLING-6176
> URL: https://issues.apache.org/jira/browse/SLING-6176
> Project: Sling
>  Issue Type: Improvement
>  Components: Installer
>Affects Versions: Installer Core 3.7.0, Installer Console 1.0.0, Installer 
> Packages Factory 1.0.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Fix For: Installer Core 3.7.2, Installer Console 1.0.2, Installer 
> Packages Factory 1.0.0
>
> Attachments: SLING-6176-console-v01.patch, SLING-6176-core-v01.patch
>
>
> Currently the OSGi installer web console will just expose a state like 
> „Ignored“ or „Install“ in case a bundle/config/package could not be 
> installed. It would be very helpful (especially in the context of SLING-5014) 
> to additionally persist some error text on the last action, if it was not 
> successful. 
> This error text should be exposed through the web console. That way one could 
> easily determine (even afterwards) why a specific artifact was not installed 
> by the installer.
> See also the discussion at 
> http://www.mail-archive.com/dev@sling.apache.org/msg60872.html.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SLING-6190) More gracefully deal with non existing natures during project import

2016-10-27 Thread Konrad Windszus (JIRA)


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

Konrad Windszus resolved SLING-6190.

Resolution: Fixed

Fixed in [r1766831|https://svn.apache.org/r1766831].

> More gracefully deal with non existing natures during project import
> 
>
> Key: SLING-6190
> URL: https://issues.apache.org/jira/browse/SLING-6190
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.1.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Fix For: Sling Eclipse IDE 1.1.2
>
>
> The project configurator from SLING-3100 fails in case a nature is not 
> available. E.g. with this stack trace in case JSDT is not available:
> {code}
> WARNING: org.eclipse.core.resources code=568 Problems encountered while 
> setting project description.
>   at 
> org.eclipse.core.internal.resources.Project.setDescription(Project.java:1255)
>   at 
> org.apache.sling.ide.eclipse.m2e.internal.ContentPackageProjectConfigurator.addNatures(ContentPackageProjectConfigurator.java:115)
>   at 
> org.apache.sling.ide.eclipse.m2e.internal.ContentPackageProjectConfigurator.access$1(ContentPackageProjectConfigurator.java:103)
>   at 
> org.apache.sling.ide.eclipse.m2e.internal.ContentPackageProjectConfigurator$WtpProjectConfigurer.configure(ContentPackageProjectConfigurator.java:139)
>   at 
> org.apache.sling.ide.eclipse.m2e.internal.ContentPackageProjectConfigurator.configure(ContentPackageProjectConfigurator.java:91)
>   at 
> org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120)
>   at 
> org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:501)
>   at 
> org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
>   at 
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
>   at 
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
>   at 
> org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:494)
>   at 
> org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:281)
>   at 
> org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:168)
>   at 
> org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
>   at 
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
>   at 
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
>   at 
> org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
>   at 
> org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355)
>   at 
> org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:136)
> ...
>   at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>   WARNING: org.eclipse.core.resources code=35 Nature does not exist: 
> org.eclipse.wst.jsdt.core.jsNature.
> {code}
> We should deal more gracefully with missing natures (which are not enforced 
> at all by Sling IDE e.g. through required bundles)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

How to access the requesting resource in the ResourceDecorator

2016-10-27 Thread Feike Visser

hi there,

Question about the ResourceDecorator [1], since the method with the request is 
deprecated I am looking to see how to retrieve the requesting resource.
This mainly in the case of script-resources.

Like /apps/x was it requested in the context of /content/a or /content/b?

Any hints/tips?

--
Feike

[1] 
https://sling.apache.org/apidocs/sling6/org/apache/sling/api/resource/ResourceDecorator.html

[jira] [Created] (SLING-6193) Integrate .mht with AEM

2016-10-27 Thread Akash (JIRA)

Akash created SLING-6193:


 Summary: Integrate .mht with AEM
 Key: SLING-6193
 URL: https://issues.apache.org/jira/browse/SLING-6193
 Project: Sling
  Issue Type: Task
Reporter: Akash


We have seen issues with .mht files not getting rendered in pages.
 Server performance issue when a huge volume of .mht files saved in AEM which 
is using SLING at the backend to render pages.
 would like to know the feasibility in displaying page using .mht.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-6192) Remove workaround for KARAF-4707

2016-10-27 Thread Oliver Lietz (JIRA)

Oliver Lietz created SLING-6192:
---

 Summary: Remove workaround for KARAF-4707
 Key: SLING-6192
 URL: https://issues.apache.org/jira/browse/SLING-6192
 Project: Sling
  Issue Type: Task
  Components: Karaf
Reporter: Oliver Lietz
Assignee: Oliver Lietz
Priority: Minor
 Fix For: Karaf Features 0.2.0, Karaf Distribution 0.2.0


workaround added in [r1766789|https://svn.apache.org/r1766789] and 
[r1766790|https://svn.apache.org/r1766790]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[RESULT][VOTE] Release Apache Sling Scheduler Support 2.5.2

2016-10-27 Thread Stefan Egli

Hi,

The release passed with 3 binding votes.

Cheers,
Stefan

On 20/10/16 17:58, "Stefan Egli"  wrote:

>Hi,
>
>We solved 1 issue in the Scheduler Support 2.5.2 release:
>https://issues.apache.org/jira/browse/SLING/fixforversion/12337997
>
>Staging repository:
>https://repository.apache.org/content/repositories/orgapachesling-1552/
>
>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 1552 /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.
>
>
>Cheers,
>Stefan
>
>

[jira] [Commented] (SLING-5750) Dynamic search path to load dynamically different component renditions

2016-10-27 Thread Feike Visser (JIRA)


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

Feike Visser commented on SLING-5750:
-

hi [~cziegeler],

Is there anyway in the ResourceDecorator to get info about the 
requesting-resource?
To know if /apps/x is requested in the context of /content/x or /content/y

> Dynamic search path to load dynamically different component renditions
> --
>
> Key: SLING-5750
> URL: https://issues.apache.org/jira/browse/SLING-5750
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Reporter: Feike Visser
>
> In the current setup in Sling there is 1:1 relation between a component and 
> the code that implements this components.
> In a multi-tenant/multi-brand environment you have a need to switch this 
> dynamically based on the tenant that you are in.
> Example
> [default]
> Component A -> /apps/components/componeneta/componeneta.html
> [Tenant A]
> Component A -> /apps/tenanta/componeneta.html
> [Tenant B]
> Component A -> /apps/tenantb/componeneta.html
> Content structure
> /tenanta/
>  sling:scriptFolder -> /apps/tenanta
> /tenantb/
>  sling:scriptFolder -> /apps/tenantb
> Suggestion: If we would implement a dynamic search path the implementation 
> can choose itself where to point to when we are in a multi-tenant environment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

50 matches

Mail list logo