[jira] [Commented] (SLING-4677) Allow to start in debug mode through a mojo parameter similar to debugForkedProcess

[ https://issues.apache.org/jira/browse/SLING-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528363#comment-14528363 ] Konrad Windszus commented on SLING-4677: With r1677798 I added a mojo parameter

Build failed in Jenkins: sling-trunk-1.7 #1793

See https://builds.apache.org/job/sling-trunk-1.7/1793/changes Changes: [bdelacretaz] SLING-4416 - change status back to CRITICAL as it was before -- [...truncated 19392 lines...] [INFO] Apache Sling Initial Content Loader ... SUCCESS

Jenkins build is unstable: sling-trunk-1.7 #1794

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

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

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

Jenkins build is back to stable : sling-trunk-1.8 #1084

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

Jenkins build is back to stable : sling-trunk-1.7 #1795

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

Re: Extracting Eclipse Reference from impl-vlt

Hi Robert In IntelliJ components are not managed by an OSGi container and so the extension of the Eclipse’s Plugin class and the use of OSGi is troublesome. I managed to create a Stub so that I can use the code from the project but I discovered other usages of the OSGi bundles like in the

Jenkins build is still unstable: sling-contrib-1.7 #58

See https://builds.apache.org/job/sling-contrib-1.7/58/

[jira] [Commented] (SLING-4417) HC Annotation should allow to configure immediate SCR property

[ https://issues.apache.org/jira/browse/SLING-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528530#comment-14528530 ] Carsten Ziegeler commented on SLING-4417: - Ok, I see your point - for servlets

Jenkins build is still unstable: sling-contrib-1.7 #57

See https://builds.apache.org/job/sling-contrib-1.7/57/

[jira] [Commented] (SLING-4417) HC Annotation should allow to configure immediate SCR property

[ https://issues.apache.org/jira/browse/SLING-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528496#comment-14528496 ] Georg Henzler commented on SLING-4417: -- @[~cziegeler] I am aware that state is lost

[jira] [Commented] (SLING-4416) Improve HC Message/Status if a HC implementation throws an exception

[ https://issues.apache.org/jira/browse/SLING-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528526#comment-14528526 ] Georg Henzler commented on SLING-4416: -- From my my project's requirements it doesn't

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

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

Jenkins build is still unstable: sling-contrib-1.7 #61

See https://builds.apache.org/job/sling-contrib-1.7/changes

Jenkins build is still unstable: sling-contrib-1.7 #59

See https://builds.apache.org/job/sling-contrib-1.7/changes

[jira] [Created] (SLING-4692) Decouple Sightly from the JCR Compiler

Radu Cotescu created SLING-4692: --- Summary: Decouple Sightly from the JCR Compiler Key: SLING-4692 URL: https://issues.apache.org/jira/browse/SLING-4692 Project: Sling Issue Type: Improvement

[jira] [Resolved] (SLING-4692) Decouple Sightly from the JCR Compiler

[ https://issues.apache.org/jira/browse/SLING-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-4692. - Resolution: Fixed Fixed in [r1677848|https://svn.apache.org/r1677848]. Decouple Sightly from

Build failed in Jenkins: sling-trunk-1.7 #1797

See https://builds.apache.org/job/sling-trunk-1.7/1797/changes Changes: [radu] SLING-4692 - Decouple Sightly from the JCR Compiler * switched to using the JavaCompiler instead of the JcrJavaCompiler for generating Java classes from Sightly scripts --

Jenkins build is back to stable : sling-trunk-1.8 #1086

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

[jira] [Commented] (SLING-4677) Allow to start in debug mode through a mojo parameter similar to debugForkedProcess

[ https://issues.apache.org/jira/browse/SLING-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528064#comment-14528064 ] Konrad Windszus commented on SLING-4677: It is all in

[jira] [Commented] (SLING-4677) Allow to start in debug mode through a mojo parameter similar to debugForkedProcess

[ https://issues.apache.org/jira/browse/SLING-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528056#comment-14528056 ] Radu Cotescu commented on SLING-4677: - [~kwin], how can I set the debug value for this

[jira] [Commented] (SLING-4677) Allow to start in debug mode through a mojo parameter similar to debugForkedProcess

[ https://issues.apache.org/jira/browse/SLING-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528069#comment-14528069 ] Radu Cotescu commented on SLING-4677: - Yeah, I looked at the patch but I can't figure

[jira] [Issue Comment Deleted] (SLING-4677) Allow to start in debug mode through a mojo parameter similar to debugForkedProcess

[ https://issues.apache.org/jira/browse/SLING-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-4677: --- Comment: was deleted (was: It is all in

[jira] [Issue Comment Deleted] (SLING-4677) Allow to start in debug mode through a mojo parameter similar to debugForkedProcess

[ https://issues.apache.org/jira/browse/SLING-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-4677: --- Comment: was deleted (was: It is all in

[jira] [Commented] (SLING-4677) Allow to start in debug mode through a mojo parameter similar to debugForkedProcess

[ https://issues.apache.org/jira/browse/SLING-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528066#comment-14528066 ] Konrad Windszus commented on SLING-4677: It is all in

[jira] [Commented] (SLING-4677) Allow to start in debug mode through a mojo parameter similar to debugForkedProcess

[ https://issues.apache.org/jira/browse/SLING-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528065#comment-14528065 ] Konrad Windszus commented on SLING-4677: It is all in

[jira] [Commented] (SLING-4417) HC Annotation should allow to configure immediate SCR property

[ https://issues.apache.org/jira/browse/SLING-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528095#comment-14528095 ] Bertrand Delacretaz commented on SLING-4417: This is useful but I don't think

[jira] [Commented] (SLING-4677) Allow to start in debug mode through a mojo parameter similar to debugForkedProcess

[ https://issues.apache.org/jira/browse/SLING-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528104#comment-14528104 ] Carsten Ziegeler commented on SLING-4677: - But we can think about doing this - We

[jira] [Commented] (SLING-4417) HC Annotation should allow to configure immediate SCR property

[ https://issues.apache.org/jira/browse/SLING-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528107#comment-14528107 ] Konrad Windszus commented on SLING-4417: According to the OSGi spec the lifecycle

[jira] [Commented] (SLING-4417) HC Annotation should allow to configure immediate SCR property

[ https://issues.apache.org/jira/browse/SLING-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528109#comment-14528109 ] Carsten Ziegeler commented on SLING-4417: - I think immediate is more an anti

[jira] [Commented] (SLING-4416) Improve HC Message/Status if a HC implementation throws an exception

[ https://issues.apache.org/jira/browse/SLING-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528131#comment-14528131 ] Carsten Ziegeler commented on SLING-4416: - [~bdelacretaz] Is it acceptable to

[jira] [Assigned] (SLING-4627) TOPOLOGY_CHANGED in an eventually consistent repository

[ https://issues.apache.org/jira/browse/SLING-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli reassigned SLING-4627: -- Assignee: Stefan Egli TOPOLOGY_CHANGED in an eventually consistent repository

[jira] [Resolved] (SLING-4416) Improve HC Message/Status if a HC implementation throws an exception

[ https://issues.apache.org/jira/browse/SLING-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-4416. Resolution: Fixed Fix Version/s: Health Check Core 1.2.4 Assignee:

[jira] [Comment Edited] (SLING-4417) HC Annotation should allow to configure immediate SCR property

[ https://issues.apache.org/jira/browse/SLING-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528114#comment-14528114 ] Carsten Ziegeler edited comment on SLING-4417 at 5/5/15 8:26 AM:

[jira] [Commented] (SLING-4417) HC Annotation should allow to configure immediate SCR property

[ https://issues.apache.org/jira/browse/SLING-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528114#comment-14528114 ] Carsten Ziegeler commented on SLING-4417: - This would be an option - kind of an

[jira] [Comment Edited] (SLING-4627) TOPOLOGY_CHANGED in an eventually consistent repository

[ https://issues.apache.org/jira/browse/SLING-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528138#comment-14528138 ] Stefan Egli edited comment on SLING-4627 at 5/5/15 9:08 AM:

[jira] [Commented] (SLING-4677) Allow to start in debug mode through a mojo parameter similar to debugForkedProcess

[ https://issues.apache.org/jira/browse/SLING-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528098#comment-14528098 ] Konrad Windszus commented on SLING-4677: Unfortunately there is no way to do that

[jira] [Commented] (SLING-4677) Allow to start in debug mode through a mojo parameter similar to debugForkedProcess

[ https://issues.apache.org/jira/browse/SLING-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528105#comment-14528105 ] Radu Cotescu commented on SLING-4677: - Sounds cool - it would definitely ease starting

[jira] [Updated] (SLING-4627) TOPOLOGY_CHANGED in an eventually consistent repository

[ https://issues.apache.org/jira/browse/SLING-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-4627: --- Attachment: SLING-4627.patch I've added [^SLING-4627.patch] with a suggestion of a

[jira] [Comment Edited] (SLING-4627) TOPOLOGY_CHANGED in an eventually consistent repository

[ https://issues.apache.org/jira/browse/SLING-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528138#comment-14528138 ] Stefan Egli edited comment on SLING-4627 at 5/5/15 9:11 AM:

[jira] [Commented] (SLING-4416) Improve HC Message/Status if a HC implementation throws an exception

[ https://issues.apache.org/jira/browse/SLING-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528158#comment-14528158 ] Bertrand Delacretaz commented on SLING-4416: Ah sorry I missed that, I agree

Jenkins build is back to normal : sling-trunk-1.7 #1798

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

[jira] [Created] (SLING-4690) Use oak's OsgiRepository instead of JcrRepositoryHacks

Robert Munteanu created SLING-4690: -- Summary: Use oak's OsgiRepository instead of JcrRepositoryHacks Key: SLING-4690 URL: https://issues.apache.org/jira/browse/SLING-4690 Project: Sling

[jira] [Updated] (SLING-4690) Use oak's OsgiRepository instead of JcrRepositoryHacks

[ https://issues.apache.org/jira/browse/SLING-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-4690: --- Description: Oak already provides a repository wrapper for usage in OSGi environments, so we

[jira] [Commented] (SLING-4690) Use oak's OsgiRepository instead of JcrRepositoryHacks

[ https://issues.apache.org/jira/browse/SLING-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528207#comment-14528207 ] Robert Munteanu commented on SLING-4690: Fixed in https://svn.apache.org/r1677768

[jira] [Resolved] (SLING-4690) Use oak's OsgiRepository instead of JcrRepositoryHacks

[ https://issues.apache.org/jira/browse/SLING-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-4690. Resolution: Fixed Use oak's OsgiRepository instead of JcrRepositoryHacks

Jenkins build is back to stable : sling-trunk-1.7 #1792

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

[jira] [Created] (SLING-4691) throws information is missing on Resource

Carsten Ziegeler created SLING-4691: --- Summary: throws information is missing on Resource Key: SLING-4691 URL: https://issues.apache.org/jira/browse/SLING-4691 Project: Sling Issue Type:

Jenkins build is still unstable: sling-contrib-1.7 #56

See https://builds.apache.org/job/sling-contrib-1.7/56/

Jenkins build is still unstable: sling-contrib-1.7 #60

See https://builds.apache.org/job/sling-contrib-1.7/changes