Hi Olli,
> On 22 Feb 2021, at 14:18, Oliver Lietz wrote:
>
> On Thursday, 18 February 2021 10:21:05 CET Radu Cotescu wrote:
>> Hi,
>
> Hi Karl, hi Radu,
>
> Sorry for coming back late, I was again hit by severe bugs in Akonadi and
> still trying to fully recover.
>
>> If nobody opposes in
On Thursday, 18 February 2021 10:21:05 CET Radu Cotescu wrote:
> Hi,
Hi Karl, hi Radu,
Sorry for coming back late, I was again hit by severe bugs in Akonadi and
still trying to fully recover.
> If nobody opposes in the next 24 hours, I will ask INFRA to rename the
> repository from [0] to
Hi,
> On 18 Feb 2021, at 10:21, Radu Cotescu wrote:
>
> If nobody opposes in the next 24 hours, I will ask INFRA to rename the
> repository from [0] to sling-org-apache-sling-scripting-spi and the API
> refactored to be in the org.apache.sling.scripting.spi.bundle package.
INFRA task at
Hi Julian,
> On 18 Feb 2021, at 11:50, Julian Sedding wrote:
>
> As it seems you are renaming packages, just a question from the side
> line. I haven't followed the discussion closely, but I always wondered
> why the package name contains the term "bundle"? Is it because the
> scripts are
Hi
As it seems you are renaming packages, just a question from the side
line. I haven't followed the discussion closely, but I always wondered
why the package name contains the term "bundle"? Is it because the
scripts are "bundled"? Wouldn't "precompiled" be more expressive and
maybe also a
Hi,
If nobody opposes in the next 24 hours, I will ask INFRA to rename the
repository from [0] to sling-org-apache-sling-scripting-spi and the API
refactored to be in the org.apache.sling.scripting.spi.bundle package.
Regards,
Radu
> On 15 Feb 2021, at 10:51, Karl Pauls wrote:
>
> So,
So, looking at this proposal by Radu,
it sounds to me like this is addressing what Olli wanted and just
needs a decision on whether we want a new scripting.spi bundle or
rather only have the scripting.api bundle.
Olli, what are your thoughts - would you be fine with the separate
bundle provided
Hi Olli,
Which of the two options below do you prefer?
1. The API from o.a.s.servlets.resolver.api bundle [0] gets moved to the
o.a.s.scripting.api bundle, in the o.a.s.scripting.api.bundle package. That
means that we’ll have the following import chains:
o.a.s.scripting.api
On Monday, February 1, 2021 1:17:23 PM CET Karl Pauls wrote:
> Hi,
Hi,
> we have a discussion going on at SLING- that needs some resolving.
>
> As far as I can see, there are the following proposals in the issue:
>
> #1 move the o.a.s.servlets.resolver.bundle.tracker package to another
>
Hi,
we have a discussion going on at SLING- that needs some resolving.
As far as I can see, there are the following proposals in the issue:
#1 move the o.a.s.servlets.resolver.bundle.tracker package to another artifact
#2 rename the package to something else
#3 split up the package to move
10 matches
Mail list logo
