[jira] [Commented] (SLING-6639) Move ResourceResolution & SightlyException to java-compiler bundle

[ https://issues.apache.org/jira/browse/SLING-6639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15922831#comment-15922831 ] Karl Pauls commented on SLING-6639: --- Well, the real problem is that both, engine and java-compiler are

[jira] [Resolved] (SLING-6621) Use official OSGi annotations

[ https://issues.apache.org/jira/browse/SLING-6621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-6621. - Resolution: Done Checks in {{QuartzScheduler#getThreadPoolName(String)}} should be sufficient. >

[jira] [Assigned] (SLING-6536) Replace JSON implementation derived from org.json code

[ https://issues.apache.org/jira/browse/SLING-6536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls reassigned SLING-6536: - Assignee: Karl Pauls > Replace JSON implementation derived from org.json code >

[jira] [Commented] (SLING-6618) Specify crx.default as workspace for AEM servers

[ https://issues.apache.org/jira/browse/SLING-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907744#comment-15907744 ] Karl Pauls commented on SLING-6618: --- Great! Maybe it really wasn't I the snapshot I tried a while ago. I

[jira] [Commented] (SLING-6618) Specify crx.default as workspace for AEM servers

[ https://issues.apache.org/jira/browse/SLING-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907648#comment-15907648 ] Konrad Windszus commented on SLING-6618: I tried with the minimal approach against the 3.0.36 of

[jira] [Updated] (SLING-5980) Duplicate Script Cache Clearing Functionality

[ https://issues.apache.org/jira/browse/SLING-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-5980: Component/s: Scripting Commons > Duplicate Script Cache Clearing Functionality >

[jira] [Assigned] (SLING-6618) Specify crx.default as workspace for AEM servers

[ https://issues.apache.org/jira/browse/SLING-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls reassigned SLING-6618: - Assignee: (was: Karl Pauls) Well, as I said in my initial comment, I think I did try the

[jira] [Closed] (SLING-6629) UserUtil reports user is not existing when user is system user

[ https://issues.apache.org/jira/browse/SLING-6629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz closed SLING-6629. --- > UserUtil reports user is not existing when user is system user >

[jira] [Closed] (SLING-6182) repoinit fails to set ACL on previously created principal

[ https://issues.apache.org/jira/browse/SLING-6182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz closed SLING-6182. --- > repoinit fails to set ACL on previously created principal >

[RESULT] [VOTE] Release Apache Sling Repoinit JCR 1.1.4

Hi, the vote has passed with the following result: +1 (binding): Oliver Lietz, Daniel Klco, Bertrand Delacretaz, Robert Munteanu, Karl Pauls I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Thanks for voting! O.

[jira] [Commented] (SLING-6639) Move ResourceResolution & SightlyException to java-compiler bundle

[ https://issues.apache.org/jira/browse/SLING-6639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907583#comment-15907583 ] Radu Cotescu commented on SLING-6639: - The engine bundle does export

[jira] [Commented] (SLING-5980) Duplicate Script Cache Clearing Functionality

[ https://issues.apache.org/jira/browse/SLING-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907522#comment-15907522 ] Dan Klco commented on SLING-5980: - [~olli] - Yes, this is done in Scripting JSP. > Duplicate Script Cache

Re: new commons component "File System Content Parser" - name?

Another remark on the API: Currently ContentFileParser methods always returns Map. If I understood correctly, the keys are both direct property names of the root resource as well as child resources. That is not good because in JCR it is perfectly valid to have a node called

RE: new commons component "File System Content Parser" - name?

On Monday 13 March 2017 12:34:45 Stefan Seifert wrote: > >and moving it to bundles/jcr (next to contentloader) > > > >>bundles/commons is for modules not related to Sling/JCR at all. > > the fscontentparser component has currently no dependency to Sling API or > any other sling bundles, so it's

[jira] [Updated] (SLING-6637) [htl] data-sly-use should not raise an exception when resource doesn't exist

[ https://issues.apache.org/jira/browse/SLING-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feike Visser updated SLING-6637: Summary: [htl] data-sly-use should not raise an exception when resource doesn't exist (was: [htl]

Re: new commons component "File System Content Parser" - name?

> On 13 Mar 2017, at 14:24, Bertrand Delacretaz wrote: > > Hi Stefan, > > On Mon, Mar 13, 2017 at 9:48 AM, Stefan Seifert > wrote: >> i've recently created a new commons sling component which i named "File >> System Content Parser"... > >

[jira] [Updated] (SLING-6634) Use new FS Content Parser module in ContentLoader

[ https://issues.apache.org/jira/browse/SLING-6634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6634: --- Summary: Use new FS Content Parser module in ContentLoader (was: Use new FS Content Provider

[jira] [Assigned] (SLING-5741) discarding complete ResourceBundleCache in case of JSON dictionary

[ https://issues.apache.org/jira/browse/SLING-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned SLING-5741: -- Assignee: (was: Konrad Windszus) > discarding complete ResourceBundleCache in case

[jira] [Assigned] (SLING-5708) discarding ResourceBundle of all locale

[ https://issues.apache.org/jira/browse/SLING-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned SLING-5708: -- Assignee: (was: Konrad Windszus) > discarding ResourceBundle of all locale >

Re: new commons component "File System Content Parser" - name?

Hi Stefan, On Mon, Mar 13, 2017 at 9:48 AM, Stefan Seifert wrote: > i've recently created a new commons sling component which i named "File > System Content Parser"... Great, thanks for this! Are you planning to reuse this in the Sling Content Loader? IIUC it

[jira] [Commented] (SLING-6313) Sling installer can duplicate factory configurations if an invalid RegisteredResourceList.ser is found

[ https://issues.apache.org/jira/browse/SLING-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907434#comment-15907434 ] Robert Munteanu commented on SLING-6313: In my scenario the fix would not have helped so I don't

[jira] [Assigned] (SLING-6313) Sling installer can duplicate factory configurations if an invalid RegisteredResourceList.ser is found

[ https://issues.apache.org/jira/browse/SLING-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-6313: -- Assignee: (was: Robert Munteanu) > Sling installer can duplicate factory

[jira] [Commented] (SLING-6618) Specify crx.default as workspace for AEM servers

[ https://issues.apache.org/jira/browse/SLING-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907401#comment-15907401 ] Robert Munteanu commented on SLING-6618: I see, then things are better than what I expected >

Re: Maven plugin documentation

I was assuming that the official Apache Maven Plugins publish snapshot versions as well, but this is not the case (https://svn.apache.org/repos/infra/websites/production/maven/components/). So probably this is not a good idea at all. > On 13 Mar 2017, at 13:22, Stefan Seifert

[jira] [Commented] (SLING-6618) Specify crx.default as workspace for AEM servers

[ https://issues.apache.org/jira/browse/SLING-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907398#comment-15907398 ] Konrad Windszus commented on SLING-6618: {quote} If we have stable Oak releases or AEM releases

[jira] [Commented] (SLING-6618) Specify crx.default as workspace for AEM servers

[ https://issues.apache.org/jira/browse/SLING-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907392#comment-15907392 ] Robert Munteanu commented on SLING-6618: {quote}For the short-term I would rather like to rely on

RE: new commons component "File System Content Parser" - name?

>and moving it to bundles/jcr (next to contentloader) >>bundles/commons is for modules not related to Sling/JCR at all. the fscontentparser component has currently no dependency to Sling API or any other sling bundles, so it's not really misplaced. it has an outside dependency to jackrabbit

Re: new commons component "File System Content Parser" - name?

I could live with both 2. and 4. > +1 for *contentparser* and moving it to bundles/jcr (next to contentloader) > as > bundles/commons is for modules not related to Sling/JCR at all. No sure whether bundles/jcr is a good fit either, as only some parser's are specific to the JCR (document XML,

RE: Maven plugin documentation

do we want to deploy SNASPHOT sites? just for a review you can do a local "mvn site" on the plugin project to see the same results. technically it would be easy using the "scm-publish:publish-scm" goal - but it always creates a new history entry in the SVN of the site and seems more intended

[jira] [Updated] (SLING-6639) Move ResourceResolution & SightlyException to java-compiler bundle

[ https://issues.apache.org/jira/browse/SLING-6639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomek Rękawek updated SLING-6639: - Description: {{ResourceResolution}} and {{SightlyException}} classes should be moved to the

[jira] [Created] (SLING-6639) Move ResourceResolution & SightlyException to java-compiler bundle

Tomek Rękawek created SLING-6639: Summary: Move ResourceResolution & SightlyException to java-compiler bundle Key: SLING-6639 URL: https://issues.apache.org/jira/browse/SLING-6639 Project: Sling

[jira] [Updated] (SLING-6639) Move ResourceResolution & SightlyException to java-compiler bundle

[ https://issues.apache.org/jira/browse/SLING-6639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomek Rękawek updated SLING-6639: - Attachment: SLING-6639.patch > Move ResourceResolution & SightlyException to java-compiler bundle

[jira] [Commented] (SLING-5980) Duplicate Script Cache Clearing Functionality

[ https://issues.apache.org/jira/browse/SLING-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907345#comment-15907345 ] Oliver Lietz commented on SLING-5980: - [~klcodanr], is it *done* for Scripting JSP? > Duplicate

Re: Maven plugin documentation

Hi Stefan, thanks a lot for your efforts. Can we also add a hint on how to deploy a SNAPSHOT site (e.g. for others to review?) Thanks, Konrad > On 10 Mar 2017, at 01:25, Stefan Seifert wrote: > > for a long time we manually maintained documentation of our maven plugins

Re: [VOTE] Apache Sling Repoinit JCR 1.1.4

+1 regards, Karl On Mon, Mar 13, 2017 at 11:15 AM, Robert Munteanu wrote: > On Thu, 2017-03-09 at 19:19 +0100, Oliver Lietz wrote: >> Please vote to approve this release: > > +1 > > Robert -- Karl Pauls karlpa...@gmail.com

[jira] [Closed] (SLING-6613) ResourceResolverFactory not registered when legacy configuration references JcrResourceProviderFactory

[ https://issues.apache.org/jira/browse/SLING-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-6613. -- > ResourceResolverFactory not registered when legacy configuration references >

Re: Pending deletion of maven plugin docs?

Thanks Konrad and Stefan for the info. I'll publish my changes and keep in mind that those deletions will not actually be performed. Robert On Mon, 2017-03-13 at 11:49 +, Stefan Seifert wrote: > and the issue is only a "display issue" - the plugin docs are not > deleted, you can safely

RE: Pending deletion of maven plugin docs?

and the issue is only a "display issue" - the plugin docs are not deleted, you can safely publish changes on the site. but the publish diff view is unfortunately quite unusable currently. stefan >-Original Message- >From: Konrad Windszus [mailto:konra...@gmx.de] >Sent: Monday, March 13,

Re: Pending deletion of maven plugin docs?

This was already raised in http://www.mail-archive.com/dev@sling.apache.org/msg65399.html. Subsequently Bertrand opened https://issues.apache.org/jira/browse/INFRA-13644. > On 13 Mar 2017, at 12:35, Robert Munteanu wrote: > > Hi, > > When trying to publish the latest

Pending deletion of maven plugin docs?

Hi, When trying to publish the latest version of the site from [1] I get a large number of deleted files from under content/components/htl-maven- plugin . Is that intended? I am going to hold on the publishing for now. Robert [1]: https://cms.apache.org/sling/publish?diff=1

[jira] [Assigned] (SLING-6638) Vault Package Builder should not allow SHA1, MD5 digest algorithm

[ https://issues.apache.org/jira/browse/SLING-6638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret reassigned SLING-6638: - Assignee: Timothee Maret > Vault Package Builder should not allow SHA1, MD5 digest

[jira] [Created] (SLING-6638) Vault Package Builder should not allow SHA1, MD5 digest algorithm

Timothee Maret created SLING-6638: - Summary: Vault Package Builder should not allow SHA1, MD5 digest algorithm Key: SLING-6638 URL: https://issues.apache.org/jira/browse/SLING-6638 Project: Sling

[jira] [Comment Edited] (SLING-6618) Specify crx.default as workspace for AEM servers

[ https://issues.apache.org/jira/browse/SLING-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907111#comment-15907111 ] Konrad Windszus edited comment on SLING-6618 at 3/13/17 10:26 AM: --

[jira] [Comment Edited] (SLING-6618) Specify crx.default as workspace for AEM servers

[ https://issues.apache.org/jira/browse/SLING-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907111#comment-15907111 ] Konrad Windszus edited comment on SLING-6618 at 3/13/17 10:24 AM: --

[RESULT][VOTE] Release Apache Sling Resource Resolver 1.5.20

Hi, The vote has passed with the following result : +1 (binding): Oliver Lietz, Karl Pauls, Stefan Seifert, Daniel Klco, Stefan Egli, Robert Munteanu I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository.

Re: [VOTE] Apache Sling Repoinit JCR 1.1.4

On Thu, 2017-03-09 at 19:19 +0100, Oliver Lietz wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part

[jira] [Commented] (SLING-6618) Specify crx.default as workspace for AEM servers

[ https://issues.apache.org/jira/browse/SLING-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907111#comment-15907111 ] Konrad Windszus commented on SLING-6618: [~karlpauls] The workaround is quite verbose as it

[jira] [Commented] (SLING-6502) JSP: java.lang.VerifyError (Bad type on operand stack)

[ https://issues.apache.org/jira/browse/SLING-6502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907103#comment-15907103 ] Robert Munteanu commented on SLING-6502: Build is back to stable, thanks [~olli].

Re: new commons component "File System Content Parser" - name?

On Monday 13 March 2017 08:48:05 Stefan Seifert wrote: > i've recently created a new commons sling component which i named "File > System Content Parser", source currently at [1] related ticket is > SLING-6592 [2]. > > it's main goal is to support various serializiation formats of resource >

[jira] [Assigned] (SLING-6620) HTL integration tests do not honor locale format

[ https://issues.apache.org/jira/browse/SLING-6620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz reassigned SLING-6620: --- Assignee: Radu Cotescu > HTL integration tests do not honor locale format >

[jira] [Commented] (SLING-6621) Use official OSGi annotations

[ https://issues.apache.org/jira/browse/SLING-6621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907064#comment-15907064 ] Oliver Lietz commented on SLING-6621: - There are several null checks in Commons Scheduler and Commons

[jira] [Updated] (SLING-6618) Specify crx.default as workspace for AEM servers

[ https://issues.apache.org/jira/browse/SLING-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6618: --- Description: The current impl-vlt does try to connect to two different repository urls - one

new commons component "File System Content Parser" - name?

i've recently created a new commons sling component which i named "File System Content Parser", source currently at [1] related ticket is SLING-6592 [2]. it's main goal is to support various serializiation formats of resource content structures which are commonly used to export and import

[jira] [Commented] (SLING-6502) JSP: java.lang.VerifyError (Bad type on operand stack)

[ https://issues.apache.org/jira/browse/SLING-6502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907018#comment-15907018 ] Oliver Lietz commented on SLING-6502: - [~rombert], should already be fixed by

[jira] [Created] (SLING-6637) [htl] data-sly-use should not raise an exception where resource doesn't exist

Feike Visser created SLING-6637: --- Summary: [htl] data-sly-use should not raise an exception where resource doesn't exist Key: SLING-6637 URL: https://issues.apache.org/jira/browse/SLING-6637 Project:

[jira] [Resolved] (SLING-6633) [HTL] NumberFormat should support String-properties with number value

[ https://issues.apache.org/jira/browse/SLING-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-6633. - Resolution: Fixed Fixed in [r1786639|https://svn.apache.org/viewvc?view=revision=1786639]. >

[jira] [Resolved] (SLING-6632) [HTL] NumberFormat is printed when format is empty

[ https://issues.apache.org/jira/browse/SLING-6632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-6632. - Resolution: Fixed Fixed in [r1786638|https://svn.apache.org/viewvc?view=revision=1786638]. >

[jira] [Resolved] (SLING-6612) HTL/Sightly sometimes fails to recompile an updated Java POJO located in the repository

[ https://issues.apache.org/jira/browse/SLING-6612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-6612. - Resolution: Fixed Fixed in [r1786637|https://svn.apache.org/viewvc?view=revision=1786637]. >

[jira] [Updated] (SLING-6633) [HTL] NumberFormat should support String-properties with number value

[ https://issues.apache.org/jira/browse/SLING-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-6633: Summary: [HTL] NumberFormat should support String-properties with number value (was: [sightly]

[jira] [Updated] (SLING-6632) [HTL] NumberFormat is printed when format is empty

[ https://issues.apache.org/jira/browse/SLING-6632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-6632: Summary: [HTL] NumberFormat is printed when format is empty (was: [sightly]NumberFormat is printed

[jira] [Commented] (SLING-6635) Implement LRU Cache for SlingServletResolver

[ https://issues.apache.org/jira/browse/SLING-6635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906959#comment-15906959 ] Carsten Ziegeler commented on SLING-6635: - Not sure if this is really an improvement. If users are

[jira] [Commented] (SLING-6502) JSP: java.lang.VerifyError (Bad type on operand stack)

[ https://issues.apache.org/jira/browse/SLING-6502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906958#comment-15906958 ] Robert Munteanu commented on SLING-6502: Thanks! I think something else slipped through the cracks

[jira] [Commented] (SLING-6287) support maxparallel for main job queue to be -1 or between 0.0 and 1.0

[ https://issues.apache.org/jira/browse/SLING-6287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906950#comment-15906950 ] Carsten Ziegeler commented on SLING-6287: - [~olli] I think it should be fine to apply this patch

[jira] [Commented] (SLING-6621) Use official OSGi annotations

[ https://issues.apache.org/jira/browse/SLING-6621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15906940#comment-15906940 ] Carsten Ziegeler commented on SLING-6621: - [~olli] I don't think it is really required, it helps