[jira] [Commented] (SLING-3734) 'org.apache.sling.api.SlingException: Failed to generate name' when posting under load

[ https://issues.apache.org/jira/browse/SLING-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14052203#comment-14052203 ] Bertrand Delacretaz commented on SLING-3734: There was indeed something about

[jira] [Comment Edited] (SLING-3734) 'org.apache.sling.api.SlingException: Failed to generate name' when posting under load

[ https://issues.apache.org/jira/browse/SLING-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14052203#comment-14052203 ] Bertrand Delacretaz edited comment on SLING-3734 at 7/4/14 6:54 AM:

[jira] [Updated] (SLING-3734) 'org.apache.sling.api.SlingException: Failed to generate name' when posting under load

[ https://issues.apache.org/jira/browse/SLING-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-3734: --- Affects Version/s: Servlets Post 2.3.4 > 'org.apache.sling.api.SlingException: Failed

[jira] [Updated] (SLING-3734) 'org.apache.sling.api.SlingException: Failed to generate name' when posting under load

[ https://issues.apache.org/jira/browse/SLING-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-3734: --- Component/s: Servlets > 'org.apache.sling.api.SlingException: Failed to generate name

[jira] [Commented] (SLING-3730) ResourceResolver does not always set the metadata "sling.resolutionPath" properly

[ https://issues.apache.org/jira/browse/SLING-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14052186#comment-14052186 ] Carsten Ziegeler commented on SLING-3730: - While it would be correct to remove the

Jenkins build is still unstable: sling-trunk-1.6 #2256

See

Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2256

See

Jenkins build is still unstable: sling-trunk-1.7 #629

See

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #629

See

Jenkins build is still unstable: sling-trunk-1.6 #2255

See

[jira] [Updated] (SLING-3734) 'org.apache.sling.api.SlingException: Failed to generate name' when posting under load

[ https://issues.apache.org/jira/browse/SLING-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert updated SLING-3734: Attachment: (was: jmeter-config.jmx) > 'org.apache.sling.api.SlingException: Failed to

[jira] [Updated] (SLING-3734) 'org.apache.sling.api.SlingException: Failed to generate name' when posting under load

[ https://issues.apache.org/jira/browse/SLING-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert updated SLING-3734: Attachment: jmeter-config.jmx > 'org.apache.sling.api.SlingException: Failed to generate na

[jira] [Updated] (SLING-3734) 'org.apache.sling.api.SlingException: Failed to generate name' when posting under load

[ https://issues.apache.org/jira/browse/SLING-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert updated SLING-3734: Attachment: jmeter-config.jmx To reproduce simply run the attached JMeter file. I noticed

[jira] [Commented] (SLING-3730) ResourceResolver does not always set the metadata "sling.resolutionPath" properly

[ https://issues.apache.org/jira/browse/SLING-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051605#comment-14051605 ] Konrad Windszus commented on SLING-3730: [~cziegeler] Would you mind removing the

[jira] [Created] (SLING-3734) 'org.apache.sling.api.SlingException: Failed to generate name' when posting under load

David Bosschaert created SLING-3734: --- Summary: 'org.apache.sling.api.SlingException: Failed to generate name' when posting under load Key: SLING-3734 URL: https://issues.apache.org/jira/browse/SLING-3734

Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2255

See

[jira] [Resolved] (SLING-3710) Incorrect handling of nt:hierarchyNode instances nested within jcr:content nodes of other nt:hieararchyNode node

[ https://issues.apache.org/jira/browse/SLING-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3710. Resolution: Fixed > Incorrect handling of nt:hierarchyNode instances nested within jcr:cont

[jira] [Commented] (SLING-3710) Incorrect handling of nt:hierarchyNode instances nested within jcr:content nodes of other nt:hieararchyNode node

[ https://issues.apache.org/jira/browse/SLING-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051599#comment-14051599 ] Robert Munteanu commented on SLING-3710: * http://svn.apache.org/viewvc?view=revis

Jenkins build is still unstable: sling-trunk-1.7 #628

See

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #628

See

[jira] [Commented] (SLING-3730) ResourceResolver does not always set the metadata "sling.resolutionPath" properly

[ https://issues.apache.org/jira/browse/SLING-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051559#comment-14051559 ] Carsten Ziegeler commented on SLING-3730: - I've added two missing calls and also r

[jira] [Updated] (SLING-3730) ResourceResolver does not always set the metadata "sling.resolutionPath" properly

[ https://issues.apache.org/jira/browse/SLING-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3730: Affects Version/s: JCR Resource 2.3.6 > ResourceResolver does not always set the metadata "

[jira] [Updated] (SLING-3730) ResourceResolver does not always set the metadata "sling.resolutionPath" properly

[ https://issues.apache.org/jira/browse/SLING-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3730: Fix Version/s: JCR Resource 2.3.8 > ResourceResolver does not always set the metadata "slin

[jira] [Updated] (SLING-3730) ResourceResolver does not always set the metadata "sling.resolutionPath" properly

[ https://issues.apache.org/jira/browse/SLING-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3730: Summary: ResourceResolver does not always set the metadata "sling.resolutionPath" properly

[jira] [Updated] (SLING-3730) MergedResource does not set the metadata "sling.resolutionPath" properly

[ https://issues.apache.org/jira/browse/SLING-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3730: Fix Version/s: Resource Resolver 1.1.2 > MergedResource does not set the metadata "sling.re

[jira] [Updated] (SLING-3730) MergedResource does not set the metadata "sling.resolutionPath" properly

[ https://issues.apache.org/jira/browse/SLING-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3730: Affects Version/s: (was: Resource Merger 1.1.2) Resource Resolver

[jira] [Assigned] (SLING-3730) MergedResource does not set the metadata "sling.resolutionPath" properly

[ https://issues.apache.org/jira/browse/SLING-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-3730: --- Assignee: Carsten Ziegeler > MergedResource does not set the metadata "sling.resoluti

[jira] [Commented] (SLING-3730) MergedResource does not set the metadata "sling.resolutionPath" properly

[ https://issues.apache.org/jira/browse/SLING-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051544#comment-14051544 ] Carsten Ziegeler commented on SLING-3730: - Good catch, yes, the resource resolver

Jenkins build is unstable: sling-trunk-1.6 #2254

See

Jenkins build is back to normal : sling-trunk-1.6 » Apache Sling Launchpad Application Builder #2254

See

Jenkins build is unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2254

See

Jenkins build is still unstable: sling-trunk-1.7 #627

See

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #627

See

[jira] [Comment Edited] (SLING-3730) MergedResource does not set the metadata "sling.resolutionPath" properly

[ https://issues.apache.org/jira/browse/SLING-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051506#comment-14051506 ] Konrad Windszus edited comment on SLING-3730 at 7/3/14 2:30 PM:

[jira] [Commented] (SLING-3730) MergedResource does not set the metadata "sling.resolutionPath" properly

[ https://issues.apache.org/jira/browse/SLING-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051506#comment-14051506 ] Konrad Windszus commented on SLING-3730: I assume that under certain circumstances

[jira] [Created] (SLING-3733) Remodel API for more natural usage of IO operations

Robert Munteanu created SLING-3733: -- Summary: Remodel API for more natural usage of IO operations Key: SLING-3733 URL: https://issues.apache.org/jira/browse/SLING-3733 Project: Sling Issue T

[jira] [Resolved] (SLING-3648) CLONE - Content Loader ignores bundles that were upgraded when the OSGi container was offline

[ https://issues.apache.org/jira/browse/SLING-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-3648. Resolution: Fixed Assignee: Bertrand Delacretaz Thanks for your contribution,

[jira] [Commented] (SLING-3730) MergedResource does not set the metadata "sling.resolutionPath" properly

[ https://issues.apache.org/jira/browse/SLING-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051498#comment-14051498 ] Konrad Windszus commented on SLING-3730: I only have an example for AEM6. You find

[jira] [Updated] (SLING-3730) MergedResource does not set the metadata "sling.resolutionPath" properly

[ https://issues.apache.org/jira/browse/SLING-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-3730: --- Attachment: rewriter-issue-1.0.zip > MergedResource does not set the metadata "sling.resoluti

Re: release of fsresource bundle?

On Monday 30 June 2014 17:09:16 Bertrand Delacretaz wrote: > On Mon, Jun 30, 2014 at 12:05 PM, Oliver Lietz wrote: > > On Monday 30 June 2014 11:44:33 Stefan Seifert wrote: > >> can we make a new release of the fsresource bundle? > > ... > > > +1 (as this is one of two snapshot bundles left ove

[jira] [Comment Edited] (SLING-3730) MergedResource does not set the metadata "sling.resolutionPath" properly

[ https://issues.apache.org/jira/browse/SLING-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051484#comment-14051484 ] Carsten Ziegeler edited comment on SLING-3730 at 7/3/14 2:16 PM: ---

[jira] [Commented] (SLING-3730) MergedResource does not set the metadata "sling.resolutionPath" properly

[ https://issues.apache.org/jira/browse/SLING-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051484#comment-14051484 ] Carsten Ziegeler commented on SLING-3730: - Actually this should be set by the reso

[jira] [Commented] (SLING-3699) [Job Scheduling] A job scheduled using JobBuilder does not get removed if the JobConsumer returns JobResult.OK

[ https://issues.apache.org/jira/browse/SLING-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051465#comment-14051465 ] Carsten Ziegeler commented on SLING-3699: - [~anshika] The workaround should not po

[jira] [Created] (SLING-3731) add an authentication module using XING API with OAuth

Oliver Lietz created SLING-3731: --- Summary: add an authentication module using XING API with OAuth Key: SLING-3731 URL: https://issues.apache.org/jira/browse/SLING-3731 Project: Sling Issue Type

[jira] [Resolved] (SLING-3701) [Job Scheduling] : No API to search through the scheduled jobs based on some properties.

[ https://issues.apache.org/jira/browse/SLING-3701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3701. - Resolution: Fixed I've added a new method getScheduledJobs with takes similar arguments a

[jira] [Created] (SLING-3732) add an authentication module using "Login with XING"

Oliver Lietz created SLING-3732: --- Summary: add an authentication module using "Login with XING" Key: SLING-3732 URL: https://issues.apache.org/jira/browse/SLING-3732 Project: Sling Issue Type:

Build failed in Jenkins: sling-trunk-1.6 #2253

See Changes: [bdelacretaz] Fix wrong comment [rombert] SLING-3681 - Enable the maven-launchpad-plugin to generate the XSD for bundles list XML document Update the target namespace. Submitted by: Simone Tripodi -

Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Launchpad Application Builder #2253

See -- [INFO] [INFO] -

Jenkins build is still unstable: sling-trunk-1.7 #626

See

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #626

See

Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Installer Integration Tests #626

See

[jira] [Updated] (SLING-3730) MergedResource does not set the metadata "sling.resolutionPath" properly

[ https://issues.apache.org/jira/browse/SLING-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-3730: --- Description: This metadata is evaluated by calling: SlingHttpServletRequest.getRequestPathIn

[jira] [Commented] (SLING-3730) MergedResource does not set the metadata "sling.resolutionPath" properly

[ https://issues.apache.org/jira/browse/SLING-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051424#comment-14051424 ] Konrad Windszus commented on SLING-3730: I would propose setting that to the resou

Re: adaptTo and results ....

On 03.07.2014, at 13:58, Justin Edelson wrote: > It won't work :) This is a hugely non-backwards compatible change. It > happens to be binary compatible, but it is not semantically compatible > (which is in some ways just as important). Callers of adaptTo() assume > (because we have told them to

[jira] [Commented] (SLING-3714) Allow for a caller to request a non-null response from adaptTo()

[ https://issues.apache.org/jira/browse/SLING-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051413#comment-14051413 ] Alexander Klimetschek commented on SLING-3714: -- Another option as discussed o

[jira] [Created] (SLING-3730) MergedResource does not set the metadata "sling.resolutionPath" properly

Konrad Windszus created SLING-3730: -- Summary: MergedResource does not set the metadata "sling.resolutionPath" properly Key: SLING-3730 URL: https://issues.apache.org/jira/browse/SLING-3730 Project: S

Re: adaptTo and results ....

On 03.07.2014, at 12:19, Felix Meschberger wrote: >>> I guess it would make sense to have adapterfactories et. al. to work like >>> this: >>> a) if it is not of the desired type, i.e. cannot semantically be adapted, >>> return null > > example: resource.adaptTo(Node.class) for a resource not b

[jira] [Updated] (SLING-3699) [Job Scheduling] A job scheduled using JobBuilder does not get removed if the JobConsumer returns JobResult.OK

[ https://issues.apache.org/jira/browse/SLING-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3699: Fix Version/s: Event 3.3.12 > [Job Scheduling] A job scheduled using JobBuilder does not ge

[jira] [Assigned] (SLING-3699) [Job Scheduling] A job scheduled using JobBuilder does not get removed if the JobConsumer returns JobResult.OK

[ https://issues.apache.org/jira/browse/SLING-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-3699: --- Assignee: Carsten Ziegeler > [Job Scheduling] A job scheduled using JobBuilder does n

Build failed in Jenkins: sling-trunk-1.6 #2252

See Changes: [rombert] SLING-3710 - Incorrect handling of nt:hierarchyNode instances nested within jcr:content nodes of other nt:hieararchyNode node Added an ignored test which shows the failure scenario --

Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Launchpad Application Builder #2252

See -- [INFO] [INFO] -

Jenkins build is still unstable: sling-trunk-1.7 #625

See

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Installer Integration Tests #625

See

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #625

See

[jira] [Commented] (SLING-3681) Enable the maven-launchpad-plugin to generate the XSD for bundles list XML document

[ https://issues.apache.org/jira/browse/SLING-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051382#comment-14051382 ] Robert Munteanu commented on SLING-3681: Updated just now. You might need to force

RE: adaptTo and results ....

>* My original suggestion of using a Result interface. This requires >more verbose code on the caller side -- the caller needs to check a >success flag -- but allows for fine-grained information (which would >be appropriate for a validation use case). +1 https://issues.apache.org/jira/browse/SLI

[jira] [Updated] (SLING-3681) Enable the maven-launchpad-plugin to generate the XSD for bundles list XML document

[ https://issues.apache.org/jira/browse/SLING-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi updated SLING-3681: -- Attachment: SLING-3681.patch [~rombert] [~cziegeler] I'd like to kindly ask you to republish th

[jira] [Commented] (SLING-3709) Sling Models: Allow caller to deal with exceptions

[ https://issues.apache.org/jira/browse/SLING-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051365#comment-14051365 ] Justin Edelson commented on SLING-3709: --- No. Such a change violates the contract of

Re: adaptTo and results ....

Hi, On Thu, Jul 3, 2014 at 4:50 AM, Alexander Klimetschek wrote: > On 03.07.2014, at 09:12, Konrad Windszus wrote: > >> - The client can decide how to expose that error (whether just logging is >> fine or something more obvious). This cannot be achieved by just setting up >> a utility method,

[jira] [Commented] (SLING-3710) Incorrect handling of nt:hierarchyNode instances nested within jcr:content nodes of other nt:hieararchyNode node

[ https://issues.apache.org/jira/browse/SLING-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051356#comment-14051356 ] Robert Munteanu commented on SLING-3710: Added a failing and ignored test in http

Re: adaptTo and results ....

Hi Am 03.07.2014 um 12:29 schrieb Konrad Windszus : > The AdapterFactory should clearly state, which RuntimeExceptions are thrown > under which condition. You know in most of the cases, which AdapterFactory is > responsible for your adaptTo-method (or you should be able to find out with > the

Re: adaptTo and results ....

The AdapterFactory should clearly state, which RuntimeExceptions are thrown under which condition. You know in most of the cases, which AdapterFactory is responsible for your adaptTo-method (or you should be able to find out with the web console) Handling in some cases is more than simple loggin

Build failed in Jenkins: sling-trunk-1.6 #2251

See Changes: [stefanegli] SLING-3690 : moved 'New Node...' action under 'New' menu to be consistent [cziegeler] [maven-release-plugin] prepare for next development iteration [cziegeler] [maven-release-plugin] prepare release org.apa

Re: adaptTo and results ....

Hi Am 03.07.2014 um 11:10 schrieb Konrad Windszus : > > On 03 Jul 2014, at 10:50, Alexander Klimetschek wrote: > >> >> I guess it would make sense to have adapterfactories et. al. to work like >> this: >> a) if it is not of the desired type, i.e. cannot semantically be adapted, >> return nu

Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Launchpad Application Builder #2251

See Changes: [cziegeler] Use latest scripting.jsp snapshot -- [INFO] [INFO] -

[jira] [Commented] (SLING-3681) Enable the maven-launchpad-plugin to generate the XSD for bundles list XML document

[ https://issues.apache.org/jira/browse/SLING-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051283#comment-14051283 ] Simone Tripodi commented on SLING-3681: --- AMAZING thanks Robert for your support! :)

[jira] [Updated] (SLING-3729) Register XML catalog contribtion for bundle list schema

[ https://issues.apache.org/jira/browse/SLING-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3729: --- Description: With SLING-3681, we now have an XML schema file which can be used to validate t

[jira] [Comment Edited] (SLING-3681) Enable the maven-launchpad-plugin to generate the XSD for bundles list XML document

[ https://issues.apache.org/jira/browse/SLING-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051225#comment-14051225 ] Robert Munteanu edited comment on SLING-3681 at 7/3/14 10:01 AM: ---

[jira] [Created] (SLING-3729) Register XML catalog contribtion for bundle list schema

Robert Munteanu created SLING-3729: -- Summary: Register XML catalog contribtion for bundle list schema Key: SLING-3729 URL: https://issues.apache.org/jira/browse/SLING-3729 Project: Sling Iss

Jenkins build is still unstable: sling-trunk-1.7 #624

See

[jira] [Commented] (SLING-3681) Enable the maven-launchpad-plugin to generate the XSD for bundles list XML document

[ https://issues.apache.org/jira/browse/SLING-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051277#comment-14051277 ] Robert Munteanu commented on SLING-3681: https://sling.apache.org/xsd/bundle-list-

[jira] [Updated] (SLING-915) [Rhino] Implement Compilable

[ https://issues.apache.org/jira/browse/SLING-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-915: Summary: [Rhino] Implement Compilable (was: Implement Compilable) > [Rhino] Implement Compi

[jira] [Updated] (SLING-914) [JSP] Implement Compilable

[ https://issues.apache.org/jira/browse/SLING-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-914: Summary: [JSP] Implement Compilable (was: Implement Compilable) > [JSP] Implement Compilabl

[jira] [Commented] (SLING-3709) Sling Models: Allow caller to deal with exceptions

[ https://issues.apache.org/jira/browse/SLING-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051269#comment-14051269 ] Konrad Windszus commented on SLING-3709: It seems that throwing a RuntimeException

Jenkins build became unstable: sling-contrib-1.6 » Apache Sling Replication Integration Tests #1167

See

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #624

See

[jira] [Commented] (SLING-3681) Enable the maven-launchpad-plugin to generate the XSD for bundles list XML document

[ https://issues.apache.org/jira/browse/SLING-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051237#comment-14051237 ] Carsten Ziegeler commented on SLING-3681: - +1 for https://sling.apache.org/xsd/bun

[jira] [Commented] (SLING-3681) Enable the maven-launchpad-plugin to generate the XSD for bundles list XML document

[ https://issues.apache.org/jira/browse/SLING-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051231#comment-14051231 ] Simone Tripodi commented on SLING-3681: --- it works for me, thanks for following-up! :

Re: adaptTo and results ....

On 03 Jul 2014, at 10:50, Alexander Klimetschek wrote: > > I guess it would make sense to have adapterfactories et. al. to work like > this: > a) if it is not of the desired type, i.e. cannot semantically be adapted, > return null > b) if it fails due to some actual exception, throw a runtime

[jira] [Commented] (SLING-3681) Enable the maven-launchpad-plugin to generate the XSD for bundles list XML document

[ https://issues.apache.org/jira/browse/SLING-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051225#comment-14051225 ] Robert Munteanu commented on SLING-3681: (Sorry, this dropped on my radar). I look

Re: adaptTo and results ....

Hi, On Tue, Jul 1, 2014 at 5:16 PM, Felix Meschberger wrote: > Am 01.07.2014 um 09:44 schrieb Bertrand Delacretaz : > ...Unfortunately, I don't think this works, because the adaptTo signature is: > > public AdapterType adaptTo(Class type); > > Hence the return type is the same as provided as t

Re: adaptTo and results ....

On 03.07.2014, at 09:12, Konrad Windszus wrote: > - The client can decide how to expose that error (whether just logging is > fine or something more obvious). This cannot be achieved by just setting up a > utility method, because that one does only see the null return value and not > the origi

[jira] [Closed] (SLING-3632) Configuration installer should ignore location events

[ https://issues.apache.org/jira/browse/SLING-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-3632. --- > Configuration installer should ignore location events > ---

Re: [VOTE] Release Apache Sling Scripting JSP 2.1.4 and Apache Sling Scripting Java 2.0.10

+1 2014-07-03 10:04 GMT+02:00 Robert Munteanu : > +1 > > Robert > > On Thu, Jul 3, 2014 at 10:39 AM, Carsten Ziegeler > wrote: > > Hi, > > > > We solved two issues for each scripting bundle, especially with > SLING-3724 > > these bundles now provide a better experience with Java 8 as they run >

Re: [VOTE] Release Apache Sling Scripting JSP 2.1.4 and Apache Sling Scripting Java 2.0.10

+1 Robert On Thu, Jul 3, 2014 at 10:39 AM, Carsten Ziegeler wrote: > Hi, > > We solved two issues for each scripting bundle, especially with SLING-3724 > these bundles now provide a better experience with Java 8 as they run > without configuration changes on Java 8 as well as previous versions.

[jira] [Resolved] (SLING-3690) Cannot create JCR Nodes under a sling:Folder

[ https://issues.apache.org/jira/browse/SLING-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-3690. Resolution: Fixed fixed: moved 'New Node...' action under 'New' menu to be consistent > Cannot cre

[VOTE] Release Apache Sling Scripting JSP 2.1.4 and Apache Sling Scripting Java 2.0.10

Hi, We solved two issues for each scripting bundle, especially with SLING-3724 these bundles now provide a better experience with Java 8 as they run without configuration changes on Java 8 as well as previous versions. Scripting JSP https://issues.apache.org/jira/browse/SLING/fixforversion/123268

[jira] [Created] (SLING-3728) MapEntries->aliasMap ds incorrect information in case of alias path removal

Antonio Sanso created SLING-3728: Summary: MapEntries->aliasMap ds incorrect information in case of alias path removal Key: SLING-3728 URL: https://issues.apache.org/jira/browse/SLING-3728 Project: Sl

Re: adaptTo and results ....

Passing through exceptions has the following advantages IMHO: - The client can decide how to expose that error (whether just logging is fine or something more obvious). This cannot be achieved by just setting up a utility method, because that one does only see the null return value and not the

Re: [VOTE] Release Apache Sling Scripting JSP 2.1.2 and Apache Sling Scripting Java 2.0.8

I have to cancel the vote as these artifacts do not run under 1.6 I accidentially check the wrong system property :( I'll fix this, create new artifacts and start a new vote Carsten 2014-07-03 7:35 GMT+02:00 Carsten Ziegeler : > +1 > > > 2014-07-02 16:37 GMT+02:00 Justin Edelson : > > +1 >> >>

  1   2   >