[GitHub] [sling-whiteboard] kwin edited a comment on issue #49: Made the path of the MetricsExporter servlet configurable.

kwin edited a comment on issue #49: Made the path of the MetricsExporter servlet configurable. URL: https://github.com/apache/sling-whiteboard/pull/49#issuecomment-528569853 This is already configurable without this PR. The only change through this PR is that there is a UI for that in the

[GitHub] [sling-whiteboard] kwin commented on issue #49: Made the path of the MetricsExporter servlet configurable.

kwin commented on issue #49: Made the path of the MetricsExporter servlet configurable. URL: https://github.com/apache/sling-whiteboard/pull/49#issuecomment-528569853 This is already configurable without this PR. The only through this PR is that there is a UI for that in the configure

[GitHub] [sling-whiteboard] bjoernweide opened a new pull request #49: Made the path of the MetricsExporter servlet configurable.

bjoernweide opened a new pull request #49: Made the path of the MetricsExporter servlet configurable. URL: https://github.com/apache/sling-whiteboard/pull/49 This makes the servlet path of the WrapperMetricsServlet configurable.

Sling Feature Converter Maven Plugin Release

Hi I am ready to create a release for the project: https://github.com/apache/sling-feature-converter-maven-plugin As the Sling Feature dependencies were just released. The only holdout is the CP Converter project which is still

Re: [hackathon] switch to feature model

Hi Thanks for the update. A few months back I created this project: https://github.com/schaefa/sling-featuremodel-starter This project does take the existing Sling Provisioning Model and converts it into a FM and then launches it. This

[jira] [Updated] (SLING-8679) CMS - Update Health Check Support

[ https://issues.apache.org/jira/browse/SLING-8679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Klco updated SLING-8679: Component/s: App CMS Fix Version/s: App CMS 0.12.2 Affects Version/s: Version App CMS

[jira] [Created] (SLING-8679) CMS - Update Health Check Support

Dan Klco created SLING-8679: --- Summary: CMS - Update Health Check Support Key: SLING-8679 URL: https://issues.apache.org/jira/browse/SLING-8679 Project: Sling Issue Type: New Feature

[jira] [Assigned] (SLING-8679) CMS - Update Health Check Support

[ https://issues.apache.org/jira/browse/SLING-8679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Klco reassigned SLING-8679: --- Assignee: Dan Klco > CMS - Update Health Check Support > - > >

[jira] [Resolved] (SLING-8678) Upgrade File Optimization from Commons Lang 2 -> 3

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

[jira] [Created] (SLING-8678) Upgrade File Optimization from Commons Lang 2 -> 3

Dan Klco created SLING-8678: --- Summary: Upgrade File Optimization from Commons Lang 2 -> 3 Key: SLING-8678 URL: https://issues.apache.org/jira/browse/SLING-8678 Project: Sling Issue Type: Bug

[jira] [Updated] (SLING-8678) Upgrade File Optimization from Commons Lang 2 -> 3

[ https://issues.apache.org/jira/browse/SLING-8678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Klco updated SLING-8678: Issue Type: Improvement (was: Bug) > Upgrade File Optimization from Commons Lang 2 -> 3 >

[jira] [Assigned] (SLING-8678) Upgrade File Optimization from Commons Lang 2 -> 3

[ https://issues.apache.org/jira/browse/SLING-8678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Klco reassigned SLING-8678: --- Assignee: Dan Klco > Upgrade File Optimization from Commons Lang 2 -> 3 >

Re: [hackathon] externalization / resource mapping / rewriter

Specifically with regard to the re-writer I'm working on a replacement for this which I'm currently calling the transformer -> https://github.com/apache/sling-whiteboard/tree/master/transformer 1. It uses an HTML tokenizer that was added to the HTML utilities to generate a stream of elements

RE: [hackathon] switch to feature model

well, currently the sling starter is defined by the provisioning model, we just want to switch to the feature model. the output will be basically the same, just the way to describe it changes. using feature model alone does not imply that the instance is immutable or cannot be used to deploy

Re: [hackathon] Sling Packager / npm tooling

Hi, On Thu, Sep 5, 2019 at 3:56 PM Stefan Seifert wrote: > ...- probably we should look at the apache openwhisk project - they have lot > of npm releases, how do they do it?... I haven't looked at the details so far but https://github.com/apache/openwhisk-client-js is published on npm,

[hackathon] other topics

- we should remove libraries embedded in our sling modules, and convert embeds of single classes probably to external dependencies - include JPMS metadata in the bundles: not planned currently, we see no use case justifying the effort version numbers of sling bundles: - we should increase (at

[hackathon] maven archetypes

- currently there are lots of sling maven archetypes, and most of them not well maintained - we would favor to have only one single "project" archetypes, probably the new "project" archetype contributed by andy - add parameters to switch features on and off, e.g. for generating only with bundle

[hackathon] externalization / resource mapping / rewriter

- resource mapping - add a new SPI to define the mapping - add a default impl that reads the mapping from /etc/map as it is done today - possible to override with service ranking - but: there is already the ResourceMapper interface - introduced 1-2 years ago, use case was to get all

Re: [hackathon] switch to feature model

Hi I am not sure what the goals are when switching to FM? As far as I understand it the FM should allow us to create an unmutable Sling instance and an update is done by creating a new Sling instance that is then deployed over the existing one keeping the user data repository alive but

[hackathon] CI experience

- Challenge: Building non-committer PRs with Jenkins is no longer allowed - problem described in SLING-7245 - Validate pull requests using Jenkins Resolved - reason are security issues, see also INFRA-18973 - we assume it will not be fixed by INFRA due to this, we need another

[hackathon] tooling for installing content packages in sling

- we currently have 2 "initiatives" - the one from composum, and the one in sling that carsten started and konrad picked up later - we should replace the composum one with the sling one in the sling starter - work on the sling one is nearly completed, a release can be done soon - uninstallation:

[hackathon] bnd plugin for removing bundle headers

- history/background: it would be better placed in bnd, but the bnd project did not want it. contributing to felix lead to lots of discussion but no resolution. - so we're fine to put it into sling in a separate repo - but the plugin and repo should not have a generic "bnd-plugins" name, as this

[hackathon] new asf.yaml feature from INFRA

- we want to make use of the new option to set github project properties via .asf.yaml - description: use the description from the module POM - url: link to module-specific docs page, otherwise sling website (we have no such mapping yet, would be helpful anyways for the users) - topics: -

[hackathon] switch to feature model

- yes, we want to switch - and soon, so it can be part of sling 12 - what the feature model tooling is currently missing is building a combined jar file or WAR file - for this it's planned to start with a "bridging solution", that means generating a provisioning out of the feature models and

[jira] [Created] (SLING-8677) Propagate/persist error message with state changes to IGNORED

Konrad Windszus created SLING-8677: -- Summary: Propagate/persist error message with state changes to IGNORED Key: SLING-8677 URL: https://issues.apache.org/jira/browse/SLING-8677 Project: Sling

[hackathon] adaptTo() 2018 - Sling Committer round table & hackathon results

on tuesday we had the Sling Committer round table @ adaptTo() in Berlin, and today the Hackathon in the office of pro!vision Berlin. i will publish the results *) of the discussions on this list using the "[hackathon]" prefix in the subject. participants of the hackathon: Carsten, Georg, Radu,

[hackathon] Sling Packager / npm tooling

- up to now we have no sling module that ends up in the npm registry - the sling packager is the first one - we need to clarify the technical details how to deploy the npm package on npm registry - an organization in NPM should be used, e.g. "apache-sling" - ci testing could be done by adding a

Re: [VOTE] Release Apache Sling Tooling Support Install 1.0.6

+1 (non-binding) - Andy > On Sep 5, 2019, at 3:50 AM, Robert Munteanu wrote: > > Hi, > > We solved 1 issue in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12342561 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2125/ >

[jira] [Resolved] (SLING-6987) Content Package Installer: Support hollow packages

[ https://issues.apache.org/jira/browse/SLING-6987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-6987. Resolution: Fixed > Content Package Installer: Support hollow packages >

[jira] [Commented] (SLING-6987) Content Package Installer: Support hollow packages

[ https://issues.apache.org/jira/browse/SLING-6987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16923381#comment-16923381 ] Konrad Windszus commented on SLING-6987: The remaining tasks are tracked in

[jira] [Updated] (SLING-6989) Package Installer Factory: Prevent package upload in case of uninstallation/2nd installation

[ https://issues.apache.org/jira/browse/SLING-6989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6989: --- Description: Currently in case a package is supposed to be uninstalled through the package

[jira] [Updated] (SLING-6989) Package Installer Factory: Prevent package upload in case of uninstallation

[ https://issues.apache.org/jira/browse/SLING-6989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6989: --- Description: Currently in case a package is supposed to be uninstalled through the package

[jira] [Updated] (SLING-6989) Package Installer Factory: Prevent package upload in case of uninstallation/2nd installation

[ https://issues.apache.org/jira/browse/SLING-6989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6989: --- Summary: Package Installer Factory: Prevent package upload in case of uninstallation/2nd

[VOTE] Release Apache Sling Tooling Support Install 1.0.6

Hi, We solved 1 issue in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12342561 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2125/ You can use this UNIX script to download the release and verify the signatures:

[jira] [Created] (SLING-8676) Prototype does not allow to remove requirements and capabilities

Carsten Ziegeler created SLING-8676: --- Summary: Prototype does not allow to remove requirements and capabilities Key: SLING-8676 URL: https://issues.apache.org/jira/browse/SLING-8676 Project: Sling

[Fwd: [NOTICE] Introducing .asf.yaml for enhanced automation of git repository services]

Hi, I have done some quick tests in the whiteboard and setting topics/descriptions works just fine. I have also marked some affected features from [1] as solved. Thanks, Robert [1]: https://cwiki.apache.org/confluence/display/SLING/Apache+Gitbox+Self+Service+Requirements --- Begin Message ---

[jira] [Commented] (SLING-8656) Get rid of deprecated/no longer maintained maven-osgi dependency

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

[jira] [Resolved] (SLING-8656) Get rid of deprecated/no longer maintained maven-osgi dependency

[ https://issues.apache.org/jira/browse/SLING-8656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-8656. Resolution: Fixed > Get rid of deprecated/no longer maintained maven-osgi dependency >

[GitHub] [sling-slingstart-maven-plugin] kwin merged pull request #5: SLING-8656 use bnd for Maven to OSGi version conversion

kwin merged pull request #5: SLING-8656 use bnd for Maven to OSGi version conversion URL: https://github.com/apache/sling-slingstart-maven-plugin/pull/5 This is an automated message from the Apache Git Service. To respond

Re: [IDEA][POC] Resource Based Caching in Sling

ok, thanks Ben Of course you have the right to continue however you like, but :) it would be ultimately nice to just have one great caching solution. Especially for users its usually hard to figure out what to choose if there are several solutions. So maybe once you're further down the road

Re: [IDEA][POC] Resource Based Caching in Sling

Hi Carsten, hi Dan, A short update: David Gonzalez, who is driving the ACS AEM Commons HTTP Cache project, just confirmed: "once it serves from cache (request or resource include) nothing within that caches response is modifiable(outside transformer pipelines). it just streams that chunk of