[jira] [Updated] (SLING-7436) Wrong content/type in the Default JSON Renderer

[ https://issues.apache.org/jira/browse/SLING-7436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso updated SLING-7436: - Description: Steps to reproduce: 1.Render a page (Renderer enabled) with JSON renderer. E.g: [ht

[jira] [Updated] (SLING-7436) Wrong content/type in the Default JSON Renderer

[ https://issues.apache.org/jira/browse/SLING-7436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso updated SLING-7436: - Description: Steps to reproduce: 1.Render a page (Renderer enabled) with JSON renderer. E.g: [ht

[jira] [Created] (SLING-7436) Wrong content/type in the Default JSON Renderer

Antonio Sanso created SLING-7436: Summary: Wrong content/type in the Default JSON Renderer Key: SLING-7436 URL: https://issues.apache.org/jira/browse/SLING-7436 Project: Sling Issue Type: Bu

[jira] [Commented] (SLING-2778) initial Sling/Jolokia integration bundle

[ https://issues.apache.org/jira/browse/SLING-2778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336890#comment-16336890 ] Chetan Mehrotra commented on SLING-2778: [~justinedelson] Can you provide the path

[jira] [Commented] (SLING-7432) Thread pool clean up code can lead to infinite loops in ThreadLocal.get

[ https://issues.apache.org/jira/browse/SLING-7432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336397#comment-16336397 ] Robert Munteanu commented on SLING-7432: Interesting, I did not know about that. I

[jira] [Comment Edited] (SLING-7432) Thread pool clean up code can lead to infinite loops in ThreadLocal.get

[ https://issues.apache.org/jira/browse/SLING-7432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336397#comment-16336397 ] Robert Munteanu edited comment on SLING-7432 at 1/23/18 9:27 PM: ---

[jira] [Commented] (SLING-7432) Thread pool clean up code can lead to infinite loops in ThreadLocal.get

[ https://issues.apache.org/jira/browse/SLING-7432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336388#comment-16336388 ] Konrad Windszus commented on SLING-7432: New threads by default carry some thread

[jira] [Commented] (SLING-7432) Thread pool clean up code can lead to infinite loops in ThreadLocal.get

[ https://issues.apache.org/jira/browse/SLING-7432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336371#comment-16336371 ] Robert Munteanu commented on SLING-7432: While going deeper and deeper in the code

Re: [VOTE] Release Apache Sling Commons Threads 3.2.12

Agree: -1 Carsten Robert Munteanu wrote > On Mon, 2018-01-22 at 14:21 +0200, Robert Munteanu wrote: >> On Mon, 2018-01-22 at 12:12 +0100, Stefan Egli wrote: >>> Please vote to approve this release: >> >> +1 > > I am changing my vote to -1 in light of a blocking issue I discovered > while doing

[jira] [Commented] (SLING-7428) StartupFilter not reliably stopped (and still returning 503) when executing org.apache.sling.scripting.sightly.testing

[ https://issues.apache.org/jira/browse/SLING-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16336259#comment-16336259 ] Carsten Ziegeler commented on SLING-7428: - [~kwin] No, it might be a timing issue,

Re: Git force push

Hi, On Tue, 2018-01-23 at 15:05 +0100, Stefan Egli wrote: > Sounds like a good idea to start with disallowing --force for now, > given > there is --force-with-lease for emergencies. The unfortunate bit is > perhaps that this opens up a way to modify history without noticing > (which > is what I've

[jira] [Created] (SLING-7434) Authorizable pipe autocreate group does not handle dryRun

Nicolas Peltier created SLING-7434: -- Summary: Authorizable pipe autocreate group does not handle dryRun Key: SLING-7434 URL: https://issues.apache.org/jira/browse/SLING-7434 Project: Sling I

[jira] [Created] (SLING-7435) Authorizable pipe autocreate group does not handle dryRun

Nicolas Peltier created SLING-7435: -- Summary: Authorizable pipe autocreate group does not handle dryRun Key: SLING-7435 URL: https://issues.apache.org/jira/browse/SLING-7435 Project: Sling I

Re: documentation locations

On Tuesday 23 January 2018 16:43:37 Bertrand Delacretaz wrote: > Hi, > > On Tue, Jan 23, 2018 at 3:40 PM, Oliver Lietz wrote: > > ...AFAIR we agreed on having basic documentation in the README and higher > > level documentation or documentation spanning multiple modules on Sling's > > site under

Re: documentation locations

Hi, On Tue, Jan 23, 2018 at 3:40 PM, Oliver Lietz wrote: > ...AFAIR we agreed on having basic documentation in the README and higher > level > documentation or documentation spanning multiple modules on Sling's site under > /documentation... That works for me - however until we have an automate

[jira] [Commented] (SLING-7320) NPE in sling commons threads

[ https://issues.apache.org/jira/browse/SLING-7320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335915#comment-16335915 ] Konrad Windszus commented on SLING-7320: Prevented the NPE in copy with https://g

[jira] [Updated] (SLING-7320) NPE in sling commons threads

[ https://issues.apache.org/jira/browse/SLING-7320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-7320: --- Fix Version/s: Commons Threads 3.2.14 > NPE in sling commons threads > ---

[jira] [Resolved] (SLING-7433) Improve logging in case ThreadLocalCleaner does not work

[ https://issues.apache.org/jira/browse/SLING-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-7433. Resolution: Fixed Fix Version/s: Commons Threads 3.2.14 Fixed in https://github.com/

[jira] [Updated] (SLING-7433) Improve logging in case ThreadLocalCleaner does not work

[ https://issues.apache.org/jira/browse/SLING-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-7433: --- Description: Currently {{ThreadLocalCleaner}} relies on exceptions in case anything in it does

[jira] [Created] (SLING-7433) Improve logging in case ThreadLocalCleaner does not work

Konrad Windszus created SLING-7433: -- Summary: Improve logging in case ThreadLocalCleaner does not work Key: SLING-7433 URL: https://issues.apache.org/jira/browse/SLING-7433 Project: Sling Is

[jira] [Assigned] (SLING-7320) NPE in sling commons threads

[ https://issues.apache.org/jira/browse/SLING-7320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned SLING-7320: -- Assignee: Konrad Windszus > NPE in sling commons threads >

[jira] [Commented] (SLING-7320) NPE in sling commons threads

[ https://issues.apache.org/jira/browse/SLING-7320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335881#comment-16335881 ] Konrad Windszus commented on SLING-7320: The latter NPE can only happen if listene

[jira] [Resolved] (SLING-7428) StartupFilter not reliably stopped (and still returning 503) when executing org.apache.sling.scripting.sightly.testing

[ https://issues.apache.org/jira/browse/SLING-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-7428. - Resolution: Fixed Fixed in [commit 771e739|https://github.com/apache/sling-org-apache-sling-scrip

[jira] [Commented] (SLING-7432) Thread pool clean up code can lead to infinite loops in ThreadLocal.get

[ https://issues.apache.org/jira/browse/SLING-7432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335864#comment-16335864 ] Robert Munteanu commented on SLING-7432: Well, I apparently fixed one problem, but

[jira] [Commented] (SLING-7432) Thread pool clean up code can lead to infinite loops in ThreadLocal.get

[ https://issues.apache.org/jira/browse/SLING-7432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335860#comment-16335860 ] Konrad Windszus commented on SLING-7432: Looks good to me. I am wondering whether

[jira] [Updated] (SLING-7428) StartupFilter not reliably stopped (and still returning 503) when executing org.apache.sling.scripting.sightly.testing

[ https://issues.apache.org/jira/browse/SLING-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-7428: Fix Version/s: Scripting HTL Testing Content 1.0.8-1.3.1 > StartupFilter not reliably stopped (and s

[jira] [Resolved] (SLING-7431) Allow the HTL IT to run against the latest stable launchpad artifact and against the latest snapshot

[ https://issues.apache.org/jira/browse/SLING-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-7431. - Resolution: Fixed Fixed in [commit f650f92|https://github.com/apache/sling-org-apache-sling-scrip

Re: documentation locations

On Tuesday 23 January 2018 13:54:30 Jason Bailey wrote: > Is there a determination on where the true source of documentation is? > We have the sling-site project, we have the README in each individual > project and the plugins are using the maven-sites-plugin. AFAIR we agreed on having basic docum

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

[ https://issues.apache.org/jira/browse/SLING-7406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335822#comment-16335822 ] Radu Cotescu edited comment on SLING-7406 at 1/23/18 2:35 PM: --

[jira] [Commented] (SLING-7432) Thread pool clean up code can lead to infinite loops in ThreadLocal.get

[ https://issues.apache.org/jira/browse/SLING-7432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335840#comment-16335840 ] Robert Munteanu commented on SLING-7432: Applied a potential fix in [sling-org-apa

[jira] [Commented] (SLING-7421) JcrResourceBundle does not correctly support multiple base names

[ https://issues.apache.org/jira/browse/SLING-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335831#comment-16335831 ] Konrad Windszus commented on SLING-7421: I added an IT for this in https://github

Re: [VOTE] Release Apache Sling Commons Threads 3.2.12

On Monday 22 January 2018 12:12:44 Stefan Egli wrote: > Hi, > > we solved 1 issue in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12341693 +1 O.

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

[ https://issues.apache.org/jira/browse/SLING-7406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-7406. - Resolution: Fixed Fixed in the following commits: * [commit af00ddd|https://github.com/apache/sli

[jira] [Commented] (SLING-7428) StartupFilter not reliably stopped (and still returning 503) when executing org.apache.sling.scripting.sightly.testing

[ https://issues.apache.org/jira/browse/SLING-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335803#comment-16335803 ] Radu Cotescu commented on SLING-7428: - ACK: I'll move the README file. :) > StartupFi

Re: Git force push

Sounds like a good idea to start with disallowing --force for now, given there is --force-with-lease for emergencies. The unfortunate bit is perhaps that this opens up a way to modify history without noticing (which is what I've used it for too). Cheers, Stefan On 23.01.18, 14:59, "Jason Bailey"

[jira] [Comment Edited] (SLING-7428) StartupFilter not reliably stopped (and still returning 503) when executing org.apache.sling.scripting.sightly.testing

[ https://issues.apache.org/jira/browse/SLING-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335806#comment-16335806 ] Radu Cotescu edited comment on SLING-7428 at 1/23/18 2:08 PM: --

[CANCELLED][VOTE] Release Apache Sling Commons Threads 3.2.12

Cancelling this release as per comment from Robert re SLING-7432. I'd suggest to use 3.2.14 for a next commons threads release once that is ready. Cheers, Stefan On 22.01.18, 12:12, "Stefan Egli" wrote: >Hi, > >we solved 1 issue in this release: >https://issues.apache.org/jira/browse/SLING/fix

[jira] [Commented] (SLING-7428) StartupFilter not reliably stopped (and still returning 503) when executing org.apache.sling.scripting.sightly.testing

[ https://issues.apache.org/jira/browse/SLING-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335806#comment-16335806 ] Konrad Windszus commented on SLING-7428: Any idea why this issue did not occur wit

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

[ https://issues.apache.org/jira/browse/SLING-7406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-7406: Fix Version/s: Scripting HTL Testing 1.0.6-1.3.1 Scripting HTL Testing Content 1.0

RE: Git force push

The methodology with GIT is usually around never committing anything directly to master, rather branch and merge. Internally I have our github projects set up to prevent force pushes to master and to allow it on branches so that the developer working on that branch has the option of fixing thing

[jira] [Comment Edited] (SLING-7432) Thread pool clean up code can lead to infinite loops in ThreadLocal.get

[ https://issues.apache.org/jira/browse/SLING-7432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335793#comment-16335793 ] Robert Munteanu edited comment on SLING-7432 at 1/23/18 1:58 PM: ---

[jira] [Commented] (SLING-7432) Thread pool clean up code can lead to infinite loops in ThreadLocal.get

[ https://issues.apache.org/jira/browse/SLING-7432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335793#comment-16335793 ] Robert Munteanu commented on SLING-7432: Added ignore test in [sling-org-apache-sl

Re: [VOTE] Release Apache Sling Commons Threads 3.2.12

On Mon, 2018-01-22 at 14:21 +0200, Robert Munteanu wrote: > On Mon, 2018-01-22 at 12:12 +0100, Stefan Egli wrote: > > Please vote to approve this release: > > +1 I am changing my vote to -1 in light of a blocking issue I discovered while doing some extensive tests. https://issues.apache.org/ji

documentation locations

Is there a determination on where the true source of documentation is? We have the sling-site project, we have the README in each individual project and the plugins are using the maven-sites-plugin. In Git projects it's usually the README or a unique docs folder. In a related note, if the READM

[jira] [Created] (SLING-7432) Thread pool clean up code can lead to infinite loops in ThreadLocal.get

Robert Munteanu created SLING-7432: -- Summary: Thread pool clean up code can lead to infinite loops in ThreadLocal.get Key: SLING-7432 URL: https://issues.apache.org/jira/browse/SLING-7432 Project: Sl

Re: Git force push

On Tue, Jan 23, 2018 at 2:33 PM, Stefan Seifert wrote: > i would also vote for *not* allowing push --force.. +1, my understanding is that one can destroy history with that...which we don't want. I have never used --force-with-lease so far but according to [1] it only allows you to force-push if

RE: Git force push

i would also vote for *not* allowing push --force stefan >-Original Message- >From: Oliver Lietz [mailto:apa...@oliverlietz.de] >Sent: Tuesday, January 23, 2018 1:21 PM >To: dev@sling.apache.org >Subject: Git force push > >Hi, > >can we have a simple rule (allow vs deny) for git push --fo

Re: Git force push

I just stumbled upon a problem where I did a commit with a wrong author email (in SLING-7407) and "thanks" to force push I was able to correct this. Not saying it is a good idea to do this often though .. ;) Cheers, Stefan On 23.01.18, 13:26, "Radu Cotescu" wrote: >Hi Oliver, > >Shouldn't we *n

[jira] [Commented] (SLING-7430) Invalid assumptions in SlingSpecificsSightlyIT#testI18nBasename

[ https://issues.apache.org/jira/browse/SLING-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335751#comment-16335751 ] Konrad Windszus commented on SLING-7430: Actually both values "die Bank" as well a

[jira] [Commented] (SLING-7426) Use bnd Maven plugins

[ https://issues.apache.org/jira/browse/SLING-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335750#comment-16335750 ] Oliver Lietz commented on SLING-7426: - bq. We export packages as soon as they have a V

[jira] [Commented] (SLING-7430) Invalid assumptions in SlingSpecificsSightlyIT#testI18nBasename

[ https://issues.apache.org/jira/browse/SLING-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335748#comment-16335748 ] Radu Cotescu commented on SLING-7430: - [~kwin], I'm afraid you didn't check the test p

[jira] [Created] (SLING-7431) Allow the HTL IT to run against the latest stable launchpad artifact and against the latest snapshot

Radu Cotescu created SLING-7431: --- Summary: Allow the HTL IT to run against the latest stable launchpad artifact and against the latest snapshot Key: SLING-7431 URL: https://issues.apache.org/jira/browse/SLING-7431

[jira] [Commented] (SLING-7421) JcrResourceBundle does not correctly support multiple base names

[ https://issues.apache.org/jira/browse/SLING-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335739#comment-16335739 ] Konrad Windszus commented on SLING-7421: [~radu.cotescu] IMHO the documentation of

[jira] [Created] (SLING-7430) Invalid assumptions in SlingSpecificsSightlyIT#testI18nBasename

Konrad Windszus created SLING-7430: -- Summary: Invalid assumptions in SlingSpecificsSightlyIT#testI18nBasename Key: SLING-7430 URL: https://issues.apache.org/jira/browse/SLING-7430 Project: Sling

[jira] [Commented] (SLING-7426) Use bnd Maven plugins

[ https://issues.apache.org/jira/browse/SLING-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335734#comment-16335734 ] Nicolas Peltier commented on SLING-7426: thanks [~cziegeler] (cc [~olli]) will run

[jira] [Created] (SLING-7429) Improve basename handling

Konrad Windszus created SLING-7429: -- Summary: Improve basename handling Key: SLING-7429 URL: https://issues.apache.org/jira/browse/SLING-7429 Project: Sling Issue Type: Improvement

[jira] [Comment Edited] (SLING-7421) JcrResourceBundle does not correctly support multiple base names

[ https://issues.apache.org/jira/browse/SLING-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335686#comment-16335686 ] Konrad Windszus edited comment on SLING-7421 at 1/23/18 12:41 PM: --

[jira] [Commented] (SLING-7421) JcrResourceBundle does not correctly support multiple base names

[ https://issues.apache.org/jira/browse/SLING-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335722#comment-16335722 ] Radu Cotescu commented on SLING-7421: - It could very well be that the Sightly IT is ma

[jira] [Commented] (SLING-7426) Use bnd Maven plugins

[ https://issues.apache.org/jira/browse/SLING-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335716#comment-16335716 ] Carsten Ziegeler commented on SLING-7426: - I think it makes sense to slowly move t

[jira] [Updated] (SLING-7428) StartupFilter not reliably stopped (and still returning 503) when executing org.apache.sling.scripting.sightly.testing

[ https://issues.apache.org/jira/browse/SLING-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-7428: --- Summary: StartupFilter not reliably stopped (and still returning 503) when executing org.apach

[jira] [Commented] (SLING-7428) StartupFilter nor reliably stopped (and still returning 503) when executing org.apache.sling.scripting.sightly.testing

[ https://issues.apache.org/jira/browse/SLING-7428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335711#comment-16335711 ] Carsten Ziegeler commented on SLING-7428: - I think waiting for untransformed resou

New i18n release and basename handling (was: [VOTE] Release Apache Sling Starter 10 + associated testing projects and archetypes (take 2))

Hi Konrad, On Tue, 2018-01-23 at 13:13 +0100, Konrad Windszus wrote: > But before spinning a new release I would like to get some more > opinions on the basename handling of the i18n bundle in general > (compare with https://issues.apache.org/jira/browse/SLING-7421?focuse > dCommentId=16335677&pag

Re: Git force push

Hi Oliver, Shouldn't we *never* allow force push? Cheers, Radu On Tue, 23 Jan 2018 at 14:20 Oliver Lietz wrote: > Hi, > > can we have a simple rule (allow vs deny) for git push --force? > > Thanks, > O. > >

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

This release is cancelled since it is affected by SLING-7421 [1]. Thanks to Radu for catching this regression and for Konrad for assessing the impact of the release. The plan is to drop the starter 10 release artifact and respin once we have a new i18n release (maybe include them in the same rele

Git force push

Hi, can we have a simple rule (allow vs deny) for git push --force? Thanks, O.

[jira] [Commented] (SLING-7421) JcrResourceBundle does not correctly support multiple base names

[ https://issues.apache.org/jira/browse/SLING-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335686#comment-16335686 ] Konrad Windszus commented on SLING-7421: Yes exactly. But even after having this o

[jira] [Commented] (SLING-7421) JcrResourceBundle does not correctly support multiple base names

[ https://issues.apache.org/jira/browse/SLING-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335683#comment-16335683 ] Robert Munteanu commented on SLING-7421: [~kwin] - that's what we risk by releasin

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

After having evaluated the impact of https://issues.apache.org/jira/browse/SLING-7421 more closely I am also voting -1 for this release. But before spinning a new release I would like to get some more opinions on the basename handling of the i

[jira] [Updated] (SLING-7421) JcrResourceBundle does not correctly support multiple base names

[ https://issues.apache.org/jira/browse/SLING-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-7421: --- Priority: Critical (was: Major) > JcrResourceBundle does not correctly support multiple base

[jira] [Commented] (SLING-7421) JcrResourceBundle does not correctly support multiple base names

[ https://issues.apache.org/jira/browse/SLING-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335679#comment-16335679 ] Konrad Windszus commented on SLING-7421: To clarify the impact of this bug: Whenev

[jira] [Comment Edited] (SLING-7421) JcrResourceBundle does not correctly support multiple base names

[ https://issues.apache.org/jira/browse/SLING-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335677#comment-16335677 ] Konrad Windszus edited comment on SLING-7421 at 1/23/18 12:06 PM: --

[jira] [Commented] (SLING-7421) JcrResourceBundle does not correctly support multiple base names

[ https://issues.apache.org/jira/browse/SLING-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335677#comment-16335677 ] Konrad Windszus commented on SLING-7421: I think the base name handling should be

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

On Tue, 2018-01-23 at 11:49 +0100, Karl Pauls wrote: > Sounds like it isn't necessarily a showstopper - I guess Robert has > to > make the call if he wants to cancel the release or have it pass. > > FWIW, I would have liked to have the latest servlets.post 2.3.24 > release included as well so if w

[jira] [Created] (SLING-7428) StartupFilter nor reliably stopped (and still returning 503) when executing org.apache.sling.scripting.sightly.testing

Konrad Windszus created SLING-7428: -- Summary: StartupFilter nor reliably stopped (and still returning 503) when executing org.apache.sling.scripting.sightly.testing Key: SLING-7428 URL: https://issues.apache.org/

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

[ https://issues.apache.org/jira/browse/SLING-7073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335648#comment-16335648 ] Konrad Windszus commented on SLING-7073: After looking at the Sightly IT more clos

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

Sounds like it isn't necessarily a showstopper - I guess Robert has to make the call if he wants to cancel the release or have it pass. FWIW, I would have liked to have the latest servlets.post 2.3.24 release included as well so if we respin the release we might include it as well :-). regards,

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

Hi Karl, A project deployed on the Sling 10 Starter that would use i18n with a resource bundle provider that should take into account the basename requested by the client might fail to get the correct translation. Cheers, Radu On Tue, 23 Jan 2018 at 12:17 Karl Pauls wrote: > Hi Radu, > > what

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

Hi Radu, what is the impact of this bug (mostly want to find out if it breaks us in a major way or if it is just a special case)? regards, Karl On Tue, Jan 23, 2018 at 11:01 AM, Radu Cotescu wrote: > -1. See > https://issues.apache.org/jira/browse/SLING-6952?focusedCommentId=16335586&page=com.

[jira] [Closed] (SLING-7346) Issues with custom fields in PostResponse as a result of fix for SLING-6681(Replace commons.json usage in org.apache.sling.servlets.post)

[ https://issues.apache.org/jira/browse/SLING-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-7346. - > Issues with custom fields in PostResponse as a result of fix for > SLING-6681(Replace commons.json usage in

Re: [RESULT][VOTE] Release Apache Sling Servlets Post 2.3.24

Time to call the vote on the Apache Sling Servlets Post 2.3.24 release. * +1 votes from Carsten Ziegeler, Stefan Seifert, and Karl Pauls. * No other votes. The vote is successful. I will make the artifacts available as soon as possible.

Re: [VOTE] Release Apache Sling Servlets Post 2.3.24

+1 regards, Karl On Fri, Jan 19, 2018 at 11:31 AM, Stefan Seifert wrote: > +1 > -- Karl Pauls karlpa...@gmail.com

[jira] [Commented] (SLING-7426) Use bnd Maven plugins

[ https://issues.apache.org/jira/browse/SLING-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335582#comment-16335582 ] Oliver Lietz commented on SLING-7426: - Yes. The bnd Maven Plugin was added by [~cziege

[jira] [Comment Edited] (SLING-6952) Release Sling 10

[ https://issues.apache.org/jira/browse/SLING-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335586#comment-16335586 ] Radu Cotescu edited comment on SLING-6952 at 1/23/18 10:02 AM: -

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

-1. See https://issues.apache.org/jira/browse/SLING-6952?focusedCommentId=16335586&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16335586 . Sorry for this... :( Radu On Mon, 22 Jan 2018 at 23:16 Karl Pauls wrote: > +1 > > regards, > > Karl > > On Fri, Jan 19, 20

[jira] [Comment Edited] (SLING-6952) Release Sling 10

[ https://issues.apache.org/jira/browse/SLING-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335586#comment-16335586 ] Radu Cotescu edited comment on SLING-6952 at 1/23/18 9:59 AM: --

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

[ https://issues.apache.org/jira/browse/SLING-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335586#comment-16335586 ] Radu Cotescu commented on SLING-6952: - [~rombert], please check my comment from \[0\].

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

[ https://issues.apache.org/jira/browse/SLING-7073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335529#comment-16335529 ] Radu Cotescu edited comment on SLING-7073 at 1/23/18 9:55 AM: --

[jira] [Resolved] (SLING-7426) Use bnd Maven plugins

[ https://issues.apache.org/jira/browse/SLING-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier resolved SLING-7426. Resolution: Fixed Fix Version/s: pipes 2.0.0 Thanks [~olli] ! > Use bnd Maven plugin

Re: Please welcome Jason Bailey, Sling committer

Hi Jason, welcome! On Mon, Jan 22, 2018 at 8:45 PM, Jason Bailey wrote: > I've been primarily a Java developer since the 1.2 days... > ...audio codec implementations, swing apps... Same here...Swing apps in 1999, and they even worked, those were the days! -Bertrand

[jira] [Commented] (SLING-7426) Use bnd Maven plugins

[ https://issues.apache.org/jira/browse/SLING-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335558#comment-16335558 ] Nicolas Peltier commented on SLING-7426: is the rationale the arguments detailed h

[jira] [Resolved] (SLING-7427) Package names should be all lowercase

[ https://issues.apache.org/jira/browse/SLING-7427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier resolved SLING-7427. Resolution: Fixed > Package names should be all lowercase >

[jira] [Commented] (SLING-7427) Package names should be all lowercase

[ https://issues.apache.org/jira/browse/SLING-7427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335554#comment-16335554 ] Nicolas Peltier commented on SLING-7427: thanks for your vigilance [~olli]! > Pac

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

[ https://issues.apache.org/jira/browse/SLING-7073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335529#comment-16335529 ] Radu Cotescu commented on SLING-7073: - Worked with 2.5.8, doesn't work with 2.5.10, wo

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

[ https://issues.apache.org/jira/browse/SLING-7073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335506#comment-16335506 ] Robert Munteanu commented on SLING-7073: If this works with 2.5.10 but not with 2.

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

[ https://issues.apache.org/jira/browse/SLING-7073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335486#comment-16335486 ] Radu Cotescu commented on SLING-7073: - {{basename}} doesn't seem to be correctly taken

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

[ https://issues.apache.org/jira/browse/SLING-7073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335486#comment-16335486 ] Radu Cotescu edited comment on SLING-7073 at 1/23/18 8:17 AM: --

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

[ https://issues.apache.org/jira/browse/SLING-7073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335481#comment-16335481 ] Robert Munteanu commented on SLING-7073: [~radu.cotescu] - what errors do you see?