[VOTE] Release Apache Sling JCR ContentLoader 2.5.0

Hi, We solved 6 issues in this release: https://issues.apache.org/jira/projects/SLING/versions/12350190 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2569/ You can use this UNIX script to download the release and verify the signatures: https://gitbox.apach

[RESULT][VOTE] Release Apache Sling JCR ContentLoader 2.5.0

Hi, The vote has passed with the following result : +1 (binding): Robert, Stefan, Dan I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Thanks for voting, Konrad

Re: Introducing Lombok to Sling?

Hi, to be honest I am rather opposed to that idea as Lombok has the following disadvantages from my PoV: - Incremental builds in Eclipse require a dedicated plugin - You need to know Lombok before you can understand the code in some cases - Another third party library - Refactoring support of ID

Extension of URIProvider to use Optional

Hi, currently URIProvider is not allowed to return null according to https://github.com/apache/sling-org-apache-sling-api/blob/333fa20f07a1d42897c9e0b6253bec5dcedb3e0b/src/main/java/org/apache/sling/api/resource/external/URIProvider.java#L48. This forces every URIProvider to throw an exception for

Re: Extension of URIProvider to use Optional

I now made a proposal in the PR attached to https://issues.apache.org/jira/browse/SLING-11067. > On 14. Jan 2022, at 10:41, Konrad Windszus wrote: > > Hi, > currently URIProvider is not allowed to return null according to > https://github.com/apache/sling-org-apache

[VOTE] Release Apache Sling Parent and Bundle Parent 47

Hi, We solved some issues in these releases: Parent 47: https://issues.apache.org/jira/projects/SLING/versions/12350630 Bundle Parent 47: https://issues.apache.org/jira/projects/SLING/versions/12350629 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2585/

[VOTE] Release Apache Sling JCR Resource 3.2.0

Hi, We solved 3 issues in this release: https://issues.apache.org/jira/projects/SLING/versions/12351238 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2586/ You can use this UNIX script to download the release and verify the signatures: https://gitbox.apa

Re: [VOTE] Release Apache Sling Parent and Bundle Parent 47

Here is my +1 Konrad > On 18. Jan 2022, at 19:32, Konrad Windszus wrote: > > Hi, > > We solved some issues in these releases: > Parent 47: https://issues.apache.org/jira/projects/SLING/versions/12350630 > Bundle Parent 47: > https://issues.apache.org/jira/projects

[RESULT] [VOTE] Release Apache Sling Parent and Bundle Parent 47

Hi, The vote has passed with the following result +1 (binding): Dan, Stefan and myself I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Thanks for voting, Konrad

[RESULT] [VOTE] Release Apache Sling JCR Resource 3.2.0

Hi, The vote has passed with the following result +1 (binding): Dan, Carsten and Stefan I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Thanks for voting, Konrad

Re: [VOTE] Release Apache Sling Sitemap version 1.0.6

+1 Konrad P.S. Can you add the managed OSGi dependencies to sling-bundle-parent, they are probably useful for other modules as well? > On 26. Jan 2022, at 17:34, Dirk Rudolph wrote: > > Hi, > > We solved 7 issues in this release: > https://issues.apache.org/jira/projects/SLING/versions/12350

Re: [VOTE] Release Apache Sling Starter 12, Apache Sling Project Archetype 1.0.6 and associated testing modules,

Hi, I cannot reproduce the issue from Stefan on my Mac. But I would like to fix the wrong API documentation (https://issues.apache.org/jira/browse/SLING-11172 ) and also the WARN around the missing/wrong service user for Sling Auth Core (https:

Re: [VOTE] Release Apache Sling Starter 12, Apache Sling Project Archetype 1.0.6 and associated testing modules,

And I found another blocker: https://issues.apache.org/jira/browse/SLING-11173 <https://issues.apache.org/jira/browse/SLING-11173> which deserves fixing prior to release. Therefore voting -1. Konrad > On 2. Mar 2022, at 18:28, Konrad Windszus wrote: > > Hi, > I cannot r

Re: [VOTE] Release Apache Sling Starter 12, Apache Sling Project Archetype 1.0.6 and associated testing modules,

For me only 1 is a blocker, as I think that running in an OSGi R8 compliant container should also be mentioned in the release notes. Konrad > Am 03.03.2022 um 11:41 schrieb Robert Munteanu : > > Hi Konrad, > >> On Wed, 2022-03-02 at 18:47 +0100, Konrad Windszus wrote: >

Re: Restarting Starter 12 vote (was: [VOTE] Release Apache Sling Starter 12, Apache Sling Project Archetype 1.0.6 and associated testing modules)

version number. > > Thoughts? > > Thanks, > Robert > > On Thu, 2022-03-03 at 11:46 +0100, Konrad Windszus wrote: >> For me only 1 is a blocker, as I think that running in an OSGi R8 >> compliant container should also be mentioned in the release notes. >> Kon

Re: Restarting Starter 12 vote (was: [VOTE] Release Apache Sling Starter 12, Apache Sling Project Archetype 1.0.6 and associated testing modules)

-released.md <https://github.com/apache/sling-site/blob/master/src/main/jbake/content/news/sling-12-released.md>. WDYT? Konrad > On 4. Mar 2022, at 15:22, Konrad Windszus wrote: > > +1 for 3. > >> On 4. Mar 2022, at 14:28, Robert Munteanu wrote: >> >> Ok,

Re: [VOTE] Release Apache Sling Starter Content 1.0.12

+1 Konrad > On 4. Mar 2022, at 16:00, Robert Munteanu wrote: > > Hi, > > We solved 1 issue in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12350928 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2606/ > > You can use t

Enable Web Analytics with Matomo?

Hi, Recently ASF set up a hosted instance of Matomo providing web analytics for ASF project’s websites [1]. WDYT about enabling web analytics with Matomo to learn more about our visitors? That would require including some Javascript similar to what was done for Maven recently in [2] to our JBake

Re: content hacks in the pipeline

Hi Nicolas, anything which eases the process of content migration for blue/green deployments will be highly appreciated. Hiding the differences on the resource level sounds like a good idea although you probably have to distinguish between read/write access. Looking forward to your proposal. Kon

Re: Enable Web Analytics with Matomo?

022-03-07 at 16:34 +0100, Konrad Windszus wrote: >> WDYT about enabling web analytics with Matomo to learn more about our >> visitors? > > Sounds good to me. Is it already defined who can access the analytics > data? > > Thanks, > Robert

Re: [Content Loader] Decide on approach to unblock Sling 12

+1 for a) for now. Afterwards we can take some time and probably do c) or improve b) by waiting for the service to become active (in case it is resolvable in the current system). Konrad > On 10. Mar 2022, at 17:33, Stefan Seifert > wrote: > > during release process of Sling 12 we discovere

Site ID for Apache Sling

Hi, I would like to request a Matomo Site ID for Apache Sling. Thanks in advance, Konrad (on behalf of the Apache Sling PMC)

Re: [NOTICE] Dependabot Updates enabled for all projects

I fully agree here. I don’t think dependabot can be controlled via .asf.yaml yet, so for now we need to disable manually per repo… > Am 07.04.2022 um 10:18 schrieb Stefan Seifert > : > > i agree with robert that probably for most of our modules dependabot is not > helpful (exceptions are the

Re: [NOTICE] Dependabot Updates enabled for all projects

I created https://issues.apache.org/jira/browse/INFRA-23111 <https://issues.apache.org/jira/browse/INFRA-23111> to allow disabling dependabot for repos. Konrad > On 7. Apr 2022, at 11:51, Konrad Windszus wrote: > > I fully agree here. I don’t think dependabot can be controlle

Re: Should Sling refuse to register multiple servlets with the same mount parameters?

IMHO the regular OSGi semantics should apply here as well, i.e. higher service ranking wins (if tie lower bundle id wins). That is also documented at https://sling.apache.org/documentation/the-sling-engine/servlets.html#servlet-resolution-order

Re: Should Sling refuse to register multiple servlets with the same mount parameters?

Just look at http://docs.osgi.org/javadoc/r4v43/core/org/osgi/framework/BundleContext.html#getServiceReference(java.lang.Class) "If multiple such services exist, the service with the highest ranking (as specified in its Constants.SERVICE_RANKING property) is returned. If there is a tie in rankin

Re: Should Sling refuse to register multiple servlets with the same mount parameters?

On 11. May 2022, at 17:22, Carsten Ziegeler wrote: > > +1 to what Konrad said. > > Service ranking is more predictable than just using the "first" > > Regards > Carsten > > Am 11.05.2022 um 17:18 schrieb Konrad Windszus: >> IMHO the regular OSGi se

Re: Should Sling refuse to register multiple servlets with the same mount parameters?

I clarified the documentation in https://github.com/apache/sling-site/commit/cb12f47c7b55bd03ccf0951c112df68a40d67fd2 and added a link to https://docs.osgi.org/specification/osgi.core/8.0.0/framework.service.html#framework.service.servicerankingorder The according code is IMHO in https://githu

Re: Should Sling refuse to register multiple servlets with the same mount parameters?

Carsten > > Am 11.05.2022 um 17:37 schrieb Konrad Windszus: >> Why doing it differently than for any other OSGi service? >> Although the service ID is not predictable in general older services beat >> newer services, which is IMHO good enough. >> I am fine with issuin

Re: [VOTE] Release Apache Sling JCR Oak Server 1.3.0

Updating KEYS is a manual process: https://sling.apache.org/documentation/development/release-management.html#appendix-a-creating-and-registering-your-pgp-key There is no automatic syncing (anymore) with the key registered in your ASF profile. Regards, Konrad > Am 16.05.2022 um 12:51 schrieb O

Re: Custom Maven Enforcer Rule hosted at Sling

the week. Konrad On 2021/05/28 07:04:45 Konrad Windszus wrote: > > Hi, > I tried to contribute a Enforcer Rule to Apache Maven Enforcer in > https://issues.apache.org/jira/browse/MENFORCER-385 (PR in > https://github.com/apache/maven-enforcer/pull/97) > Unfortunately the Maven

Re: Custom Maven Enforcer Rule hosted at Sling

I see, then “sling-maven-enforcer-rules” and "maven-enforcer-rules” make more sense. WDYT? Konrad > On 2. Jun 2022, at 13:58, Robert Munteanu wrote: > > On Thu, 2022-06-02 at 09:56 +, Konrad Windszus wrote: >> Coming back to this topic after a long time I propose to u

[VOTE] Release Apache Sling (Bundle) Parent 48

Hi, We solved some issues in these releases: https://issues.apache.org/jira/projects/SLING/versions/12351253 and https://issues.apache.org/jira/projects/SLING/versions/12351252 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2642/ You can use this UNIX scrip

Re: Improve JSON serialization and response data types

In places where the size/number of dependencies really matters we also embedded (via Bnds conditionalpackage, https://bnd.bndtools.org/instructions/conditionalpackage.html) the minimum implementation provided by Felix Utils: https://github.com/apache/felix-dev/tree/master/utils/src/main/java/or

[VOTE] Release Apache Sling Installer WebConsole Plugin version 1.0.4

Hi, This is mostly a back port of version 1.1.0 to ensure compatibility with OSGi Installer Core: https://issues.apache.org/jira/browse/SLING-11344 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2643/ You can use this UNIX script to download the release an

Re: [VOTE] Release Apache Sling (Bundle) Parent 48

> Also, should https://issues.apache.org/jira/browse/SLING-9463 be moved > to the next release? > Good point, done.

Re: Custom Maven Enforcer Rule hosted at Sling

> > I will not argue about the names as they make totally sense but we should try > to be more consistent. Back then I was asked to use a more specific project/ > repo: sling-org-apache-sling-bnd-plugin-headers-parameters-remove¹ instead of > just sling-org-apache-sling-bnd-plugins² > > O. >

[RESULT] [VOTE] Release Apache Sling (Bundle) Parent 48

Hi, The vote has passed with the following result : +1 (binding): Robert, Oli, Stefan I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Thanks for voting, Konrad > On 3. Jun 2022, at 12:01, Konrad Windszus wrote: >

[RESULT] [VOTE] Release Apache Sling Installer WebConsole Plugin version 1.0.4

Hi, The vote has passed with the following result : +1 (binding): Robert, Stefan, Carsten I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Thanks for voting, Konrad > On 3. Jun 2022, at 14:39, Konrad Windszus wrote: >

[VOTE] Release Apache Sling Maven Enforcer Rules 1.0.0

Hi, This is the first release of the Sling Maven Enforcer Rules: https://issues.apache.org/jira/projects/SLING/versions/12351835 Currently it only contains a single rule (https://issues.apache.org/jira/browse/SLING-11369) which was used in the PRs connected to https://issues.apache.org/jira/b

Re: [VOTE] Release Apache Sling Maven Enforcer Rules 1.0.0

Here is my +1 I need more votes, please. Konrad > On 9. Jun 2022, at 10:26, Konrad Windszus wrote: > > Hi, > > This is the first release of the Sling Maven Enforcer Rules: > https://issues.apache.org/jira/projects/SLING/versions/12351835 > > Currently it onl

[RESULT] [VOTE] Release Apache Sling Maven Enforcer Rules 1.0.0

Hi, The vote has passed with the following result : +1 (binding): Stefan, Carsten and myself I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Thanks for voting. Konrad > On 9. Jun 2022, at 10:26, Konrad Windszus wrote: >

Enhancements in Jenkins Build

Hi, In the context of https://issues.apache.org/jira/browse/SLING-9948 I adjusted the Jenkins Library which is used for all our builds. Now we can have multiple Maven builds on different JDKs executed in parallel. You can see an example execution in https://ci-builds.apache.org/blue/organizatio

Switch to Java 11

Hi, AFAIK all our Sling bundles still target Java 8. I think for major feature updates we could increase this to Java 11 to leverage the newly introduced features (https://www.geeksforgeeks.org/java-11-features-and-comparison/, https://ondro.inginea.eu/index.php/new-features-in-java-versions-sin

Re: Sling Model AdapterFactory - iterating all injectors?

Hi, Shouldn’t we instead just more prominently promote injector-specific annotations (https://sling.apache.org/documentation/bundles/models.html#injector-specific-annotations )? IMHO this should be fixed i

Feature Launcher used as OSGi bundle

Hi, In the context of https://issues.apache.org/jira/browse/SLING-10211 OSGi metadata has been added to the Sling Feature Launcher. Some concerns were raised in the PR at https://github.com/apache/sling-org-apache-sling-feature-launcher/pull/19#pullrequestreview-611745073 but never answered. Ca

Sling Parent: Set scope in dependencyManagement?

Hi, Currently sling-(bundle)-parent always also managed the scope (in most cases “provided”) for (almost all) its managed dependencies: https://github.com/apache/sling-parent/blob/e42fd6e5fac8ed9becf722b5241d01d3147338c4/sling-parent/pom.xml#L939-L1001

Re: Sling Parent: Set scope in dependencyManagement?

gt; dependencies as well, e.g. for sling mocks). > > however, doing this switch now is dangerous, as you will get different > dependency scopes probably without any warning or build failure if you > carelessly update to latest parent POMs. > > stefan > > >> -O

Re: Sling Parent: Set scope in dependencyManagement?

I quickly drafted such an enforcer rule in https://github.com/apache/sling-maven-enforcer-rules/pull/2 <https://github.com/apache/sling-maven-enforcer-rules/pull/2>. > On 23. Jun 2022, at 16:39, Konrad Windszus wrote: > > What about a custom Maven enforcer rule “require

Re: Sling Parent: Set scope in dependencyManagement?

x27;m setting the scope also in all "my" projects) > > O. > > >> however, doing this switch now is dangerous, as you will get different >> dependency scopes probably without any warning or build failure if you >> carelessly update to latest parent POMs. > >

[VOTE] Release Apache Sling Maven Enforcer Rules version 1.1.0

Hi, We solved 1 issue in this release: https://issues.apache.org/jira/browse/SLING-11410 which adds a new Maven enforcer rule which we intend to leverage in the context of https://issues.apache.org/jira/browse/SLING-11411. I also proposed to add this rule to the standard set of Maven Enforcer i

Re: [VOTE] Release Apache Sling Maven Enforcer Rules version 1.1.0

+1 I need more votes, please. Thanks, Konrad > On 24. Jun 2022, at 14:24, Konrad Windszus wrote: > > Hi, > We solved 1 issue in this release: > https://issues.apache.org/jira/browse/SLING-11410 which adds a new Maven > enforcer rule which we intend to leverage in the c

[RESULT] [VOTE] Release Apache Sling Maven Enforcer Rules version 1.1.0

Hi, The vote has passed with the following result : +1 (binding): Stefan, Radu and myself +1 (non binding): Ashok I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Thanks for voting, Konrad > On 24. Jun 2022, at 14:24, Kon

[VOTE] Release Apache Sling Testing Sling Mock 3.3.2

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

Re: Feature Launcher used as OSGi bundle

Ping, anyone? > On 23. Jun 2022, at 09:28, Konrad Windszus wrote: > > Hi, > In the context of https://issues.apache.org/jira/browse/SLING-10211 OSGi > metadata has been added to the Sling Feature Launcher. Some concerns were > raised in the PR at > https://github.com/ap

Re: [RT] Decoupling the OSGi spec version from the parent version

Hi, I recently had a discussion with BJ around that in https://github.com/osgi/osgi/issues/452. His opinion was that one should always depend on the minimum version providing the necessary API, which kind of makes sense, but also is more effort to manage for our huge amount of bundles. According

Re: [VOTE] Release Apache Sling Testing Sling Mock 3.3.2

Here is my +1 Konrad > On 30. Jun 2022, at 09:23, Konrad Windszus wrote: > > Hi, > We solved 1 issue in this release: > https://issues.apache.org/jira/browse/SLING-11362 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2

[RESULT][VOTE] Release Apache Sling Testing Sling Mock 3.3.2

Hi, The vote has passed with the following result : +1 (binding): Stefan, Robert and myself I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Thanks for voting, Konrad > On 30. Jun 2022, at 09:23, Konrad Windszus wrote: >

Re: 256 MB static buffer in the feature launcher

https://docs.oracle.com/javase/7/docs/api/java/nio/file/Files.html#copy(java.io.InputStream,%20java.nio.file.Path,%20java.nio.file.CopyOption...) ha

Re: [VOTE] Release Apache Sling Installer Health Checks 2.1.0

+1, I don’t think that the changes for https://issues.apache.org/jira/browse/SLING-11463 were actually necessary as a DS component is reactivated if a configuration is changed and doesn’t have a modified method. Compare with https://github.

Re: [VOTE] Release Apache Sling Installer Health Checks 2.1.0

z wrote: > > On Wednesday, 20 July 2022 10:41:04 CEST Oliver Lietz wrote: >> On Tuesday, 19 July 2022 08:27:23 CEST Konrad Windszus wrote: >>> +1, >>> >>> I don’t think that the changes for >>> https://issues.apache.org/jira/browse/SLING-11463 >

[VOTE] Release Apache Sling Parent and Bundle Parent 49

Hi, We solved some issues in these releases: https://issues.apache.org/jira/projects/SLING/versions/12351823 (Parent 49) https://issues.apache.org/jira/projects/SLING/versions/12351824 (Bundle Parent 49) Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2661

Re: User impersonation in the web console

Hi Robert, According to https://sling.apache.org/documentation/the-sling-engine/resources.html#jcr-based-resources the key “user.impersonation” “...Must be combined with one of the other authentication info keys.” So I guess you need to add at least one other key to the AuthenticationInfo map

Re: [VOTE] Release Apache Sling Parent and Bundle Parent 49

Here is my +1 Konrad > On 3. Aug 2022, at 21:01, Konrad Windszus wrote: > > Hi, > We solved some issues in these releases: > https://issues.apache.org/jira/projects/SLING/versions/12351823 (Parent 49) > https://issues.apache.org/jira/projects/SLING/versions/12351824 (B

[RESULT] [VOTE] Release Apache Sling Parent and Bundle Parent 49

Hi, the vote has passed with the following result: +1 (binding): Robert, Jörg and myself I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Thanks for voting, Konrad > On 3. Aug 2022, at 21:01, Konrad Windszus wrote: > >

Re: [parent pom] missing site distribution management

gt; On 21 Sep 2021, at 19:35, Konrad Windszus wrote: > > > > Hi Radu, > > I never use the site goals "deploy" or "stage" for Sling modules. Instead > > of the former we have a rather manual process outlined in > > https://sling.apache.org/document

[VOTE] Release Apache Sling Maven Plugin version 3.0.0

Hi, We solved some issues in this release: https://issues.apache.org/jira/projects/SLING/versions/12345612 This plugin now requires at least Maven 3.3.1 and got rid of all legacy Maven 2 dependencies. Quite some effort went into cleaning up the generated Maven Site to ease usage of the plugin

[CANCELLED] [VOTE] Release Apache Sling Maven Plugin version 3.0.0

! looks good overall, however > i've detected a problem with "sling:install" when using as single goal, > reported in > https://issues.apache.org/jira/browse/SLING-11543 > > stefan > >> -Original Message- >> From: Konrad Windszus >> Se

[VOTE] Release Apache Sling Maven Plugin version 3.0.2

Hi, We solved some issues in this release: https://issues.apache.org/jira/projects/SLING/versions/12352197 This plugin now requires at least Maven 3.3.1 and got rid of all legacy Maven 2 dependencies. Quite some effort went into cleaning up the generated Maven Site to ease usage of the plugin

Re: [VOTE] Release Apache Sling Pipes 4.5.0

+1 (Although an update to the latest parent would be nice) Konrad > On 20. Aug 2022, at 07:58, Nicolas Peltier wrote: > > Gentle bump for a third vote > > Le jeu. 18 août 2022 à 14:03, Nicolas Peltier a > écrit : > >> +1 :) >> >> Le mer. 17 août 2022 à 14:01, Stefan Seifert >> a écrit : >

Re: [VOTE] Release Apache Sling Maven Plugin version 3.0.2

+1 Konrad > On 17. Aug 2022, at 10:57, Konrad Windszus wrote: > > Hi, > > We solved some issues in this release: > https://issues.apache.org/jira/projects/SLING/versions/12352197 > > This plugin now requires at least Maven 3.3.1 and got rid of all legacy Maven &

[RESULT] [VOTE] Release Apache Sling Maven Plugin version 3.0.2

Hi, The vote has passed with the following result : +1 (binding): Nicolas, Stefan and myself I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Thanks for voting, Konrad

Re: [VOTE] Release Apache Sling API version 2.27.0, JCR Jackrabbit User Manager version 2.2.26

+1 Konrad > On 20. Aug 2022, at 22:32, Eric Norman wrote: > > Hi, > > We solved 2 issues in the API release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12352198 > > We solved 1 issues in the JCR Jackrabbit User Manager release: > https://issues.apache.org/jira/browse/SLING/fi

Re: Discuss policy for updating dependencies

Hi, There are lots of vulnerabilities reported which do not affect our usage of dependencies. Therefore I am still in favour of putting the responsibility towards those who build applications/distributions out of Sling bundles. For Sling Starter this is obviously us. I would recommend to introdu

Re: Discuss policy for updating dependencies

> > >> For Sling Starter this is obviously us. >> >> I would recommend to introduce some automated means (apart from >> dependabot) to check for vulnerabilities on all Maven projects which are >> not OSGi bundles. >> Something like >> https://jeremylong.github.io/DependencyCheck/dependency-check

Re: Failed to release org.apache.sling.feature.cpconverter

Hi Angela, In order to help you and resolve the issues you need to share the errors you are facing together with the Java version and OS you are using. Preferably as a JIRA issue. In general I think it makes sense to already build javadoc during CI builds to detect those issues earlier. Thanks,

Re: sling-site build is failing

The local Git clone seems to be corrupt. I cleared the workspace with the approach from https://stackoverflow.com/a/52885920 I just replayed the following steps in https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/578/: pipeline

Re: Fwd: [ANNOUNCE] Changes to Jira Account Creation (issues.a.o/jira)

This is now effective: https://infra.apache.org/blog/jira-public-signup-disabled So we should at least update https://sling.apache.org/contributing.html#how-to-contribute with instructions how to get an account. Every PMC member can request accounts via https://selfserve.apache.org/jira-acct.h

Re: [RESULT] [VOTE] Release Apache Apache Sling Feature Launcher Maven Plugin version 0.1.4

Thanks for the release, can you also publish the Maven site according to https://sling.apache.org/documentation/development/release-management.html#appendix-b-deploy-maven-plugin-documentation-if-applicable

[VOTE] Release Apache Sling Tooling Support Source and Install version 1.1.0

Hi, We solved some issues in these releases: - Install: https://issues.apache.org/jira/projects/SLING/versions/12346143 - Source: https://issues.apache.org/jira/projects/SLING/versions/12342560 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2697/ You can

Re: [VOTE] Release Apache Sling Tooling Support Source and Install version 1.1.0

Here is my +1 Konrad > On 25. Nov 2022, at 09:28, Konrad Windszus wrote: > > Hi, > > We solved some issues in these releases: > - Install: https://issues.apache.org/jira/projects/SLING/versions/12346143 > - Source: https://issues.apache.org/jira/projects/SLING/versions/

[RESULT][VOTE] Release Apache Sling Tooling Support Source and Install version 1.1.0

Hi, The vote has passed with the following result: +1 (binding): Robert, Stefan and myself I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Thanks for voting, Konrad

[VOTE] Release Apache Sling Scripting HTL Engine version 1.4.22-1.4.0

Hi, We solved some issues in this release: https://issues.apache.org/jira/projects/SLING/versions/12352203 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2702/ You can use this UNIX script to download the release and verify the signatures: https://gitbox

Principal names used in org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl and "everyone" group

Hi, With https://issues.apache.org/jira/browse/SLING-6963 the support for principal names has been added to the Service User Mapper. That in general does not consider group memberships. What about the special group “everyone” (https://jackrabbit

[RESULT] [VOTE] Release Apache Sling Scripting HTL Engine version 1.4.22-1.4.0

Hi, The vote has passed with the following result : +1 (binding): Stefan, Robert, Radu, Carsten I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Thanks for voting, Konrad > On 1. Dec 2022, at 18:01, Konrad Windszus wr

Re: Principal names used in org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl and "everyone" group

To answer my own question: Even the "everyone" group membership is not considered (if not explicitly added as principal name to the config). Konrad On 2022/12/02 19:01:57 Konrad Windszus wrote: > Hi, > With https://issues.apache.org/jira/browse/SLING-6963 > <https://

New repository for SLING-11729 (RepoInit FileVault Validator)

Hi, I proposed a FileVault validator for RepoInit in https://issues.apache.org/jira/browse/SLING-11729 . The initial source can be found in https://github.com/apache/sling-whiteboard/tree/master/org.apache.sling.repoinit.filevault.validator

Re: SLING-11709 - Set up Jira autolinks to all Sling Github projects

Sounds good to me. Could we at the same reestablish auto-linking of GitHub PRs with https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Jiranotificationoptions I would suggest just adding "jira_optionsL link", as the other options probably cause too m

RepoInit: Intended behaviour in case of failures and backwards-compatibility

Hi, There are some issue with RepoInit with regards to failure behaviour like [1] and [2] and the discussion initially raised in JIRA and/or GitHub PR was a bit tough I try to summarise the issue and status quo here in order to get some more feedback. Most repoinit statements lead to an excepti

Re: RepoInit: Intended behaviour in case of failures and backwards-compatibility

> On 16. Dec 2022, at 14:31, Bertrand Delacretaz wrote: > > So in the case of SLING-11736 I have proposed adding a [strict] option > to "create path", exemple: > > create path [strict] (nt:folder) /one(mixin nt:art)/step(mixin > nt:dance)/two/steps > > which activates the improved behavior p

Re: RepoInit: Intended behaviour in case of failures and backwards-compatibility

> On 16. Dec 2022, at 14:58, Bertrand Delacretaz wrote: > > So (assumption A) for SLING-11736 you would add a completely new > "create node" command, that has the exact same behavior as "create > path" except for the behavior changes of SLING-11736 ? Exactly, this is what is proposed in [4] an

Re: RepoInit: Intended behaviour in case of failures and backwards-compatibility

It is more about that this answers all the questions you had about the proposal because it is code (which says more than 1000 words). Konrad > On 16. Dec 2022, at 15:08, Bertrand Delacretaz wrote: > > Konrad Windszus wrote: >> ...I would really appreciate direct feedback in t

Re: RepoInit: Intended behaviour in case of failures and backwards-compatibility

and mixinTypes where > specified > createOrUpdate node (nt:folder) /one(mixin > nt:art)/step(mixin nt:dance)/two/steps > > > > Regards, > -Eric > > On Fri, Dec 16, 2022 at 6:53 AM Julian Reschke > wrote: > >> On 16.12.2022 14:38, Konrad Windszus wrote:

Re: RepoInit: Intended behaviour in case of failures and backwards-compatibility

ke that for set properties AFAIK) >>> >> >> I think the "[set|default] propertyName ..." syntax is conceptually >> similar. In that, the "default" operator would only modify the value if it >> does not already have a non-default value. >>

Re: New repository for SLING-11729 (RepoInit FileVault Validator)

Done now in https://gitbox.apache.org/repos/asf/sling-org-apache-sling-repoinit-filevault-validator.git <https://gitbox.apache.org/repos/asf/sling-org-apache-sling-repoinit-filevault-validator.git>. > On 15. Dec 2022, at 10:41, Konrad Windszus wrote: > > Hi, > I pr

Re: RepoInit: Intended behaviour in case of failures and backwards-compatibility

ich to me seems likely the most common case. > > Regards > Julian > > PS: my preference is also with deprecating "create path" in favour of > a new clearly defined instruction. > > On Mon, Dec 19, 2022 at 7:21 AM Konrad Windszus wrote: >> >> Thanks

Re: RepoInit: Intended behaviour in case of failures and backwards-compatibility

deprecating "create path" and implementing new instructions. > > But I'm not sure why you would need two new instructions: > > Konrad Windszus wrote: > ... >> a) ensure node (for creating or updating node(s) with primary and mixin type) >> b) update n

Re: RepoInit: Intended behaviour in case of failures and backwards-compatibility

e comes up in reality? > > Regards > Carsten > > > Am 19.12.2022 um 13:09 schrieb Konrad Windszus: >> Please read the full mailing list thread. >> This were the use cases brought up by Eric >> "I can envision a highly modular distribution in which two >>

Re: RepoInit: Intended behaviour in case of failures and backwards-compatibility

> On 19. Dec 2022, at 14:45, Bertrand Delacretaz wrote: > > So my preference goes to "set nodes ...", but if the majority prefers > "ensure nodes" that also works. Sounds better to me as well. Konrad

Re: RepoInit: Intended behaviour in case of failures and backwards-compatibility

Hi Eric, Actually your concern/use case lead to a modified proposal (ensure nodes) to allow for future other instructions (like update nodes). But I agree with Carsten here (and I am not Adobe): personal accusations don’t belong here and your are offending others with comments like these. Konrad

<    1   2   3   4   5   6   7   8   9   10   >