[jira] [Updated] (SLING-8623) Add support to cpConverter to drop content-packages of PackageType.CONTENT from targetmodel

[ https://issues.apache.org/jira/browse/SLING-8623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert updated SLING-8623: Fix Version/s: (was: Content-Package to Feature Model Converter 1.0.4)

[jira] [Updated] (SLING-8924) Some tests fail on Java 11

[ https://issues.apache.org/jira/browse/SLING-8924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert updated SLING-8924: Fix Version/s: (was: Content-Package to Feature Model Converter 1.0.4)

[jira] [Updated] (SLING-8976) [API Regions] Resolving bundles in different version fails

[ https://issues.apache.org/jira/browse/SLING-8976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-8976: -- Fix Version/s: Feature Model API Regions Runtime Fragment 1.0.6 > [API Regions] Resolving bundles in

[jira] [Updated] (SLING-8976) [API Regions] Resolving bundles in different version fails

[ https://issues.apache.org/jira/browse/SLING-8976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-8976: -- Affects Version/s: (was: Feature Model API Regions Extension 1.0.4) Feature

[jira] [Updated] (SLING-8974) Shows a 200 OK for a delete operation even if the node does not exist.

[ https://issues.apache.org/jira/browse/SLING-8974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-8974: --- Fix Version/s: Servlets POST 2.3.38 > Shows a 200 OK for a delete operation even if the node

[jira] [Resolved] (SLING-8973) Repoinit convertion is not respecting runmodes

[ https://issues.apache.org/jira/browse/SLING-8973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert resolved SLING-8973. - Resolution: Fixed > Repoinit convertion is not respecting runmodes >

[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: [VOTE] Release Apache Sling Feature Model Converter Plugin 1.0.2

On Wed, 2020-01-08 at 07:55 -0800, Andreas Schaefer wrote: > If a subsequent build works it would mean that in the 2nd build it > would find the dependency on *.core but not in the first. > > This is my env: > > mvn --version > Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 2019-

[jira] [Updated] (SLING-7534) Release policy - stop providing MD5 and start providing SHA-512 signatures

[ https://issues.apache.org/jira/browse/SLING-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-7534: --- Fix Version/s: (was: Parent 36) Parent 37 > Release policy - stop

[jira] [Updated] (SLING-8974) Shows a 200 OK for a delete operation even if the node does not exist.

[ https://issues.apache.org/jira/browse/SLING-8974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-8974: --- Component/s: (was: Sling Query) Servlets > Shows a 200 OK for a delete

[jira] [Commented] (SLING-8974) Shows a 200 OK for a delete operation even if the node does not exist.

[ https://issues.apache.org/jira/browse/SLING-8974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17011635#comment-17011635 ] Robert Munteanu commented on SLING-8974: Thank you for the report [~anarang]. This definitely

[jira] [Created] (SLING-8976) [API Regions]resolving bundles in different version causes

Karl Pauls created SLING-8976: - Summary: [API Regions]resolving bundles in different version causes Key: SLING-8976 URL: https://issues.apache.org/jira/browse/SLING-8976 Project: Sling Issue

Re: Feature Launcher System in a Background Thread, where?

On Wed, 2020-01-08 at 18:06 +0100, Bertrand Delacretaz wrote: > On Wed, Jan 8, 2020 at 5:59 PM Carsten Ziegeler > wrote: > > Do we still need to support the webapp case?.. > > I was going to ask the same thing - I suggest *not* doing webapp > anymore, leaving space for someone to implement it if

Re: [tools] docker committer tools failed

On Wed, 2020-01-08 at 13:36 -0500, Daniel Klco wrote: > Could the code pull the list of open releases and then offer > suggestions > sorted by the number of matching terms? Something like mvn > archetype:generate? It would only work in interactive mode, but it > would > give you a recovery path if

Retire feature application builder

Hi, the feature applicationbuilder module [1] steams from an old, discarded idea. It hasn't been maintained for a while and is not needed. I think we should retire it. What is the process for that ? As we never released it, we can probably just delete it? Regards Carsten [1]

Retiring Sling modules (was: Retire feature application builder)

Hi, On Thu, Jan 9, 2020 at 10:15 AM Robert Munteanu wrote: > ...I don't think we have a process (for retiring modules) since we moved to > Git https://cwiki.apache.org/confluence/display/SLING/Deprecating+Sling+Modules was discussed a few months ago. I see it's been used for (at least)

Re: [RESULT][VOTE] Release Apache Sling Feature Model API Regions Runtime Fragment 1.0.4

It seems like this release has some issues and it didn't really make it out there. I will have to rollback some of the changes done for SLING-8815 via SLING-8976 anyways - hence, I'll go ahead and drop the staging for this release (1.0.4) and do a new 1.0.6 release soon. regards, Karl On Tue,

Re: Retiring Sling modules (was: Retire feature application builder)

On Thu, Jan 9, 2020 at 10:33 AM Bertrand Delacretaz wrote: > ...https://cwiki.apache.org/confluence/display/SLING/Deprecating+Sling+Modules > was discussed a few months ago... I have now applied that to 3 crankstart modules which I suppose we agree to deprecate (if not, it's easy to undo).

[jira] [Updated] (SLING-8976) [API Regions] Resolving bundles in different version fails

[ https://issues.apache.org/jira/browse/SLING-8976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-8976: -- Summary: [API Regions] Resolving bundles in different version fails (was: [API Regions]resolving

[jira] [Updated] (SLING-8976) [API Regions] Resolving bundles in different version fails

[ https://issues.apache.org/jira/browse/SLING-8976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-8976: -- Component/s: Feature Model > [API Regions] Resolving bundles in different version fails >

[jira] [Updated] (SLING-8976) [API Regions] Resolving bundles in different version fails

[ https://issues.apache.org/jira/browse/SLING-8976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-8976: -- Affects Version/s: Feature Model API Regions Extension 1.0.4 > [API Regions] Resolving bundles in

[jira] [Updated] (SLING-8735) Ignore bundle version baselining messages

[ https://issues.apache.org/jira/browse/SLING-8735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-8735: --- Fix Version/s: (was: Bundle Parent 36) Bundle Parent 37 > Ignore

[jira] [Updated] (SLING-8738) Trigger an error during build if an API uses a private reference in its public methods' signatures

[ https://issues.apache.org/jira/browse/SLING-8738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-8738: --- Fix Version/s: (was: Bundle Parent 36) Bundle Parent 37 > Trigger an

Re: Retire feature application builder

Hi Carsten, On Thu, 2020-01-09 at 09:27 +0100, Carsten Ziegeler wrote: > Hi, > > the feature applicationbuilder module [1] steams from an old, > discarded > idea. > > It hasn't been maintained for a while and is not needed. > > I think we should retire it. What is the process for that ? > As

Re: Retiring Sling modules (was: Retire feature application builder)

On Thu, 2020-01-09 at 10:33 +0100, Bertrand Delacretaz wrote: > Hi, > > On Thu, Jan 9, 2020 at 10:15 AM Robert Munteanu > wrote: > > ...I don't think we have a process (for retiring modules) since we > > moved to Git > >

[jira] [Updated] (SLING-8537) Avoid weird url inheritance rules in Maven leading to incorrect Bundle-DocURL header

[ https://issues.apache.org/jira/browse/SLING-8537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-8537: --- Fix Version/s: (was: Parent 36) Parent 37 > Avoid weird url

[jira] [Resolved] (SLING-8951) Enable reproducible builds by default

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

[jira] [Commented] (SLING-8904) Stop waiting for 10 seconds before tagging a release

[ https://issues.apache.org/jira/browse/SLING-8904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17011708#comment-17011708 ] Konrad Windszus commented on SLING-8904: No longer necessary with the new ASF parent and

[jira] [Comment Edited] (SLING-8904) Stop waiting for 10 seconds before tagging a release

[ https://issues.apache.org/jira/browse/SLING-8904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17011708#comment-17011708 ] Konrad Windszus edited comment on SLING-8904 at 1/9/20 11:15 AM: -

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

[jira] [Updated] (SLING-8964) sling-bundle-parent: Disable baseline check for bundle versions

[ https://issues.apache.org/jira/browse/SLING-8964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-8964: --- Fix Version/s: (was: Bundle Parent 36) > sling-bundle-parent: Disable baseline check for

[jira] [Commented] (SLING-8964) sling-bundle-parent: Disable baseline check for bundle versions

[ https://issues.apache.org/jira/browse/SLING-8964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17011802#comment-17011802 ] Robert Munteanu commented on SLING-8964: Removing fix version as it was not actually fixed, but a

[jira] [Commented] (SLING-8951) Enable reproducible builds by default

[ https://issues.apache.org/jira/browse/SLING-8951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17011806#comment-17011806 ] Robert Munteanu commented on SLING-8951: [~kwin] - how would this work in practice? If I run `mvn

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

+1 Carsten On 09.01.2020 13:13, Konrad Windszus wrote: 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:

[VOTE] Release Apache Sling Content-Package to Feature Model Converter 1.0.4

Hi all, I would like to call the release on the Content-Package to Feature Model Converter 1.0.4. We fixed the following issue: https://issues.apache.org/jira/projects/SLING/versions/12346630 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2182 You can use

[jira] [Assigned] (SLING-8973) Repoinit convertion is not respecting runmodes

[ https://issues.apache.org/jira/browse/SLING-8973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-8973: -- Assignee: Carsten Ziegeler > Repoinit convertion is not respecting runmodes >

Re: Resource Type mandatory or optional?

Agreed with Carsten. Reading the docs and considering how people use the API, all resources should have types, the potential for breaking changes in downstream code if Resource Types are allowed to be nullable is significant. On Thu, Jan 9, 2020 at 8:37 AM Carsten Ziegeler wrote: > Thanks for

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

On Thu, 2020-01-09 at 13:13 +0100, Konrad Windszus wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part

Re: [VOTE] Release Apache Sling Content-Package to Feature Model Converter 1.0.4

I can see it: https://repository.apache.org/content/repositories/orgapachesling-2182/org/apache/sling/org.apache.sling.feature.cpconverter/1.0.4/org.apache.sling.feature.cpconverter-1.0.4-sources.jar Regards Carsten On 09.01.2020 14:43, Robert Munteanu wrote: Hi David, On Thu, 2020-01-09 at

[jira] [Commented] (SLING-8962) Use Sling API 2.22.0

[ https://issues.apache.org/jira/browse/SLING-8962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17011986#comment-17011986 ] Bertrand Delacretaz commented on SLING-8962: The change to 2.22.0-SNAPSHOT breaks the new

Re: [VOTE] Release Apache Sling Content-Package to Feature Model Converter 1.0.4

Hi David, On Thu, 2020-01-09 at 13:30 +, dav...@apache.org wrote: > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2182 There seems to be no source release file at that repository. Robert

[jira] [Commented] (SLING-8936) Improve test coverage for path-mounted servlets

[ https://issues.apache.org/jira/browse/SLING-8936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17011988#comment-17011988 ] Bertrand Delacretaz commented on SLING-8936:

Re: [VOTE] Release Apache Sling Content-Package to Feature Model Converter 1.0.4

+1 Carsten On 09.01.2020 14:30, dav...@apache.org wrote: Hi all, I would like to call the release on the Content-Package to Feature Model Converter 1.0.4. We fixed the following issue: https://issues.apache.org/jira/projects/SLING/versions/12346630 Staging repository:

Re: Resource Type mandatory or optional?

Thanks for the pointer, Konrad: that page clearly states: "Each resource has a resource type which is used by the Servlet and Script resolver to find the appropriate Servlet or Script to handle the request for the Resource." The javadocs are not very precise, but they do not mention that it

[Jenkins] Sling » sling-org-apache-sling-launchpad-testing » master #510 is FIXED

Please see https://builds.apache.org/job/Sling/job/sling-org-apache-sling-launchpad-testing/job/master/510/ for details. No further emails will be sent until the status of the build is changed.

[jira] [Commented] (SLING-8951) Enable reproducible builds by default

[ https://issues.apache.org/jira/browse/SLING-8951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17011960#comment-17011960 ] Konrad Windszus commented on SLING-8951: That is a misunderstanding (i.e. expected behaviour),

[jira] [Commented] (SLING-8951) Enable reproducible builds by default

[ https://issues.apache.org/jira/browse/SLING-8951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17011809#comment-17011809 ] Konrad Windszus commented on SLING-8951: Yes, further hints are available at

[jira] [Commented] (SLING-8951) Enable reproducible builds by default

[ https://issues.apache.org/jira/browse/SLING-8951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17011820#comment-17011820 ] Robert Munteanu commented on SLING-8951: I think it would be useful to document it somewhere on

[Jenkins] Sling » sling-org-apache-sling-launchpad-testing » master #509 is BROKEN

Please see https://builds.apache.org/job/Sling/job/sling-org-apache-sling-launchpad-testing/job/master/509/ for details. No further emails will be sent until the status of the build is changed. Build log follows below: [...truncated 3495 lines...] at

[jira] [Resolved] (SLING-8978) sling-mock: Update Dependencies to 2017

[ https://issues.apache.org/jira/browse/SLING-8978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-8978. --- Resolution: Fixed

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 resource type should be

[jira] [Assigned] (SLING-8959) Update to bnd-maven-plugin 4.3.1

[ https://issues.apache.org/jira/browse/SLING-8959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-8959: -- Assignee: Konrad Windszus > Update to bnd-maven-plugin 4.3.1 >

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

+1 David On Thu, 9 Jan 2020 at 12:13, Konrad Windszus wrote: > 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: >

[jira] [Created] (SLING-8977) Support run modes for repo init conversion

Carsten Ziegeler created SLING-8977: --- Summary: Support run modes for repo init conversion Key: SLING-8977 URL: https://issues.apache.org/jira/browse/SLING-8977 Project: Sling Issue Type:

[jira] [Resolved] (SLING-8977) Support run modes for repo init conversion

[ https://issues.apache.org/jira/browse/SLING-8977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-8977. - Resolution: Fixed Added support in rev c89423c Added a test case for this > Support run

Resource Type mandatory or optional?

i've created a ticket concerning the Sling API that the method Resource.getResourceType should be marke das @Nullable, i always thought it was a bug and that the resource type is optional [1]. carsten pointed out that the resource type is mandatory. the javadocs are not precise on this, i've

[jira] [Updated] (SLING-8673) Upgrade to bnd plugin 4.3.0

[ https://issues.apache.org/jira/browse/SLING-8673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-8673: --- Fix Version/s: (was: Bundle Parent 36) > Upgrade to bnd plugin 4.3.0 >

[jira] [Commented] (SLING-8951) Enable reproducible builds by default

[ https://issues.apache.org/jira/browse/SLING-8951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17011970#comment-17011970 ] Robert Munteanu commented on SLING-8951: Setting the version to a different timestamp on each

[jira] [Updated] (SLING-8490) Create Maven Plugin for FM Content Package Converter

[ https://issues.apache.org/jira/browse/SLING-8490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-8490: Fix Version/s: (was: Feature Model Converter Plugin 1.0.2) Feature

[jira] [Updated] (SLING-8641) Onboard sling-feature-converter-maven-plugin to SonarCloud

[ https://issues.apache.org/jira/browse/SLING-8641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-8641: Fix Version/s: (was: Feature Model Converter Plugin 1.0.2) Feature

Re: [VOTE] Release Apache Sling Feature Model Converter Plugin 1.0.2

Hi Robert I will check out the build with Java 11 and then try to run it under Ubuntu in a VM. I will pull the plug on the release as I agree that a build must work but I was not aware that the build failed until you pointed it out. Keep you posted - Andy > On Jan 9, 2020, at 2:04 AM, Robert

[CANCEL VOTE]: Cancel Release of Apache Sling Feature Model Converter Plugin 1.0.2

Hi I am cancelling the vote as the IT tests fails on Jenkins as well as for Robert. I will investigate the issue and create a new release when the issue is fixed. - Andy

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

+1 (non-binding) - Andy > On Jan 9, 2020, at 4:13 AM, Konrad Windszus wrote: > > 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: >

Re: [VOTE] Release Apache Sling Content-Package to Feature Model Converter 1.0.4

Hi Robert, I have created https://issues.apache.org/jira/browse/SLING-8979 and am cancelling this release. Best regards, David On Thu, 9 Jan 2020 at 15:17, Robert Munteanu wrote: > > > On Thu, 2020-01-09 at 15:13 +, David Bosschaert wrote: > > Hi Robert, > > > > AFAIK the 1.0.2 version

[jira] [Created] (SLING-8979) Include the -source-release.zip file in releases

David Bosschaert created SLING-8979: --- Summary: Include the -source-release.zip file in releases Key: SLING-8979 URL: https://issues.apache.org/jira/browse/SLING-8979 Project: Sling Issue

Re: [VOTE] Release Apache Sling Content-Package to Feature Model Converter 1.0.4

On Thu, 2020-01-09 at 15:26 +0100, Carsten Ziegeler wrote: > I can see it: > > https://repository.apache.org/content/repositories/orgapachesling-2182/org/apache/sling/org.apache.sling.feature.cpconverter/1.0.4/org.apache.sling.feature.cpconverter-1.0.4-sources.jar I was looking for a

Re: [VOTE] Release Apache Sling Content-Package to Feature Model Converter 1.0.4

Hi Robert, AFAIK the 1.0.2 version of this component didn't have that -source-release.zip file either. Can we maybe file a JIRA to add this to the cpconverter build and address it for 1.0.6? Cheers, David On Thu, 9 Jan 2020 at 15:05, Robert Munteanu wrote: > On Thu, 2020-01-09 at 15:26

[jira] [Commented] (SLING-8951) Enable reproducible builds by default

[ https://issues.apache.org/jira/browse/SLING-8951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17011935#comment-17011935 ] Konrad Windszus commented on SLING-8951: I have not tried it out myself. Can you please

Re: [hackathon] maven archetypes

On Sat, 2019-10-05 at 23:32 -0500, Daniel Klco wrote: (snip) > I've put together a simple project archetype for Sling CMS here, but > I'd > wonder if it'd be similar to back it into the overall > sling-project-archetype as a separate content option from the sample > content. Options for sample

Re: [VOTE] Release Apache Sling Content-Package to Feature Model Converter 1.0.4

On Thu, 2020-01-09 at 15:13 +, David Bosschaert wrote: > Hi Robert, > > AFAIK the 1.0.2 version of this component didn't have that > -source-release.zip file either. Can we maybe file a JIRA to add this > to > the cpconverter build and address it for 1.0.6? That is an unfortunate

[jira] [Commented] (SLING-8976) [API Regions] Resolving bundles in different version fails

[ https://issues.apache.org/jira/browse/SLING-8976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17011946#comment-17011946 ] Karl Pauls commented on SLING-8976: --- This need to revert the commits from SLING-8815 as they where not

[jira] [Created] (SLING-8978) sling-mock: Update Dependencies to 2017

Stefan Seifert created SLING-8978: - Summary: sling-mock: Update Dependencies to 2017 Key: SLING-8978 URL: https://issues.apache.org/jira/browse/SLING-8978 Project: Sling Issue Type:

[jira] [Commented] (SLING-8951) Enable reproducible builds by default

[ https://issues.apache.org/jira/browse/SLING-8951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17011958#comment-17011958 ] Robert Munteanu commented on SLING-8951: [~kwin] - see

[jira] [Created] (SLING-8980) Set bundle-version of SNAPSHOT versions to the static String "SNAPSHOT"

Konrad Windszus created SLING-8980: -- Summary: Set bundle-version of SNAPSHOT versions to the static String "SNAPSHOT" Key: SLING-8980 URL: https://issues.apache.org/jira/browse/SLING-8980 Project:

[jira] [Updated] (SLING-8980) Set bundle-version suffix of SNAPSHOT versions to the static String "-SNAPSHOT" instead of a timestamp

[ https://issues.apache.org/jira/browse/SLING-8980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-8980: --- Summary: Set bundle-version suffix of SNAPSHOT versions to the static String "-SNAPSHOT"

[jira] [Updated] (SLING-8980) Set bundle-version suffix of SNAPSHOT versions to the static String "-SNAPSHOT" instead of a timestamp

[ https://issues.apache.org/jira/browse/SLING-8980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-8980: --- Description: Despite the discussion in

[jira] [Commented] (SLING-8962) Use Sling API 2.22.0

[ https://issues.apache.org/jira/browse/SLING-8962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17012169#comment-17012169 ] Oliver Lietz commented on SLING-8962: - [~bdelacretaz], AFAIR API has an impact on package imports

Re: Resource Type mandatory or optional?

I believe always delivering a resource type is also the right thing to do. It shouldn't be up to the provider of the resource to dictate how the resource is to be rendered. Rather it's up to the Sling implementation. By stating it must return a resource type even if it's the default allows for

RE: Resource Type mandatory or optional?

to sum up the opinions: 1. Sling API should always return a resource type, even if it's a fallback one 2. setting a sling:resourceType property is optional, if it's not set a fallback resource type is returned 3. the JCR resource provider always uses the JCR primrary type as fallback -> open

Sling Feature Maven Converter Plugin: Fix for failing IT tests

Hi I got the issue with the failing IT test fixed and now the Jenkins build https://builds.apache.org/job/Sling/job/sling-feature-converter-maven-plugin/ did pass. If anyone could run a local tests to verify that

[jira] [Commented] (SLING-8951) Enable reproducible builds by default

[ https://issues.apache.org/jira/browse/SLING-8951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17012230#comment-17012230 ] Konrad Windszus commented on SLING-8951: I created followup SLING-8980 for improving the

Re: Resource Type mandatory or optional?

I looked at some of our provider implementations and all of them make sure to return a default resource type; so I think we're safe here. The only place where we potentially could handle this is inside the resource resolver implementation after a resource is returned from a provider. If the

Re: [VOTE] Release Apache Sling API 2.22.0

On Tuesday, January 7, 2020 3:43:23 PM CET Radu Cotescu wrote: > Hi, > > We solved 2 issues in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12344636 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2178/ +1 O.

[jira] [Created] (SLING-8981) Update slingstart plugin to Maven 3.5.0

Carsten Ziegeler created SLING-8981: --- Summary: Update slingstart plugin to Maven 3.5.0 Key: SLING-8981 URL: https://issues.apache.org/jira/browse/SLING-8981 Project: Sling Issue Type:

[jira] [Resolved] (SLING-8981) Update slingstart plugin to Maven 3.5.0

[ https://issues.apache.org/jira/browse/SLING-8981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-8981. - Resolution: Fixed > Update slingstart plugin to Maven 3.5.0 >

[jira] [Commented] (SLING-8974) Shows a 200 OK for a delete operation even if the node does not exist.

[ https://issues.apache.org/jira/browse/SLING-8974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17012521#comment-17012521 ] Anisha Narang commented on SLING-8974: -- [~rombert] that's awesome, thanks. :) > Shows a 200 OK for