Re: Release Sling Feature Model related components soon

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

[jira] [Updated] (SLING-8483) Sling Feature Launcher with Content Package depends on Classpath Order and Needs Package Init Bundle

[ https://issues.apache.org/jira/browse/SLING-8483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-8483: Description: There are two issues with the Feature Launcher to support Package Content

[jira] [Resolved] (SLING-8479) Model Converter should handle Runmodes correctly

[ https://issues.apache.org/jira/browse/SLING-8479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer resolved SLING-8479. - Resolution: Fixed In 2019-6-7 I created a PR that allows the user to limit the

Re: Release Sling Feature Model related components soon

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

Re: Release Sling Feature Model related components soon

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

[jira] [Resolved] (SLING-8234) Feature launcher does not specify which content package requires a missing dependency

[ https://issues.apache.org/jira/browse/SLING-8234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert resolved SLING-8234. - Resolution: Won't Fix This is now handled by an analyzer which is implemented via

[jira] [Resolved] (SLING-8477) Make merge extensions configurable via the Feature Model launcher

[ https://issues.apache.org/jira/browse/SLING-8477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert resolved SLING-8477. - Resolution: Fixed Fixed with #11 > Make merge extensions configurable via the Feature

[GitHub] [sling-org-apache-sling-feature-launcher] bosschaert merged pull request #11: SLING-8477 Make merge extensions configurable via the Feature Model launcher

bosschaert merged pull request #11: SLING-8477 Make merge extensions configurable via the Feature Model launcher URL: https://github.com/apache/sling-org-apache-sling-feature-launcher/pull/11 This is an automated message

[jira] [Commented] (SLING-8541) slingfeature-maven-plugin should allow for generated feature model files

[ https://issues.apache.org/jira/browse/SLING-8541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895332#comment-16895332 ] Andreas Schaefer commented on SLING-8541: - I created a plugin for the CP converter and

[jira] [Updated] (SLING-8594) Create an API Jar analyser that checks that it's transitively closed

[ https://issues.apache.org/jira/browse/SLING-8594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert updated SLING-8594: Fix Version/s: (was: Feature Model Analyser 1.0.6) Feature Model

[jira] [Closed] (SLING-8570) Extract a generic Content Parser API from org.apache.sling.jcr.contentparser with pluggable implementations

[ https://issues.apache.org/jira/browse/SLING-8570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu closed SLING-8570. --- > Extract a generic Content Parser API from org.apache.sling.jcr.contentparser > with pluggable

[RESULT] [VOTE] Release Apache Sling Content Parser API 2.0.0, Apache Sling Content Parser JSON 2.0.0, Apache Sling Content Parser XML 2.0.0, Apache Sling Content Parser XML JCR 2.0.0, Apache Sling Co

Hi, The vote has passed with the following result: +1 (binding): Stefan Seifert, Carsten Ziegeler, Radu Cotescu +1 (non-binding): Andreas Schaefer I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Regards, Radu Cotescu

[jira] [Resolved] (SLING-8556) Experiments with Sling and GraalVM native images

[ https://issues.apache.org/jira/browse/SLING-8556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-8556. Resolution: Fixed FWIW, I've changed strategy for my "serverless & Sling" talk at

Re: [VOTE] Release Apache Sling Content Parser API 2.0.0, Apache Sling Content Parser JSON 2.0.0, Apache Sling Content Parser XML 2.0.0, Apache Sling Content Parser XML JCR 2.0.0, Apache Sling Content

+1 > On 24 Jul 2019, at 16:55, Radu Cotescu wrote: > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours.