[
https://issues.apache.org/jira/browse/SLING-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-9359.
-
Resolution: Done
> Provide Installer Factory Configuration Option
>
[
https://issues.apache.org/jira/browse/SLING-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-9360.
-
Resolution: Done
> Provide Installer Factory Packages Option
>
[
https://issues.apache.org/jira/browse/SLING-9686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz reopened SLING-9686:
-
Check and fix broken {{README}}s.
> Update project badges to point to ci-builds.apache.org
>
Please see
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-launchpad-testing/job/master/52/
for details.
No further emails will be sent until the status of the build is changed.
Build log follows below:
[...truncated 1545 lines...]
[INFO] Tests run: 15, Failures:
Please see
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-launchpad-testing/job/master/51/
for details.
No further emails will be sent until the status of the build is changed.
sonarcloud[bot] commented on pull request #1:
URL:
https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/pull/1#issuecomment-679404970
SonarCloud Quality Gate failed.
sonarcloud[bot] removed a comment on pull request #1:
URL:
https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/pull/1#issuecomment-679298315
SonarCloud Quality Gate failed.
Please see
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-launchpad-testing/job/master/48/
for details.
No further emails will be sent until the status of the build is changed.
--
[INFO] Total time: 03:12 min
[INFO] Finished at: 2020-08-24T22:37:27Z
[INFO]
[INFO] [jenkins-event-spy] Generated
/home/jenkins/jenkins-agent/workspace/e-sl
Hi Carsten,
And if you still need this, you can do this differently without using
the resource mapping functionality.
This happens too often today because of the missing extensibility of
the resource resolver. The point of the Resource Mapping SPI is to
improve the situation and to be able
Please see
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-launchpad-testing/job/master/44/
for details.
No further emails will be sent until the status of the build is changed.
Build log follows below:
[...truncated 1446 lines...]
at
Please see
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-launchpad-testing/job/master/42/
for details.
No further emails will be sent until the status of the build is changed.
sonarcloud[bot] removed a comment on pull request #1:
URL:
https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/pull/1#issuecomment-674438610
SonarCloud Quality Gate failed.
sonarcloud[bot] commented on pull request #1:
URL:
https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/pull/1#issuecomment-679298315
SonarCloud Quality Gate failed.
[
https://issues.apache.org/jira/browse/SLING-9686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17183535#comment-17183535
]
Dan Klco edited comment on SLING-9686 at 8/24/20, 6:39 PM:
---
Oh, shoot [~radu] I
[
https://issues.apache.org/jira/browse/SLING-9686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17183535#comment-17183535
]
Dan Klco commented on SLING-9686:
-
Oh, shoot [~radu] I was working on this on SLING-9686 as well.
>
[INFO] Total time: 03:21 min
[INFO] Finished at: 2020-08-24T18:36:23Z
[INFO]
[INFO] [jenkins-event-spy] Generated
/home/jenkins/workspace/e-sling-launchpad-testing_master@tmp/withMaven5a397be2/maven-spy-20200824-18
[
https://issues.apache.org/jira/browse/SLING-9686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu resolved SLING-9686.
-
Resolution: Fixed
> Update project badges to point to ci-builds.apache.org
>
[
https://issues.apache.org/jira/browse/SLING-9686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17183505#comment-17183505
]
Oliver Lietz commented on SLING-9686:
-
[~radu], The script used to update the badges trashes {{\n}},
[
https://issues.apache.org/jira/browse/SLING-9594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17183497#comment-17183497
]
Radu Cotescu commented on SLING-9594:
-
I've created SLING-9686 for updating the badges. [~dklco]
[
https://issues.apache.org/jira/browse/SLING-9651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu reassigned SLING-9651:
---
Assignee: Radu Cotescu
> Committer CLI release checks should use ci-builds.apache.org
>
Yes, backwards compatibility is important and I think if we introduce
new methods in the ResourceResolver (deprecating the old ones), we'll
get that easily. For now, I wouldn't introduce a different content model
for the mapping in /etc - that could be done independently if required
Regards
Hi Georg,
at least today, the user context is not really taken into account for
mapping. And I think everything stays nicer and cleaner if we don't open
this up - otherwise you need to think about setting correct caching
headers etc.
And if you still need this, you can do this differently
Radu Cotescu created SLING-9686:
---
Summary: Update project badges to point to ci-builds.apache.org
Key: SLING-9686
URL: https://issues.apache.org/jira/browse/SLING-9686
Project: Sling
Issue
+1
Hi,
We solved 1 issue in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12347866
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-2322/
You can use this UNIX script to download the release and verify the signatures:
[
https://issues.apache.org/jira/browse/SLING-9685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-9685.
Resolution: Fixed
Fixed with [sling-org-apache-sling-starter commit
[
https://issues.apache.org/jira/browse/SLING-9685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-9685:
---
Labels: Sling-12-ReleaseNotes (was: )
> Support principal-based authentication
>
[
https://issues.apache.org/jira/browse/SLING-9685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-9685:
---
Description: The [oak principal-based
Robert Munteanu created SLING-9685:
--
Summary: Support principal-based authentication
Key: SLING-9685
URL: https://issues.apache.org/jira/browse/SLING-9685
Project: Sling
Issue Type:
Hi Carsten,
good opportunity to rethink mapping / resolving in general.
so you are referring to SLING-9622 and more specifically to comment
[1] I suppose... I have thought it a bit through and I think there
are valid use cases for having "the user context" (=rr) available
for both resolve()
[
https://issues.apache.org/jira/browse/SLING-9657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu closed SLING-9657.
---
> Same-name JS Use dependencies are not always correctly resolved
>
[
https://issues.apache.org/jira/browse/SLING-9671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu closed SLING-9671.
---
> Allow non-bundled inheriting resource types to override Use-API templates
>
[
https://issues.apache.org/jira/browse/SLING-9677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu closed SLING-9677.
---
> Remove redundant
> org.apache.sling.scripting.core.impl.bundled.ProtectedBindings class
>
[
https://issues.apache.org/jira/browse/SLING-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu closed SLING-9607.
---
> Fix conflicting dependency to commons-io where two different versions are
> listed
>
[
https://issues.apache.org/jira/browse/SLING-9679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu closed SLING-9679.
---
> Add the executable name in the servlet properties for the BundledScriptServlet
>
Hi,
The vote has passed with the following result:
+1 (binding): Robert Munteanu, Andrei Dulvac, Nicolas Peltier, Karl Pauls,
Stefan Seifert
+1 (non-binding): none
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
Regards,
Radu
Hi,
The vote has passed with the following result:
+1 (binding): Robert Munteanu, Dan Klco, Eric Norman, Stefan Seifert, Karl Pauls
+1 (non-binding): none
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
Regards,
Radu Cotescu
Hi,
The vote has passed with the following result:
+1 (binding): Robert Munteanu, Nicolas Peltier, Karl Pauls, Stefan Seifert
+1 (non-binding): none
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
Regards,
Radu Cotescu
Georg, thanks for the reply - agree my use cases should be covered with that
On 8/24/2020 7:42 AM, Georg Henzler wrote:
Hi Ruben,
One use case that probably also should be considered here is the case
where static pages are generated with sling. In that case the
rendering of the page is not
Hi Ruben,
One use case that probably also should be considered here is the case
where static pages are generated with sling. In that case the
rendering of the page is not tied to a request.
While [1] has a request in the signature, the idea is not that this
needs to be "a currently active"
[
https://issues.apache.org/jira/browse/SLING-9663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-9663.
Resolution: Fixed
Fixed with
rombert merged pull request #3:
URL: https://github.com/apache/sling-org-apache-sling-jcr-oak-server/pull/3
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
[
https://issues.apache.org/jira/browse/SLING-9681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17183200#comment-17183200
]
Bertrand Delacretaz commented on SLING-9681:
That sounds good, in general we love modularity!
[
https://issues.apache.org/jira/browse/SLING-9681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17183199#comment-17183199
]
Dan Klco commented on SLING-9681:
-
Good point [~bdelacretaz] -- Honestly I've been thinking that the
On Sat, 2020-08-22 at 14:24 +0200, Carsten Ziegeler wrote:
> I always liked the fact, that there are no high requirements for
> installing the demo
Yes, that is correct. A single bundle (well, with repoinit and configs
in the sling starter feature model ) is quite simple. On the other hand
we
Robert Munteanu created SLING-9684:
--
Summary: Support resolving variables within variables
Key: SLING-9684
URL: https://issues.apache.org/jira/browse/SLING-9684
Project: Sling
Issue Type:
Thanks Carsten and David.
I created https://issues.apache.org/jira/browse/SLING-9684 for this.
Robert
On Mon, 2020-08-24 at 12:05 +0100, David Bosschaert wrote:
> HI all,
>
> I also thought that recursively replacing variables was supported,
> but I
> tried it this morning quickly and
HI all,
I also thought that recursively replacing variables was supported, but I
tried it this morning quickly and apparently it's not.
Maybe create a JIRA for it?
Best regards,
David
On Mon, 24 Aug 2020 at 12:00, Carsten Ziegeler wrote:
> Hi Robert,
>
> ok, thanks for clarifying. Yes, I
Hi Robert,
ok, thanks for clarifying. Yes, I agree it makes sense to support a) as
well - and actually I'm a little bit surprised that it is not :)
I guess the only change needed is to recursively process replacements of
variables which should be an easy fix
Regards
Carsten
Am 24.08.2020 um
[
https://issues.apache.org/jira/browse/SLING-9622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17183156#comment-17183156
]
Robert Munteanu commented on SLING-9622:
+1, I think the situation is already improved ( both
+1
Hi Carsten,
On Sat, 2020-08-22 at 14:27 +0200, Carsten Ziegeler wrote:
> Hi,
>
> I guess it depends on how this support should look like. I would
> assume,
> that "-V persistence.dir=/data" with your example works and uses
> "/data"
> for the persistence. It will not use "${sling.home}/data" -
+1
regards,
Karl
On Mon, Aug 24, 2020 at 12:36 PM Stefan Seifert wrote:
>
> +1
>
>
--
Karl Pauls
karlpa...@gmail.com
+1
+1
[
https://issues.apache.org/jira/browse/SLING-9681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17183099#comment-17183099
]
Bertrand Delacretaz commented on SLING-9681:
While you're at it, it would be nice IMHO to add
Hi,
On Mon, Aug 24, 2020 at 10:50 AM Karl Pauls wrote:
> ...the old tracker can either be deprecated or maybe be
> repurposed (see above)...
For now, I have added a note mentioning this at
https://github.com/apache/sling-org-apache-sling-scripting-bundle-tracker
-Bertrand
Hi,
the bundle.tracker was merged into the resolver mostly for efficiency
reasons - however, it isn't a bad fit there so I wouldn't say that is
a problem. That there is now a dependency from the scripting core to
the resolver is a side-effect of the whiteboard pattern used in this
case and I
Hi,
On Sun, Aug 23, 2020 at 9:33 PM Oliver Lietz wrote:
> ...Why was the (standalone) module o.a.s.scripting.bundle.tracker merged into
> o.a.s.servlets.resolver?..
That's strange indeed, we now have very similar code at [1] and [2].
If there was a good reason for that (I don't know about
Hi,
On Sun, Aug 23, 2020 at 11:24 AM Carsten Ziegeler wrote:
> ...PathMapperFactory (its probably not a good name...
I think "rewriter" instead of "mapper" might be a good term, in the
end it's similar to the famous mod_rewrite?
> ...So how about moving the mapping part out of the resource
+1
regards,
Karl
On Mon, Aug 24, 2020 at 9:13 AM Nicolas Peltier
wrote:
>
> builds & signatures check worked for me, so here's my +1
>
> Le ven. 21 août 2020 à 18:01, Radu Cotescu a écrit :
>
> > Hi Daniel,
> >
> > > On 21 Aug 2020, at 15:40, Daniel Klco wrote:
> > >
> > > Hm, I am seeing
+1
regards,
Karl
On Mon, Aug 24, 2020 at 9:06 AM Nicolas Peltier wrote:
>
> +1
>
> Le ven. 21 août 2020 à 15:35, Andrei Dulvac a écrit :
>
> > +1
> >
> > - Andrei
> >
> > On Fri, 21 Aug 2020 at 14:22, Robert Munteanu wrote:
> >
> > > On Fri, 2020-08-21 at 11:17 +, Radu Cotescu wrote:
> >
builds & signatures check worked for me, so here's my +1
Le ven. 21 août 2020 à 18:01, Radu Cotescu a écrit :
> Hi Daniel,
>
> > On 21 Aug 2020, at 15:40, Daniel Klco wrote:
> >
> > Hm, I am seeing some test failures:
> >
> >
>
+1
Le ven. 21 août 2020 à 15:35, Andrei Dulvac a écrit :
> +1
>
> - Andrei
>
> On Fri, 21 Aug 2020 at 14:22, Robert Munteanu wrote:
>
> > On Fri, 2020-08-21 at 11:17 +, Radu Cotescu wrote:
> >
> > > sh check_staged_release.sh 2321 /tmp/sling-staging
> >
> >
> >
> > +1
> >
> > Robert
> >
>
65 matches
Mail list logo
