+1
Le jeu. 4 févr. 2021 à 08:40, Robert Munteanu a écrit :
> On Wed, 2021-02-03 at 15:09 +0100, Christian Schneider wrote:
> > Please vote to approve this release:
>
> +1
> Robert
>
On Wed, 2021-02-03 at 15:09 +0100, Christian Schneider wrote:
> Please vote to approve this release:
+1
Robert
signature.asc
Description: This is a digitally signed message part
akankshajain18 closed pull request #12:
URL: https://github.com/apache/sling-org-apache-sling-engine/pull/12
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and us
+1
Carsten
Am 03.02.2021 um 15:09 schrieb Christian Schneider:
Hi,
We solved 3 issues in this release:
https://issues.apache.org/jira/projects/SLING/versions/12348397
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-2406/
You can use this UNIX script to d
Stefan,
Thanks for the note. At one point my thought was that there should be a SPI
exposed for extending the logic for Version Purging, but until required,
YAGNI. I missed consolidating the packages during refactoring, but as
stated since they're not exposed it could be done at any point.
On Tue
+1
On Wed, Feb 3, 2021 at 9:09 AM Christian Schneider
wrote:
> Hi,
>
> We solved 3 issues in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12348397
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-2406/
>
> You can use this UNIX
[
https://issues.apache.org/jira/browse/SLING-10122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17278339#comment-17278339
]
Andreas Schaefer commented on SLING-10122:
--
Enhanced the Repository Initializer
Thank you for the suggestion! I'll give it a try!
On Wed, Feb 3, 2021 at 11:36 AM Daniel Klco wrote:
> Unless I'm missing something, this sounds like you'd to assign the user
> into an administrative group and give that administrative group the JCR
> repository permissions as well as adding the
[
https://issues.apache.org/jira/browse/SLING-10124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roy Teeuwen updated SLING-10124:
Component/s: Testing
> OSGi Mock - Service reference order is not correct
> --
[
https://issues.apache.org/jira/browse/SLING-10124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17278216#comment-17278216
]
Roy Teeuwen commented on SLING-10124:
-
[~sseifert] I see you committed the code for
Roy Teeuwen created SLING-10124:
---
Summary: OSGi Mock - Service reference order is not correct
Key: SLING-10124
URL: https://issues.apache.org/jira/browse/SLING-10124
Project: Sling
Issue Type:
sonarcloud[bot] commented on pull request #12:
URL:
https://github.com/apache/sling-org-apache-sling-engine/pull/12#issuecomment-772663657
SonarCloud Quality Gate failed.
[](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-engine&pullRequest=12&resolved=false&typ
akankshajain18 opened a new pull request #12:
URL: https://github.com/apache/sling-org-apache-sling-engine/pull/12
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
Unless I'm missing something, this sounds like you'd to assign the user
into an administrative group and give that administrative group the JCR
repository permissions as well as adding the administrative group into the
groups list for the WebConsole Security Provider:
https://sling.apache.org/docum
Eric,
I'm integrating with keycloak. After the user is authenticated, if user
does not exist, I create a new user via UserManager.
I currently have a need to be able to grant a particular user admin rights
so that it can access
Browse Content
System Console
System Configuration
O
[
https://issues.apache.org/jira/browse/SLING-10106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-10106.
--
Resolution: Fixed
Updated all to cm.json 1.0.6
> Update to Apache Felix cm.json 1.0.6
sonarcloud[bot] commented on pull request #11:
URL:
https://github.com/apache/sling-org-apache-sling-engine/pull/11#issuecomment-772588324
SonarCloud Quality Gate failed.
[](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-engine&pullRequest=11&resolved=false&typ
akankshajain18 opened a new pull request #11:
URL: https://github.com/apache/sling-org-apache-sling-engine/pull/11
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
Hi Stefan,
I think we have more than two worlds - it's a multi-verse
For example, for our projects we don't want to have initial content at
all - thats why we need to have an analyser checking for this.
If I think about other projects I can envision that some are fine with
initial content fo
[
https://issues.apache.org/jira/browse/SLING-10095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated SLING-10095:
Fix Version/s: (was: Content Distribution Journal Core 0.1.18)
[
https://issues.apache.org/jira/browse/SLING-9649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated SLING-9649:
---
Fix Version/s: (was: Content Distribution Journal Core 0.1.20)
hello carsten.
can you give some more details about the "setups and requirements" that differ?
i fear if we introduce a switch to distinguish on those things we create
different "worlds" of scenarios which all have to be maintained and tested
separately in the already quite complex toolchain ar
Hi,
We solved 3 issues in this release:
https://issues.apache.org/jira/projects/SLING/versions/12348397
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-2406/
You can use this UNIX script to download the release and verify the
signatures:
https://gitbox.apach
[
https://issues.apache.org/jira/browse/SLING-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17277989#comment-17277989
]
Fabrice Bellingard commented on SLING-10105:
Done [~radu]! =>
https://sonar
[
https://issues.apache.org/jira/browse/SLING-10096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17277988#comment-17277988
]
Robert Munteanu commented on SLING-10096:
-
Thanks for raising the issue and subm
sonarcloud[bot] commented on pull request #7:
URL:
https://github.com/apache/sling-org-apache-sling-servlets-resolver/pull/7#issuecomment-772494666
SonarCloud Quality Gate failed.
[](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-servlets-resolver&pullRequest=7
sonarcloud[bot] removed a comment on pull request #7:
URL:
https://github.com/apache/sling-org-apache-sling-servlets-resolver/pull/7#issuecomment-769719133
SonarCloud Quality Gate failed.
[](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-servlets-resolver&pullR
sonarcloud[bot] removed a comment on pull request #11:
URL:
https://github.com/apache/sling-org-apache-sling-servlets-post/pull/11#issuecomment-769914538
SonarCloud Quality Gate failed.
[](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-servlets-post&pullRequest
sonarcloud[bot] commented on pull request #11:
URL:
https://github.com/apache/sling-org-apache-sling-servlets-post/pull/11#issuecomment-772491020
SonarCloud Quality Gate failed.
[](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-servlets-post&pullRequest=11&reso
/tools/maven/latest3
Java version: 1.8.0_281, vendor: Oracle Corporation, runtime:
/usr/local/asfpackages/java/oraclejdk-1.8.0-281/jre
Default locale: en_US, platform encoding: ISO-8859-1
OS name: "linux", version: "4.15.0-58-generic", arch: "amd64"
Please see
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-launchpad-testing/job/master/332/
for details.
No further emails will be sent until the status of the build is changed.
[
https://issues.apache.org/jira/browse/SLING-10123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohit Arora updated SLING-10123:
Description:
In case of recoverable exceptions, distribution agent queue processor does not
evict
[
https://issues.apache.org/jira/browse/SLING-10123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohit Arora updated SLING-10123:
Description:
In case of recoverable exceptions, distribution agent queue processor does not
evict
Mohit Arora created SLING-10123:
---
Summary: Distribution agent queue processor should implement a
backoff in case of retries for processing an item
Key: SLING-10123
URL: https://issues.apache.org/jira/browse/SLING-10
[
https://issues.apache.org/jira/browse/SLING-10123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohit Arora updated SLING-10123:
Description:
In case of recoverable exceptions, distribution agent queue processor does not
evict
[
https://issues.apache.org/jira/browse/SLING-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider resolved SLING-9504.
Resolution: Fixed
> Switch from protobuf to json
>
>
>
Cancelling the vote due to the issues found, follow-up SLING-10120
Cheers,
Stefan
On 02.02.21 09:53, Stefan Egli wrote:
Hi,
We solved 2 issues in this release:
https://issues.apache.org/jira/projects/SLING/versions/12344827
Staging repository:
https://repository.apache.org/content/repositorie
[
https://issues.apache.org/jira/browse/SLING-10120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli reassigned SLING-10120:
---
Assignee: Stefan Egli
> Upgrade event to parent 40
> --
>
>
Thx for the findings, I'll revert the vote and look into SLING-10120
Cheers,
Stefan
On 03.02.21 11:29, Robert Munteanu wrote:
All of these are due to using an old parent pom. The improvement to
move to a recent parent pom is tracked at
https://issues.apache.org/jira/browse/SLING-10120
Than
All of these are due to using an old parent pom. The improvement to
move to a recent parent pom is tracked at
https://issues.apache.org/jira/browse/SLING-10120
Thanks,
Robert
On Tue, 2021-02-02 at 19:23 -0500, Daniel Klco wrote:
> I'm also seeing a failure on the latest build:
> https://ci-bui
[
https://issues.apache.org/jira/browse/SLING-8595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-8595:
---
Parent: SLING-8734
Issue Type: Sub-task (was: Improvement)
> Update of sling parent
[
https://issues.apache.org/jira/browse/SLING-8595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated SLING-8595:
---
Fix Version/s: (was: Content Distribution Core 0.4.6)
Content D
[
https://issues.apache.org/jira/browse/SLING-8994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated SLING-8994:
---
Fix Version/s: (was: Content Distribution Core 0.4.6)
Content D
[
https://issues.apache.org/jira/browse/SLING-9017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated SLING-9017:
---
Fix Version/s: (was: Content Distribution Core 0.4.6)
Content D
[
https://issues.apache.org/jira/browse/SLING-10097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated SLING-10097:
Fix Version/s: (was: Content Distribution Core 0.4.6)
Conten
Hi,
On Tue, Feb 2, 2021 at 9:56 PM Lisa Davidson wrote:
> ...I have a need to update an existing user to be admin...
In general I think the recommendation is to create a group that has
the necessary access rights, with that user as a member.
Using the JCR admin user more than strictly needed is
[
https://issues.apache.org/jira/browse/SLING-10088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider resolved SLING-10088.
-
Fix Version/s: (was: Content Distribution Core 0.4.4)
Cont
47 matches
Mail list logo
