+1
Robert Munteanu wrote
> Hi,
>
> We solved 2 issues in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12338911
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1974
>
> You can use this UNIX script to download the release
+1
Robert Munteanu wrote
> Hi,
>
> We solved 4 issues in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12341398
>
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1975
>
> You can use this UNIX script to download the release
+1
Robert Munteanu wrote
> Hi,
>
> We solved 5 issues in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12340294
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1976
>
> You can use this UNIX script to download the release
+1
Nicolas Peltier wrote
> Hi,
>
> We solved 1 issue in this release:
>
> https://issues.apache.org/jira/projects/SLING/versions/12344107
>
> There are still some outstanding issues:
>
>
+1
Nicolas Peltier wrote
> Hi,
>
> We solved 21 issues in this
> release:https://issues.apache.org/jira/projects/SLING/versions/12342862
>
> There are still 5 outstanding
> issues:https://issues.apache.org/jira/browse/SLING-7250
> https://issues.apache.org/jira/browse/SLING-7772
>
Konrad Windszus created SLING-7924:
--
Summary: ValidationModelRetriever does not correctly evaluate
"applicable path"
Key: SLING-7924
URL: https://issues.apache.org/jira/browse/SLING-7924
Project:
+1
On Thu, Sep 13, 2018 at 10:50 AM Robert Munteanu wrote:
> On Thu, 2018-09-13 at 12:31 +0200, Nicolas Peltier wrote:
> > Please vote to approve this release:
>
> +1
>
> And BTW, you probably want to fix this
>
> [WARNING]
>
+1
On Thu, Sep 13, 2018 at 10:59 AM Nicolas Peltier
wrote:
> Hi,
>
> We solved 1 issue in this release:
>
> https://issues.apache.org/jira/projects/SLING/versions/12344107
>
> There are still some outstanding issues:
>
>
>
- the sling metrics module is available for some time, but not much used to
instrument sling currently
- we should apply it to the important parts of sling - e.g.:
- sling engine: render times of requests, components, includes
- filters execution times (currently custom "metrics" in web
- problems with current scripting implementation
- some existing script engines do not check for existence of sling object
- remove dependency on resource paths in sling scripting - should focus only
on compiling the scripts, regardless of their source
- planned actions:
- try to get rid of
- currently there is some overlap between sling health checks and the new felix
system readyness framework presented [1]
- the idea is to bring this together within felix
- provide a facade for the sling healthcheck API for backwards compatibility
stefan
[1]
- our current contributing [1] page is very outdated - we have to update it
- search over all sling git repos is difficult currently - possible solutions
which all have some drawbacks
- search via https://sourcegraph.com - this does not seem to work properly
(does not find all occurences),
On Thursday 13 September 2018 10:23:30 Christian Schneider wrote:
> In some cases I want to pull up a sling instances in pax exam but want to
> remove some lower level bundles and replace them with some custom bundle.
> This can not be handled by simply providing a different version.
Right, you
- no need to release the modules which were migrated jetbrains null annotations
before releasing sling 11
- move all starter-related testing modules to a single git repo, releasing them
together
- long-term goal: move integration tests to the modules they test, but add
support for running them
- in the future new JRE version will come up quite often
- we should set up integration tests for new JRE releases as soon as possible
- with the changes karl already did for supporting the current JRE versions is
should no longer needed to do any manual changes to the code (e.g. properties
- the current osgi-installer is a candidate for deprecation
- the current feature model is indented to be used for "from-scratch"
deployments defining and setting up a full instance - not for delta deployments
of changes to an existing instance
- it would be nice if there would be some support
One concern I have with the experimental (or perhaps the definition
therein) is that it seems much more bleeding edge than what we currently
consider contrib. Is there some more middle ground here, between "not part
of the "core"" and "use on your own risk, probably not well maintained"?
On Thu,
- current contrib/deprecated state maintained in [1]
- status explanations pages missing e.g. [2]
- we currently have not process when a module should be marked as deprecated -
here is a proposal:
- export statistics on module usage (downloads) from maven central statistics
- mark modules as
- we would like to switch completely to bnd-maven-plugin, but without the need
for a separate bnd file
- we currently have only one parent pom for bundle modules and non-bundle
modules, making it difficult to configure the bnd-maven-plugin globally so it
gets up picked only for bundles, not for
- in the past, it was not possible to use Sling without JCR, but there was some
work on it lately to remove this hard dependency
- Sling servlets are cleaned up and do no longer have a dependency
- A remaining blocker is the usage of service users all over the code base -
providing service users
Oliver Lietz created SLING-7923:
---
Summary: Simplify integration tests
Key: SLING-7923
URL: https://issues.apache.org/jira/browse/SLING-7923
Project: Sling
Issue Type: Improvement
on tuesday we had the Sling Committer round table @ adaptTo() in Potsdam, and
today the Hackathon in the office of pro!vision Berlin.
i will publish the results *) of the discussions on this list using the
"[hackathon]" prefix in the subject.
participants of the hackathon: Carsten, Nicolas,
i pushed the current snapshot site to
http://sling.apache.org/components/slingfeature-maven-plugin/
stefan
>-Original Message-
>From: Konrad Windszus
>Sent: Tuesday, September 11, 2018 11:32 AM
>To: dev@sling.apache.org
>Subject: Maven Site for slingfeature-maven-plugin
>
>Would it be
+1
Le mer. 12 sept. 2018 à 21:28, Eric Norman a
écrit :
> +1
>
> On Wed, Sep 12, 2018 at 8:47 AM Daniel Klco wrote:
>
> > +1
> >
> > On Wed, Sep 12, 2018 at 8:24 AM Robert Munteanu
> > wrote:
> >
> > > Hi,
> > >
> > > We solved 5 issues in this release:
> > >
+1
Le mer. 12 sept. 2018 à 21:27, Eric Norman a
écrit :
> +1
>
> On Wed, Sep 12, 2018 at 8:43 AM Daniel Klco wrote:
>
> > +1
> >
> > On Wed, Sep 12, 2018 at 8:22 AM Robert Munteanu
> > wrote:
> >
> > > Hi,
> > >
> > > We solved 4 issues in this release:
> > >
+1
Le mer. 12 sept. 2018 à 17:31, Daniel Klco a écrit :
> +1
>
> On Wed, Sep 12, 2018 at 8:20 AM Robert Munteanu
> wrote:
>
> > Hi,
> >
> > We solved 2 issues in this release:
> > https://issues.apache.org/jira/projects/SLING/versions/12338911
> >
> > Staging repository:
> >
Hi,
We solved 1 issue in this release:
https://issues.apache.org/jira/projects/SLING/versions/12344107
There are still some outstanding issues:
Robert,
My understanding is these dependencies are coming from Gulp, our build tool
not from the built code. While the warnings aren't ideal, we're not
including minmatch, lodash or graceful-fs in our final JS / CSS builds,
they are just used to build our code.
I'll try to figure out which
On Thu, 2018-09-13 at 12:31 +0200, Nicolas Peltier wrote:
> Please vote to approve this release:
+1
And BTW, you probably want to fix this
[WARNING]
[
https://issues.apache.org/jira/browse/SLING-7902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier reassigned SLING-7902:
--
Assignee: Nicolas Peltier
> The http.conn.timeout property on
[
https://issues.apache.org/jira/browse/SLING-7902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-7902:
---
Fix Version/s: Content Distribution Core 0.3.2
> The http.conn.timeout property on
[
https://issues.apache.org/jira/browse/SLING-5760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-5760:
---
Fix Version/s: (was: Content Distribution Core 0.3.0)
> Allow to support certificate
[
https://issues.apache.org/jira/browse/SLING-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-5916:
---
Fix Version/s: (was: Content Distribution Core 0.3.0)
> Remove all usages of
[
https://issues.apache.org/jira/browse/SLING-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-4797:
---
Fix Version/s: (was: Content Distribution Core 0.3.0)
> Improve handling of Move events
[
https://issues.apache.org/jira/browse/SLING-6211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-6211:
---
Fix Version/s: (was: Content Distribution Core 0.3.0)
> Clarify AbstractJcrEventTrigger
[
https://issues.apache.org/jira/browse/SLING-7472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-7472:
---
Fix Version/s: (was: Content Distribution Core 0.3.0)
> Simplify factory mapping
>
[
https://issues.apache.org/jira/browse/SLING-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-7733:
---
Fix Version/s: (was: Content Distribution Core 0.3.0)
> Do not rewrite
[
https://issues.apache.org/jira/browse/SLING-7513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-7513:
---
Fix Version/s: (was: Content Distribution Core 0.3.0)
> VltUtils#createFilter adds an
[
https://issues.apache.org/jira/browse/SLING-7902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier updated SLING-7902:
---
Fix Version/s: (was: Content Distribution Core 0.3.0)
> The http.conn.timeout property
[
https://issues.apache.org/jira/browse/SLING-7902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier resolved SLING-7902.
Resolution: Fixed
Fix Version/s: Content Distribution Core 0.3.0
> The
Hi,
I noticed the following when building the CMS
[WARNING] npm WARN notice [SECURITY] lodash has the following vulnerability: 1
low. Go here for more details:
https://nodesecurity.io/advisories?search=lodash=1.0.2 - Run `npm i
npm@latest -g` to upgrade your npm version, and then `npm audit`
A note on Javadocs - we generate them from the list of artifacts in the
starter.
Any additional artifacts ( like annotations ) must be listed manually
in the generate_javadoc.sh script [1], so please add them there (or let
me know and I will add them).
Thanks,
Robert
[1]:
On Wed, 2018-09-12 at 06:29 +, Stefan Seifert wrote:
> what about the missing releases of the jsr-305->jetbrains migration -
> see column "released" in
> https://issues.apache.org/jira/browse/SLING-7798
>
> should we release them before releasing sling 11?
Sorry, missed this.
No, we don't
[
https://issues.apache.org/jira/browse/SLING-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16613498#comment-16613498
]
Robert Munteanu commented on SLING-7922:
As [~cziegeler] noted, these are the Sling dependencies
I raised https://issues.apache.org/jira/browse/SLING-7922 for this.
Robert
On Tue, 2018-09-11 at 15:09 +0200, Carsten Ziegeler wrote:
> I also see that some of our sling modules are not updated to the
> latest:
>
>
> org.apache.sling:org.apache.sling.caconfig.api 1.1.0 ->
> 1.1.2
>
[
https://issues.apache.org/jira/browse/SLING-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-7922:
---
Description:
Should look into:
- Sling modules that are released but not included
- Felix
Robert Munteanu created SLING-7922:
--
Summary: Update to latest available releases for Sling 11
Key: SLING-7922
URL: https://issues.apache.org/jira/browse/SLING-7922
Project: Sling
Issue
[
https://issues.apache.org/jira/browse/SLING-7885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu reassigned SLING-7885:
--
Assignee: Dan Klco
> CMS - Core - UGC Service Not Registered
>
Nicolas Peltier created SLING-7921:
--
Summary: upgrade to parent 34
Key: SLING-7921
URL: https://issues.apache.org/jira/browse/SLING-7921
Project: Sling
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/SLING-7919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-7919.
Resolution: Fixed
Fixed by commit 22a7f13. Shouldn't impact anything, but the
[
https://issues.apache.org/jira/browse/SLING-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16613307#comment-16613307
]
Bertrand Delacretaz commented on SLING-7920:
Fixed with this commit, by accumulating multiple
Hi,
We solved 21 issues in this
release:https://issues.apache.org/jira/projects/SLING/versions/12342862
There are still 5 outstanding
issues:https://issues.apache.org/jira/browse/SLING-7250
https://issues.apache.org/jira/browse/SLING-7772
https://issues.apache.org/jira/browse/SLING-7708 (doc bug
Bertrand Delacretaz created SLING-7920:
--
Summary: IllegalStateException in Model-to-Feature converter for
multiple repoinit sections
Key: SLING-7920
URL: https://issues.apache.org/jira/browse/SLING-7920
Bertrand Delacretaz created SLING-7919:
--
Summary: Duplicate feature name "sling-event" in
sling-org-apache-sling-starter
Key: SLING-7919
URL: https://issues.apache.org/jira/browse/SLING-7919
In some cases I want to pull up a sling instances in pax exam but want to
remove some lower level bundles and replace them with some custom bundle.
This can not be handled by simply providing a different version.
An example is:
I want to load sling using SlingOptions.slingDistribution() but I
55 matches
Mail list logo
