Re: [VOTE] Release Apache Sling Starter 10 + associated testing projects and archetypes

[Daniel Klco]

Hi Robert,

I don't see Apache Sling Starter 10 included in the release repository. Am
I missing something?

https://repository.apache.org/content/repositories/orgapachesling-1857/org/apache/sling/

Thanks,
Dan

On Fri, Jan 19, 2018 at 11:42 AM, Robert Munteanu 
wrote:

> Hi,
>
> Time to release Sling 10. This year I've added all the testing
> projects, to retain what was working at the time of the release and the
> archetypes, to allow users to start using the new features immediately
> rather than releasing them separately.
>
> This has lead to a rather large release though.
>
> The following artifacts, with the associated changelogs, are included
> in this release
>
> - Apache Sling Starter 10
> https://issues.apache.org/jira/projects/SLING/versions/12340941 (13
> issues)
>
> - Apache Sling Launchpad Testing 10
> https://issues.apache.org/jira/projects/SLING/versions/12317575 (33
> issues)
>
> - Apache Sling Launchpad Testing WAR 10
> https://issues.apache.org/jira/projects/SLING/versions/12342164 (0 issues)
>
> - Apache Sling Launchpad Integration Tests 1.0.6
> https://issues.apache.org/jira/projects/SLING/versions/12341715 (0 issues)
>
> - Apache Sling Launchpad Test Bundles 0.0.4 (no changelog)
> - Apache Sling Launchpad Testing Fragment Bundle 2.0.14 (no changelog)
>
> - Apache Sling Launchpad Testing Services 2.0.14
> https://issues.apache.org/jira/projects/SLING/versions/12338823 (2 issues)
>
> - Apache Sling Launchpad Testing Services WAR 2.0.14 (no changelog)
>
> - Apache Sling Archetype Parent 5
> https://issues.apache.org/jira/projects/SLING/versions/12333898 (2 issues)
>
> - Apache Sling Bundle Archetype 1.0.6
> https://issues.apache.org/jira/browse/SLING/fixforversion/12333900 (2
> issues)
>
> - Apache Sling JCRInstall Bundle Archetype 1.0.6
> https://issues.apache.org/jira/browse/SLING/fixforversion/12333901 (2
> issues)
>
> - Apache Sling Initial Content Archetype 1.0.6
> https://issues.apache.org/jira/browse/SLING/fixforversion/12333902 (2
> issues)
>
> - Apache Sling Slingstart Archetype 1.0.6
> https://issues.apache.org/jira/browse/SLING/fixforversion/12340954 (2
> issues)
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1857
>
> You can use this UNIX script to download the release and verify the
> signatures:
> https://gitbox.apache.org/repos/asf?p=sling-tooling-
> release.git;a=blob;f=check_staged_release.sh;hb=HEAD
>
> Usage:
> sh check_staged_release.sh 1857 /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, but I'd be more than
> happy to allow extensions if anyone needs more time to validate the
> release.
>
> Thanks,
>
> Robert
>

Re: Please welcome Andreas Schaefer, Sling committer

[Andreas Schaefer]

Hi

I honored to join the list of Sling committer.

I started Java back in the 1.0 days and joined JBoss in 2000 after moving
to the sunny SoCal. Around 2012 I started working with CQ and Sling and
for most part that is what I do beside IntelliJ and InDesign plugin development
or iOS Apps.

In my free time I like to play my electric guitars, clarinet and drive my 4 boys
around. Then from time to time I ride my HD V-Rod Muscle and go sky
diving.

Looking forward to work with you guy

Cheers - Andy Schaefer



> On Jan 19, 2018, at 1:34 PM, Robert Munteanu  wrote:
> 
> Hi Sling community,
> 
> Based on his ongoing and valuable contributions to the project, the
> Sling PMC has elected Andreas Schaefer as a Sling committer, and he has
> accepted the invitation.
> 
> Please join me in welcoming him!
> 
> Andreas - if you want to honor the old tradition of new committers
> briefly introducing themselves to the list, feel free. And maybe take
> the time to verify your Git permissions and update http://sling.apache.
> org/project-information/project-team.html :-)
> 
> Best,
> 
> Robert

Re: [VOTE] Release Apache Sling IDE Tooling version 1.2.0

[Daniel Klco]

+1

On Fri, Jan 19, 2018 at 9:37 AM, Karl Pauls  wrote:

> +1
>
> regards,
>
> Karl
>
> On Fri, Jan 19, 2018 at 3:10 PM, Robert Munteanu 
> wrote:
> > On Fri, 2018-01-19 at 14:18 +0100, Konrad Windszus wrote:
> >> Finally I got the right file. Seems that some intermediate cache
> >> (maybe some CDN?) still delivered the old version yesterday.
> >> Now looks good although https://issues.apache.org/jira/browse/SLING-7
> >> 403  is still not
> >> fixed.
> >> But since this is only a minor issue I am gonna vote for release.
> >
> > Thanks! I would rather only respin if necessary since code signing
> > costs the ASF money, and I already signed twice for this release :-)
> >
> > Robert
>
>
>
> --
> Karl Pauls
> karlpa...@gmail.com
>

[jira] [Created] (SLING-7415) [ServiceUser WebConsole] - Remove Unnecessary Exposed Package

[Dan Klco (JIRA)]

Dan Klco created SLING-7415:
---

 Summary: [ServiceUser WebConsole] - Remove Unnecessary Exposed 
Package
 Key: SLING-7415
 URL: https://issues.apache.org/jira/browse/SLING-7415
 Project: Sling
  Issue Type: Bug
Reporter: Dan Klco
 Fix For: Service User WebConsole 1.0.2


Currently the ServiceUser WebConsole exposes the package 
org.apache.sling.serviceuser.webconsole which should be removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (SLING-7368) Add Service User OSGi Console

[Dan Klco (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dan Klco closed SLING-7368.
---

Closed with the release of ServiceUser Mapper 1.4.0 and ServiceUser WebConsole 
1.0.0

> Add Service User OSGi Console
> -
>
> Key: SLING-7368
> URL: https://issues.apache.org/jira/browse/SLING-7368
> Project: Sling
>  Issue Type: New Feature
>Affects Versions: Service User Mapper 1.3.6
>Reporter: Dan Klco
>Assignee: Dan Klco
>Priority: Major
>  Labels: Sling-10-ReleaseNotes, security, usability
> Fix For: Service User Mapper 1.4.0
>
> Attachments: Screen Shot 2018-01-08 at 5.09.56 PM.png, Screen Shot 
> 2018-01-08 at 5.10.07 PM.png
>
>
> Currently, the process for creating Service Users is fairly painful for 
> developers. It requires creating the user (and changing the UUID if you want 
> to move the user to something besides the autogenerated path), creating an 
> OSGi config, then adding that user into the correct permissions and finally 
> getting it all out of the repository into your project.
> To make this process simpler, I think we should add a console allowing users 
> to:
> * Create Service Users
> * Assign Permissions
> * Update Service Users
> * View a Service User's information
> I've attached some images of a console I created for this purpose. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

RE: Please welcome Andreas Schaefer, Sling committer

[Stefan Seifert]

welcome, andreas!

stefan

>-Original Message-
>From: Robert Munteanu [mailto:romb...@apache.org]
>Sent: Friday, January 19, 2018 10:35 PM
>To: dev@sling.apache.org
>Subject: Please welcome Andreas Schaefer, Sling committer
>
>Hi Sling community,
>
>Based on his ongoing and valuable contributions to the project, the
>Sling PMC has elected Andreas Schaefer as a Sling committer, and he has
>accepted the invitation.
>
>Please join me in welcoming him!
>
>Andreas - if you want to honor the old tradition of new committers
>briefly introducing themselves to the list, feel free. And maybe take
>the time to verify your Git permissions and update http://sling.apache.
>org/project-information/project-team.html :-)
>
>Best,
>
>Robert

Please welcome Andreas Schaefer, Sling committer

[Robert Munteanu]

Hi Sling community,

Based on his ongoing and valuable contributions to the project, the
Sling PMC has elected Andreas Schaefer as a Sling committer, and he has
accepted the invitation.

Please join me in welcoming him!

Andreas - if you want to honor the old tradition of new committers
briefly introducing themselves to the list, feel free. And maybe take
the time to verify your Git permissions and update http://sling.apache.
org/project-information/project-team.html :-)

Best,

Robert

[github] Intent to create new repo - sling-org-apache-sling-starter-docker

[Robert Munteanu]

Hi,

I missed migrating the Dockerfile from /launchpad/docker [1] and would
like to create a new repo for this. It will also help with docker image
builds whenever we tag a release.

My proposal is sling-org-apache-sling-starter-docker . Unless someone
objects I will create this on Tuesday.

Thanks,

Robert


[1]: https://svn.apache.org/repos/asf/sling/trunk/launchpad/docker/

Re: [VOTE] Release Apache Sling Starter 10 + associated testing projects and archetypes (take 2)

[Robert Munteanu]

On Fri, 2018-01-19 at 19:24 +0200, Robert Munteanu wrote:
> Please vote to approve this release:

+1

Robert

signature.asc
Description: This is a digitally signed message part

[jira] [Commented] (SLING-7407) A thread pool with min size 1 uses only 1 thread for processing

[Stefan Egli (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332596#comment-16332596
 ] 

Stefan Egli commented on SLING-7407:


note that unfortunately the commit was done with my wrong user (@adobe.com 
instead of @apache.org) - but I hope this is fine

> A thread pool with min size 1 uses only 1 thread for processing
> ---
>
> Key: SLING-7407
> URL: https://issues.apache.org/jira/browse/SLING-7407
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Reporter: Chetan Mehrotra
>Assignee: Stefan Egli
>Priority: Major
> Fix For: Commons Threads 3.2.12
>
>
> If a thread pool is configured like below
> {noformat}
>  org.apache.sling.commons.threads.impl.DefaultThreadPool.factory-oak
> name="oak"
> minPoolSize=I"1"
> maxPoolSize=I"5"
> {noformat}
> Then only 1 thread would be used even if multiple jobs are assigned to the 
> pool. This happens because of strange behaviour of Java 
> [ThreadPoolExecutor|https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/ThreadPoolExecutor.html]
> bq. If there are more than corePoolSize but less than maximumPoolSize threads 
> running, a new thread will be created only *if the queue is full*
> With unbounded queue used this lead to current behaviour. As a fix Sling 
> Thread Pool should adapt such a config 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Release Apache Sling Starter 10 + associated testing projects and archetypes (take 2)

[Carsten Ziegeler]

+1


Robert Munteanu wrote
> Hi,
> 
> Update note: I've chosen to respin the Starter release with the same
> version, for 2 reasons:
> 
> - it would generate confusion to skip a release
> - chances of anyone depending on the staged slingstart are slim
> 
> If anyone thinks otherwise, I'll restart the release vote as Sling 11.
> 
> 
> Time to release Sling 10. This year I've added all the testing
> projects, to retain what was working at the time of the release and the
> archetypes, to allow users to start using the new features immediately
> rather than releasing them separately.
> 
> This has lead to a rather large release though.
> 
> The following artifacts, with the associated changelogs, are included
> in this release
> 
> - Apache Sling Starter 10
> https://issues.apache.org/jira/projects/SLING/versions/12340941 (13 issues)
> 
> - Apache Sling Launchpad Testing 10
> https://issues.apache.org/jira/projects/SLING/versions/12317575 (33 issues)
> 
> - Apache Sling Launchpad Testing WAR 10
> https://issues.apache.org/jira/projects/SLING/versions/12342164 (0 issues)
> 
> - Apache Sling Launchpad Integration Tests 1.0.6
> https://issues.apache.org/jira/projects/SLING/versions/12341715 (0 issues)
> 
> - Apache Sling Launchpad Test Bundles 0.0.4 (no changelog)
> - Apache Sling Launchpad Testing Fragment Bundle 2.0.14 (no changelog)
> 
> - Apache Sling Launchpad Testing Services 2.0.14
> https://issues.apache.org/jira/projects/SLING/versions/12338823 (2 issues)
> 
> - Apache Sling Launchpad Testing Services WAR 2.0.14 (no changelog)
> 
> - Apache Sling Archetype Parent 5
> https://issues.apache.org/jira/projects/SLING/versions/12333898 (2 issues)
> 
> - Apache Sling Bundle Archetype 1.0.6
> https://issues.apache.org/jira/browse/SLING/fixforversion/12333900 (2 issues)
> 
> - Apache Sling JCRInstall Bundle Archetype 1.0.6
> https://issues.apache.org/jira/browse/SLING/fixforversion/12333901 (2 issues)
> 
> - Apache Sling Initial Content Archetype 1.0.6
> https://issues.apache.org/jira/browse/SLING/fixforversion/12333902 (2 issues)
> 
> - Apache Sling Slingstart Archetype 1.0.6
> https://issues.apache.org/jira/browse/SLING/fixforversion/12340954 (2 issues)
> 
> Staging repositories:
> https://repository.apache.org/content/repositories/orgapachesling-1857
> https://repository.apache.org/content/repositories/orgapachesling-1858
> 
> You can use this UNIX script to download the release and verify the
> signatures:
> https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD
> 
> Usage:
> sh check_staged_release.sh 1857 /tmp/sling-stagingsh check_staged_release.sh 
> 1858 /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, but I'd be more than
> happy to allow extensions if anyone needs more time to validate the
> release.
> 
> Thanks,
> 
> Robert
> 
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

[VOTE] Release Apache Sling Starter 10 + associated testing projects and archetypes (take 2)

[Robert Munteanu]

Hi,

Update note: I've chosen to respin the Starter release with the same
version, for 2 reasons:

- it would generate confusion to skip a release
- chances of anyone depending on the staged slingstart are slim

If anyone thinks otherwise, I'll restart the release vote as Sling 11.


Time to release Sling 10. This year I've added all the testing
projects, to retain what was working at the time of the release and the
archetypes, to allow users to start using the new features immediately
rather than releasing them separately.

This has lead to a rather large release though.

The following artifacts, with the associated changelogs, are included
in this release

- Apache Sling Starter 10
https://issues.apache.org/jira/projects/SLING/versions/12340941 (13 issues)

- Apache Sling Launchpad Testing 10
https://issues.apache.org/jira/projects/SLING/versions/12317575 (33 issues)

- Apache Sling Launchpad Testing WAR 10
https://issues.apache.org/jira/projects/SLING/versions/12342164 (0 issues)

- Apache Sling Launchpad Integration Tests 1.0.6
https://issues.apache.org/jira/projects/SLING/versions/12341715 (0 issues)

- Apache Sling Launchpad Test Bundles 0.0.4 (no changelog)
- Apache Sling Launchpad Testing Fragment Bundle 2.0.14 (no changelog)

- Apache Sling Launchpad Testing Services 2.0.14
https://issues.apache.org/jira/projects/SLING/versions/12338823 (2 issues)

- Apache Sling Launchpad Testing Services WAR 2.0.14 (no changelog)

- Apache Sling Archetype Parent 5
https://issues.apache.org/jira/projects/SLING/versions/12333898 (2 issues)

- Apache Sling Bundle Archetype 1.0.6
https://issues.apache.org/jira/browse/SLING/fixforversion/12333900 (2 issues)

- Apache Sling JCRInstall Bundle Archetype 1.0.6
https://issues.apache.org/jira/browse/SLING/fixforversion/12333901 (2 issues)

- Apache Sling Initial Content Archetype 1.0.6
https://issues.apache.org/jira/browse/SLING/fixforversion/12333902 (2 issues)

- Apache Sling Slingstart Archetype 1.0.6
https://issues.apache.org/jira/browse/SLING/fixforversion/12340954 (2 issues)

Staging repositories:
https://repository.apache.org/content/repositories/orgapachesling-1857
https://repository.apache.org/content/repositories/orgapachesling-1858

You can use this UNIX script to download the release and verify the
signatures:
https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD

Usage:
sh check_staged_release.sh 1857 /tmp/sling-stagingsh check_staged_release.sh 
1858 /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, but I'd be more than
happy to allow extensions if anyone needs more time to validate the
release.

Thanks,

Robert

[CANCELLED] [VOTE][ Release Apache Sling Starter 10 + associated testing projects and archetypes

[Robert Munteanu]

Hi,

I misssed a dependency upgrade for the starter project, which is
essential for Java 10 support. I'll drop and re-spin only the starter
project.

Thanks,

Robert

On Fri, 2018-01-19 at 18:42 +0200, Robert Munteanu wrote:
> Hi,
> 
> Time to release Sling 10. This year I've added all the testing
> projects, to retain what was working at the time of the release and
> the
> archetypes, to allow users to start using the new features
> immediately
> rather than releasing them separately.
> 
> This has lead to a rather large release though.
> 
> The following artifacts, with the associated changelogs, are included
> in this release
> 
> - Apache Sling Starter 10
> https://issues.apache.org/jira/projects/SLING/versions/12340941 (13
> issues)
> 
> - Apache Sling Launchpad Testing 10
> https://issues.apache.org/jira/projects/SLING/versions/12317575 (33
> issues)
> 
> - Apache Sling Launchpad Testing WAR 10
> https://issues.apache.org/jira/projects/SLING/versions/12342164 (0
> issues)
> 
> - Apache Sling Launchpad Integration Tests 1.0.6
> https://issues.apache.org/jira/projects/SLING/versions/12341715 (0
> issues)
> 
> - Apache Sling Launchpad Test Bundles 0.0.4 (no changelog)
> - Apache Sling Launchpad Testing Fragment Bundle 2.0.14 (no
> changelog)
> 
> - Apache Sling Launchpad Testing Services 2.0.14
> https://issues.apache.org/jira/projects/SLING/versions/12338823 (2
> issues)
> 
> - Apache Sling Launchpad Testing Services WAR 2.0.14 (no changelog)
> 
> - Apache Sling Archetype Parent 5
> https://issues.apache.org/jira/projects/SLING/versions/12333898 (2
> issues)
> 
> - Apache Sling Bundle Archetype 1.0.6
> https://issues.apache.org/jira/browse/SLING/fixforversion/12333900 (2
> issues)
> 
> - Apache Sling JCRInstall Bundle Archetype 1.0.6
> https://issues.apache.org/jira/browse/SLING/fixforversion/12333901 (2
> issues)
> 
> - Apache Sling Initial Content Archetype 1.0.6
> https://issues.apache.org/jira/browse/SLING/fixforversion/12333902 (2
> issues)
> 
> - Apache Sling Slingstart Archetype 1.0.6
> https://issues.apache.org/jira/browse/SLING/fixforversion/12340954 (2
> issues)
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-185
> 7
> 
> You can use this UNIX script to download the release and verify the
> signatures:
> https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blo
> b;f=check_staged_release.sh;hb=HEAD
> 
> Usage:
> sh check_staged_release.sh 1857 /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, but I'd be more
> than
> happy to allow extensions if anyone needs more time to validate the
> release.
> 
> Thanks,
> 
> Robert

[VOTE] Release Apache Sling Starter 10 + associated testing projects and archetypes

[Robert Munteanu]

Hi,

Time to release Sling 10. This year I've added all the testing
projects, to retain what was working at the time of the release and the
archetypes, to allow users to start using the new features immediately
rather than releasing them separately.

This has lead to a rather large release though.

The following artifacts, with the associated changelogs, are included
in this release

- Apache Sling Starter 10
https://issues.apache.org/jira/projects/SLING/versions/12340941 (13 issues)

- Apache Sling Launchpad Testing 10
https://issues.apache.org/jira/projects/SLING/versions/12317575 (33 issues)

- Apache Sling Launchpad Testing WAR 10
https://issues.apache.org/jira/projects/SLING/versions/12342164 (0 issues)

- Apache Sling Launchpad Integration Tests 1.0.6
https://issues.apache.org/jira/projects/SLING/versions/12341715 (0 issues)

- Apache Sling Launchpad Test Bundles 0.0.4 (no changelog)
- Apache Sling Launchpad Testing Fragment Bundle 2.0.14 (no changelog)

- Apache Sling Launchpad Testing Services 2.0.14
https://issues.apache.org/jira/projects/SLING/versions/12338823 (2 issues)

- Apache Sling Launchpad Testing Services WAR 2.0.14 (no changelog)

- Apache Sling Archetype Parent 5
https://issues.apache.org/jira/projects/SLING/versions/12333898 (2 issues)

- Apache Sling Bundle Archetype 1.0.6
https://issues.apache.org/jira/browse/SLING/fixforversion/12333900 (2 issues)

- Apache Sling JCRInstall Bundle Archetype 1.0.6
https://issues.apache.org/jira/browse/SLING/fixforversion/12333901 (2 issues)

- Apache Sling Initial Content Archetype 1.0.6
https://issues.apache.org/jira/browse/SLING/fixforversion/12333902 (2 issues)

- Apache Sling Slingstart Archetype 1.0.6
https://issues.apache.org/jira/browse/SLING/fixforversion/12340954 (2 issues)

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1857

You can use this UNIX script to download the release and verify the signatures:
https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD

Usage:
sh check_staged_release.sh 1857 /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, but I'd be more than
happy to allow extensions if anyone needs more time to validate the
release.

Thanks,

Robert

[jira] [Updated] (SLING-7106) JaxbMarshallingTest fails with Java 9

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-7106:
---
Fix Version/s: (was: Launchpad Testing 9)
   Launchpad Testing 11

> JaxbMarshallingTest fails with Java 9
> -
>
> Key: SLING-7106
> URL: https://issues.apache.org/jira/browse/SLING-7106
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Reporter: Robert Munteanu
>Priority: Major
> Fix For: Launchpad Testing 11
>
>
> {noformat}Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 0.005 sec <<< FAILURE! - in 
> org.apache.sling.launchpad.webapp.integrationtest.jaxb.JaxbMarshallingTest
> testJaxbEntityIsMarshalled(org.apache.sling.launchpad.webapp.integrationtest.jaxb.JaxbMarshallingTest)
>   Time elapsed: 0.005 sec  <<< FAILURE!
> junit.framework.AssertionFailedError: Expected status 200 for 
> http://localhost:41000/bin/jaxb.xml (content= "-//IETF//DTD HTML 2.0//EN">
> 
> 
> 404 Resource at /bin/jaxb.xml not found: No resource 
> found
> 
> 
> Resource at /bin/jaxb.xml not found: No resource found 
> (404)
> The requested URL /bin/jaxb.xml resulted in an error in 
> org.apache.sling.servlets.resolver.internal.defaults.DefaultErrorHandlerServlet.
> Request Progress:
> 
>   0 TIMER_START{Request Processing}
>   1 COMMENT timer_end format is {elapsed microseconds,timer 
> name} optional message
>   4 LOG Method=GET, PathInfo=null
>   5 TIMER_START{handleSecurity}
>1423 TIMER_END{1416,handleSecurity} authenticator 
> org.apache.sling.auth.core.impl.SlingAuthenticator@4d8e3503 returns true
>2207 TIMER_START{ResourceResolution}
>2405 TIMER_END{197,ResourceResolution} URI=/bin/jaxb.xml resolves to 
> Resource=NonExistingResource, path=/bin/jaxb.xml
>2411 LOG Resource Path Info: SlingRequestPathInfo: 
> path=/bin/jaxb.xml, selectorString=null, 
> extension=xml, suffix=null
>2411 TIMER_START{ServletResolution}
>2413 TIMER_START{resolveServlet(/bin/jaxb.xml)}
>2708 TIMER_END{294,resolveServlet(/bin/jaxb.xml)} Using servlet 
> org.apache.sling.servlets.get.DefaultGetServlet
>2711 TIMER_END{299,ServletResolution} URI=/bin/jaxb.xml handled by 
> Servlet=org.apache.sling.servlets.get.DefaultGetServlet
>2713 LOG Applying Requestfilters
>2715 LOG Calling filter: org.apache.sling.i18n.impl.I18NFilter
>2717 LOG Calling filter: 
> org.apache.sling.launchpad.testservices.filters.SlingFilter
>2723 LOG Calling filter: 
> org.apache.sling.launchpad.testservices.filters.NoPropertyFilter
>2727 LOG Calling filter: 
> org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter
>2730 LOG Applying Componentfilters
>2733 TIMER_START{org.apache.sling.servlets.get.DefaultGetServlet#0}
>2782 TIMER_END{47,org.apache.sling.servlets.get.DefaultGetServlet#0}
>2814 LOG Filter timing: 
> filter=org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter, 
> inner=0, total=0, outer=0
>2816 LOG Filter timing: 
> filter=org.apache.sling.launchpad.testservices.filters.SlingFilterWithPattern,
>  inner=0, total=0, outer=0
>2817 LOG Filter timing: 
> filter=org.apache.sling.launchpad.testservices.filters.NoPropertyFilter, 
> inner=0, total=0, outer=0
>2819 LOG Filter timing: 
> filter=org.apache.sling.launchpad.testservices.filters.SlingFilter, inner=0, 
> total=0, outer=0
>2892 LOG Applying Error filters
>2894 LOG Calling filter: org.apache.sling.i18n.impl.I18NFilter
>2900 TIMER_START{handleError:status=404}
>3084 TIMER_END{182,handleError:status=404} Using handler 
> org.apache.sling.servlets.resolver.internal.defaults.DefaultErrorHandlerServlet
>3195 TIMER_END{3194,Request Processing} Dumping 
> SlingRequestProgressTracker Entries
> 
> 
> ApacheSling/2.6 (jetty/9.3.20.v20170531, Java HotSpot(TM) 64-Bit 
> Server VM 9, Linux 3.19.0-25-generic amd64)
> 
> 
> ) expected:<200> but was:<404>
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.Assert.assertEquals(Assert.java:234)
>   at junit.framework.TestCase.assertEquals(TestCase.java:401)
>   at 
> org.apache.sling.commons.testing.integration.HttpTestBase.getContent(HttpTestBase.java:457)
>   at 
> org.apache.sling.commons.testing.integration.HttpTestBase.getContent(HttpTestBase.java:432)
>   at 
> org.apache.sling.commons.testing.integration.HttpTestBase.getContent(HttpTestBase.java:424)
>   at 
> org.apache.sling.commons.testing.integration.HttpTestBase.getContent(HttpTestBase.java:419)
>   at 
> 

[jira] [Updated] (SLING-6950) Support Content-Package based development

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-6950:
---
Fix Version/s: (was: Starter 10)
   Starter 11

> Support Content-Package based development
> -
>
> Key: SLING-6950
> URL: https://issues.apache.org/jira/browse/SLING-6950
> Project: Sling
>  Issue Type: Bug
>  Components: General
>Reporter: Robert Munteanu
>Priority: Major
> Fix For: Starter 11
>
>
> Tracking task for supporting development based on Content Packages with Sling.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (SLING-7202) o.a.j.o.j.o.ObservationManagerImpl times out eventually in pax container init

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz resolved SLING-7202.
-
Resolution: Not A Bug

> o.a.j.o.j.o.ObservationManagerImpl times out eventually in pax container init
> -
>
> Key: SLING-7202
> URL: https://issues.apache.org/jira/browse/SLING-7202
> Project: Sling
>  Issue Type: Bug
>Reporter: Nicolas Peltier
>Assignee: Oliver Lietz
>Priority: Major
> Attachments: success-fail-logs.tar
>
>
> pipes IT intermittently fail. When they do, after having compared to when 
> they don't, look like the core cause is
> {Code}
> 2017-10-10 22:32:13,092 WARN [FelixStartLevel] 
> o.a.j.o.j.o.ObservationManagerImpl [ObservationManagerImpl.java : 457] Timed 
> out waiting for change processor to stop after 1000 milliseconds. Falling 
> back to asynchronous stop on ChangeProcessor [listenerId=10, 
> tracker=//*[1b]@org.apache.sling.jcr.resource.internal.JcrResourceListener,
>  contentSession=session-17, 
> eventCount=org.apache.jackrabbit.oak.stats.SimpleStats@4405759a, 
> eventDuration=org.apache.jackrabbit.oak.stats.SimpleStats@4aa43935, 
> commitRateLimiter=null, running=false] (listener details: 
> 'JcrResourceListener [BasicObserverConfiguration [includeExternal=true, 
> paths=PathSet [paths=[Path [path=/]]], excludedPaths=PathSet [paths=[Path 
> [path=/libs/sling/sightly/js], Path 
> [path=/apps/sling/servlet/default/SLING_av... (1907 chars cut), 
> propertyNamesHint=null, changeTypes=[ADDED, REMOVED, CHANGED], 
> listeners=[ResourceChangeListenerInfo [paths=PathSet [paths=[Path [path=/]]], 
> resourceChangeTypes=[ADDED, REMOVED, CHANGED], 
> providerChangeTypes=[PROVIDER_ADDED, PROVIDER_REMOVED], 
> propertyNamesHint=null, valid=true, external=true, 
> listener=org.apache.sling.servlets.resolver.internal.SlingServletResolver@3993ddcd],
>  ResourceChangeListenerInfo [paths=PathSet [paths=[Path [path=/]]], 
> resourceChangeTypes=[ADDED, REMOVED, CHANGED], 
> providerChangeTypes=[PROVIDER_ADDED, PROVIDER_REMOVED], 
> propertyNamesHint=null, valid=true, external=true, 
> listener=org.apache.sling.resourceresolver.impl.mapping.MapEntries@70b4e2df], 
> ResourceChangeListenerInfo [paths=PathSet [paths=[Path [path=/]]], 
> resourceChangeTypes=[ADDED, REMOVED, CHANGED], 
> providerChangeTypes=[PROVIDER_ADDED, PROVIDER_REMOVED], 
> propertyNamesHint=null, valid=true, external=true, 
> listener=org.apache.sling.i18n.impl.JcrResourceBundleProvider@60af913d')
> {Code}
> after which content loading does not work, resulting in test failing 
> cc [~olli]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-6953) Move Dockerfile to the launchpad/builder directory

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-6953:
---
Fix Version/s: (was: Starter 10)
   Starter 11

> Move Dockerfile to the launchpad/builder directory
> --
>
> Key: SLING-6953
> URL: https://issues.apache.org/jira/browse/SLING-6953
> Project: Sling
>  Issue Type: Improvement
>  Components: Launchpad
>Reporter: Robert Munteanu
>Priority: Major
> Fix For: Starter 11
>
>
> If we do that, the dockerfile will get tagged as part of the release and 
> we'll be able to participate in the dockerhub automatic builds and then 
> release our image as part of the apache org.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (SLING-7202) o.a.j.o.j.o.ObservationManagerImpl times out eventually in pax container init

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz closed SLING-7202.
---

> o.a.j.o.j.o.ObservationManagerImpl times out eventually in pax container init
> -
>
> Key: SLING-7202
> URL: https://issues.apache.org/jira/browse/SLING-7202
> Project: Sling
>  Issue Type: Bug
>Reporter: Nicolas Peltier
>Assignee: Oliver Lietz
>Priority: Major
> Attachments: success-fail-logs.tar
>
>
> pipes IT intermittently fail. When they do, after having compared to when 
> they don't, look like the core cause is
> {Code}
> 2017-10-10 22:32:13,092 WARN [FelixStartLevel] 
> o.a.j.o.j.o.ObservationManagerImpl [ObservationManagerImpl.java : 457] Timed 
> out waiting for change processor to stop after 1000 milliseconds. Falling 
> back to asynchronous stop on ChangeProcessor [listenerId=10, 
> tracker=//*[1b]@org.apache.sling.jcr.resource.internal.JcrResourceListener,
>  contentSession=session-17, 
> eventCount=org.apache.jackrabbit.oak.stats.SimpleStats@4405759a, 
> eventDuration=org.apache.jackrabbit.oak.stats.SimpleStats@4aa43935, 
> commitRateLimiter=null, running=false] (listener details: 
> 'JcrResourceListener [BasicObserverConfiguration [includeExternal=true, 
> paths=PathSet [paths=[Path [path=/]]], excludedPaths=PathSet [paths=[Path 
> [path=/libs/sling/sightly/js], Path 
> [path=/apps/sling/servlet/default/SLING_av... (1907 chars cut), 
> propertyNamesHint=null, changeTypes=[ADDED, REMOVED, CHANGED], 
> listeners=[ResourceChangeListenerInfo [paths=PathSet [paths=[Path [path=/]]], 
> resourceChangeTypes=[ADDED, REMOVED, CHANGED], 
> providerChangeTypes=[PROVIDER_ADDED, PROVIDER_REMOVED], 
> propertyNamesHint=null, valid=true, external=true, 
> listener=org.apache.sling.servlets.resolver.internal.SlingServletResolver@3993ddcd],
>  ResourceChangeListenerInfo [paths=PathSet [paths=[Path [path=/]]], 
> resourceChangeTypes=[ADDED, REMOVED, CHANGED], 
> providerChangeTypes=[PROVIDER_ADDED, PROVIDER_REMOVED], 
> propertyNamesHint=null, valid=true, external=true, 
> listener=org.apache.sling.resourceresolver.impl.mapping.MapEntries@70b4e2df], 
> ResourceChangeListenerInfo [paths=PathSet [paths=[Path [path=/]]], 
> resourceChangeTypes=[ADDED, REMOVED, CHANGED], 
> providerChangeTypes=[PROVIDER_ADDED, PROVIDER_REMOVED], 
> propertyNamesHint=null, valid=true, external=true, 
> listener=org.apache.sling.i18n.impl.JcrResourceBundleProvider@60af913d')
> {Code}
> after which content loading does not work, resulting in test failing 
> cc [~olli]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-7312) Java 9 requires javax.annotation to be added to the classpath

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-7312:
---
Fix Version/s: (was: Starter 10)
   Starter 11

> Java 9 requires javax.annotation to be added to the classpath
> -
>
> Key: SLING-7312
> URL: https://issues.apache.org/jira/browse/SLING-7312
> Project: Sling
>  Issue Type: Bug
>  Components: Launchpad
>Reporter: Robert Munteanu
>Priority: Major
> Fix For: Starter 11
>
>
> When running on Java 9 post SLING-7186 startup fails due to the 
> {{javax.annotation}} package no longer being exported by default, e.g.
> {noformat}org.osgi.framework.BundleException: Unable to resolve 
> org.apache.sling.installer.core [2](R 2.0): missing requirement 
> [org.apache.sling.installer.core [2](R 2.0)] osgi.wiring.package; 
> (osgi.wiring.package=javax.annotation) Unresolved requirements: 
> [[org.apache.sling.installer.core [2](R 2.0)] osgi.wiring.package; 
> (osgi.wiring.package=javax.annotation)]
>   at 
> org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4149)
>   at org.apache.felix.framework.Felix.startBundle(Felix.java:2119)
>   at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1373)
>   at 
> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
>   at java.base/java.lang.Thread.run(Thread.java:844){noformat}
> The interesting part here is that the {{javax.annotation}} classes that are 
> required - for instance {{javax.annotation.CheckForNull}} are _not_ part of 
> the JDK-provided {{javax.annotation}} package, they must come from another 
> jar. In fact, we don't have that Jar deployed in the starter, but instead the 
> JDK provides:
> {noformat}
> Generated.class
> PostConstruct.class
> PreDestroy.class
> Resource.class
> Resources.class
> {noformat}
> In a sense, this is very close to the root cause of SLING-7135 - solving one 
> might solve both but the symptoms are very different so raising it separately.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-7202) o.a.j.o.j.o.ObservationManagerImpl times out eventually in pax container init

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-7202:

Affects Version/s: (was: Testing PaxExam 0.0.4)
  Component/s: (was: Testing)

> o.a.j.o.j.o.ObservationManagerImpl times out eventually in pax container init
> -
>
> Key: SLING-7202
> URL: https://issues.apache.org/jira/browse/SLING-7202
> Project: Sling
>  Issue Type: Bug
>Reporter: Nicolas Peltier
>Assignee: Oliver Lietz
>Priority: Major
> Attachments: success-fail-logs.tar
>
>
> pipes IT intermittently fail. When they do, after having compared to when 
> they don't, look like the core cause is
> {Code}
> 2017-10-10 22:32:13,092 WARN [FelixStartLevel] 
> o.a.j.o.j.o.ObservationManagerImpl [ObservationManagerImpl.java : 457] Timed 
> out waiting for change processor to stop after 1000 milliseconds. Falling 
> back to asynchronous stop on ChangeProcessor [listenerId=10, 
> tracker=//*[1b]@org.apache.sling.jcr.resource.internal.JcrResourceListener,
>  contentSession=session-17, 
> eventCount=org.apache.jackrabbit.oak.stats.SimpleStats@4405759a, 
> eventDuration=org.apache.jackrabbit.oak.stats.SimpleStats@4aa43935, 
> commitRateLimiter=null, running=false] (listener details: 
> 'JcrResourceListener [BasicObserverConfiguration [includeExternal=true, 
> paths=PathSet [paths=[Path [path=/]]], excludedPaths=PathSet [paths=[Path 
> [path=/libs/sling/sightly/js], Path 
> [path=/apps/sling/servlet/default/SLING_av... (1907 chars cut), 
> propertyNamesHint=null, changeTypes=[ADDED, REMOVED, CHANGED], 
> listeners=[ResourceChangeListenerInfo [paths=PathSet [paths=[Path [path=/]]], 
> resourceChangeTypes=[ADDED, REMOVED, CHANGED], 
> providerChangeTypes=[PROVIDER_ADDED, PROVIDER_REMOVED], 
> propertyNamesHint=null, valid=true, external=true, 
> listener=org.apache.sling.servlets.resolver.internal.SlingServletResolver@3993ddcd],
>  ResourceChangeListenerInfo [paths=PathSet [paths=[Path [path=/]]], 
> resourceChangeTypes=[ADDED, REMOVED, CHANGED], 
> providerChangeTypes=[PROVIDER_ADDED, PROVIDER_REMOVED], 
> propertyNamesHint=null, valid=true, external=true, 
> listener=org.apache.sling.resourceresolver.impl.mapping.MapEntries@70b4e2df], 
> ResourceChangeListenerInfo [paths=PathSet [paths=[Path [path=/]]], 
> resourceChangeTypes=[ADDED, REMOVED, CHANGED], 
> providerChangeTypes=[PROVIDER_ADDED, PROVIDER_REMOVED], 
> propertyNamesHint=null, valid=true, external=true, 
> listener=org.apache.sling.i18n.impl.JcrResourceBundleProvider@60af913d')
> {Code}
> after which content loading does not work, resulting in test failing 
> cc [~olli]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7407) A thread pool with min size 1 uses only 1 thread for processing

[Stefan Egli (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332464#comment-16332464
 ] 

Stefan Egli commented on SLING-7407:


good point, [lowered to 
info|https://github.com/apache/sling-org-apache-sling-commons-threads/commit/ea49cff1ce0d2f3e00fbf16d3b0d35e1b39a6a12],
 perhaps useful to have at info for visibility as we're changing a user's 
config.

> A thread pool with min size 1 uses only 1 thread for processing
> ---
>
> Key: SLING-7407
> URL: https://issues.apache.org/jira/browse/SLING-7407
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Reporter: Chetan Mehrotra
>Assignee: Stefan Egli
>Priority: Major
> Fix For: Commons Threads 3.2.12
>
>
> If a thread pool is configured like below
> {noformat}
>  org.apache.sling.commons.threads.impl.DefaultThreadPool.factory-oak
> name="oak"
> minPoolSize=I"1"
> maxPoolSize=I"5"
> {noformat}
> Then only 1 thread would be used even if multiple jobs are assigned to the 
> pool. This happens because of strange behaviour of Java 
> [ThreadPoolExecutor|https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/ThreadPoolExecutor.html]
> bq. If there are more than corePoolSize but less than maximumPoolSize threads 
> running, a new thread will be created only *if the queue is full*
> With unbounded queue used this lead to current behaviour. As a fix Sling 
> Thread Pool should adapt such a config 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (SLING-7073) Update bundle versions

[Robert Munteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332415#comment-16332415
 ] 

Robert Munteanu edited comment on SLING-7073 at 1/19/18 3:58 PM:
-

[~reschke] - we're late with the Sling 10 release and integrating Oak 1.8 would 
bring another delay. I expect that we can upgrade to 1.8 shortly after the 
release.


was (Author: rombert):
[~reschke] - we've late with the Sling 10 release and integrating Oak 1.8 would 
bring another delay. I expect that we can upgrade to 1.8 shortly after the 
release.

> Update bundle versions
> --
>
> Key: SLING-7073
> URL: https://issues.apache.org/jira/browse/SLING-7073
> Project: Sling
>  Issue Type: Sub-task
>  Components: Launchpad
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Starter 10
>
>
> Before the launchpad release, include the latest versions of external bundles 
> and also check that our own bundles are at the latest versions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7407) A thread pool with min size 1 uses only 1 thread for processing

[Carsten Ziegeler (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332432#comment-16332432
 ] 

Carsten Ziegeler commented on SLING-7407:
-

[~egli] Lgtm, thanks - not sure if we should log with level warn, info or debug 
might be ok as well.

> A thread pool with min size 1 uses only 1 thread for processing
> ---
>
> Key: SLING-7407
> URL: https://issues.apache.org/jira/browse/SLING-7407
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Reporter: Chetan Mehrotra
>Assignee: Stefan Egli
>Priority: Major
> Fix For: Commons Threads 3.2.12
>
>
> If a thread pool is configured like below
> {noformat}
>  org.apache.sling.commons.threads.impl.DefaultThreadPool.factory-oak
> name="oak"
> minPoolSize=I"1"
> maxPoolSize=I"5"
> {noformat}
> Then only 1 thread would be used even if multiple jobs are assigned to the 
> pool. This happens because of strange behaviour of Java 
> [ThreadPoolExecutor|https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/ThreadPoolExecutor.html]
> bq. If there are more than corePoolSize but less than maximumPoolSize threads 
> running, a new thread will be created only *if the queue is full*
> With unbounded queue used this lead to current behaviour. As a fix Sling 
> Thread Pool should adapt such a config 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7073) Update bundle versions

[Robert Munteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332415#comment-16332415
 ] 

Robert Munteanu commented on SLING-7073:


[~reschke] - we've late with the Sling 10 release and integrating Oak 1.8 would 
bring another delay. I expect that we can upgrade to 1.8 shortly after the 
release.

> Update bundle versions
> --
>
> Key: SLING-7073
> URL: https://issues.apache.org/jira/browse/SLING-7073
> Project: Sling
>  Issue Type: Sub-task
>  Components: Launchpad
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Starter 10
>
>
> Before the launchpad release, include the latest versions of external bundles 
> and also check that our own bundles are at the latest versions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7407) A thread pool with min size 1 uses only 1 thread for processing

[Stefan Egli (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332409#comment-16332409
 ] 

Stefan Egli commented on SLING-7407:


* committed change in 
https://github.com/apache/sling-org-apache-sling-commons-threads/commit/7fb9afbdd13b05947bf8b302e94ef9ba533dc6d7
* [~chetanm] or [~cziegeler] could you please have a quick review of the above 
change before I release, thx!

> A thread pool with min size 1 uses only 1 thread for processing
> ---
>
> Key: SLING-7407
> URL: https://issues.apache.org/jira/browse/SLING-7407
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Reporter: Chetan Mehrotra
>Assignee: Stefan Egli
>Priority: Major
> Fix For: Commons Threads 3.2.12
>
>
> If a thread pool is configured like below
> {noformat}
>  org.apache.sling.commons.threads.impl.DefaultThreadPool.factory-oak
> name="oak"
> minPoolSize=I"1"
> maxPoolSize=I"5"
> {noformat}
> Then only 1 thread would be used even if multiple jobs are assigned to the 
> pool. This happens because of strange behaviour of Java 
> [ThreadPoolExecutor|https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/ThreadPoolExecutor.html]
> bq. If there are more than corePoolSize but less than maximumPoolSize threads 
> running, a new thread will be created only *if the queue is full*
> With unbounded queue used this lead to current behaviour. As a fix Sling 
> Thread Pool should adapt such a config 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7202) o.a.j.o.j.o.ObservationManagerImpl times out eventually in pax container init

[Nicolas Peltier (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332408#comment-16332408
 ] 

Nicolas Peltier commented on SLING-7202:


[~olli] yes i do. Not sure how i was generating that message with pipes IT, but 
i confirm it's gone now

> o.a.j.o.j.o.ObservationManagerImpl times out eventually in pax container init
> -
>
> Key: SLING-7202
> URL: https://issues.apache.org/jira/browse/SLING-7202
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Affects Versions: Testing PaxExam 0.0.4
>Reporter: Nicolas Peltier
>Assignee: Oliver Lietz
>Priority: Major
> Attachments: success-fail-logs.tar
>
>
> pipes IT intermittently fail. When they do, after having compared to when 
> they don't, look like the core cause is
> {Code}
> 2017-10-10 22:32:13,092 WARN [FelixStartLevel] 
> o.a.j.o.j.o.ObservationManagerImpl [ObservationManagerImpl.java : 457] Timed 
> out waiting for change processor to stop after 1000 milliseconds. Falling 
> back to asynchronous stop on ChangeProcessor [listenerId=10, 
> tracker=//*[1b]@org.apache.sling.jcr.resource.internal.JcrResourceListener,
>  contentSession=session-17, 
> eventCount=org.apache.jackrabbit.oak.stats.SimpleStats@4405759a, 
> eventDuration=org.apache.jackrabbit.oak.stats.SimpleStats@4aa43935, 
> commitRateLimiter=null, running=false] (listener details: 
> 'JcrResourceListener [BasicObserverConfiguration [includeExternal=true, 
> paths=PathSet [paths=[Path [path=/]]], excludedPaths=PathSet [paths=[Path 
> [path=/libs/sling/sightly/js], Path 
> [path=/apps/sling/servlet/default/SLING_av... (1907 chars cut), 
> propertyNamesHint=null, changeTypes=[ADDED, REMOVED, CHANGED], 
> listeners=[ResourceChangeListenerInfo [paths=PathSet [paths=[Path [path=/]]], 
> resourceChangeTypes=[ADDED, REMOVED, CHANGED], 
> providerChangeTypes=[PROVIDER_ADDED, PROVIDER_REMOVED], 
> propertyNamesHint=null, valid=true, external=true, 
> listener=org.apache.sling.servlets.resolver.internal.SlingServletResolver@3993ddcd],
>  ResourceChangeListenerInfo [paths=PathSet [paths=[Path [path=/]]], 
> resourceChangeTypes=[ADDED, REMOVED, CHANGED], 
> providerChangeTypes=[PROVIDER_ADDED, PROVIDER_REMOVED], 
> propertyNamesHint=null, valid=true, external=true, 
> listener=org.apache.sling.resourceresolver.impl.mapping.MapEntries@70b4e2df], 
> ResourceChangeListenerInfo [paths=PathSet [paths=[Path [path=/]]], 
> resourceChangeTypes=[ADDED, REMOVED, CHANGED], 
> providerChangeTypes=[PROVIDER_ADDED, PROVIDER_REMOVED], 
> propertyNamesHint=null, valid=true, external=true, 
> listener=org.apache.sling.i18n.impl.JcrResourceBundleProvider@60af913d')
> {Code}
> after which content loading does not work, resulting in test failing 
> cc [~olli]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7202) o.a.j.o.j.o.ObservationManagerImpl times out eventually in pax container init

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332355#comment-16332355
 ] 

Oliver Lietz commented on SLING-7202:
-

[~npeltier], can you confirm: Not an issue with Testing PaxExam?

> o.a.j.o.j.o.ObservationManagerImpl times out eventually in pax container init
> -
>
> Key: SLING-7202
> URL: https://issues.apache.org/jira/browse/SLING-7202
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Affects Versions: Testing PaxExam 0.0.4
>Reporter: Nicolas Peltier
>Assignee: Oliver Lietz
>Priority: Major
> Attachments: success-fail-logs.tar
>
>
> pipes IT intermittently fail. When they do, after having compared to when 
> they don't, look like the core cause is
> {Code}
> 2017-10-10 22:32:13,092 WARN [FelixStartLevel] 
> o.a.j.o.j.o.ObservationManagerImpl [ObservationManagerImpl.java : 457] Timed 
> out waiting for change processor to stop after 1000 milliseconds. Falling 
> back to asynchronous stop on ChangeProcessor [listenerId=10, 
> tracker=//*[1b]@org.apache.sling.jcr.resource.internal.JcrResourceListener,
>  contentSession=session-17, 
> eventCount=org.apache.jackrabbit.oak.stats.SimpleStats@4405759a, 
> eventDuration=org.apache.jackrabbit.oak.stats.SimpleStats@4aa43935, 
> commitRateLimiter=null, running=false] (listener details: 
> 'JcrResourceListener [BasicObserverConfiguration [includeExternal=true, 
> paths=PathSet [paths=[Path [path=/]]], excludedPaths=PathSet [paths=[Path 
> [path=/libs/sling/sightly/js], Path 
> [path=/apps/sling/servlet/default/SLING_av... (1907 chars cut), 
> propertyNamesHint=null, changeTypes=[ADDED, REMOVED, CHANGED], 
> listeners=[ResourceChangeListenerInfo [paths=PathSet [paths=[Path [path=/]]], 
> resourceChangeTypes=[ADDED, REMOVED, CHANGED], 
> providerChangeTypes=[PROVIDER_ADDED, PROVIDER_REMOVED], 
> propertyNamesHint=null, valid=true, external=true, 
> listener=org.apache.sling.servlets.resolver.internal.SlingServletResolver@3993ddcd],
>  ResourceChangeListenerInfo [paths=PathSet [paths=[Path [path=/]]], 
> resourceChangeTypes=[ADDED, REMOVED, CHANGED], 
> providerChangeTypes=[PROVIDER_ADDED, PROVIDER_REMOVED], 
> propertyNamesHint=null, valid=true, external=true, 
> listener=org.apache.sling.resourceresolver.impl.mapping.MapEntries@70b4e2df], 
> ResourceChangeListenerInfo [paths=PathSet [paths=[Path [path=/]]], 
> resourceChangeTypes=[ADDED, REMOVED, CHANGED], 
> providerChangeTypes=[PROVIDER_ADDED, PROVIDER_REMOVED], 
> propertyNamesHint=null, valid=true, external=true, 
> listener=org.apache.sling.i18n.impl.JcrResourceBundleProvider@60af913d')
> {Code}
> after which content loading does not work, resulting in test failing 
> cc [~olli]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7251) Fix pipes plumber servlet IT

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332353#comment-16332353
 ] 

Oliver Lietz commented on SLING-7251:
-

[~npeltier], no. Calls in ITs from test bundle are allowed by whitelisting the 
bundle:

{noformat}

newConfiguration("org.apache.sling.jcr.base.internal.LoginAdminWhitelist")
.put("whitelist.bundles.regexp", "^PAXEXAM.*$")
.asOption(),
{noformat}

Now I see service user is configurable. So the current configuration in 
{{PipesTestSupport}} is fine (can we restrict write to {{/content}} and 
{{/var}} though?), but required. AFAIR tests failed due to NPE when adapting to 
{{ModifiableValueMap}} in {{PlumberImpl}}. 



> Fix pipes plumber servlet IT 
> -
>
> Key: SLING-7251
> URL: https://issues.apache.org/jira/browse/SLING-7251
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: pipes 2.0.0
>Reporter: Nicolas Peltier
>Assignee: Nicolas Peltier
>Priority: Major
> Fix For: pipes 2.0.0
>
>
> new Plumber servlet IT fail. This should be fixed



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-7251) Fix pipes plumber servlet IT

[Nicolas Peltier (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nicolas Peltier updated SLING-7251:
---
Fix Version/s: pipes 2.0.0

> Fix pipes plumber servlet IT 
> -
>
> Key: SLING-7251
> URL: https://issues.apache.org/jira/browse/SLING-7251
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: pipes 2.0.0
>Reporter: Nicolas Peltier
>Assignee: Nicolas Peltier
>Priority: Major
> Fix For: pipes 2.0.0
>
>
> new Plumber servlet IT fail. This should be fixed



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7251) Fix pipes plumber servlet IT

[Nicolas Peltier (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332337#comment-16332337
 ] 

Nicolas Peltier commented on SLING-7251:


[~olli] for the ACLs, are you referring to loginAdministrative in integration 
tests?

everything under {{src/main}} is tied to 
- either passed in resolver (delegating to caller code the security)
- either service-user's resolver (i hadn't created in test)

if you are referring to {{src/test}}, i'll change that (now i know how to do 
:-))

> Fix pipes plumber servlet IT 
> -
>
> Key: SLING-7251
> URL: https://issues.apache.org/jira/browse/SLING-7251
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: pipes 2.0.0
>Reporter: Nicolas Peltier
>Assignee: Nicolas Peltier
>Priority: Major
>
> new Plumber servlet IT fail. This should be fixed



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Release Apache Sling IDE Tooling version 1.2.0

[Karl Pauls]

+1

regards,

Karl

On Fri, Jan 19, 2018 at 3:10 PM, Robert Munteanu  wrote:
> On Fri, 2018-01-19 at 14:18 +0100, Konrad Windszus wrote:
>> Finally I got the right file. Seems that some intermediate cache
>> (maybe some CDN?) still delivered the old version yesterday.
>> Now looks good although https://issues.apache.org/jira/browse/SLING-7
>> 403  is still not
>> fixed.
>> But since this is only a minor issue I am gonna vote for release.
>
> Thanks! I would rather only respin if necessary since code signing
> costs the ASF money, and I already signed twice for this release :-)
>
> Robert



-- 
Karl Pauls
karlpa...@gmail.com

[jira] [Commented] (SLING-7251) Fix pipes plumber servlet IT

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332324#comment-16332324
 ] 

Oliver Lietz commented on SLING-7251:
-

Pipes is writing to the repository (not using the authenticated request 
resource resolver), this should be restricted as much as possible with a 
dedicated service user. The current configuration (which I had to add) in 
{{PipesTestSupport}} allows full read/write on {{/}}.

The logs in {{target/failsafe-reports}} are in plain text.

> Fix pipes plumber servlet IT 
> -
>
> Key: SLING-7251
> URL: https://issues.apache.org/jira/browse/SLING-7251
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: pipes 2.0.0
>Reporter: Nicolas Peltier
>Assignee: Nicolas Peltier
>Priority: Major
>
> new Plumber servlet IT fail. This should be fixed



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7251) Fix pipes plumber servlet IT

[Nicolas Peltier (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332307#comment-16332307
 ] 

Nicolas Peltier commented on SLING-7251:


wow thanks a lot [~olli]!
 * for ACLs i don't see where you'd want some? i was assuming the ones we have 
in the parents (/etc, /var) are already good?
 * Service user is required for certain tasks (async pipes mostly), but for the 
rest, i use the user from the request.
 * {{target/failsafe-reports}} is good but i hate the xml format

> Fix pipes plumber servlet IT 
> -
>
> Key: SLING-7251
> URL: https://issues.apache.org/jira/browse/SLING-7251
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: pipes 2.0.0
>Reporter: Nicolas Peltier
>Assignee: Nicolas Peltier
>Priority: Major
>
> new Plumber servlet IT fail. This should be fixed



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-7414) WebConsole security provider 1.1.0 or newer do not work with the Sling Starter

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-7414:
---
Description: 
When upgrading the webconsole security provider in the Sling starter to 1.2.0, 
the following problems occur:

* the SmokeIT fails since accessing {{/system/console/bundles.json}} redirects 
to an HTML login form
* accessing the OSGi console at {{/system/console}} presents a login form at 
http://localhost:8080/system/sling/form/login?resource=%2Fsystem%2Fconsole, but 
then redirects to http://localhost:8080/system/console/j_security_check . 
Re-accessing {{/system/console}} brings up the login form again.

  was:
When upgrading the webconsole security provider in the Sling starter to 1.2.0, 
the following problems occur:

* the SmokeIT fails since accessing {{/system/console/bundles.json}} redirects 
to an HTML login form
* accessing the OSGi console at {{/system/console}} presents a login form at 
http://localhost:8080/system/sling/form/login?resource=%2Fsystem%2Fconsole}}, 
but then redirects to http://localhost:8080/system/console/j_security_check . 
Re-accessing {{/system/console}} brings up the login form again.


> WebConsole security provider 1.1.0 or newer do not work with the Sling Starter
> --
>
> Key: SLING-7414
> URL: https://issues.apache.org/jira/browse/SLING-7414
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Web Console Security Provider 1.1.0
>Reporter: Robert Munteanu
>Priority: Major
> Fix For: Web Console Security Provider 1.2.2
>
>
> When upgrading the webconsole security provider in the Sling starter to 
> 1.2.0, the following problems occur:
> * the SmokeIT fails since accessing {{/system/console/bundles.json}} 
> redirects to an HTML login form
> * accessing the OSGi console at {{/system/console}} presents a login form at 
> http://localhost:8080/system/sling/form/login?resource=%2Fsystem%2Fconsole, 
> but then redirects to http://localhost:8080/system/console/j_security_check . 
> Re-accessing {{/system/console}} brings up the login form again.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SLING-7414) WebConsole security provider 1.1.0 or newer do not work with the Sling Starter

[Robert Munteanu (JIRA)]

Robert Munteanu created SLING-7414:
--

 Summary: WebConsole security provider 1.1.0 or newer do not work 
with the Sling Starter
 Key: SLING-7414
 URL: https://issues.apache.org/jira/browse/SLING-7414
 Project: Sling
  Issue Type: Bug
  Components: Extensions
Affects Versions: Web Console Security Provider 1.1.0
Reporter: Robert Munteanu
 Fix For: Web Console Security Provider 1.2.2


When upgrading the webconsole security provider in the Sling starter to 1.2.0, 
the following problems occur:

* the SmokeIT fails since accessing {{/system/console/bundles.json}} redirects 
to an HTML login form
* accessing the OSGi console at {{/system/console}} presents a login form at 
http://localhost:8080/system/sling/form/login?resource=%2Fsystem%2Fconsole}}, 
but then redirects to http://localhost:8080/system/console/j_security_check . 
Re-accessing {{/system/console}} brings up the login form again.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-7414) WebConsole security provider 1.1.0 or newer do not work with the Sling Starter

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-7414:
---
Priority: Critical  (was: Major)

> WebConsole security provider 1.1.0 or newer do not work with the Sling Starter
> --
>
> Key: SLING-7414
> URL: https://issues.apache.org/jira/browse/SLING-7414
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Web Console Security Provider 1.1.0
>Reporter: Robert Munteanu
>Priority: Critical
> Fix For: Web Console Security Provider 1.2.2
>
>
> When upgrading the webconsole security provider in the Sling starter to 
> 1.2.0, the following problems occur:
> * the SmokeIT fails since accessing {{/system/console/bundles.json}} 
> redirects to an HTML login form
> * accessing the OSGi console at {{/system/console}} presents a login form at 
> http://localhost:8080/system/sling/form/login?resource=%2Fsystem%2Fconsole, 
> but then redirects to http://localhost:8080/system/console/j_security_check . 
> Re-accessing {{/system/console}} brings up the login form again.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7404) ObjectModel and similar classes need consistent null checks

[Radu Cotescu (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332301#comment-16332301
 ] 

Radu Cotescu commented on SLING-7404:
-

Fixed in [commit 
0afdc96|https://github.com/apache/sling-org-apache-sling-scripting-sightly-compiler/commit/0afdc96],
 [commit 
e9bdb14|https://github.com/apache/sling-org-apache-sling-scripting-sightly-compiler-java/commit/e9bdb14]
 and [commit 
d8bfb67|https://github.com/apache/sling-org-apache-sling-scripting-sightly/commit/d8bfb67].

> ObjectModel and similar classes need consistent null checks
> ---
>
> Key: SLING-7404
> URL: https://issues.apache.org/jira/browse/SLING-7404
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting HTL Engine 1.0.38, Scripting HTL Compiler 
> 1.0.12, Scripting HTL Java Compiler 1.0.12
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Java Compiler 1.0.22-1.3.1, Scripting HTL 
> Compiler 1.0.20-1.3.1, Scripting HTL Engine 1.0.48-1.3.1
>
>
> {{org.apache.sling.scripting.sightly.compiler.util.ObjectModel}} and similar 
> classes need consistent null checks, so that none of the public methods can 
> throw a {{NullPointerException}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7073) Update bundle versions

[Julian Reschke (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332302#comment-16332302
 ] 

Julian Reschke commented on SLING-7073:
---

{quote}jackkrabbit, oak - stick with 1.6
{quote}
The reason being?

> Update bundle versions
> --
>
> Key: SLING-7073
> URL: https://issues.apache.org/jira/browse/SLING-7073
> Project: Sling
>  Issue Type: Sub-task
>  Components: Launchpad
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Starter 10
>
>
> Before the launchpad release, include the latest versions of external bundles 
> and also check that our own bundles are at the latest versions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (SLING-7404) ObjectModel and similar classes need consistent null checks

[Radu Cotescu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-7404.
-
Resolution: Fixed

> ObjectModel and similar classes need consistent null checks
> ---
>
> Key: SLING-7404
> URL: https://issues.apache.org/jira/browse/SLING-7404
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting HTL Engine 1.0.38, Scripting HTL Compiler 
> 1.0.12, Scripting HTL Java Compiler 1.0.12
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Java Compiler 1.0.22-1.3.1, Scripting HTL 
> Compiler 1.0.20-1.3.1, Scripting HTL Engine 1.0.48-1.3.1
>
>
> {{org.apache.sling.scripting.sightly.compiler.util.ObjectModel}} and similar 
> classes need consistent null checks, so that none of the public methods can 
> throw a {{NullPointerException}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Release Apache Sling IDE Tooling version 1.2.0

[Robert Munteanu]

On Fri, 2018-01-19 at 14:18 +0100, Konrad Windszus wrote:
> Finally I got the right file. Seems that some intermediate cache
> (maybe some CDN?) still delivered the old version yesterday.
> Now looks good although https://issues.apache.org/jira/browse/SLING-7
> 403  is still not
> fixed.
> But since this is only a minor issue I am gonna vote for release.

Thanks! I would rather only respin if necessary since code signing
costs the ASF money, and I already signed twice for this release :-)

Robert

[jira] [Assigned] (SLING-6952) Release Sling 10

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu reassigned SLING-6952:
--

Assignee: Robert Munteanu

> Release Sling 10
> 
>
> Key: SLING-6952
> URL: https://issues.apache.org/jira/browse/SLING-6952
> Project: Sling
>  Issue Type: Task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
>
> Never too early to start planning :-)
> Documentation at 
> https://cwiki.apache.org/confluence/display/SLING/Releasing+a+new+version+of+the+Sling+Launchpad



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SLING-7413) Send announcement to u...@sling.apache.org and annou...@apache.org

[Robert Munteanu (JIRA)]

Robert Munteanu created SLING-7413:
--

 Summary: Send announcement to u...@sling.apache.org and 
annou...@apache.org
 Key: SLING-7413
 URL: https://issues.apache.org/jira/browse/SLING-7413
 Project: Sling
  Issue Type: Sub-task
Reporter: Robert Munteanu






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SLING-7412) Create 'New and Noteworthy' page for Sling 10

[Robert Munteanu (JIRA)]

Robert Munteanu created SLING-7412:
--

 Summary: Create 'New and Noteworthy' page for Sling 10
 Key: SLING-7412
 URL: https://issues.apache.org/jira/browse/SLING-7412
 Project: Sling
  Issue Type: Sub-task
Reporter: Robert Munteanu






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SLING-7409) Update local starter references to 10 or 11-SNAPSHOT

[Robert Munteanu (JIRA)]

Robert Munteanu created SLING-7409:
--

 Summary: Update local starter references to 10 or 11-SNAPSHOT
 Key: SLING-7409
 URL: https://issues.apache.org/jira/browse/SLING-7409
 Project: Sling
  Issue Type: Sub-task
Reporter: Robert Munteanu






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SLING-7408) Release Sling Starter 10 and associated artifacts

[Robert Munteanu (JIRA)]

Robert Munteanu created SLING-7408:
--

 Summary: Release Sling Starter 10 and associated artifacts
 Key: SLING-7408
 URL: https://issues.apache.org/jira/browse/SLING-7408
 Project: Sling
  Issue Type: Sub-task
  Components: Launchpad
Reporter: Robert Munteanu
Assignee: Robert Munteanu


- starter 10
- launchpad.testing and associated projects
- Maven archetypes



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SLING-7411) Deploy Sling 10 docker image to Docker Hub

[Robert Munteanu (JIRA)]

Robert Munteanu created SLING-7411:
--

 Summary: Deploy Sling 10 docker image to Docker Hub
 Key: SLING-7411
 URL: https://issues.apache.org/jira/browse/SLING-7411
 Project: Sling
  Issue Type: Sub-task
Reporter: Robert Munteanu






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SLING-7410) Deploy API documentation for Sling 10

[Robert Munteanu (JIRA)]

Robert Munteanu created SLING-7410:
--

 Summary: Deploy API documentation for Sling 10
 Key: SLING-7410
 URL: https://issues.apache.org/jira/browse/SLING-7410
 Project: Sling
  Issue Type: Sub-task
Reporter: Robert Munteanu






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (SLING-7403) Sling IDE: Provider and Plugin Name not provided for Sling IDE plugins

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu reopened SLING-7403:


Sorry, looked at the wrong screen - I thought this was the 'Installed software' 
tab.

It is an issue that I can reproduce as well and I suggest we fix it for the 
next release.

> Sling IDE: Provider and Plugin Name not provided for Sling IDE plugins
> --
>
> Key: SLING-7403
> URL: https://issues.apache.org/jira/browse/SLING-7403
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.2.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: Sling Eclipse IDE 1.2.2
>
> Attachments: Eclipse_Installation_Details.png, 
> Eclipse_Installation_Details_and_About_Eclipse.png
>
>
> When clicking on Eclipse -> About Eclipse -> Installation Details all plugins 
> from Sling are lacking the provider and plugin name details (see attached 
> screenshot). 
>  !Eclipse_Installation_Details_and_About_Eclipse.png! 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (SLING-7403) Sling IDE: Provider and Plugin Name not provided for Sling IDE plugins

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved SLING-7403.

Resolution: Fixed

> Sling IDE: Provider and Plugin Name not provided for Sling IDE plugins
> --
>
> Key: SLING-7403
> URL: https://issues.apache.org/jira/browse/SLING-7403
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.2.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: Sling Eclipse IDE 1.2.2
>
> Attachments: Eclipse_Installation_Details.png, 
> Eclipse_Installation_Details_and_About_Eclipse.png
>
>
> When clicking on Eclipse -> About Eclipse -> Installation Details all plugins 
> from Sling are lacking the provider and plugin name details (see attached 
> screenshot). 
>  !Eclipse_Installation_Details_and_About_Eclipse.png! 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7404) ObjectModel and similar classes need consistent null checks

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332292#comment-16332292
 ] 

ASF GitHub Bot commented on SLING-7404:
---

raducotescu closed pull request #1: SLING-7404 - ObjectModel and similar 
classes need consistent null checks
URL: https://github.com/apache/sling-org-apache-sling-scripting-sightly/pull/1
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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


> ObjectModel and similar classes need consistent null checks
> ---
>
> Key: SLING-7404
> URL: https://issues.apache.org/jira/browse/SLING-7404
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting HTL Engine 1.0.38, Scripting HTL Compiler 
> 1.0.12, Scripting HTL Java Compiler 1.0.12
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Java Compiler 1.0.22-1.3.1, Scripting HTL 
> Compiler 1.0.20-1.3.1, Scripting HTL Engine 1.0.48-1.3.1
>
>
> {{org.apache.sling.scripting.sightly.compiler.util.ObjectModel}} and similar 
> classes need consistent null checks, so that none of the public methods can 
> throw a {{NullPointerException}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7073) Update bundle versions

[Robert Munteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332290#comment-16332290
 ] 

Robert Munteanu commented on SLING-7073:


Thanks for the info [~kwin], I skipped that as well, Also the 
webconsolesecurityprovider upgrade breaks the SmokeIT, presumably due to 
SLING-3193

> Update bundle versions
> --
>
> Key: SLING-7073
> URL: https://issues.apache.org/jira/browse/SLING-7073
> Project: Sling
>  Issue Type: Sub-task
>  Components: Launchpad
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Starter 10
>
>
> Before the launchpad release, include the latest versions of external bundles 
> and also check that our own bundles are at the latest versions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (SLING-7073) Update bundle versions

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved SLING-7073.

Resolution: Fixed

> Update bundle versions
> --
>
> Key: SLING-7073
> URL: https://issues.apache.org/jira/browse/SLING-7073
> Project: Sling
>  Issue Type: Sub-task
>  Components: Launchpad
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Starter 10
>
>
> Before the launchpad release, include the latest versions of external bundles 
> and also check that our own bundles are at the latest versions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7404) ObjectModel and similar classes need consistent null checks

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332288#comment-16332288
 ] 

ASF GitHub Bot commented on SLING-7404:
---

raducotescu closed pull request #2: SLING-7404 - ObjectModel and similar 
classes need consistent null checks
URL: 
https://github.com/apache/sling-org-apache-sling-scripting-sightly-compiler-java/pull/2
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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


> ObjectModel and similar classes need consistent null checks
> ---
>
> Key: SLING-7404
> URL: https://issues.apache.org/jira/browse/SLING-7404
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting HTL Engine 1.0.38, Scripting HTL Compiler 
> 1.0.12, Scripting HTL Java Compiler 1.0.12
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Java Compiler 1.0.22-1.3.1, Scripting HTL 
> Compiler 1.0.20-1.3.1, Scripting HTL Engine 1.0.48-1.3.1
>
>
> {{org.apache.sling.scripting.sightly.compiler.util.ObjectModel}} and similar 
> classes need consistent null checks, so that none of the public methods can 
> throw a {{NullPointerException}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7404) ObjectModel and similar classes need consistent null checks

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332287#comment-16332287
 ] 

ASF GitHub Bot commented on SLING-7404:
---

raducotescu closed pull request #2: SLING-7404 - ObjectModel and similar 
classes need consistent null checks
URL: 
https://github.com/apache/sling-org-apache-sling-scripting-sightly-compiler/pull/2
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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


> ObjectModel and similar classes need consistent null checks
> ---
>
> Key: SLING-7404
> URL: https://issues.apache.org/jira/browse/SLING-7404
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting HTL Engine 1.0.38, Scripting HTL Compiler 
> 1.0.12, Scripting HTL Java Compiler 1.0.12
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Java Compiler 1.0.22-1.3.1, Scripting HTL 
> Compiler 1.0.20-1.3.1, Scripting HTL Engine 1.0.48-1.3.1
>
>
> {{org.apache.sling.scripting.sightly.compiler.util.ObjectModel}} and similar 
> classes need consistent null checks, so that none of the public methods can 
> throw a {{NullPointerException}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] raducotescu closed pull request #2: SLING-7404 - ObjectModel and similar classes need consistent null checks

[GitBox]

raducotescu closed pull request #2: SLING-7404 - ObjectModel and similar 
classes need consistent null checks
URL: 
https://github.com/apache/sling-org-apache-sling-scripting-sightly-compiler-java/pull/2
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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-7404) ObjectModel and similar classes need consistent null checks

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332265#comment-16332265
 ] 

ASF GitHub Bot commented on SLING-7404:
---

raducotescu opened a new pull request #2: SLING-7404 - ObjectModel and similar 
classes need consistent null checks
URL: 
https://github.com/apache/sling-org-apache-sling-scripting-sightly-compiler-java/pull/2
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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


> ObjectModel and similar classes need consistent null checks
> ---
>
> Key: SLING-7404
> URL: https://issues.apache.org/jira/browse/SLING-7404
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting HTL Engine 1.0.38, Scripting HTL Compiler 
> 1.0.12, Scripting HTL Java Compiler 1.0.12
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Java Compiler 1.0.22-1.3.1, Scripting HTL 
> Compiler 1.0.20-1.3.1, Scripting HTL Engine 1.0.48-1.3.1
>
>
> {{org.apache.sling.scripting.sightly.compiler.util.ObjectModel}} and similar 
> classes need consistent null checks, so that none of the public methods can 
> throw a {{NullPointerException}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7404) ObjectModel and similar classes need consistent null checks

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332266#comment-16332266
 ] 

ASF GitHub Bot commented on SLING-7404:
---

raducotescu opened a new pull request #1: SLING-7404 - ObjectModel and similar 
classes need consistent null checks
URL: https://github.com/apache/sling-org-apache-sling-scripting-sightly/pull/1
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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


> ObjectModel and similar classes need consistent null checks
> ---
>
> Key: SLING-7404
> URL: https://issues.apache.org/jira/browse/SLING-7404
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting HTL Engine 1.0.38, Scripting HTL Compiler 
> 1.0.12, Scripting HTL Java Compiler 1.0.12
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Java Compiler 1.0.22-1.3.1, Scripting HTL 
> Compiler 1.0.20-1.3.1, Scripting HTL Engine 1.0.48-1.3.1
>
>
> {{org.apache.sling.scripting.sightly.compiler.util.ObjectModel}} and similar 
> classes need consistent null checks, so that none of the public methods can 
> throw a {{NullPointerException}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7404) ObjectModel and similar classes need consistent null checks

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332264#comment-16332264
 ] 

ASF GitHub Bot commented on SLING-7404:
---

raducotescu opened a new pull request #2: SLING-7404 - ObjectModel and similar 
classes need consistent null checks
URL: 
https://github.com/apache/sling-org-apache-sling-scripting-sightly-compiler/pull/2
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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


> ObjectModel and similar classes need consistent null checks
> ---
>
> Key: SLING-7404
> URL: https://issues.apache.org/jira/browse/SLING-7404
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting HTL Engine 1.0.38, Scripting HTL Compiler 
> 1.0.12, Scripting HTL Java Compiler 1.0.12
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Java Compiler 1.0.22-1.3.1, Scripting HTL 
> Compiler 1.0.20-1.3.1, Scripting HTL Engine 1.0.48-1.3.1
>
>
> {{org.apache.sling.scripting.sightly.compiler.util.ObjectModel}} and similar 
> classes need consistent null checks, so that none of the public methods can 
> throw a {{NullPointerException}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] raducotescu opened a new pull request #2: SLING-7404 - ObjectModel and similar classes need consistent null checks

[GitBox]

raducotescu opened a new pull request #2: SLING-7404 - ObjectModel and similar 
classes need consistent null checks
URL: 
https://github.com/apache/sling-org-apache-sling-scripting-sightly-compiler-java/pull/2
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on 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] [Assigned] (SLING-7407) A thread pool with min size 1 uses only 1 thread for processing

[Stefan Egli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Egli reassigned SLING-7407:
--

Assignee: Stefan Egli

> A thread pool with min size 1 uses only 1 thread for processing
> ---
>
> Key: SLING-7407
> URL: https://issues.apache.org/jira/browse/SLING-7407
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Reporter: Chetan Mehrotra
>Assignee: Stefan Egli
>Priority: Major
> Fix For: Commons Threads 3.2.12
>
>
> If a thread pool is configured like below
> {noformat}
>  org.apache.sling.commons.threads.impl.DefaultThreadPool.factory-oak
> name="oak"
> minPoolSize=I"1"
> maxPoolSize=I"5"
> {noformat}
> Then only 1 thread would be used even if multiple jobs are assigned to the 
> pool. This happens because of strange behaviour of Java 
> [ThreadPoolExecutor|https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/ThreadPoolExecutor.html]
> bq. If there are more than corePoolSize but less than maximumPoolSize threads 
> running, a new thread will be created only *if the queue is full*
> With unbounded queue used this lead to current behaviour. As a fix Sling 
> Thread Pool should adapt such a config 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (SLING-7403) Sling IDE: Provider and Plugin Name not provided for Sling IDE plugins

[Konrad Windszus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus resolved SLING-7403.

Resolution: Fixed

Fixed with 
https://github.com/apache/sling-ide-tooling/commit/720b412f087e8b2f9fce81da9dbe71eaa5d60297.

> Sling IDE: Provider and Plugin Name not provided for Sling IDE plugins
> --
>
> Key: SLING-7403
> URL: https://issues.apache.org/jira/browse/SLING-7403
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.2.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: Sling Eclipse IDE 1.2.2
>
> Attachments: Eclipse_Installation_Details.png, 
> Eclipse_Installation_Details_and_About_Eclipse.png
>
>
> When clicking on Eclipse -> About Eclipse -> Installation Details all plugins 
> from Sling are lacking the provider and plugin name details (see attached 
> screenshot). 
>  !Eclipse_Installation_Details_and_About_Eclipse.png! 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-7403) Sling IDE: Provider and Plugin Name not provided for Sling IDE plugins

[Konrad Windszus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus updated SLING-7403:
---
Fix Version/s: Sling Eclipse IDE 1.2.2

> Sling IDE: Provider and Plugin Name not provided for Sling IDE plugins
> --
>
> Key: SLING-7403
> URL: https://issues.apache.org/jira/browse/SLING-7403
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.2.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: Sling Eclipse IDE 1.2.2
>
> Attachments: Eclipse_Installation_Details.png, 
> Eclipse_Installation_Details_and_About_Eclipse.png
>
>
> When clicking on Eclipse -> About Eclipse -> Installation Details all plugins 
> from Sling are lacking the provider and plugin name details (see attached 
> screenshot). 
>  !Eclipse_Installation_Details_and_About_Eclipse.png! 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7403) Sling IDE: Provider and Plugin Name not provided for Sling IDE plugins

[Konrad Windszus (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332244#comment-16332244
 ] 

Konrad Windszus commented on SLING-7403:


Column "Provider" is extracted from the Manifest header "Bundle-Vendor" whild 
the name is extracted from header "Bundle-Name". Both headers are maintained in 
only very few plugins.

> Sling IDE: Provider and Plugin Name not provided for Sling IDE plugins
> --
>
> Key: SLING-7403
> URL: https://issues.apache.org/jira/browse/SLING-7403
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.2.0
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: Sling Eclipse IDE 1.2.2
>
> Attachments: Eclipse_Installation_Details.png, 
> Eclipse_Installation_Details_and_About_Eclipse.png
>
>
> When clicking on Eclipse -> About Eclipse -> Installation Details all plugins 
> from Sling are lacking the provider and plugin name details (see attached 
> screenshot). 
>  !Eclipse_Installation_Details_and_About_Eclipse.png! 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (SLING-7403) Sling IDE: Provider and Plugin Name not provided for Sling IDE plugins

[Konrad Windszus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus reassigned SLING-7403:
--

Assignee: Konrad Windszus

> Sling IDE: Provider and Plugin Name not provided for Sling IDE plugins
> --
>
> Key: SLING-7403
> URL: https://issues.apache.org/jira/browse/SLING-7403
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.2.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: Sling Eclipse IDE 1.2.2
>
> Attachments: Eclipse_Installation_Details.png, 
> Eclipse_Installation_Details_and_About_Eclipse.png
>
>
> When clicking on Eclipse -> About Eclipse -> Installation Details all plugins 
> from Sling are lacking the provider and plugin name details (see attached 
> screenshot). 
>  !Eclipse_Installation_Details_and_About_Eclipse.png! 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Release Apache Sling IDE Tooling version 1.2.0

[Konrad Windszus]

+1 
Konrad

> On 17. Jan 2018, at 22:38, Robert Munteanu  wrote:
> 
> Hi,
> 
> We solved 30 issues in this release:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12334907
> 
> There are still some outstanding issues:
> https://issues.apache.org/jira/browse/SLING/component/12320908
> 
> The release candidate has been uploaded at
> https://dist.apache.org/repos/dist/dev/sling, The release artifact is
> the source bundle - org.apache.sling.ide.source-bundle-1.2.0.zip -
> which can be used to build the project using
> 
>mvn clean package
> 
> The resulting binaries can be installed into an Eclipse instance from
> the update site which is found at p2update/target/repository after
> building the project.
> 
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/sling/trunk/tooling/ide/check_staged_re
> lease.sh
> 
> Usage:
> sh check_staged_release.sh 1.2.0 /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
> 
> Thanks,
> 
> Robert

Re: [VOTE] Release Apache Sling IDE Tooling version 1.2.0

[Konrad Windszus]

Finally I got the right file. Seems that some intermediate cache (maybe some 
CDN?) still delivered the old version yesterday.
Now looks good although https://issues.apache.org/jira/browse/SLING-7403 
 is still not fixed.
But since this is only a minor issue I am gonna vote for release.

> On 19. Jan 2018, at 08:56, Robert Munteanu  wrote:
> 
> I think you're looking at the wrong file, somehow.
> 
>$ svn up
>Updating '.':
>At revision 24311.
>$ md5sum org.apache.sling.ide.p2update-1.2.0.zip
>36f4aadc5be250c4ed6654e9a3d17fb0  org.apache.sling.ide.p2update-1.2.0.zip
>$ cat org.apache.sling.ide.p2update-1.2.0.zip.md5 
>36f4aadc5be250c4ed6654e9a3d17fb0
> 
> Also, downloading the file results in an archive with the same checksum as 
> above.
> 
> Robert
> 
> On Thu, 2018-01-18 at 22:47 +0100, Konrad Windszus wrote:
>> I just redownloaded https://dist.apache.org/repos/dist/dev/sling/ide-
>> tooling-1.2.0/org.apache.sling.ide.p2update-1.2.0.zip > pache.org/repos/dist/dev/sling/ide-tooling-
>> 1.2.0/org.apache.sling.ide.p2update-1.2.0.zip>. Still the same issue
>> that the contained /plugins/org.apache.sling.ide.eclipse-ui_1.2.0.jar 
>> is in fact the core module.
>> The md5 for the downloaded zip is 2ffdab4588a047d493c78e5bce8e7f55.
>> Am I looking at the right thing?
>> 
>>> On 18. Jan 2018, at 22:33, Robert Munteanu 
>>> wrote:
>>> 
>>> On Thu, 2018-01-18 at 18:28 +0200, Robert Munteanu wrote:
 Hi Konrad,
 
 On Thu, 2018-01-18 at 16:54 +0100, Konrad Windszus wrote:
> Something must have gone really wrong. After more closely
> inspecting
> the contents of https://dist.apache.org/repos/dist/dev/sling/id
> e-to
> ol
> ing-1.2.0/org.apache.sling.ide.p2update-1.2.0.zip  .apa
> ch
> e.org/repos/dist/dev/sling/ide-tooling-
> 1.2.0/org.apache.sling.ide.p2update-1.2.0.zip> it seems that
> the
> contained "org.apache.sling.ide.eclipse-core_1.2.0.jar"
> contains
> the
> plugin.xml from the m2e-ui module. Also the other JARs look
> weird.
> @Robert: Can you check again?
 
 It seems that the jar contents are correct, but the names are
 mixed
 up.
 I'll look into a fix.
>>> 
>>> I have corrected the signing process and submitted the files with
>>> the
>>> correct names in the zip file.
>>> 
>>> I am not sure if we should respin the release, given that the
>>> artifacts
>>> are built from the exact same source code. At any rate, Konrad -
>>> can
>>> you please retest with the new artifacts?
>>> 
>>> Thanks,
>>> 
>>> Robert
>> 
>> 
> 

[jira] [Updated] (SLING-7403) Sling IDE: Provider and Plugin Name not provided for Sling IDE plugins

[Konrad Windszus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus updated SLING-7403:
---
Attachment: Eclipse_Installation_Details.png

> Sling IDE: Provider and Plugin Name not provided for Sling IDE plugins
> --
>
> Key: SLING-7403
> URL: https://issues.apache.org/jira/browse/SLING-7403
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.2.0
>Reporter: Konrad Windszus
>Priority: Major
> Attachments: Eclipse_Installation_Details.png, 
> Eclipse_Installation_Details_and_About_Eclipse.png
>
>
> When clicking on Eclipse -> About Eclipse -> Installation Details all plugins 
> from Sling are lacking the provider and plugin name details (see attached 
> screenshot). 
>  !Eclipse_Installation_Details_and_About_Eclipse.png! 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7403) Sling IDE: Provider and Plugin Name not provided for Sling IDE plugins

[Konrad Windszus (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332233#comment-16332233
 ] 

Konrad Windszus commented on SLING-7403:


Even with the updated version this is very sparsely filled. See updated screen 
!Eclipse_Installation_Details.png! 

> Sling IDE: Provider and Plugin Name not provided for Sling IDE plugins
> --
>
> Key: SLING-7403
> URL: https://issues.apache.org/jira/browse/SLING-7403
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.2.0
>Reporter: Konrad Windszus
>Priority: Major
> Attachments: Eclipse_Installation_Details.png, 
> Eclipse_Installation_Details_and_About_Eclipse.png
>
>
> When clicking on Eclipse -> About Eclipse -> Installation Details all plugins 
> from Sling are lacking the provider and plugin name details (see attached 
> screenshot). 
>  !Eclipse_Installation_Details_and_About_Eclipse.png! 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (SLING-7403) Sling IDE: Provider and Plugin Name not provided for Sling IDE plugins

[Konrad Windszus (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus reopened SLING-7403:


> Sling IDE: Provider and Plugin Name not provided for Sling IDE plugins
> --
>
> Key: SLING-7403
> URL: https://issues.apache.org/jira/browse/SLING-7403
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.2.0
>Reporter: Konrad Windszus
>Priority: Major
> Attachments: Eclipse_Installation_Details.png, 
> Eclipse_Installation_Details_and_About_Eclipse.png
>
>
> When clicking on Eclipse -> About Eclipse -> Installation Details all plugins 
> from Sling are lacking the provider and plugin name details (see attached 
> screenshot). 
>  !Eclipse_Installation_Details_and_About_Eclipse.png! 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7251) Fix pipes plumber servlet IT

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332219#comment-16332219
 ] 

Oliver Lietz commented on SLING-7251:
-

[~npeltier], didn't notice I had to activate ITs with profile... after that no 
succesful build at all.
The IT has several issues (don't forget: you're testing against real Sling):
* request is not authenticated
* IT uses private Pipes package ({{org.apache.sling.pipes.internal.JsonWriter}} 
and {{org.apache.sling.pipes.internal.JsonUtil}})
* there is no service user and ACL for Pipes

I've done some more optimization:
* updated to Parent 33-SNAPSHOT and Testing PaxExam 1.0.0-SNAPSHOT (not 
required, for convenience only) 
* added [Resource 
Presence|https://github.com/apache/sling-org-apache-sling-resource-presence] to 
ensure presence of {{/etc/pipes-it}}
* removed {{logging()}} as {{exam.properties}} is missing and log in 
{{target/failsafe-reports}} is sufficient

Please have a look at branch 
[issue/SLING-7251|https://github.com/apache/sling-org-apache-sling-pipes/tree/issue/SLING-7251].
* ACL should be improved
* {{assertEquals("there should be 2 elements", 2, ((Double) 
main.get("size")).intValue());}} is ugly
* use {{bnd-maven-plugin}} instead of {{maven-bundle-plugin}}


> Fix pipes plumber servlet IT 
> -
>
> Key: SLING-7251
> URL: https://issues.apache.org/jira/browse/SLING-7251
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: pipes 2.0.0
>Reporter: Nicolas Peltier
>Assignee: Oliver Lietz
>Priority: Major
>
> new Plumber servlet IT fail. This should be fixed



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7073) Update bundle versions

[Konrad Windszus (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332210#comment-16332210
 ] 

Konrad Windszus commented on SLING-7073:


We cannot upgrade {{com.google.code.findbugs:jsr305}} either due to 
https://github.com/amaembo/jsr-305/issues/31 (also outlined in 
https://sling.apache.org/documentation/development/jsr-305.html#annotations).

> Update bundle versions
> --
>
> Key: SLING-7073
> URL: https://issues.apache.org/jira/browse/SLING-7073
> Project: Sling
>  Issue Type: Sub-task
>  Components: Launchpad
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Starter 10
>
>
> Before the launchpad release, include the latest versions of external bundles 
> and also check that our own bundles are at the latest versions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SLING-7407) A thread pool with min size 1 uses only 1 thread for processing

[Chetan Mehrotra (JIRA)]

Chetan Mehrotra created SLING-7407:
--

 Summary: A thread pool with min size 1 uses only 1 thread for 
processing
 Key: SLING-7407
 URL: https://issues.apache.org/jira/browse/SLING-7407
 Project: Sling
  Issue Type: Improvement
  Components: Commons
Reporter: Chetan Mehrotra
 Fix For: Commons Threads 3.2.12


If a thread pool is configured like below

{noformat}
 org.apache.sling.commons.threads.impl.DefaultThreadPool.factory-oak
name="oak"
minPoolSize=I"1"
maxPoolSize=I"5"
{noformat}

Then only 1 thread would be used even if multiple jobs are assigned to the 
pool. This happens because of strange behaviour of Java 
[ThreadPoolExecutor|https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/ThreadPoolExecutor.html]

bq. If there are more than corePoolSize but less than maximumPoolSize threads 
running, a new thread will be created only *if the queue is full*

With unbounded queue used this lead to current behaviour. As a fix Sling Thread 
Pool should adapt such a config 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-7407) A thread pool with min size 1 uses only 1 thread for processing

[Chetan Mehrotra (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chetan Mehrotra updated SLING-7407:
---
Issue Type: Bug  (was: Improvement)

> A thread pool with min size 1 uses only 1 thread for processing
> ---
>
> Key: SLING-7407
> URL: https://issues.apache.org/jira/browse/SLING-7407
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Reporter: Chetan Mehrotra
>Priority: Major
> Fix For: Commons Threads 3.2.12
>
>
> If a thread pool is configured like below
> {noformat}
>  org.apache.sling.commons.threads.impl.DefaultThreadPool.factory-oak
> name="oak"
> minPoolSize=I"1"
> maxPoolSize=I"5"
> {noformat}
> Then only 1 thread would be used even if multiple jobs are assigned to the 
> pool. This happens because of strange behaviour of Java 
> [ThreadPoolExecutor|https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/ThreadPoolExecutor.html]
> bq. If there are more than corePoolSize but less than maximumPoolSize threads 
> running, a new thread will be created only *if the queue is full*
> With unbounded queue used this lead to current behaviour. As a fix Sling 
> Thread Pool should adapt such a config 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SLING-7406) Provide HTL specification version info in artifact names

[Radu Cotescu (JIRA)]

Radu Cotescu created SLING-7406:
---

 Summary: Provide HTL specification version info in artifact names
 Key: SLING-7406
 URL: https://issues.apache.org/jira/browse/SLING-7406
 Project: Sling
  Issue Type: Improvement
  Components: Scripting, Tooling
Reporter: Radu Cotescu
Assignee: Radu Cotescu
 Fix For: Scripting HTL Java Compiler 1.0.22-1.3.1, HTL Maven 
Plugin 1.1.4-1.3.1, Scripting HTL Compiler 1.0.20-1.3.1, Scripting HTL Engine 
1.0.48-1.3.1


As discussed in \[0\], the HTL modules versioning scheme should be updated to 
reflect what HTP specification version they support, in addition to the bundle 
headers the modules already provide.

\[0\] - 
https://lists.apache.org/thread.html/ea63bcfe6fd75b6318b4e27d88b67d9783d945baecef692a5d08ae75@%3Cdev.sling.apache.org%3E



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-7404) ObjectModel and similar classes need consistent null checks

[Radu Cotescu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-7404:

Fix Version/s: Scripting HTL Engine 1.0.48-1.3.1
   Scripting HTL Compiler 1.0.20-1.3.1
   Scripting HTL Java Compiler 1.0.22-1.3.1

> ObjectModel and similar classes need consistent null checks
> ---
>
> Key: SLING-7404
> URL: https://issues.apache.org/jira/browse/SLING-7404
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting HTL Engine 1.0.38, Scripting HTL Compiler 
> 1.0.12, Scripting HTL Java Compiler 1.0.12
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Java Compiler 1.0.22-1.3.1, Scripting HTL 
> Compiler 1.0.20-1.3.1, Scripting HTL Engine 1.0.48-1.3.1
>
>
> {{org.apache.sling.scripting.sightly.compiler.util.ObjectModel}} and similar 
> classes need consistent null checks, so that none of the public methods can 
> throw a {{NullPointerException}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [proposal] HTL modules versioning scheme

[Radu Cotescu]

Hello Oliver,

The ScriptEngineFactory already exposes this info. I just want to be able
to figure out the spec version from the module's file name. In the end I
will go with Robert's proposal.

The way HTL is implemented right now is that we have front-end and back-end
compilers (which are Sling API independent), and then there's the Script
Engine module that glues everything into Sling's platform, which is why,
IMO, the info about which specification is supported should be present in
all modules in a way or another.

Cheers,
Radu

On Fri, 19 Jan 2018 at 10:24 Oliver Lietz  wrote:

>
>
> that is not quite correct. The language version is exposed by the
> ScriptEngineFactory (JSR 223).
>
> I would not couple bundle version to language version at all (it's fine to
> have multiple engines per bundle, e.g. one for 1.x and another for 2.x).
>
> Regards,
> O.
>

[jira] [Commented] (SLING-7073) Update bundle versions

[Robert Munteanu (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332137#comment-16332137
 ] 

Robert Munteanu commented on SLING-7073:


The full report is: {noformat}[INFO] The following dependencies in Dependency 
Management have newer versions:
[INFO]   com.google.code.findbugs:jsr305 ... 3.0.0 -> 3.0.2
[INFO]   javax.servlet:javax.servlet-api ... 3.1.0 -> 4.0.0
[INFO]   org.jmock:jmock-junit4  2.8.2 -> 2.8.4
[INFO]   org.slf4j:slf4j-api  1.7.25 -> 1.8.0-beta0
[INFO]   org.slf4j:slf4j-simple . 1.7.25 -> 1.8.0-beta0

[INFO] The following dependencies in Dependencies have newer versions:
[INFO]   com.fasterxml.jackson.core:jackson-annotations  2.8.7 -> 2.9.3
[INFO]   com.fasterxml.jackson.core:jackson-core ... 2.8.7 -> 2.9.3
[INFO]   com.fasterxml.jackson.core:jackson-databind ... 2.8.7 -> 2.9.3
[INFO]   com.google.guava:guava .. 15.0 -> 23.6-jre
[INFO]   com.h2database:h2-mvstore . 1.4.194 -> 1.4.196
[INFO]   commons-codec:commons-codec .. 1.9 -> 1.11
[INFO]   commons-collections:commons-collections  3.2.2 -> 20040616
[INFO]   commons-fileupload:commons-fileupload . 1.3.2 -> 1.3.3
[INFO]   commons-io:commons-io . 2.5 -> 2.6
[INFO]   io.dropwizard.metrics:metrics-core  3.2.4 -> 4.0.2
[INFO]   javax.mail:mail ... 1.4.7 -> 1.5.0-b01
[INFO]   org.apache.aries.jmx:org.apache.aries.jmx.core  1.1.7 -> 1.1.8
[INFO]   org.apache.aries.jmx:org.apache.aries.jmx.whiteboard ...
[INFO]   1.1.5 -> 1.2.0
[INFO]   org.apache.commons:commons-lang3 .. 3.6 -> 3.7
[INFO]   org.apache.felix:org.apache.felix.bundlerepository ... 1.6.4 -> 2.0.10
[INFO]   org.apache.felix:org.apache.felix.http.jetty .. 3.4.6 -> 3.4.8
[INFO]   org.apache.felix:org.apache.felix.inventory ... 1.0.4 -> 1.0.6
[INFO]   org.apache.felix:org.apache.felix.utils .. 1.9.0 -> 1.10.4
[INFO]   org.apache.geronimo.bundles:commons-httpclient  3.1_1 -> 3.1_2
[INFO]   org.apache.httpcomponents:httpclient .. 4.5.2 -> 4.5.4
[INFO]   org.apache.httpcomponents:httpclient-osgi . 4.4.1 -> 4.5.4
[INFO]   org.apache.httpcomponents:httpcore-osgi ... 4.4.1 -> 4.4.9
[INFO]   org.apache.jackrabbit:jackrabbit-api  2.14.4 -> 2.17.0
[INFO]   org.apache.jackrabbit:jackrabbit-data ... 2.14.4 -> 2.17.0
[INFO]   org.apache.jackrabbit:jackrabbit-jcr-commons  2.14.4 -> 2.17.0
[INFO]   org.apache.jackrabbit:jackrabbit-jcr-rmi  2.14.4 -> 2.17.0
[INFO]   org.apache.jackrabbit:jackrabbit-spi  2.14.4 -> 2.17.0
[INFO]   org.apache.jackrabbit:jackrabbit-spi-commons  2.14.4 -> 2.17.0
[INFO]   org.apache.jackrabbit:jackrabbit-webdav . 2.14.4 -> 2.17.0
[INFO]   org.apache.jackrabbit:oak-blob  1.6.8 -> 1.8.0
[INFO]   org.apache.jackrabbit:oak-commons . 1.6.8 -> 1.8.0
[INFO]   org.apache.jackrabbit:oak-core  1.6.8 -> 1.8.0
[INFO]   org.apache.jackrabbit:oak-jcr . 1.6.8 -> 1.8.0
[INFO]   org.apache.jackrabbit:oak-lucene .. 1.6.8 -> 1.8.0
[INFO]   org.apache.jackrabbit:oak-segment-tar . 1.6.8 -> 1.8.0
[INFO]   org.apache.jackrabbit.vault:org.apache.jackrabbit.vault ...
[INFO] 3.1.30 -> 3.1.42
[INFO]   org.apache.pdfbox:fontbox . 2.0.7 -> 2.0.8
[INFO]   org.apache.pdfbox:pdfbox .. 2.0.7 -> 2.0.8
[INFO]   org.apache.servicemix.bundles:org.apache.servicemix.bundles.rhino ...
[INFO]   1.7.7.1_1 -> 1.7.7.2_1
[INFO]   org.apache.sling:org.apache.sling.caconfig.impl .. 1.4.6 -> 1.4.10
[INFO]   org.apache.sling:org.apache.sling.commons.compiler  2.3.4 -> 2.3.6
[INFO]   org.apache.sling:org.apache.sling.discovery.base .. 2.0.0 -> 2.0.4
[INFO]   org.apache.sling:org.apache.sling.discovery.oak . 1.2.18 -> 1.2.22
[INFO]   
org.apache.sling:org.apache.sling.extensions.webconsolesecurityprovider ...
[INFO]   1.0.0 -> 1.2.0
[INFO]   org.apache.sling:org.apache.sling.fsresource . 2.1.8 -> 2.1.10
[INFO]   org.apache.sling:org.apache.sling.i18n ... 2.5.8 -> 2.5.10
[INFO]   org.apache.sling:org.apache.sling.jcr.registration  1.0.2 -> 1.0.4
[INFO]   org.apache.sling:org.apache.sling.models.impl . 1.4.4 -> 1.4.6
[INFO]   

[jira] [Assigned] (SLING-7073) Update bundle versions

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu reassigned SLING-7073:
--

Assignee: Robert Munteanu

> Update bundle versions
> --
>
> Key: SLING-7073
> URL: https://issues.apache.org/jira/browse/SLING-7073
> Project: Sling
>  Issue Type: Sub-task
>  Components: Launchpad
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Starter 10
>
>
> Before the launchpad release, include the latest versions of external bundles 
> and also check that our own bundles are at the latest versions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (SLING-7365) Some JSP tests fail under Java 10 - parameterized types are only available if source level is 1.5 or greater

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu closed SLING-7365.
--

> Some JSP tests fail under Java 10 -  parameterized types are only available 
> if source level is 1.5 or greater
> -
>
> Key: SLING-7365
> URL: https://issues.apache.org/jira/browse/SLING-7365
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Affects Versions: Commons Compiler 2.3.4
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>  Labels: Sling-10-ReleaseNotes
> Fix For: Commons Compiler 2.3.6
>
>
> {noformat}An error occurred at line: 792 in the generated java file
> Syntax error, parameterized types are only available if source level is 1.5 
> or greater
>   at 
> org.apache.sling.scripting.jsp.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:92)
>   at 
> org.apache.sling.scripting.jsp.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:330)
>   at 
> org.apache.sling.scripting.jsp.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:136)
>   at 
> org.apache.sling.scripting.jsp.jasper.compiler.Compiler.compile(Compiler.java:304)
>   at 
> org.apache.sling.scripting.jsp.jasper.compiler.Compiler.compile(Compiler.java:282)
>   at 
> org.apache.sling.scripting.jsp.jasper.compiler.Compiler.compile(Compiler.java:269)
>   at 
> org.apache.sling.scripting.jsp.jasper.JspCompilationContext.compile(JspCompilationContext.java:501)
>   at 
> org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.prepareServlet(JspServletWrapper.java:427)
>   at 
> org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:486)
>   at 
> org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:449)
>   at 
> org.apache.sling.scripting.jsp.JspScriptEngineFactory.callJsp(JspScriptEngineFactory.java:342)
>   at 
> org.apache.sling.scripting.jsp.JspScriptEngineFactory.access$100(JspScriptEngineFactory.java:97)
>   at 
> org.apache.sling.scripting.jsp.JspScriptEngineFactory$JspScriptEngine.eval(JspScriptEngineFactory.java:603)
>   at 
> org.apache.sling.scripting.core.impl.DefaultSlingScript.call(DefaultSlingScript.java:388)
>   at 
> org.apache.sling.scripting.core.impl.DefaultSlingScript.eval(DefaultSlingScript.java:184)
>   at 
> org.apache.sling.scripting.core.impl.DefaultSlingScript.service(DefaultSlingScript.java:491)
>   at 
> org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:552)
>   at 
> org.apache.sling.engine.impl.filter.SlingComponentFilterChain.render(SlingComponentFilterChain.java:44)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:77)
>   at 
> org.apache.sling.engine.impl.SlingRequestProcessorImpl.processComponent(SlingRequestProcessorImpl.java:282)
>   at 
> org.apache.sling.engine.impl.filter.RequestSlingFilterChain.render(RequestSlingFilterChain.java:49)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:77)
>   at 
> org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter.doFilter(RequestProgressTrackerLogFilter.java:107)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:68)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:73)
>   at 
> org.apache.sling.launchpad.testservices.filters.TestFilter.doFilter(TestFilter.java:47)
>   at 
> org.apache.sling.launchpad.testservices.filters.NoPropertyFilter.doFilter(NoPropertyFilter.java:25)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:68)
>   at 
> org.apache.sling.launchpad.testservices.filters.TestFilter.doFilter(TestFilter.java:47)
>   at 
> org.apache.sling.launchpad.testservices.filters.SlingFilter.doFilter(SlingFilter.java:25)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:68)
>   at org.apache.sling.i18n.impl.I18NFilter.doFilter(I18NFilter.java:138)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:68)
>   at 
> org.apache.sling.engine.impl.SlingRequestProcessorImpl.doProcessRequest(SlingRequestProcessorImpl.java:151)
>   at 
> org.apache.sling.engine.impl.SlingMainServlet.service(SlingMainServlet.java:234)
>   at 
> 

[RESULT] [VOTE] Release Apache Sling Commons Java Compiler version 2.3.6

[Robert Munteanu]

Hi,

The vote has passed with the following result :

+1 (binding): Konrad Windszus, Daniel Klco, Radu Cotescu, Robert
Munteanu.

I will copy this release to the Sling dist directory and promote the
artifacts to the central Maven repository.

Thanks,

Robert

Re: [Fwd: [apache/sling-org-apache-sling-testing-clients] @trivial - The poller should wait for the delay even in case of exceptions (#4)]

[Robert Munteanu]

On Fri, 2018-01-19 at 10:29 +, Andrei Dulvac wrote:
> Hi Robert.
> 
> Agree on all points above :)
> 
> I'll create an issue and link it.

Thanks!.

Robert

[jira] [Updated] (SLING-7405) [o.a.s.testing.clients] The poller in {{Polling}} should wait for the delay even in case of exceptions

[Andrei Dulvac (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrei Dulvac updated SLING-7405:
-
Description: In case of an exception, 
[{{Polling#poll}}|[https://github.com/andreituicu/sling-org-apache-sling-testing-clients/blob/master/src/main/java/org/apache/sling/testing/clients/util/poller/Polling.java]]
 doesn't get to the {{Thread.sleep}}  (was: In case of an exception, 
{{Polling#poll}} 
([https://github.com/andreituicu/sling-org-apache-sling-testing-clients/blob/master/src/main/java/org/apache/sling/testing/clients/util/poller/Polling.java|https://github.com/andreituicu/sling-org-apache-sling-testing-clients/blob/master/src/main/java/org/apache/sling/testing/clients/util/poller/Polling.java)]
 doesn't get to the {{Thread.sleep}})

> [o.a.s.testing.clients] The poller in {{Polling}} should wait for the delay 
> even in case of exceptions
> --
>
> Key: SLING-7405
> URL: https://issues.apache.org/jira/browse/SLING-7405
> Project: Sling
>  Issue Type: Bug
>  Components: Apache Sling Testing Clients
>Affects Versions: Apache Sling Testing Clients 1.1.12
>Reporter: Andrei Dulvac
>Assignee: Andrei Dulvac
>Priority: Major
> Fix For: Apache Sling Testing Clients 1.1.14
>
>
> In case of an exception, 
> [{{Polling#poll}}|[https://github.com/andreituicu/sling-org-apache-sling-testing-clients/blob/master/src/main/java/org/apache/sling/testing/clients/util/poller/Polling.java]]
>  doesn't get to the {{Thread.sleep}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (SLING-3967) Define replication strategy for big trees

[Dirk Rudolph (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332072#comment-16332072
 ] 

Dirk Rudolph edited comment on SLING-3967 at 1/19/18 10:41 AM:
---

Another thing that counts in here is guarantee of processing. With introduction 
of supporting other systems then sling and with supporting any customisation in 
the serialisation of DistributionRequests the time and resources taken to 
export a "package" in whether format this will be is undefined. So the bigger 
the DistributionRequests are the more likely it might become that creating the 
package already fails - which depending on the trigger used might cause the 
loss of the entire request. 

For example. Using SCD to index solr for binary documents might require parsing 
them with tika and sending only the plaintext as result. Depending on documents 
to distribute it might make sense to split the DistributionRequest to achieve 
an approximated mean of package creation time.

This can probably be done on DistributionPackageExporter level (not taking deep 
paths into account) or on DistributionPackageBuilder level which would require 
an API change to be made. 


was (Author: diru):
Another thing that counts in here is guarantee of processing. With introduction 
of supporting other systems then sling and with supporting any customisation in 
the serialisation of DistributionRequests the time and resources taken to 
export a "package" in whether format this will be is undefined. So the bigger 
the DistributionRequests are the more likely it might become that creating the 
package already fails - which depending on the trigger used might cause the 
loss of the entire request. 

For example. Using SCD to index solr for binary documents might require parsing 
them with tika and sending only the plaintext as result. Depending on documents 
to distribute it might make sense to split the DistributionRequest to achieve 
an approximated mean of package creation time.

This looks like a change being necessary in the 
LocalDistributionPackageExporter only if deep paths are not taken into account.

> Define replication strategy for big trees
> -
>
> Key: SLING-3967
> URL: https://issues.apache.org/jira/browse/SLING-3967
> Project: Sling
>  Issue Type: Improvement
>  Components: Content Distribution
>Reporter: Marius Petria
>Priority: Major
>
> An extreme case for replication is the replication of an entire big tree (for 
> example a /content/bigtree/* with GBs of content).
> One should be able to define a way to replicate this in smaller packages such 
> that it does not creates too big packages that affect performance.
> Options to do the split:
> - number of nodes (every 100 nodes)
> - size of data (every 100 MB)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-7405) [o.a.s.testing.clients] The poller in {{Polling}} should wait for the delay even in case of exceptions

[Andrei Dulvac (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrei Dulvac updated SLING-7405:
-
Description: In case of an exception, 
[Polling#poll|https://github.com/andreituicu/sling-org-apache-sling-testing-clients/blob/master/src/main/java/org/apache/sling/testing/clients/util/poller/Polling.java]
 doesn't get to the {{Thread.sleep}}  (was: In case of an exception, 
[{{Polling#poll}}|[https://github.com/andreituicu/sling-org-apache-sling-testing-clients/blob/master/src/main/java/org/apache/sling/testing/clients/util/poller/Polling.java]]
 doesn't get to the {{Thread.sleep}})

> [o.a.s.testing.clients] The poller in {{Polling}} should wait for the delay 
> even in case of exceptions
> --
>
> Key: SLING-7405
> URL: https://issues.apache.org/jira/browse/SLING-7405
> Project: Sling
>  Issue Type: Bug
>  Components: Apache Sling Testing Clients
>Affects Versions: Apache Sling Testing Clients 1.1.12
>Reporter: Andrei Dulvac
>Assignee: Andrei Dulvac
>Priority: Major
> Fix For: Apache Sling Testing Clients 1.1.14
>
>
> In case of an exception, 
> [Polling#poll|https://github.com/andreituicu/sling-org-apache-sling-testing-clients/blob/master/src/main/java/org/apache/sling/testing/clients/util/poller/Polling.java]
>  doesn't get to the {{Thread.sleep}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-7405) [o.a.s.testing.clients] The poller in {{Polling}} should wait for the delay even in case of exceptions

[Andrei Dulvac (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrei Dulvac updated SLING-7405:
-
Description: In case of an exception, {{Polling#poll}} 
([https://github.com/andreituicu/sling-org-apache-sling-testing-clients/blob/master/src/main/java/org/apache/sling/testing/clients/util/poller/Polling.java|https://github.com/andreituicu/sling-org-apache-sling-testing-clients/blob/master/src/main/java/org/apache/sling/testing/clients/util/poller/Polling.java)]
 doesn't get to the {{Thread.sleep}}  (was: In case of an exception, 
{{Polling#poll}} 
([https://github.com/andreituicu/sling-org-apache-sling-testing-clients/blob/master/src/main/java/org/apache/sling/testing/clients/util/poller/Polling.java)]
 doesn't get to the {{Thread.sleep}})

> [o.a.s.testing.clients] The poller in {{Polling}} should wait for the delay 
> even in case of exceptions
> --
>
> Key: SLING-7405
> URL: https://issues.apache.org/jira/browse/SLING-7405
> Project: Sling
>  Issue Type: Bug
>  Components: Apache Sling Testing Clients
>Affects Versions: Apache Sling Testing Clients 1.1.12
>Reporter: Andrei Dulvac
>Assignee: Andrei Dulvac
>Priority: Major
> Fix For: Apache Sling Testing Clients 1.1.14
>
>
> In case of an exception, {{Polling#poll}} 
> ([https://github.com/andreituicu/sling-org-apache-sling-testing-clients/blob/master/src/main/java/org/apache/sling/testing/clients/util/poller/Polling.java|https://github.com/andreituicu/sling-org-apache-sling-testing-clients/blob/master/src/main/java/org/apache/sling/testing/clients/util/poller/Polling.java)]
>  doesn't get to the {{Thread.sleep}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (SLING-7361) CAConfig Impl: Fix potential NPE in ConfigurationBuilder

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert closed SLING-7361.
-

> CAConfig Impl: Fix potential NPE in ConfigurationBuilder
> 
>
> Key: SLING-7361
> URL: https://issues.apache.org/jira/browse/SLING-7361
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Context-Aware Configuration Impl 1.4.8
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Major
>  Labels: contextaware-config
> Fix For: Context-Aware Configuration Impl 1.4.10
>
>
> the method ConfigurationBuilderImpl.convert accesses a configResource object 
> which may be null at this position.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (SLING-7405) [o.a.s.testing.clients] The poller in {{Polling}} should wait for the delay even in case of exceptions

[Andrei Dulvac (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrei Dulvac resolved SLING-7405.
--
Resolution: Fixed

Fixed in 
[https://github.com/apache/sling-org-apache-sling-testing-clients/pull/4]

Thanks [~andrei.tuicu]

> [o.a.s.testing.clients] The poller in {{Polling}} should wait for the delay 
> even in case of exceptions
> --
>
> Key: SLING-7405
> URL: https://issues.apache.org/jira/browse/SLING-7405
> Project: Sling
>  Issue Type: Bug
>  Components: Apache Sling Testing Clients
>Affects Versions: Apache Sling Testing Clients 1.1.12
>Reporter: Andrei Dulvac
>Assignee: Andrei Dulvac
>Priority: Major
> Fix For: Apache Sling Testing Clients 1.1.14
>
>
> In case of an exception, {{Polling#poll}} 
> ([https://github.com/andreituicu/sling-org-apache-sling-testing-clients/blob/master/src/main/java/org/apache/sling/testing/clients/util/poller/Polling.java)]
>  doesn't get to the {{Thread.sleep}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[RESULT] [VOTE] Release Apache Sling Context-Aware Configuration Impl 1.4.10

[Stefan Seifert]

Hi,

The vote has passed with the following result :

+1 (binding): Stefan Seifert, Robert Munteanu, Radu Cotescu, Daniel Klco

I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.

stefan

[jira] [Created] (SLING-7405) [o.a.s.testing.clients] The poller in {{Polling}} should wait for the delay even in case of exceptions

[Andrei Dulvac (JIRA)]

Andrei Dulvac created SLING-7405:


 Summary: [o.a.s.testing.clients] The poller in {{Polling}} should 
wait for the delay even in case of exceptions
 Key: SLING-7405
 URL: https://issues.apache.org/jira/browse/SLING-7405
 Project: Sling
  Issue Type: Bug
  Components: Apache Sling Testing Clients
Affects Versions: Apache Sling Testing Clients 1.1.12
Reporter: Andrei Dulvac
Assignee: Andrei Dulvac
 Fix For: Apache Sling Testing Clients 1.1.14


In case of an exception, {{Polling#poll}} 
([https://github.com/andreituicu/sling-org-apache-sling-testing-clients/blob/master/src/main/java/org/apache/sling/testing/clients/util/poller/Polling.java)]
 doesn't get to the {{Thread.sleep}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-7297) OSGiConsoleClient: Add methods to wait for OSGi components and OSGi services

[Andrei Dulvac (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrei Dulvac updated SLING-7297:
-
Fix Version/s: Apache Sling Testing Clients 1.1.14

> OSGiConsoleClient: Add methods to wait for OSGi components and OSGi services
> 
>
> Key: SLING-7297
> URL: https://issues.apache.org/jira/browse/SLING-7297
> Project: Sling
>  Issue Type: Improvement
>  Components: Apache Sling Testing Clients
>Affects Versions: Apache Sling Testing Clients 1.1.12
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: Apache Sling Testing Clients 1.1.14
>
>
> Sometimes in an IT you need to wait for a specific OSGi component or service 
> to be available (i.e. active). Just waiting for the bundle is not necessarily 
> enough, as the contained services/components might not yet have been started. 
> Therefore having the following additional two methods would be beneficial: 
> # {{waitComponentRegistered(String componentName, long, long}} to wait until 
> the component with given name is active and 
> # {{waitServiceRegistered(String Type, String bundleSymbolicName, long, 
> long)}} to wait until a service of the given type is available. If the 
> bundleSymbolicName is not null it should also check that this service is 
> being registered from the given bundle.
> The following ReST calls against the Apache Felix WebConsole can be used to 
> check for that.
> {{/system/console/components/.json}} returns metadata about a 
> specific component. All services are listed via 
> {{/system/console/services.json}}. This can be used to extract information 
> about a specific service.
> Unfortunately there is not yet the possibility to extract services by type 
> (FELIX-5761).
> See also the related discussion at: 
> https://mail.osgi.org/pipermail/osgi-dev/2017-December/006638.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (SLING-7297) OSGiConsoleClient: Add methods to wait for OSGi components and OSGi services

[Andrei Dulvac (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrei Dulvac resolved SLING-7297.
--
Resolution: Fixed
  Assignee: Andrei Dulvac

> OSGiConsoleClient: Add methods to wait for OSGi components and OSGi services
> 
>
> Key: SLING-7297
> URL: https://issues.apache.org/jira/browse/SLING-7297
> Project: Sling
>  Issue Type: Improvement
>  Components: Apache Sling Testing Clients
>Affects Versions: Apache Sling Testing Clients 1.1.12
>Reporter: Konrad Windszus
>Assignee: Andrei Dulvac
>Priority: Major
> Fix For: Apache Sling Testing Clients 1.1.14
>
>
> Sometimes in an IT you need to wait for a specific OSGi component or service 
> to be available (i.e. active). Just waiting for the bundle is not necessarily 
> enough, as the contained services/components might not yet have been started. 
> Therefore having the following additional two methods would be beneficial: 
> # {{waitComponentRegistered(String componentName, long, long}} to wait until 
> the component with given name is active and 
> # {{waitServiceRegistered(String Type, String bundleSymbolicName, long, 
> long)}} to wait until a service of the given type is available. If the 
> bundleSymbolicName is not null it should also check that this service is 
> being registered from the given bundle.
> The following ReST calls against the Apache Felix WebConsole can be used to 
> check for that.
> {{/system/console/components/.json}} returns metadata about a 
> specific component. All services are listed via 
> {{/system/console/services.json}}. This can be used to extract information 
> about a specific service.
> Unfortunately there is not yet the possibility to extract services by type 
> (FELIX-5761).
> See also the related discussion at: 
> https://mail.osgi.org/pipermail/osgi-dev/2017-December/006638.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

RE: [VOTE] Release Apache Sling Servlets Post 2.3.24

[Stefan Seifert]

+1

Re: [Fwd: [apache/sling-org-apache-sling-testing-clients] @trivial - The poller should wait for the delay even in case of exceptions (#4)]

[Andrei Dulvac]

Hi Robert.

Agree on all points above :)

I'll create an issue and link it.

- Andrei

On Thu, Jan 18, 2018 at 5:17 PM Robert Munteanu  wrote:

> Hi Andrei,
>
> Even though '@trivial', these kind of changes deserve their own Jira
> issue. Please create one after the fact and link to commit to it ( via
> a Jira comment).
>
> I agree not all changes need a Jira issue, but 'trivial' issues IMO are
> mostly formatting and Javadoc fixes, not ones that change behaviour.
>
> Thanks,
>
> Robert
>
> P.S. We should stop mentioning https://github.com/trivial on our
> commits, I guess it's kind of annoying :-)
>
>
> -- Forwarded message --
> From: Andrei Tuicu 
> To: "apache/sling-org-apache-sling-testing-clients" <
> sling-org-apache-sling-testing-clie...@noreply.github.com>
> Cc: Subscribed 
> Bcc:
> Date: Thu, 18 Jan 2018 14:47:03 + (UTC)
> Subject: [apache/sling-org-apache-sling-testing-clients] @trivial - The
> poller should wait for the delay even in case of exceptions (#4)
> --
> You can view, comment on, or merge this pull request online at:
>
>   https://github.com/apache/sling-org-apache-sling-testing-clients/pull/4
> Commit Summary
>
>- @trivial - The poller should wait for the delay even in case of
>exceptions
>
> File Changes
>
>- *M*
>src/main/java/org/apache/sling/testing/clients/util/poller/Polling.java
>
> 
>(4)
>
> Patch Links:
>
>-
>
> https://github.com/apache/sling-org-apache-sling-testing-clients/pull/4.patch
>-
>
> https://github.com/apache/sling-org-apache-sling-testing-clients/pull/4.diff
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> ,
> or mute the thread
> 
> .
>

[jira] [Comment Edited] (SLING-3967) Define replication strategy for big trees

[Dirk Rudolph (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332072#comment-16332072
 ] 

Dirk Rudolph edited comment on SLING-3967 at 1/19/18 10:25 AM:
---

Another thing that counts in here is guarantee of processing. With introduction 
of supporting other systems then sling and with supporting any customisation in 
the serialisation of DistributionRequests the time and resources taken to 
export a "package" in whether format this will be is undefined. So the bigger 
the DistributionRequests are the more likely it might become that creating the 
package already fails - which depending on the trigger used might cause the 
loss of the entire request. 

For example. Using SCD to index solr for binary documents might require parsing 
them with tika and sending only the plaintext as result. Depending on documents 
to distribute it might make sense to split the DistributionRequest to achieve 
an approximated mean of package creation time.

This looks like a change being necessary in the 
LocalDistributionPackageExporter only if deep paths are not taken into account.


was (Author: diru):
Another thing that counts in here is guarantee of processing. With introduction 
of supporting other systems then sling and with supporting any customisation in 
the serialisation of DistributionRequests the time and resources taken to 
export a "package" in whether format this will be is undefined. So the bigger 
the DistributionRequests are the more likely it might become that creating the 
package already fails - which depending on the trigger used might cause the 
loss of the entire request. 

For example. Using SCD to index solr for binary documents might require parsing 
them with tika and sending only the plaintext as result. Depending on documents 
to distribute it might make sense to split the DistributionRequest to achieve 
an approximated mean of package creation time.

This looks like a change being necessary in the 
LocalDistributionPackageExporter only.

> Define replication strategy for big trees
> -
>
> Key: SLING-3967
> URL: https://issues.apache.org/jira/browse/SLING-3967
> Project: Sling
>  Issue Type: Improvement
>  Components: Content Distribution
>Reporter: Marius Petria
>Priority: Major
>
> An extreme case for replication is the replication of an entire big tree (for 
> example a /content/bigtree/* with GBs of content).
> One should be able to define a way to replicate this in smaller packages such 
> that it does not creates too big packages that affect performance.
> Options to do the split:
> - number of nodes (every 100 nodes)
> - size of data (every 100 MB)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (SLING-3967) Define replication strategy for big trees

[Dirk Rudolph (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332072#comment-16332072
 ] 

Dirk Rudolph edited comment on SLING-3967 at 1/19/18 10:20 AM:
---

Another thing that counts in here is guarantee of processing. With introduction 
of supporting other systems then sling and with supporting any customisation in 
the serialisation of DistributionRequests the time and resources taken to 
export a "package" in whether format this will be is undefined. So the bigger 
the DistributionRequests are the more likely it might become that creating the 
package already fails - which depending on the trigger used might cause the 
loss of the entire request. 

For example. Using SCD to index solr for binary documents might require parsing 
them with tika and sending only the plaintext as result. Depending on documents 
to distribute it might make sense to split the DistributionRequest to achieve 
an approximated mean of package creation time.

This looks like a change being necessary in the 
LocalDistributionPackageExporter only.


was (Author: diru):
Another thing that counts in here is guarantee of processing. With introduction 
of supporting other systems then sling and with supporting any customisation in 
the serialisation of DistributionRequests the time and resources taken to 
export a "package" in whether format this will be is undefined. So the bigger 
the DistributionRequests are the more likely it might become that creating the 
package already fails - which depending on the trigger used might cause the 
loss of the entire request. 

For example. Using SCD to index solr for binary documents might require parsing 
them with tika and sending only the plaintext as result. Depending on documents 
to distribute it might make sense to split the DistributionRequest to achieve 
an approximated mean of package creation time.

> Define replication strategy for big trees
> -
>
> Key: SLING-3967
> URL: https://issues.apache.org/jira/browse/SLING-3967
> Project: Sling
>  Issue Type: Improvement
>  Components: Content Distribution
>Reporter: Marius Petria
>Priority: Major
>
> An extreme case for replication is the replication of an entire big tree (for 
> example a /content/bigtree/* with GBs of content).
> One should be able to define a way to replicate this in smaller packages such 
> that it does not creates too big packages that affect performance.
> Options to do the split:
> - number of nodes (every 100 nodes)
> - size of data (every 100 MB)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-3967) Define replication strategy for big trees

[Dirk Rudolph (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332072#comment-16332072
 ] 

Dirk Rudolph commented on SLING-3967:
-

Another thing that counts in here is guarantee of processing. With introduction 
of supporting other systems then sling and with supporting any customisation in 
the serialisation of DistributionRequests the time and resources taken to 
export a "package" in whether format this will be is undefined. So the bigger 
the DistributionRequests are the more likely it might become that creating the 
package already fails - which depending on the trigger used might cause the 
loss of the entire request. 

For example. Using SCD to index solr for binary documents might require parsing 
them with tika and sending only the plaintext as result. Depending on documents 
to distribute it might make sense to split the DistributionRequest to achieve 
an approximated mean of package creation time.

> Define replication strategy for big trees
> -
>
> Key: SLING-3967
> URL: https://issues.apache.org/jira/browse/SLING-3967
> Project: Sling
>  Issue Type: Improvement
>  Components: Content Distribution
>Reporter: Marius Petria
>Priority: Major
>
> An extreme case for replication is the replication of an entire big tree (for 
> example a /content/bigtree/* with GBs of content).
> One should be able to define a way to replicate this in smaller packages such 
> that it does not creates too big packages that affect performance.
> Options to do the split:
> - number of nodes (every 100 nodes)
> - size of data (every 100 MB)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7251) Fix pipes plumber servlet IT

[Nicolas Peltier (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332021#comment-16332021
 ] 

Nicolas Peltier commented on SLING-7251:


[~olli] interesting. How long does the tests take for you (good indicator of 
load i guess):

 

for me

{Code}

---
 T E S T S
---
Running org.apache.sling.pipes.it.PipeBuilderIT
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 21.548 sec - in 
org.apache.sling.pipes.it.PipeBuilderIT
Running org.apache.sling.pipes.it.PlumberTestIT
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.367 sec - in 
org.apache.sling.pipes.it.PlumberTestIT
Running org.apache.sling.pipes.it.PlumberServletIT
Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 14.186 sec - in 
org.apache.sling.pipes.it.PlumberServletIT
Running org.apache.sling.pipes.it.PipeModelIT
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 18.167 sec <<< 
FAILURE! - in org.apache.sling.pipes.it.PipeModelIT
testListComponent(org.apache.sling.pipes.it.PipeModelIT)  Time elapsed: 3.586 
sec  <<< ERROR!
java.io.FileNotFoundException: 
http://localhost:62056/content/list-component.html
    at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1872)
    at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474)
    at java.net.URL.openStream(URL.java:1045)
    at 
org.apache.sling.pipes.it.PipeModelIT.testListComponent(PipeModelIT.java:53)

{Code}

> Fix pipes plumber servlet IT 
> -
>
> Key: SLING-7251
> URL: https://issues.apache.org/jira/browse/SLING-7251
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: pipes 2.0.0
>Reporter: Nicolas Peltier
>Assignee: Oliver Lietz
>Priority: Major
>
> new Plumber servlet IT fail. This should be fixed



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (SLING-7251) Fix pipes plumber servlet IT

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz reopened SLING-7251:
-
  Assignee: Oliver Lietz

[~npeltier], no – not a single failure after nearly 20 builds on my system. 
Will enable the test and build every 15 mins on Jenkins.

> Fix pipes plumber servlet IT 
> -
>
> Key: SLING-7251
> URL: https://issues.apache.org/jira/browse/SLING-7251
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: pipes 2.0.0
>Reporter: Nicolas Peltier
>Assignee: Oliver Lietz
>Priority: Major
>
> new Plumber servlet IT fail. This should be fixed



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (SLING-7202) o.a.j.o.j.o.ObservationManagerImpl times out eventually in pax container init

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz reassigned SLING-7202:
---

Assignee: Oliver Lietz

> o.a.j.o.j.o.ObservationManagerImpl times out eventually in pax container init
> -
>
> Key: SLING-7202
> URL: https://issues.apache.org/jira/browse/SLING-7202
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Affects Versions: Testing PaxExam 0.0.4
>Reporter: Nicolas Peltier
>Assignee: Oliver Lietz
>Priority: Major
> Attachments: success-fail-logs.tar
>
>
> pipes IT intermittently fail. When they do, after having compared to when 
> they don't, look like the core cause is
> {Code}
> 2017-10-10 22:32:13,092 WARN [FelixStartLevel] 
> o.a.j.o.j.o.ObservationManagerImpl [ObservationManagerImpl.java : 457] Timed 
> out waiting for change processor to stop after 1000 milliseconds. Falling 
> back to asynchronous stop on ChangeProcessor [listenerId=10, 
> tracker=//*[1b]@org.apache.sling.jcr.resource.internal.JcrResourceListener,
>  contentSession=session-17, 
> eventCount=org.apache.jackrabbit.oak.stats.SimpleStats@4405759a, 
> eventDuration=org.apache.jackrabbit.oak.stats.SimpleStats@4aa43935, 
> commitRateLimiter=null, running=false] (listener details: 
> 'JcrResourceListener [BasicObserverConfiguration [includeExternal=true, 
> paths=PathSet [paths=[Path [path=/]]], excludedPaths=PathSet [paths=[Path 
> [path=/libs/sling/sightly/js], Path 
> [path=/apps/sling/servlet/default/SLING_av... (1907 chars cut), 
> propertyNamesHint=null, changeTypes=[ADDED, REMOVED, CHANGED], 
> listeners=[ResourceChangeListenerInfo [paths=PathSet [paths=[Path [path=/]]], 
> resourceChangeTypes=[ADDED, REMOVED, CHANGED], 
> providerChangeTypes=[PROVIDER_ADDED, PROVIDER_REMOVED], 
> propertyNamesHint=null, valid=true, external=true, 
> listener=org.apache.sling.servlets.resolver.internal.SlingServletResolver@3993ddcd],
>  ResourceChangeListenerInfo [paths=PathSet [paths=[Path [path=/]]], 
> resourceChangeTypes=[ADDED, REMOVED, CHANGED], 
> providerChangeTypes=[PROVIDER_ADDED, PROVIDER_REMOVED], 
> propertyNamesHint=null, valid=true, external=true, 
> listener=org.apache.sling.resourceresolver.impl.mapping.MapEntries@70b4e2df], 
> ResourceChangeListenerInfo [paths=PathSet [paths=[Path [path=/]]], 
> resourceChangeTypes=[ADDED, REMOVED, CHANGED], 
> providerChangeTypes=[PROVIDER_ADDED, PROVIDER_REMOVED], 
> propertyNamesHint=null, valid=true, external=true, 
> listener=org.apache.sling.i18n.impl.JcrResourceBundleProvider@60af913d')
> {Code}
> after which content loading does not work, resulting in test failing 
> cc [~olli]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)