Deprecate https://github.com/apache/sling-org-apache-sling-installer-factory-subsystems?

Hi, there has been only 1 release in 2015 of https://github.com/apache/sling-org-apache-sling-installer-factory-subsystems . Also it is not contained in the Sling Starter. I would suggest that we formally deprecate

Re: 404 for https://www.apache.org/dist/sling/KEYS

Konrad > On 4. Mar 2020, at 17:26, Radu Cotescu wrote: > > Hi Konrad, > >> On 4 Mar 2020, at 17:16, Konrad Windszus wrote: >> >> Hi, >> after fixing the download links to ASC and SHA1 files in >> https://sling.apache.org/downloads.cgi I noticed that >

404 for https://www.apache.org/dist/sling/KEYS

Hi, after fixing the download links to ASC and SHA1 files in https://sling.apache.org/downloads.cgi I noticed that https://www.apache.org/dist/sling/KEYS is no longer working. How is that file being generated? I also cannot find it in https://dist.apache.org/repos/dist/release/sling/ Before I

Re: [Starter] Startup detection not working reliable anymore

g, but the simple use case for the starter could be achieved with a much >> simpler solution without annoying users. >> Regards >> Carsten >> On 02.03.2020 09:12, Konrad Windszus wrote: >>> This has been adjusted in the context of >>> https://issues.apache.org/jira

Re: 404 for https://www.apache.org/dist/sling/KEYS

ets replaced by > https://downloads.apache.org/. > > We're asked to update all our references eventually. > > Regards > Carsten > > On 05.03.2020 10:10, Bertrand Delacretaz wrote: >> Hi, >> On Wed, Mar 4, 2020 at 5:17 PM Konrad Windszus wrote: >>> ...I noticed

Re: 404 for https://www.apache.org/dist/sling/KEYS

, Konrad > On 5. Mar 2020, at 10:37, Konrad Windszus wrote: > > I did that for most of the download links already > (https://github.com/apache/sling-site/commit/d9c831d79013cdcb755244908f1fbe8026af70bb > > <https://github.com/apache/sling-site/commit/d9c831d79013cdcb755

Re: 404 for https://www.apache.org/dist/sling/KEYS

has changed without us getting > aware of it. > > Regards > Carsten > > On 05.03.2020 11:02, Konrad Windszus wrote: >> Found it via svn log -v https://dist.apache.org/repos/dist/release/sling/ >> >> r2679 | cziegeler | 2013-08-05 09:26:19 +0200 (Mon, 05 Au

Re: 404 for https://www.apache.org/dist/sling/KEYS

I created https://issues.apache.org/jira/browse/INFRA-19927 <https://issues.apache.org/jira/browse/INFRA-19927> now. > On 5. Mar 2020, at 10:10, Bertrand Delacretaz wrote: > > Hi, > > On Wed, Mar 4, 2020 at 5:17 PM Konrad Windszus wrote: >> ...I noticed that https:

[RESULT] [VOTE] Release Apache Sling OSGi Installer Core version 3.10.2

Hi, The vote has passed with the following result : +1 (binding): Carsten, Stefan, Radu, David, Dan +1 (non binding): Andy 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 OSGi Installer Core version 3.10.2

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

Re: [Starter] Startup detection not working reliable anymore

This has been adjusted in the context of https://issues.apache.org/jira/browse/SLING-8418 . I think the exceptions are related to the order: https://issues.apache.org/jira/browse/SLING-8355 .

[RESULT] [VOTE] Apache Sling OSGi Installer Core 3.10.0, Console 1.1.0, Packages Factory 1.0.0, JCR Installer 3.2.0, File Installer 1.2.0, Configuration Factory 1.3.0

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

[VOTE] Release Apache Sling Parent 37 and Sling Bundle Parent 37

Hi, We solved several issues in this release: https://issues.apache.org/jira/projects/SLING/versions/12346744 (Parent 37) https://issues.apache.org/jira/projects/SLING/versions/12346745 (Bundle Parent 37) Most importantly one regression from Parent 36 which prevents us from releasing:

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

Here is my +1 Konrad > Am 04.02.2020 um 16:47 schrieb Konrad Windszus : > > Hi, > > We solved several issues in this release: > https://issues.apache.org/jira/projects/SLING/versions/12346744 (Parent 37) > https://issues.apache.org/jira/projects/SLING/versions/12346745

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

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

[VOTE] Release Apache Sling Parent and Apache Sling Bundle Parent 38

Hi, Unfortunately there was another regression with releasing with Parent 37 (https://issues.apache.org/jira/browse/SLING-9058) which requires yet another parent release: We solved 2 issues in this release: https://issues.apache.org/jira/projects/SLING/versions/12346946 (Parent 38)

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

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

[VOTE] Apache Sling OSGi Installer Core 3.10.0, Console 1.1.0, Packages Factory 1.0.0, JCR Installer 3.2.0, File Installer 1.2.0, Configuration Factory 1.3.0

Hi, We solved several issues in this release: https://issues.apache.org/jira/projects/SLING/versions/12343870 (Core 3.10.0) https://issues.apache.org/jira/projects/SLING/versions/12338914 (Console 1.1.0) https://issues.apache.org/jira/projects/SLING/versions/12338384 (Packages Factory 1.0.0)

[VOTE] Release Apache Sling Parent and Apache Sling Bundle Parent 36

Hi, We solved several issues in this release: https://issues.apache.org/jira/projects/SLING/versions/12345403 https://issues.apache.org/jira/projects/SLING/versions/12345414 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2181/ You can use this UNIX script

Re: Resource Type mandatory or optional?

I tend to agree with the statement that the resource type should be optional. Not every resource should be rendered and having no resource type set on those resources feels natural to me. Enforcing a non-null resource type for every resource is more complicated as each resource provider must be

Re: Resource Type mandatory or optional?

One more clarification: Via the implicit resource super type "sling/servlet/default" technically each resource has a resource type which is used for rendering resources. > On 9. Jan 2020, at 14:09, Konrad Windszus wrote: > > I tend to agree with the statement that the r

Re: [hackathon] externalization / resource mapping / rewriter

I would like to revive this. @Georg: IIRC you wanted to come up with a proposal for a externalizer API. Are you working on this? Can we start by creating a JIRA ticket? There has been a related ticket opened today: https://issues.apache.org/jira/browse/SLING-9005

Release for Sling OSGi Installer bundles

Hi, does anything speak against releasing all OSGi installer bundles soon (including the first release of https://github.com/apache/sling-org-apache-sling-installer-factory-packages )? My plan is to get the release

Re: [VOTE] Release Sling Feature Model 1.1.2, Feature Model IO 1.2.2, Feature Model Analyser 1.2.4, Feature Model Converter 1.0.12, Feature Model Launcher 1.1.2, Feature Model API Regions Runtime Frag

Can we have at least one JIRA issue per new release? This is currently empty: https://issues.apache.org/jira/projects/SLING/versions/12346774 > On 21. Jan 2020, at 12:29, dav...@apache.org wrote: > > Hi all, > > I would like to

[VOTE] Release Apache Sling Feature Model IO 1.2.0

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

Dealing with the Sling Dist folder

Hi, the release management is a bit painful due to the huge amount of files in https://dist.apache.org/repos/dist/release/sling/. Would it be possible to split this up a bit, that we reduce the amount of sibling files? All UI tools I tried for cleaning up the old release artifacts simply screw

[RESULT][VOTE] Release Apache Sling Feature Model IO 1.2.0

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

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

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

Re: [VOTE] Release Apache Sling Installer Vault Package Install Hook 1.1.0

+1 (checked build and checksums) Konrad > On 21. Dec 2019, at 10:09, Georg Henzler wrote: > > Hi, > > We solved 5 issues in this release: > https://issues.apache.org/jira/projects/SLING/versions/12346655 > > Staging repository: >

OSGi Installer JCR Provider - Dependency on jcr-commons?

Hi and happy new year to everyone, I am currently bringing the OSGi installer to the newest parent and therefore reviewing the dependencies. In

Re: OSGi Installer JCR Provider - Dependency on jcr-commons?

13:16, Konrad Windszus wrote: > > Hi and happy new year to everyone, > I am currently bringing the OSGi installer to the newest parent and therefore > reviewing the dependencies. > In > https://github.com/apache/sling-org-apache-sling-instal

[RESULT][VOTE] Release Apache Sling Commons Johnzon 1.2.0

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

New Sling Committer: Dirk Rudolph

Hi Sling community, The Sling PMC has elected Dirk Rudolph as a Sling committer, and he has accepted the invitation. Please join me in welcoming Dirk! Dirk - if you want to honor the old tradition of new committers briefly introducing themselves to the list, feel free. Welcome! Konrad

Re: [VOTE] Deprecate org.apache.launchpad.test-services-war

). Then I am clearly +1 for deprecating it, because we already have a lot of other regularly registered Sling servlets! Konrad > On 10. Apr 2020, at 11:11, Robert Munteanu wrote: > > Hi Konrad, > > On Thu, 2020-04-09 at 18:25 +0200, Konrad Windszus wrote: >> For me the

Enabling JIRA Github Integration

Hi, I asked in https://issues.apache.org/jira/browse/INFRA-19695 about enabling a Github JIRA integration so that commits automatically become visible in the related JIRA ticket. The standard Atlassian JIRA Github integration cannot be used

Re: Consistently failing ITs

2020-04-01 at 16:06 +0200, Robert Munteanu wrote: >> Sounds like a reasonable explanation to me. >> >> Thanks, >> Robert >> >> On Wed, 2020-04-01 at 16:03 +0200, Konrad Windszus wrote: >>> What I assume happened was the following: >>> >>&

Re: [VOTE] Deprecate org.apache.launchpad.test-services-war

For me the tests are interesting (although an edge case). But the deployment should not be as a bundle into OSGi but rather as a dedicated 2nd war (https://www.eclipse.org/jetty/documentation/9.4.x/jetty-maven-plugin.html#deploy-war-running-pre-assembled-war

Re: Deprecate the org.apache.sling.scripting.sightly.models.provider module?

t; Thanks, > Radu > >> On 15 Apr 2020, at 19:09, Konrad Windszus wrote: >> >> Wrapping the exception is ok as long as the old exception is still >> accessible. One can easily write a ServletFilter which catches (and unwraps) >> the exception to throw the 500!

[VOTE] JCR Installer 3.2.2, File Installer 1.2.2, Installer Packages Factory 1.0.2

Hi, We solved several issues in these releases: JCR Installer 3.2.2: https://issues.apache.org/jira/projects/SLING/versions/12347037 File Installer 1.2.2: https://issues.apache.org/jira/projects/SLING/versions/12347038 Installer Packages Factory 1.0.2:

Merge launchpad-testing into sling-starter

Hi, does anything speak against moving the ITs from https://github.com/apache/sling-org-apache-sling-launchpad-testing into https://github.com/apache/sling-org-apache-sling-starter?

Re: Consistently failing ITs

I can do releases on JCR Provider, File Provider and Package Feature but first someone should investigate org.apache.sling.launchpad.webapp.integrationtest.installer.ServerSideInstallerTest.noUntransformedResources I unfortunately won't have time to look into that this week. Konrad > On 1. Apr

Re: Consistently failing ITs

taller-core/commit/33eeae619c5aae2a7a52903edbdd6a85b08e0891, but processing WAR resources with the bundle transformer probably never was a good idea. So right now I tend to just remove the WAR dependency in the bundles.txt. WDYT? Konrad > On 1. Apr 2020, at 13:43, Konrad Windszus wrote: > > I can do releases on

Re: Merge launchpad-testing into sling-starter

ctured Resource super type: - ** Resource properties ** jcr:primaryType: nt:unstructured text: This is a test node 1585747503113 ) > On 1. Apr 2020, at 15:25, Robert Munteanu wrote: > > On Wed, 2020-04-01 at 15:02 +0200, Konrad Windszus wrote: >> Hi, >> does anything speak

Re: Consistently failing ITs

t 15:21, Robert Munteanu wrote: > > On Wed, 2020-04-01 at 15:16 +0200, Konrad Windszus wrote: >> The test fails with the following output >> >> [ERROR] Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time >> elapsed: 0.292 s <<< FAILURE! - in >> org.apach

Re: [RT] Feature archives, launcher and Sling Starter

> > In any case, we should probably add support to the feature launcher to launch > feature archives directly - regardless of what we do with the starter. That's > a minor addition to the launcher rounding up our tooling story about features. What about a default lookup path for local

Re: Deprecate https://github.com/apache/sling-org-apache-sling-installer-factory-subsystems?

20, at 16:50, Carsten Ziegeler wrote: > > +1 > > Carsten > > On 04.03.2020 16:38, Konrad Windszus wrote: >> Hi, >> there has been only 1 release in 2015 of >> https://github.com/apache/sling-org-apache-sling-installer-factory-subsystems >> >> &l

Re: [DISCUSS] Resource Mapping SPI

e >> as is). Rather I‘d like to provide an SPI that allows to customize the >> way of the behavior of resourceResolver.map() - I‘m thinking of a >> ranked list of ResourceMapper services (default one being today’s >> behavior). Robert also has done some work into this directi

Re: Consistently failing ITs

t why did these not fail until now? > > Thanks, > Robert > > On Wed, 2020-04-01 at 15:39 +0200, Konrad Windszus wrote: >> IMHO there are some test which should only be executed from >> https://github.com/apache/sling-org-apache-sling-launchpad-testing-war >> , name

Re: Consistently failing ITs

? Konrad > On 1. Apr 2020, at 15:29, Konrad Windszus wrote: > > Done with > https://github.com/apache/sling-org-apache-sling-launchpad-test-bundles/commit/43956dd07234ddc3263ce29c5b7c3f7198ad4caf > > <https://github.com/apache/sling-org-apache-sling-launchpa

[RESULT] [VOTE] JCR Installer 3.2.2, File Installer 1.2.2, Installer Packages Factory 1.0.2

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

Re: [website] build marked as failed, needs git identity

This used to work for previous commits (https://github.com/apache/sling-site/commits/asf-site ) so I guess something changed with the Jenkins node... I guess INFRA needs to look into that. > On 27. Apr 2020, at 16:05, Bertrand Delacretaz

Re: [VOTE] Release Apache Sling Installer Core 3.11.4

+1 Konrad > On 27. Apr 2020, at 19:16, Carsten Ziegeler wrote: > > Hi, > > > We solved 2 issues in this release: > https://issues.apache.org/jira/browse/SLING-9400?jql=project%20%3D%20SLING%20AND%20fixVersion%20%3D%20%22Installer%20Core%203.11.4%22 > > Staging repository: >

[RESULT][VOTE] Release Apache Sling Commons Johnzon version 1.2.2

Hi, The vote has passed with the following result : +1 (binding): Carsten, Karl, Nicolas +1 (non-binding): Eri I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Konrad > On 22. Apr 2020, at 15:48, Konrad Windszus wr

[VOTE] Release Apache Sling Commons Johnzon version 1.2.2

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

Re: [website] build marked as failed, needs git identity

failing only recently? Konrad > On 27. Apr 2020, at 16:47, Konrad Windszus wrote: > > This used to work for previous commits > (https://github.com/apache/sling-site/commits/asf-site) so I guess something > changed with the Jenkins node... > > I guess INFRA needs to look i

Re: [website] build marked as failed, needs git identity

I opened https://issues.apache.org/jira/browse/SLING-9414 <https://issues.apache.org/jira/browse/SLING-9414> to allow to disable SonarQube for this job. > On 30. Apr 2020, at 21:44, Konrad Windszus wrote: > > I had a closer look and the funny thing is that this fails not during

Re: Sling Starter 12-SNAPSHOT java.lang.InterruptedException

Hi Robert, thanks for your response. I agree with all points except for > One option is to ask Oak to > make a configuration required for some components [3], but IMO this is > not fixing the root cause. Oak is not to blame for the way we manage > components and configurations. > IMHO every

Re: [VOTE] Move OSGi Installer Support for feature models to its own git repository

+1 but I would appreciate if the error logging feature (https://issues.apache.org/jira/browse/SLING-6176 ) would be leveraged in all setFinishState calls

Re: Ianal Maven Plugin?

It is still listed here: https://www.mojohaus.org/plugins.html but was not (yet) moved to Github nor is any documentation available at the www.mojohaus.org Maybe some of the alternatives listed in

Re: Deprecate the org.apache.sling.scripting.sightly.models.provider module?

p the original exception in a > org.apache.sling.scripting.sightly.SightlyException (RuntimeException) and > throw. > > Thanks, > Radu > >> On 15 Apr 2020, at 17:07, Konrad Windszus wrote: >> >> There is one important difference: The Java Use Provider uses >> adapt

Re: Deprecate the org.apache.sling.scripting.sightly.models.provider module?

There is one important difference: The Java Use Provider uses adaptTo(...)(https://github.com/apache/sling-org-apache-sling-scripting-sightly/blob/a0f0e77a30ecf3091cfa69d21ff46e0994e4e19f/src/main/java/org/apache/sling/scripting/sightly/impl/engine/extension/use/JavaUseProvider.java#L160

Re: Deprecate the org.apache.sling.scripting.sightly.models.provider module?

scu wrote: > > But that already happens in this case. If none of the Use providers can > provide an object the HTL engine throws a SightlyException. The logging I > mentioned is only supposed to help with debugging. > >> On 15 Apr 2020, at 17:56, Konrad Windszus wrote: &

Re: Ianal Maven Plugin?

Hi, interesting finding but unfortunately last updated in 2008 ( https://search.maven.org/artifact/org.apache.geronimo.genesis.plugins/tools-maven-plugin). Seems dead as well Konrad > On 5. May 2020, at 17:19, Bertrand Delacretaz wrote: > > Hi, > > On Tue, May 5, 2020 at 11:23 AM Robert

[RESULT] [VOTE] Release Apache Sling Installer Configuration Admin Support version 1.3.2

Hi, The vote has passed with the following result : +1 (binding): Carsten, Dan, Georg I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Thanks for voting, Konrad > On 7. May 2020, at 18:07, Konrad Windszus wrote: > > &g

Re: [VOTE] Release Apache Sling Parent 39, Apache Sling Bundle Parent 39, Apache Sling Jar Resource Bundle 1.0.2

> On 11. May 2020, at 09:32, Robert Munteanu wrote: > > Please vote to approve this release: +1 Konrad

Re: [VOTE] Release Apache Sling Installer Packages Factory 1.0.4

+1 Konrad > Am 08.05.2020 um 13:31 schrieb Robert Munteanu : > > Hi, > > We solved 1 issue in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12347878 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2261/ > > You can use

Re: Release Sling IDE 1.2.4

020, at 13:23, Robert Munteanu wrote: > > On Thu, 2020-05-14 at 13:17 +0200, Robert Munteanu wrote: >> Hi Konrad, >> >> On Thu, 2020-05-14 at 13:12 +0200, Konrad Windszus wrote: >>> Hi, >>> the last release of the Sling IDE is from February 2018

Re: Reproducible builds documentation? (was: [jira] [Closed] (SLING-9307) Make build fully reproducible)

Hi, Yes, all bundles built with the latest parent should be reproducible (i.e. generate always the same checksum under certain circumstances). There is some documentation at https://maven.apache.org/guides/mini/guide-reproducible-builds.html

Re: Reproducible builds documentation? (was: [jira] [Closed] (SLING-9307) Make build fully reproducible)

Maven-release-plugin will update it automatically during the release. So it is just a one time thing to add it with an arbitrary value to the pom.xml > On 14. May 2020, at 11:59, Robert Munteanu wrote: > > I think it would be nice to configure the release process to > automatically add the

Release Sling IDE 1.2.4

Hi, the last release of the Sling IDE is from February 2018. Since then some issues have been fixed https://issues.apache.org/jira/projects/SLING/versions/12342835 . WDYT about a new release. Since signing is tricky I would

Re: [VOTE] Release Apache Sling Installer Core 3.11.0

+1 (checked checksums, signatures and deployed in latest Sling Starter 12-SNAPSHOT) Konrad > On 20. Mar 2020, at 18:10, Robert Munteanu wrote: > > Hi, > > We solved 6 issues in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12347164 > > Staging repository: >

[VOTE] Release Apache Sling Commons Johnzon 1.2.0

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

Re: Building a main + test jar from the provisioning model

Hi Robert, I guess you need some tweaks in https://github.com/apache/sling-slingstart-maven-plugin/blob/5bbdae1d61698ac202845e5f242ecc8b602e7ed6/src/main/java/org/apache/sling/maven/slingstart/run/StartMojo.java#L366. The launchpad to start must consist of the merged 2 provisioning models, so

[VOTE] Release Apache Sling Installer Configuration Admin Support version 1.3.2

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

Sling Starter 12-SNAPSHOT java.lang.InterruptedException

Hi, I just experienced this exception when starting Sling Starter 12-SNAPSHOT: 03.05.2020 11:22:33.372 *INFO* [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.jackrabbit.oak.spi.security.user.action.DefaultAuthorizableActionProvider)]

Re: [DISCUSS] Automatic Mapping of URIs in HTL

+1 for a dedicated option. Not sure about the naming though. Konrad > Am 11.09.2020 um 14:07 schrieb Radu Cotescu : > > Hi Georg, > >> On 11 Sep 2020, at 01:09, Georg Henzler wrote: >> >> Hi all, >> >> as briefly mentioned in the thread about the resource >> mapping SPI [1], it would be

Re: How to 'spin a release'

-0400, Cris Rockwell wrote: >> Regarding >> >> >> Konrad Windszus commented on SLING-9648: >> >> Someone would need to spin a release. [~cris_rockwell] Do you want to >> give it a try? >> >> >

Re: How to 'spin a release'

at by > indicating the role of the person in charge of step #4 > > Thanks > Cris > > >> On Oct 19, 2020, at 3:33 AM, Konrad Windszus wrote: >> >> Hi Cris and Robert, >> >> after doing those steps you still need to manually add your key to the key

Re: New committer setup

ite/commit/144fa82c012006525cbf769a86f629ccc527a167>. That is IMHO enough. Sorry for the noise. Konrad > On 17. Aug 2020, at 10:22, Robert Munteanu wrote: > > On Thu, 2020-08-13 at 17:19 +0200, Konrad Windszus wrote: >> Looks good, should we link from >> https://sli

Re: Jira version names vs Maven module names

I would also personally prefer artifact id instead of name in JIRA. But the majority of version names in JIRA is right now named after the artifact name (https://issues.apache.org/jira/projects/SLING?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page=released). Also our

Re: Jira version names vs Maven module names

On 24. Sep 2020, at 11:58, Robert Munteanu wrote: > > We created Jira versions in the form of 'Artifact Name' 'Version' for > quite some time, only one of them stands out by being different. Just a > note, not something bad by itself. I would very much appreciate consistency in the naming. This

Re: [VOTE] Release Apache Sling API 2.23.0

+1 Konrad > On 23. Sep 2020, at 20:58, Georg Henzler wrote: > > Hi all, > > We solved 6 issues in this release: > https://issues.apache.org/jira/projects/SLING/versions/12346965 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2338 > > You can use

Re: Jira version names vs Maven module names

ears, and I don't understand >> why a new tool developed by ourselves should force us now to change >> things. Why can't the tool simply look for both, id and name - and we're >> done with this? >> >> Regards >> Carsten >> >> Am 22.09.2020 um 20:38 schr

New git repositories: sling-org-apache-sling-adapter-annotations and sling-org-apache-sling-adapter-annotations-it

Hi, in the context of https://issues.apache.org/jira/browse/SLING-2938 Henry Kuijpers is contributing code in two new repositories: - for adapter annotations (based on OSGi property type annotations) - for ITs for those I propose to create the

Re: Documentation for content-package based development

I enriched a bit further with regards to OSGi installer support in https://github.com/apache/sling-site/commit/b0951a5c2fb56b68d036d2e52a5adf488a19d8f0 > On 8. May 2020, at 16:53, Robert Munteanu wrote: >

Check if bundle resolves during build

Hi, I recently integrated https://github.com/bndtools/bnd/tree/master/maven/bnd-resolver-maven-plugin in the FileVault plugin [1] and I would propose to do something similar for Sling. That way incompatibilities of bundles would be more visible (and not only once you integrate those in the

Re: Intra Sling Calls

If you don’t have a request at hand it will be impossible to implement fully. If you have a request just use regular request dispatching. Konrad > Am 02.06.2020 um 08:21 schrieb Carsten Ziegeler : > > So you want to make an HTTP request from within Sling to itself? > I wouldn't recommend

Re: Check if bundle resolves during build

On 31. May 2020, at 16:42, Konrad Windszus wrote: > > Hi, > I recently integrated > https://github.com/bndtools/bnd/tree/master/maven/bnd-resolver-maven-plugin > in the FileVault plugin [1] and I would propose to do something similar for > Sling. > > That way incompatibi

Re: [roundtable] Code coverage

Hi Radu, I am wondering why we need to still generate reports for both unit and integration test separately in https://github.com/apache/sling-parent/blob/3e7b3edb7411440b6a5dcd4836da2c45f4cc7166/sling-parent/pom.xml#L509

Re: [VOTE] Release Apache Sling Feature Model 1.2.6, Analysers 1.3.6 and Slingfeature Maven Plugin 1.3.14

+1 Konrad > On 30. Jul 2020, at 07:55, Carsten Ziegeler wrote: > > Hi, > > We solved 1 issue in the feature model > https://issues.apache.org/jira/projects/SLING/versions/12348589 > > Two issues in the analysers > https://issues.apache.org/jira/projects/SLING/versions/12348614 > > and three

[VOTE] Release Apache Sling Settings 1.4.0, File Installer 1.3.0 and JCR Installer 3.3.0

Hi, We solved some issues in these releases: Settings: https://issues.apache.org/jira/projects/SLING/versions/12344046 Installer JCR Provider: https://issues.apache.org/jira/projects/SLING/versions/12348454 Installer File Provider: https://issues.apache.org/jira/projects/SLING/versions/12348453

[RESULT] [VOTE] Release Apache Sling Settings 1.4.0, File Installer 1.3.0 and JCR Installer 3.3.0

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

Re: New committer setup

Looks good, should we link from https://sling.apache.org/documentation/development.html or even move that to the site? > On 13. Aug 2020, at 09:18, Robert Munteanu wrote: > > Hi, > > I wrote down a couple of items hopefully useful

Re: Bootstrapping of new Jenkins Multibranch Jobs

4, Robert Munteanu wrote: > > Hi Konrad, > > On Thu, 2020-07-30 at 15:33 +0200, Konrad Windszus wrote: >> Hi, >> In the context of https://issues.apache.org/jira/browse/SLING-9594 < >> https://issues.apache.org/jira/browse/SLING-9594> I am currently >>

Re: Sling Starter switched to the Feature Model

Thanks a lot Robert, looks great at first glance. Konrad > On 5. Aug 2020, at 19:35, Robert Munteanu wrote: > > Hi, > > With the merge of the two PRs for the Sling Starter [1] and Launchpad- > Testing [2] the Sling starter is now switched to the feature model. > > This completes Phase 2, as

Sling Settings 1.4.0 not resolvable against Felix SCR 2.1.20

Hi, When trying to start Sling Starter 12 with Sling Settings 1.4.0 the following error is logged 03.08.2020 09:59:27.402 *ERROR* [FelixStartLevel] ERROR: Bundle '6' Error starting slinginstall:org.apache.sling.settings-1.4.0.jar (org.osgi.framework.BundleException: Unable to resolve

Re: Sling Settings 1.4.0 not resolvable against Felix SCR 2.1.20

Nevermind, this is just a start level issue. We must start SCR first now after https://issues.apache.org/jira/browse/SLING-9561 <https://issues.apache.org/jira/browse/SLING-9561> > On 3. Aug 2020, at 10:17, Konrad Windszus wrote: > > Hi, > When trying to start Sling Sta

OSGi property "service.vendor"

Hi, I am wondering if we should set the OSGi service property "service.vendor" at all for our services (https://docs.osgi.org/specification/osgi.core/7.0.0/framework.service.html#framework.service.serviceproperties

Re: OSGi property "service.vendor"

Given the lack of response I would like to propose to no longer define service.vendor in our bundles. IMHO just unnecessary overhead. Please raise you voice if you don't agree Thanks, Konrad > On 7. Jul 2020, at 15:46, Konrad Windszus wrote: > > Hi, > I am wondering if we should

Prevent Default Sling Post servlet from ever processing certain requests

Hi, it is quite common that applications register custom POST servlet (via OSGi DS) to a certain resource type. If that custom POST servlet component for whatever reason is not running the default Sling POST servlet will kick in. That is never intended and will in the worst case add content to

<    3   4   5   6   7   8   9   10   11   12   >