[jira] [Commented] (SLING-1437) GSoC project: create more unit and integration tests for Sling and expand test coverage information

[ https://issues.apache.org/jira/browse/SLING-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383398#comment-14383398 ] Petr Shypila commented on SLING-1437: - My proposal for this project:

Re: [VOTE] Release Apache Sling Content Distribution (api, core, sample, it) 0.1.0

On Tuesday 24 March 2015 16:24:21 Tommaso Teofili wrote: Hi all, This is the vote for the first Sling Content Distribution [1] release (version 0.1.0) which includes 4 modules (org.apache.sling.distribution.[api,core,sample,it]) We solved 101 issues there:

Re: Sling Content Distribution ITs (was: Re: [VOTE] Release Apache Sling Content Distribution (api, core, sample, it) 0.1.0)

I installed (mvn clean install) org.apache.sling.distribution.api, org.apache.sling.distribution.core, org.apache.sling.distribution.sample and then org.apache.sling.distribution.it from their respective svn tags [1,2,3,4] and everything worked for me (tried multiple times). May it be a platform

[jira] [Commented] (SLING-4432) Sling Models: Include more specific information in model adaption failure log messages

[ https://issues.apache.org/jira/browse/SLING-4432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383672#comment-14383672 ] Stefan Seifert commented on SLING-4432: --- Completed: At revision: 1669540 make

Re: [VOTE] Accept the donation of the Hypermedia API Tools via SLING-4513

+1 -- Sandro Am 25.03.15 um 16:53 schrieb Andrei Dulvac: Hello, Following a recent discussion on this list, I'm starting a [VOTE] thread regarding the donation of HApi (Hypermedia API tools). Issue: SLING-4513 Github repo: https://github.com/dulvac/hapi MD5 of archive: MD5 (hapi.tar.gz) =

Re: Sling Content Distribution ITs (was: Re: [VOTE] Release Apache Sling Content Distribution (api, core, sample, it) 0.1.0)

2015-03-27 10:03 GMT+01:00 Oliver Lietz apa...@oliverlietz.de: On Friday 27 March 2015 09:39:20 Tommaso Teofili wrote: Hi Oliver, Hi Tommaso, nope, nothing special. All the ITs can fail if the setup of the base test fails, as that happens in a static block; this may happen if the

Re: Sling Content Distribution ITs (was: Re: [VOTE] Release Apache Sling Content Distribution (api, core, sample, it) 0.1.0)

On Friday 27 March 2015 09:39:20 Tommaso Teofili wrote: Hi Oliver, Hi Tommaso, nope, nothing special. All the ITs can fail if the setup of the base test fails, as that happens in a static block; this may happen if the Sling servers started for integration testing fail to start within 1

Re: Sling Content Distribution ITs (was: Re: [VOTE] Release Apache Sling Content Distribution (api, core, sample, it) 0.1.0)

On Friday 27 March 2015 10:21:18 Tommaso Teofili wrote: [...] I tried several times and it failed always. Here's the output: https://gist.github.com/oliverlietz/1dd00350ea551679c407 Can you have a look? sure, are you running from the 0.1.0 svn tag or from trunk ? I just tried from

Sling Content Distribution ITs (was: Re: [VOTE] Release Apache Sling Content Distribution (api, core, sample, it) 0.1.0)

Hi Oliver, nope, nothing special. All the ITs can fail if the setup of the base test fails, as that happens in a static block; this may happen if the Sling servers started for integration testing fail to start within 1 minute, that should however be clear from the console output; look for the

[jira] [Reopened] (SLING-4161) Support Sling Validation through a new field of the Model annotation

[ https://issues.apache.org/jira/browse/SLING-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert reopened SLING-4161: --- this has to be moved to a separate bundle. according to [recent mailing list

[jira] [Resolved] (SLING-4532) Performance: DefaultSlingScript has too much overhead

[ https://issues.apache.org/jira/browse/SLING-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Richard resolved SLING-4532. - Resolution: Invalid Closing because the overhead is added in a BindingsValuesProvider which is

[jira] [Created] (SLING-4547) JcrResourceBundle does not support multiple base names

Andrei Pilets created SLING-4547: Summary: JcrResourceBundle does not support multiple base names Key: SLING-4547 URL: https://issues.apache.org/jira/browse/SLING-4547 Project: Sling Issue

[jira] [Reopened] (SLING-4447) Improve JavaUseProvider to not fall back to a simple Pojo instantiation in case a Java class with @Model annotation cannot be instantiated

[ https://issues.apache.org/jira/browse/SLING-4447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert reopened SLING-4447: --- this has to be moved to a separate bundle. according to [recent mailing list

[jira] [Commented] (SLING-4544) Performance: MessageFormat shouldn't be used for logging in SlingRequestProgressTracker

[ https://issues.apache.org/jira/browse/SLING-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383781#comment-14383781 ] Robert Munteanu commented on SLING-4544: Well, the problem with that is we have a

[jira] [Commented] (SLING-4544) Performance: MessageFormat shouldn't be used for logging in SlingRequestProgressTracker

[ https://issues.apache.org/jira/browse/SLING-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383784#comment-14383784 ] Joel Richard commented on SLING-4544: - [~rombert], although the log-API mentions

Re: svn commit: r1668712 - /sling/trunk/launchpad/testing/pom.xml

On Tue, 2015-03-24 at 13:10 +0100, Julian Sedding wrote: Hi Robert I was wondering whether these changes are at the right place. There is a sling.properties file in launchpad/testing, which still has the old run mode definition. Sightly testing may also be affected. Note that I didn't run

[jira] [Commented] (SLING-4544) Performance: MessageFormat shouldn't be used for logging in SlingRequestProgressTracker

[ https://issues.apache.org/jira/browse/SLING-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383793#comment-14383793 ] Robert Munteanu commented on SLING-4544: [~joelrich] - I missed the fact that this

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

[ https://issues.apache.org/jira/browse/SLING-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrei Pilets updated SLING-4547: - Description: The sling:basename property may be multi-valued, that is the messages of a

Infra asking for feedback on CMS decommissioning proposal

Hi, The infra team has started a discussion on infrastructure-dev [1] regarding their proposal to decommission the CMS service as it currently stands. I would encourage you to skim the thread and also look at the official FAQ [2]. If there are any concerns/clarifications needs from the Sling

[jira] [Commented] (SLING-4544) Performance: MessageFormat shouldn't be used for logging in SlingRequestProgressTracker

[ https://issues.apache.org/jira/browse/SLING-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383818#comment-14383818 ] Bertrand Delacretaz commented on SLING-4544: A limited MessageFormat

Re: Infra asking for feedback on CMS decommissioning proposal

*happily says bye bye to the CMS service* Tommaso 2015-03-27 14:50 GMT+01:00 Robert Munteanu romb...@apache.org: Hi, The infra team has started a discussion on infrastructure-dev [1] regarding their proposal to decommission the CMS service as it currently stands. I would encourage you to

[jira] [Updated] (SLING-4543) i18n: support for json dictionaries

[ https://issues.apache.org/jira/browse/SLING-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-4543: - Affects Version/s: i18n 2.3.2 Fix Version/s: i18n 2.3.4 i18n: support for json

Re: sling mocks, null pointer exception when checking the resource type of the root node

Hi Santiago, On Tue, Mar 24, 2015 at 6:31 PM, Santiago García Pimentel santiago.pimen...@netcentric.biz wrote: Hello, I recently created SLING-4500 because of a bug in sling mocks, when using the default resource resolver in sling mocks, the root node does not have any jcr:primary type, this

[jira] [Assigned] (SLING-4543) i18n: support for json dictionaries

[ https://issues.apache.org/jira/browse/SLING-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-4543: Assignee: Felix Meschberger i18n: support for json dictionaries

[jira] [Resolved] (SLING-4543) i18n: support for json dictionaries

[ https://issues.apache.org/jira/browse/SLING-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4543. -- Resolution: Fixed I have applied the patch in Rev. 1669598. i18n: support for json

[jira] [Commented] (SLING-4543) i18n: support for json dictionaries

[ https://issues.apache.org/jira/browse/SLING-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383911#comment-14383911 ] Felix Meschberger commented on SLING-4543: -- Thanks [~alexander.klimetschek] for

Re: Infra asking for feedback on CMS decommissioning proposal

On Fri, Mar 27, 2015 at 3:13 PM, Tommaso Teofili tommaso.teof...@gmail.com wrote: *happily says bye bye to the CMS service*... So you're volunteering for any required content conversions? ;-) I like the current Apache CMS workflow - edit in svn or git, preview on a staging website (on my box

[jira] [Created] (SLING-4548) Loading files with the JCR_MOCK resource resolver type logs leads to exceptions being logged

Robert Munteanu created SLING-4548: -- Summary: Loading files with the JCR_MOCK resource resolver type logs leads to exceptions being logged Key: SLING-4548 URL: https://issues.apache.org/jira/browse/SLING-4548

[jira] [Commented] (SLING-4548) Loading files with the JCR_MOCK resource resolver type logs leads to exceptions being logged

[ https://issues.apache.org/jira/browse/SLING-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14383956#comment-14383956 ] Robert Munteanu commented on SLING-4548: [~sseif...@pro-vision.de] - thoughts? I'd

Jenkins build became unstable: sling-trunk-1.8 #907

See https://builds.apache.org/job/sling-trunk-1.8/907/changes

[jira] [Comment Edited] (SLING-4544) Performance: MessageFormat shouldn't be used for logging in SlingRequestProgressTracker

[ https://issues.apache.org/jira/browse/SLING-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384093#comment-14384093 ] Felix Meschberger edited comment on SLING-4544 at 3/27/15 4:29 PM:

[jira] [Commented] (SLING-4544) Performance: MessageFormat shouldn't be used for logging in SlingRequestProgressTracker

[ https://issues.apache.org/jira/browse/SLING-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384065#comment-14384065 ] Felix Meschberger commented on SLING-4544: -- The API defines MessageFormat pattern

[jira] [Commented] (SLING-4544) Performance: MessageFormat shouldn't be used for logging in SlingRequestProgressTracker

[ https://issues.apache.org/jira/browse/SLING-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384093#comment-14384093 ] Felix Meschberger commented on SLING-4544: -- I think this can be cheap: scan the

Jenkins build is still unstable: sling-trunk-1.8 #908

See https://builds.apache.org/job/sling-trunk-1.8/changes

[jira] [Commented] (SLING-4544) Performance: MessageFormat shouldn't be used for logging in SlingRequestProgressTracker

[ https://issues.apache.org/jira/browse/SLING-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384076#comment-14384076 ] Bertrand Delacretaz commented on SLING-4544: Good point about keeping

[jira] [Comment Edited] (SLING-4544) Performance: MessageFormat shouldn't be used for logging in SlingRequestProgressTracker

[ https://issues.apache.org/jira/browse/SLING-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384065#comment-14384065 ] Felix Meschberger edited comment on SLING-4544 at 3/27/15 4:16 PM:

Re: Infra asking for feedback on CMS decommissioning proposal

2015-03-27 15:32 GMT+01:00 Bertrand Delacretaz bdelacre...@apache.org: On Fri, Mar 27, 2015 at 3:13 PM, Tommaso Teofili tommaso.teof...@gmail.com wrote: *happily says bye bye to the CMS service*... So you're volunteering for any required content conversions? ;-) oh no! :-) I like the

Re: Infra asking for feedback on CMS decommissioning proposal

On Fri, Mar 27, 2015 at 10:32 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Fri, Mar 27, 2015 at 3:13 PM, Tommaso Teofili tommaso.teof...@gmail.com wrote: *happily says bye bye to the CMS service*... So you're volunteering for any required content conversions? ;-) I like the

[jira] [Commented] (SLING-4544) Performance: MessageFormat shouldn't be used for logging in SlingRequestProgressTracker

[ https://issues.apache.org/jira/browse/SLING-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384496#comment-14384496 ] Robert Munteanu commented on SLING-4544: {quote}The API defines MessageFormat

[jira] [Commented] (SLING-4544) Performance: MessageFormat shouldn't be used for logging in SlingRequestProgressTracker

[ https://issues.apache.org/jira/browse/SLING-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384694#comment-14384694 ] Alexander Klimetschek commented on SLING-4544: -- BTW, the request progress

[jira] [Created] (SLING-4549) i18n documentation typo in sling:Message sling:MessageEntry node type

Alexander Klimetschek created SLING-4549: Summary: i18n documentation typo in sling:Message sling:MessageEntry node type Key: SLING-4549 URL: https://issues.apache.org/jira/browse/SLING-4549

[jira] [Updated] (SLING-4549) i18n documentation typo in sling:Message sling:MessageEntry node type

[ https://issues.apache.org/jira/browse/SLING-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-4549: - Component/s: Extensions i18n documentation typo in sling:Message

build version numbering in sling jenkins build and debian package version number

I'd like to make the debian package that's built by jenkins have a unique version number that reflects the jenkins build number or some other meaningful version string. Currently it's stuck at 8-SNAPSHOT because this started off being tied to the launchpad build. It's not even related to

[jira] [Updated] (SLING-4512) Traversal Warnings in OAK while creating i18n JcrResourceBundle

[ https://issues.apache.org/jira/browse/SLING-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-4512: - Attachment: SLING-4512-alex.patch Here is a new patch on top of trunk (since

[jira] [Updated] (SLING-4512) Traversal Warnings in OAK while creating i18n JcrResourceBundle

[ https://issues.apache.org/jira/browse/SLING-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-4512: - Attachment: SLING-4512-alex.patch Traversal Warnings in OAK while creating i18n

[jira] [Updated] (SLING-4512) Traversal Warnings in OAK while creating i18n JcrResourceBundle

[ https://issues.apache.org/jira/browse/SLING-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-4512: - Attachment: (was: SLING-4512-alex.patch) Traversal Warnings in OAK while

[jira] [Comment Edited] (SLING-4512) Traversal Warnings in OAK while creating i18n JcrResourceBundle

[ https://issues.apache.org/jira/browse/SLING-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384754#comment-14384754 ] Alexander Klimetschek edited comment on SLING-4512 at 3/27/15 9:56 PM:

[jira] [Comment Edited] (SLING-4512) Traversal Warnings in OAK while creating i18n JcrResourceBundle

[ https://issues.apache.org/jira/browse/SLING-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384754#comment-14384754 ] Alexander Klimetschek edited comment on SLING-4512 at 3/27/15 9:56 PM: