[RESULT][VOTE] Release Apache Sling Testing Clients 1.2.2
The vote has passed with: * 3 +1 binding votes * No other votes I'll go on with the release. On Wed, Jul 3, 2019 at 3:17 PM Andrei Dulvac wrote: > Hi all. > > I'd like to call a vote for releasing Apache Sling Testing Clients 1.2.2 > (last release a year ago) > > We solved 4 issues in this release > https://issues.apache.org/jira/browse/SLING-8227 > https://issues.apache.org/jira/browse/SLING-8160 > https://issues.apache.org/jira/browse/SLING-7724 > https://issues.apache.org/jira/browse/SLING-7680 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2104/ > > You can use this UNIX script to download the release and verify the > signatures: > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh > > Usage: > sh check_staged_release.sh 2104 /tmp/sling-staging > > 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. >
[GitHub] [sling-org-apache-sling-commons-html] JEBailey merged pull request #4: SLING-8566 support processing instruction and xml declaration in SAX processing
JEBailey merged pull request #4: SLING-8566 support processing instruction and xml declaration in SAX processing URL: https://github.com/apache/sling-org-apache-sling-commons-html/pull/4 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (SLING-8569) Detect & reports PackageTypes and nesting structures during conversion
[ https://issues.apache.org/jira/browse/SLING-8569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16881266#comment-16881266 ] Simone Tripodi commented on SLING-8569: --- [~dsuess] initial implementation on https://github.com/apache/sling-org-apache-sling-feature-cpconverter/tree/SLING-8569 feature branch > Detect & reports PackageTypes and nesting structures during conversion > -- > > Key: SLING-8569 > URL: https://issues.apache.org/jira/browse/SLING-8569 > Project: Sling > Issue Type: New Feature > Components: Content-Package to Feature Model Converter >Reporter: Dominik Süß >Assignee: Simone Tripodi >Priority: Major > > To be able to support legacy deployment structures that mixed (initial & > permission) content and application packages with application packages the > converter should generate an analysis of the originally passed packages in a > file reporting the following information: > * For each passed file report the nesting structures (including the paths > within the hosting packages) including multilevel nesting > * For each found package & subpackage detect & report the Package Type > (Application, Mixed, Content) > ** this should be detected from scratch as the optionally declared property > is not reliable (might be a false declaration) > ** detectionlogic should follow filevault semantics > (https://github.com/apache/jackrabbit-filevault/blob/6df76ba4a45316a84ec1cd10636296d191a82260/vault-core/src/main/java/org/apache/jackrabbit/vault/fs/io/AbstractExporter.java#L374-L399) > but consider the type of nested packages - the jackrabbit implementation > currently doesn't analyze subpackages but considers those as "content" as > they are defined in "/etc" > This report should allow to detect any package that (either directly or in > its nested containers) contains content (nothing in apps & libs) and indicate > the location within the original package (potentially also requiring > unpacking multiple nesting levels). > //[~simone.tripodi] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SLING-8569) Detect & reports PackageTypes and nesting structures during conversion
[ https://issues.apache.org/jira/browse/SLING-8569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi reassigned SLING-8569: - Assignee: Simone Tripodi > Detect & reports PackageTypes and nesting structures during conversion > -- > > Key: SLING-8569 > URL: https://issues.apache.org/jira/browse/SLING-8569 > Project: Sling > Issue Type: New Feature > Components: Content-Package to Feature Model Converter >Reporter: Dominik Süß >Assignee: Simone Tripodi >Priority: Major > > To be able to support legacy deployment structures that mixed (initial & > permission) content and application packages with application packages the > converter should generate an analysis of the originally passed packages in a > file reporting the following information: > * For each passed file report the nesting structures (including the paths > within the hosting packages) including multilevel nesting > * For each found package & subpackage detect & report the Package Type > (Application, Mixed, Content) > ** this should be detected from scratch as the optionally declared property > is not reliable (might be a false declaration) > ** detectionlogic should follow filevault semantics > (https://github.com/apache/jackrabbit-filevault/blob/6df76ba4a45316a84ec1cd10636296d191a82260/vault-core/src/main/java/org/apache/jackrabbit/vault/fs/io/AbstractExporter.java#L374-L399) > but consider the type of nested packages - the jackrabbit implementation > currently doesn't analyze subpackages but considers those as "content" as > they are defined in "/etc" > This report should allow to detect any package that (either directly or in > its nested containers) contains content (nothing in apps & libs) and indicate > the location within the original package (potentially also requiring > unpacking multiple nesting levels). > //[~simone.tripodi] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SLING-8570) Extract a generic Content Parser API from org.apache.sling.jcr.contentparser with pluggable implementations
Radu Cotescu created SLING-8570:
---
Summary: Extract a generic Content Parser API from
org.apache.sling.jcr.contentparser with pluggable implementations
Key: SLING-8570
URL: https://issues.apache.org/jira/browse/SLING-8570
Project: Sling
Issue Type: New Feature
Reporter: Radu Cotescu
Assignee: Radu Cotescu
Fix For: Content Parser API 1.0.0
The {{org.apache.sling.jcr.contentparser}} bundle provides the API and three
parser implementations supporting JSON, XML and Vault XML structures for
generating Sling resource trees. The goal of this issue is to modularise
{{org.apache.sling.jcr.contentparser}}, by extracting 4 bundles:
# org.apache.sling.contentparser.api - API only, no JCR / Jackrabbit
dependencies
# org.apache.sling.contentparser.json - JSON parser implementation
# org.apache.sling.contentparser.xml - XML parser implementation
# org.apache.sling.contentparser.xml.jcr - JackRabbit FileVault parser
implementation
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SLING-8569) Detect & reports PackageTypes and nesting structures during conversion
Dominik Süß created SLING-8569: -- Summary: Detect & reports PackageTypes and nesting structures during conversion Key: SLING-8569 URL: https://issues.apache.org/jira/browse/SLING-8569 Project: Sling Issue Type: New Feature Components: Content-Package to Feature Model Converter Reporter: Dominik Süß To be able to support legacy deployment structures that mixed (initial & permission) content and application packages with application packages the converter should generate an analysis of the originally passed packages in a file reporting the following information: * For each passed file report the nesting structures (including the paths within the hosting packages) including multilevel nesting * For each found package & subpackage detect & report the Package Type (Application, Mixed, Content) ** this should be detected from scratch as the optionally declared property is not reliable (might be a false declaration) ** detectionlogic should follow filevault semantics (https://github.com/apache/jackrabbit-filevault/blob/6df76ba4a45316a84ec1cd10636296d191a82260/vault-core/src/main/java/org/apache/jackrabbit/vault/fs/io/AbstractExporter.java#L374-L399) but consider the type of nested packages - the jackrabbit implementation currently doesn't analyze subpackages but considers those as "content" as they are defined in "/etc" This report should allow to detect any package that (either directly or in its nested containers) contains content (nothing in apps & libs) and indicate the location within the original package (potentially also requiring unpacking multiple nesting levels). //[~simone.tripodi] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SLING-8568) Allow the API Regions runtime to be disabled using dynamic configuration
[ https://issues.apache.org/jira/browse/SLING-8568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert updated SLING-8568: Summary: Allow the API Regions runtime to be disabled using dynamic configuration (was: Allow the API Regions runtime to be disabled at runtime) > Allow the API Regions runtime to be disabled using dynamic configuration > > > Key: SLING-8568 > URL: https://issues.apache.org/jira/browse/SLING-8568 > Project: Sling > Issue Type: Improvement > Components: Feature Model >Affects Versions: Feature Model API Regions Runtime Fragment 1.0.0 >Reporter: David Bosschaert >Assignee: David Bosschaert >Priority: Major > Fix For: Feature Model API Regions Runtime Fragment 1.0.2 > > > The API Regions component is currently enabled via the framework property. > This allows the framement to be active in the framework as early as possible, > since framework properties are specified at launch time. > However, framework properties are not dynamic. In some cases it is desirable > to disable the API Regions component at runtime, for example during > troubleshooting sessions. > We should allow the API Regions runtime fragment to be configured at runtime > so that it can be disabled if needed... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SLING-8568) Allow the API Regions runtime to be disabled at runtime
David Bosschaert created SLING-8568: --- Summary: Allow the API Regions runtime to be disabled at runtime Key: SLING-8568 URL: https://issues.apache.org/jira/browse/SLING-8568 Project: Sling Issue Type: Improvement Components: Feature Model Affects Versions: Feature Model API Regions Runtime Fragment 1.0.0 Reporter: David Bosschaert Assignee: David Bosschaert Fix For: Feature Model API Regions Runtime Fragment 1.0.2 The API Regions component is currently enabled via the framework property. This allows the framement to be active in the framework as early as possible, since framework properties are specified at launch time. However, framework properties are not dynamic. In some cases it is desirable to disable the API Regions component at runtime, for example during troubleshooting sessions. We should allow the API Regions runtime fragment to be configured at runtime so that it can be disabled if needed... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SLING-8567) Support start levels declared via JCR path in input packages to cp2sf
[ https://issues.apache.org/jira/browse/SLING-8567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16881091#comment-16881091 ] Georg Henzler commented on SLING-8567: -- Fixed in [424e121130b|https://github.com/apache/sling-org-apache-sling-feature-cpconverter/commit/424e121130b75f296a2b327b01e4796468c35602] > Support start levels declared via JCR path in input packages to cp2sf > - > > Key: SLING-8567 > URL: https://issues.apache.org/jira/browse/SLING-8567 > Project: Sling > Issue Type: Improvement > Components: Content-Package to Feature Model Converter >Reporter: Georg Henzler >Assignee: Georg Henzler >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > The JCR Installer provider supports start levels [1], hence the > Content-Package to Feature Model Converter should also support this feature. > [1] > https://sling.apache.org/documentation/bundles/jcr-installer-provider.html#start-level-support > - this was introduced with SLING-2011 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SLING-8567) Support start levels declared via JCR path in input packages to cp2sf
[ https://issues.apache.org/jira/browse/SLING-8567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Georg Henzler resolved SLING-8567. -- Resolution: Fixed > Support start levels declared via JCR path in input packages to cp2sf > - > > Key: SLING-8567 > URL: https://issues.apache.org/jira/browse/SLING-8567 > Project: Sling > Issue Type: Improvement > Components: Content-Package to Feature Model Converter >Reporter: Georg Henzler >Assignee: Georg Henzler >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > The JCR Installer provider supports start levels [1], hence the > Content-Package to Feature Model Converter should also support this feature. > [1] > https://sling.apache.org/documentation/bundles/jcr-installer-provider.html#start-level-support > - this was introduced with SLING-2011 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [sling-org-apache-sling-feature-cpconverter] ghenzler merged pull request #9: SLING-8567 respect start levels from JCR path and translate to feature
ghenzler merged pull request #9: SLING-8567 respect start levels from JCR path and translate to feature URL: https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/9 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [sling-org-apache-sling-feature-cpconverter] ghenzler opened a new pull request #9: SLING-8567 respect start levels from JCR path and translate to feature
ghenzler opened a new pull request #9: SLING-8567 respect start levels from JCR path and translate to feature URL: https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/9 model start-order if present This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
