[jira] [Created] (SLING-7311) The SlingScriptEngineManager doesn't correctly flush script engine associations

Radu Cotescu created SLING-7311: --- Summary: The SlingScriptEngineManager doesn't correctly flush script engine associations Key: SLING-7311 URL: https://issues.apache.org/jira/browse/SLING-7311 Project:

[jira] [Assigned] (SLING-7308) HTLBlog sample - rendering scripts not used

[ https://issues.apache.org/jira/browse/SLING-7308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu reassigned SLING-7308: --- Assignee: Radu Cotescu > HTLBlog sample - rendering scripts not used >

[jira] [Commented] (SLING-7309) SlingBucks sample - rendering scripts not used

[ https://issues.apache.org/jira/browse/SLING-7309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289984#comment-16289984 ] Chris Millar commented on SLING-7309: - I think this is a result HTLBlog incorrectly installing first.

[jira] [Updated] (SLING-7309) SlingBucks sample - rendering scripts not used

[ https://issues.apache.org/jira/browse/SLING-7309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Millar updated SLING-7309: Attachment: Screen Shot 2017-12-13 at 2.48.38 PM.png > SlingBucks sample - rendering scripts not

[jira] [Commented] (SLING-7308) HTLBlog sample - rendering scripts not used

[ https://issues.apache.org/jira/browse/SLING-7308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289968#comment-16289968 ] Chris Millar commented on SLING-7308: - This PR fixes this issue:

[jira] [Commented] (SLING-7308) HTLBlog sample - rendering scripts not used

[ https://issues.apache.org/jira/browse/SLING-7308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289964#comment-16289964 ] ASF GitHub Bot commented on SLING-7308: --- auniverseaway opened a new pull request #1: SLING-7308 -

[GitHub] auniverseaway opened a new pull request #1: SLING-7308 - Sling 9 Compatibility

auniverseaway opened a new pull request #1: SLING-7308 - Sling 9 Compatibility URL: https://github.com/apache/sling-samples/pull/1 It appears initial content loader has changed in Sling 9 which caused this sample to break HTL rendering. Resolves: SLING-7308

[jira] [Assigned] (SLING-7255) Donating Sling Resource Encryption Utils

[ https://issues.apache.org/jira/browse/SLING-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-7255: -- Assignee: Robert Munteanu > Donating Sling Resource Encryption Utils >

[jira] [Updated] (SLING-7255) Donating Sling Resource Encryption Utils

[ https://issues.apache.org/jira/browse/SLING-7255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7255: --- Component/s: Extensions > Donating Sling Resource Encryption Utils >

Re: value level encryption - Donating?

Sure thing. I'll start working on that. -- Jason On Wed, Dec 13, 2017, at 12:33 PM, Robert Munteanu wrote: > Hi again Jason, > > I took a quick look at the code and here are my suggestions before > starting the official donation process: > > 1. Merge the two bundles into a single one > > The

Re: value level encryption - Donating?

Hi again Jason, I took a quick look at the code and here are my suggestions before starting the official donation process: 1. Merge the two bundles into a single one The separation from an API point of view is sound, but I'm not sure it's really needed. Having a single bundle would help with

[jira] [Resolved] (SLING-7304) Add support for primitive arrays in ObjectModel#toString and ObjectModel#toCollection

[ https://issues.apache.org/jira/browse/SLING-7304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-7304. - Resolution: Fixed Fixed in

[jira] [Commented] (SLING-7310) Sling Dynamic Include: When HTML file is initially created, the includes are not processed

[ https://issues.apache.org/jira/browse/SLING-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289513#comment-16289513 ] Henry Kuijpers commented on SLING-7310: --- For our use-case, using JSI is for now a viable workaround.

[jira] [Created] (SLING-7310) Sling Dynamic Include: When HTML file is initially created, the includes are not processed

Henry Kuijpers created SLING-7310: - Summary: Sling Dynamic Include: When HTML file is initially created, the includes are not processed Key: SLING-7310 URL: https://issues.apache.org/jira/browse/SLING-7310

[jira] [Resolved] (SLING-7306) The JS Use Provider bundle should explicitly depend on the Rhino Script Engine

[ https://issues.apache.org/jira/browse/SLING-7306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-7306. - Resolution: Fixed Fixed in

[jira] [Resolved] (SLING-7234) ServiceFactory.getService() resulted in a cycle in sling karaf

[ https://issues.apache.org/jira/browse/SLING-7234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-7234. - Resolution: Cannot Reproduce [~ivoleitao], I'm resolving this issue. Please open new issues for

RE: Maven Sling Plugin - fsmount

currently the goal is to provide a "full automatic experience" - when calling "sling:fsmount" on a maven project it is detected automatically if it is a Sling-Initial-Content or filevault project and creates the OSGi mapping accordingly. you need a custom additional mapping beyond this

[jira] [Commented] (SLING-7298) Validation IT: Use slingstart-maven-plugin in favour of pax-exam

[ https://issues.apache.org/jira/browse/SLING-7298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289466#comment-16289466 ] Oliver Lietz commented on SLING-7298: - bq. That is all I care about right now in the context of the

[jira] [Created] (SLING-7309) SlingBucks sample - rendering scripts not used

Robert Munteanu created SLING-7309: -- Summary: SlingBucks sample - rendering scripts not used Key: SLING-7309 URL: https://issues.apache.org/jira/browse/SLING-7309 Project: Sling Issue Type:

[jira] [Assigned] (SLING-7306) The JS Use Provider bundle should explicitly depend on the Rhino Script Engine

[ https://issues.apache.org/jira/browse/SLING-7306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu reassigned SLING-7306: --- Assignee: Radu Cotescu > The JS Use Provider bundle should explicitly depend on the Rhino

[jira] [Commented] (SLING-7308) HTLBlog sample - rendering scripts not used

[ https://issues.apache.org/jira/browse/SLING-7308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289440#comment-16289440 ] Robert Munteanu commented on SLING-7308: [~radu.cotescu] - you initially imported this sample so

[jira] [Created] (SLING-7308) HTLBlog sample - rendering scripts not used

Robert Munteanu created SLING-7308: -- Summary: HTLBlog sample - rendering scripts not used Key: SLING-7308 URL: https://issues.apache.org/jira/browse/SLING-7308 Project: Sling Issue Type:

[jira] [Commented] (SLING-7307) Sling Model impl should not embed beanutils

[ https://issues.apache.org/jira/browse/SLING-7307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289406#comment-16289406 ] Justin Edelson commented on SLING-7307: --- True, but for the worst possible reason. Fixed in

[jira] [Commented] (SLING-7307) Sling Model impl should not embed beanutils

[ https://issues.apache.org/jira/browse/SLING-7307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289386#comment-16289386 ] Robert Munteanu commented on SLING-7307: I think this caused a failure in the models ITs, see

[jira] [Resolved] (SLING-7307) Sling Model impl should not embed beanutils

[ https://issues.apache.org/jira/browse/SLING-7307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-7307. --- Resolution: Fixed PR Merged > Sling Model impl should not embed beanutils >

[jira] [Resolved] (SLING-7305) The org.apache.sling.scripting.javascript bundle should add more specific information about the Script Engine it provides

[ https://issues.apache.org/jira/browse/SLING-7305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-7305. - Resolution: Fixed Fixed in

[jira] [Commented] (SLING-7307) Sling Model impl should not embed beanutils

[ https://issues.apache.org/jira/browse/SLING-7307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16289334#comment-16289334 ] ASF GitHub Bot commented on SLING-7307: --- justinedelson closed pull request #2: SLING-7307 - remove

[GitHub] justinedelson closed pull request #2: SLING-7307 - remove embedded BeanUtils

justinedelson closed pull request #2: SLING-7307 - remove embedded BeanUtils URL: https://github.com/apache/sling-org-apache-sling-models-impl/pull/2 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance:

Re: Maven Sling Plugin - fsmount

Hi Stefan Thanks for your reply. I was hoping that we could avoid generating build artifacts inside the "src" folder. It just doesn't feel quite right. Also, I would like to locate the respective "*.ts" and "*.scss" files in the location where the compiled "*.js" and "*.css" files end up. I

RE: Maven Sling Plugin - fsmount

hello julian. yes, i think your assumptions are right. in case of filevault project there is currently no way to add some "custom additional mappings" (although you could of course add an additional mapping with only "files and folders" only for your target dir, when there are no content

Maven Sling Plugin - fsmount

Hi all and Stefan in particular I am in the process of setting up a maven build for a joint frontend (HTML, CSS, JS) and backend team (Sling / AEM). The goals for the frontend team workflow are: - use Node.js based tooling / frontend build (integrated using frontend-maven-plugin - works) -

[jira] [Resolved] (SLING-7299) slingstart-maven-plugin: Do not always attach artifact in goal "package"

[ https://issues.apache.org/jira/browse/SLING-7299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-7299. Resolution: Fixed > slingstart-maven-plugin: Do not always attach artifact in goal

[jira] [Commented] (SLING-7299) slingstart-maven-plugin: Do not always attach artifact in goal "package"

[ https://issues.apache.org/jira/browse/SLING-7299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16288897#comment-16288897 ] ASF GitHub Bot commented on SLING-7299: --- kwin closed pull request #1: SLING-7299 do not always

[jira] [Commented] (SLING-7299) slingstart-maven-plugin: Do not always attach artifact in goal "package"

[ https://issues.apache.org/jira/browse/SLING-7299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16288898#comment-16288898 ] Konrad Windszus commented on SLING-7299: Merged PR in

[GitHub] kwin closed pull request #1: SLING-7299 do not always attach built artifact

kwin closed pull request #1: SLING-7299 do not always attach built artifact URL: https://github.com/apache/sling-slingstart-maven-plugin/pull/1 This is an automated message from the Apache Git Service. To respond to the

[jira] [Commented] (SLING-7302) slingstart-maven-plugin: Also consider the project's version itself in the PomArtifactVersionResolver

[ https://issues.apache.org/jira/browse/SLING-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16288896#comment-16288896 ] Konrad Windszus commented on SLING-7302: Merged PR in

[jira] [Commented] (SLING-7302) slingstart-maven-plugin: Also consider the project's version itself in the PomArtifactVersionResolver

[ https://issues.apache.org/jira/browse/SLING-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16288893#comment-16288893 ] ASF GitHub Bot commented on SLING-7302: --- kwin closed pull request #2: SLING-7302 consider the

[jira] [Resolved] (SLING-7302) slingstart-maven-plugin: Also consider the project's version itself in the PomArtifactVersionResolver

[ https://issues.apache.org/jira/browse/SLING-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-7302. Resolution: Fixed > slingstart-maven-plugin: Also consider the project's version itself in

[GitHub] kwin closed pull request #2: SLING-7302 consider the project's artifact itself for the

kwin closed pull request #2: SLING-7302 consider the project's artifact itself for the URL: https://github.com/apache/sling-slingstart-maven-plugin/pull/2 This is an automated message from the Apache Git Service. To respond

Re: NPE in Oak with PaxExam IT

Hi Robert, the version from Oak was the one being provided in pax-exam 0.0.4 (https://github.com/apache/sling-org-apache-sling-testing-paxexam/tree/org.apache.sling.testing.paxexam-0.0.4

Re: Git repo for sling testing tools?

I don't have plans to work on it. But moving to a new GitHub attic sound fine, as we missed moving it to SVN contrib before the migration. > On 11. Dec 2017, at 22:09, Robert Munteanu wrote: > > Hi Konrad, > > On Fri, 2017-12-08 at 16:35 +0100, Konrad Windszus wrote: >>

[jira] [Closed] (SLING-7290) The Sling Servlet Resolver does not work correctly in some inheritance scenarios

[ https://issues.apache.org/jira/browse/SLING-7290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu closed SLING-7290. --- > The Sling Servlet Resolver does not work correctly in some inheritance > scenarios >