[jira] [Resolved] (SLING-6241) Enable Pack200 compression for Sling IDE

[ https://issues.apache.org/jira/browse/SLING-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-6241. Resolution: Won't Fix > Enable Pack200 compression for Sling IDE >

[jira] [Commented] (SLING-6241) Enable Pack200 compression for Sling IDE

[ https://issues.apache.org/jira/browse/SLING-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992891#comment-16992891 ] Konrad Windszus commented on SLING-6241: Pack200 is now deprecated: https://openj

Re: Issue with Eclipse Tooling with AEM Cloudready

Maybe this is related to Sling IDE not detecting the filter roots correctly (e.g. caused by https://issues.apache.org/jira/browse/SLING-6344 ) and therefore trying to sync everything. Actually, since Sling IDE 2.0 (https://issues.apache.org/jira/

Re: Issue with Eclipse Tooling with AEM Cloudready

Fair enough. I don’t think this is an AEM issue but I will double check with a Sling project first. - Andy > On Dec 10, 2019, at 12:38 AM, Bertrand Delacretaz > wrote: > > Hi, > > On Mon, Dec 9, 2019 at 7:08 PM Andreas Schaefer > wrote: >> ...I had a look into Eclipse AEM Tooling with AEM C

Release of CP Convert

Hi Simone asked a while ago if anyone objected to release the CP Convert module but then nothing has happened since. As my Maven Plugin (Sling Feature Converter Maven Plugin) depends on it and I have a project that uses it I would love to have it released to avoid having to create local Maven r

Re: [VOTE] Apache Sling OSGi Feature Maven Plugin 1.1.12, Apache Sling Feature Analyser 1.2.2

+1 (non-binding) - Andy > On Dec 10, 2019, at 4:33 AM, Robert Munteanu wrote: > > Hi, > > We solved 13 issues in these releases: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20SLING%20AND%20fixVersion%20%3D%20%22OSGi%20Feature%20Maven%20Plugin%201.1.12%22 > https://issues.apache.

[jira] [Updated] (SLING-8864) Report authentication errors immediately without looking at the response's body

[ https://issues.apache.org/jira/browse/SLING-8864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-8864: Description: When the JIRA password is not passed correctly, the 401 errors should be reported in

[jira] [Updated] (SLING-8864) Report authentication errors immediately without looking at the response's body

[ https://issues.apache.org/jira/browse/SLING-8864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-8864: Summary: Report authentication errors immediately without looking at the response's body (was: Cre

[jira] [Commented] (SLING-8864) Creating a new JIRA version fails

[ https://issues.apache.org/jira/browse/SLING-8864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992728#comment-16992728 ] Radu Cotescu commented on SLING-8864: - There's no test case we need to add. I think w

Re: [VOTE] Release Apache Sling Scripting HTL Compiler 1.2.4-1.4.0, Apache Sling HTL Maven Plugin 1.3.4-1.4.0

+1 On Tue, Dec 10, 2019 at 9:31 AM Robert Munteanu wrote: > On Fri, 2019-12-06 at 20:11 +, Radu Cotescu wrote: > > Please vote to approve this release: > > +1 > Robert >

[jira] [Assigned] (SLING-8864) Creating a new JIRA version fails

[ https://issues.apache.org/jira/browse/SLING-8864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu reassigned SLING-8864: --- Assignee: Radu Cotescu (was: Robert Munteanu) > Creating a new JIRA version fails > ---

Re: [VOTE] Release Apache Sling Scripting JavaScript 3.1.2

+1 Le mar. 10 déc. 2019 à 15:31, Robert Munteanu a écrit : > On Fri, 2019-12-06 at 13:53 +, Radu Cotescu wrote: > > Please vote to approve this release: > > +1 > Robert >

Re: [VOTE] Apache Sling OSGi Feature Maven Plugin 1.1.12, Apache Sling Feature Analyser 1.2.2

+1 > On 10 Dec 2019, at 13:33, Robert Munteanu wrote: > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... >

Re: [VOTE] Apache Sling OSGi Feature Maven Plugin 1.1.12, Apache Sling Feature Analyser 1.2.2

+1 Le mar. 10 déc. 2019 à 14:54, Carsten Ziegeler a écrit : > +1 > > Carsten > > Am 10.12.2019 um 13:33 schrieb Robert Munteanu: > > Hi, > > > > We solved 13 issues in these releases: > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20SLING%20AND%20fixVersion%20%3D%20%22OSGi%20Feat

Re: [VOTE] Release Apache Sling Scripting HTL Compiler 1.2.4-1.4.0, Apache Sling HTL Maven Plugin 1.3.4-1.4.0

On Fri, 2019-12-06 at 20:11 +, Radu Cotescu wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part

Re: [VOTE] Release Apache Sling Scripting JavaScript 3.1.2

On Fri, 2019-12-06 at 13:53 +, Radu Cotescu wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part

Re: [VOTE] Apache Sling OSGi Feature Maven Plugin 1.1.12, Apache Sling Feature Analyser 1.2.2

+1 Carsten Am 10.12.2019 um 13:33 schrieb Robert Munteanu: Hi, We solved 13 issues in these releases: https://issues.apache.org/jira/issues/?jql=project%20%3D%20SLING%20AND%20fixVersion%20%3D%20%22OSGi%20Feature%20Maven%20Plugin%201.1.12%22 https://issues.apache.org/jira/issues/?jql=project%20

[Jenkins] Sling » sling-org-apache-sling-launchpad-testing » master #445 is BROKEN

Please see https://builds.apache.org/job/Sling/job/sling-org-apache-sling-launchpad-testing/job/master/445/ for details. No further emails will be sent until the status of the build is changed. Build log follows below: [...truncated 3274 lines...] at java.lang.reflect.Method.invoke(Meth

[Jenkins] Sling » sling-org-apache-sling-launchpad-testing » master #443 is FIXED

Please see https://builds.apache.org/job/Sling/job/sling-org-apache-sling-launchpad-testing/job/master/443/ for details. No further emails will be sent until the status of the build is changed.

Re: [VOTE] Apache Sling OSGi Feature Maven Plugin 1.1.12, Apache Sling Feature Analyser 1.2.2

Correction: Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2170 sh check_staged_release.sh 2170 /tmp/sling-staging Thanks, Robert

[VOTE] Apache Sling OSGi Feature Maven Plugin 1.1.12, Apache Sling Feature Analyser 1.2.2

Hi, We solved 13 issues in these releases: https://issues.apache.org/jira/issues/?jql=project%20%3D%20SLING%20AND%20fixVersion%20%3D%20%22OSGi%20Feature%20Maven%20Plugin%201.1.12%22 https://issues.apache.org/jira/issues/?jql=project%20%3D%20SLING%20AND%20fixVersion%20%3D%20%22Feature%20Model%20Ana

[jira] [Updated] (SLING-8875) Create new Goal to create a FM Descriptor from a Maven Module

[ https://issues.apache.org/jira/browse/SLING-8875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-8875: --- Fix Version/s: (was: OSGi Feature Maven Plugin 1.1.12) OSGi Feature Mav

[jira] [Resolved] (SLING-8905) Always use scm-location if defined

[ https://issues.apache.org/jira/browse/SLING-8905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-8905. Resolution: Fixed > Always use scm-location if defined > --

[GitHub] [sling-slingfeature-maven-plugin] rombert merged pull request #48: SLING-8905 - Always use scm-location if defined

rombert merged pull request #48: SLING-8905 - Always use scm-location if defined URL: https://github.com/apache/sling-slingfeature-maven-plugin/pull/48 This is an automated message from the Apache Git Service. To respond to t

[GitHub] [sling-slingfeature-maven-plugin] rombert commented on issue #48: SLING-8905 - Always use scm-location if defined

rombert commented on issue #48: SLING-8905 - Always use scm-location if defined URL: https://github.com/apache/sling-slingfeature-maven-plugin/pull/48#issuecomment-564007735 Code coverage is not gathered, but code is tested using ITs. ---

[GitHub] [sling-slingfeature-maven-plugin] rombert opened a new pull request #48: SLING-8905 - Always use scm-location if defined

rombert opened a new pull request #48: SLING-8905 - Always use scm-location if defined URL: https://github.com/apache/sling-slingfeature-maven-plugin/pull/48 This is an automated message from the Apache Git Service. To respo

[jira] [Created] (SLING-8908) DistributionSubscriber does not keep track of skipped packages as processed

Timothee Maret created SLING-8908: - Summary: DistributionSubscriber does not keep track of skipped packages as processed Key: SLING-8908 URL: https://issues.apache.org/jira/browse/SLING-8908 Project:

[jira] [Created] (SLING-8907) Journal distribution agents with empty names are invalid

Timothee Maret created SLING-8907: - Summary: Journal distribution agents with empty names are invalid Key: SLING-8907 URL: https://issues.apache.org/jira/browse/SLING-8907 Project: Sling Iss

[jira] [Assigned] (SLING-8905) Always use scm-location if defined

[ https://issues.apache.org/jira/browse/SLING-8905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-8905: -- Assignee: Robert Munteanu > Always use scm-location if defined > -

[jira] [Resolved] (SLING-8906) Include filters are too wide and can pull in unwanted resources

[ https://issues.apache.org/jira/browse/SLING-8906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-8906. Resolution: Fixed > Include filters are too wide and can pull in unwanted resources > -

[GitHub] [sling-slingfeature-maven-plugin] rombert merged pull request #47: SLING-8906 - Include filters are too wide and can pull in unwanted resources

rombert merged pull request #47: SLING-8906 - Include filters are too wide and can pull in unwanted resources URL: https://github.com/apache/sling-slingfeature-maven-plugin/pull/47 This is an automated message from the Apach

[GitHub] [sling-slingfeature-maven-plugin] rombert opened a new pull request #47: SLING-8906 - Include filters are too wide and can pull in unwanted resources

rombert opened a new pull request #47: SLING-8906 - Include filters are too wide and can pull in unwanted resources URL: https://github.com/apache/sling-slingfeature-maven-plugin/pull/47 Use strict filtering (one parent) when including resources from deflated bins and sources, and relaxe

Re: Issue with Eclipse Tooling with AEM Cloudready

Hi, On Mon, Dec 9, 2019 at 7:08 PM Andreas Schaefer wrote: > ...I had a look into Eclipse AEM Tooling with AEM Cloud Ready (version > 16979)... This is not an AEM list, so you'll need to provide more technical evidence as to what's failing ;-) -Bertrand

[jira] [Updated] (SLING-8906) Include filters are too wide and can pull in unwanted resources

[ https://issues.apache.org/jira/browse/SLING-8906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-8906: --- Description: Include filters generated from exported API packages are generated with prefix w

[jira] [Updated] (SLING-8906) Include filters are too wide and can pull in unwanted resources

[ https://issues.apache.org/jira/browse/SLING-8906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-8906: --- Description: Include filters generated from exported API packages are generated with prefix w