Thanks for confirming, Andy!
After some further digging I can confirm that Carsten is right, and we
don't need releases for the extensions that weren't modified. Even though
these are included as part of the slingfeature-maven-plugin at runtime,
Maven is smart enough to pick the latest version of
SLING-8479: I provided a fix for that and it was merged into master so I marked
that ticket as resolved.
SLING-8483: I do not think this is a high priority for this release.
Cheers - Andy
> On Jul 29, 2019, at 8:24 AM, David Bosschaert
> wrote:
>
> Hi Carsten,
>
> On Fri, 26 Jul 2019 at
Did you ever experience the classpath issue described below in Maven?
I thought Maven does a dependency resolution and creates a classloader
per plugin which I believe should solve the problem. Unless of course we
embed dependencies somewhere
Carsten
David Bosschaert wrote
Hi Carsten,
On
Hi Carsten,
On Fri, 26 Jul 2019 at 17:34, Carsten Ziegeler wrote:
>
> +1 for a release.
>
> The analyser, modelconverter, launcher have open issues. Not sure how
> important they are.
>
For the analyser, I think we can postpone SLING-8594, maybe the analyser
described in this issue is already
Hi Carsten
I updated the Ticket SLING-8541 and my branch of the Slingfeature Maven Plugin
(merge-cpconverter-plugin) has a solution for it.
Let me know if that works for you.
I tested it with Sling 11 and Peregrine CMS and it works for me (Converting
both PMs and CPs, building it and launching
+1 for a release.
The analyser, modelconverter, launcher have open issues. Not sure how
important they are.
Both extensions (apiregions and content) have no issues at all, so I
don't think we need a release. Unless the issues are not in jira of course.
The slingstart plugin has no issues
Hi all,
I would like to release the following feature model related components some
soon, possibly next week.
org.apache.sling.feature
org.apache.sling.feature.io
org.apache.sling.feature.analyser
org.apache.sling.feature.modelconverter
org.apache.sling.feature.launcher
