DropQueueTest failure
-
Key: SLING-1849
URL: https://issues.apache.org/jira/browse/SLING-1849
Project: Sling
Issue Type: Bug
Components: Extensions
Environment: $ mvn -v
Apache Maven 2.2.1 (r801777;
Hi Felix,
event is not triggered. Do you have an idea what might be different in
your environment?
right now I'm on a good way to find out why the compilationDone event is
not triggered so there is no need for you to invest time in that right now.
Best,
Sandro
Hi Sandro,
On 22.10.2010 16:15, Sandro Boehme wrote:
Hi Felix,
event is not triggered. Do you have an idea what might be different in
your environment?
right now I'm on a good way to find out why the compilationDone event is
not triggered so there is no need for you to invest time in that
Make sure error response is sent back even if the response cannot be reset
--
Key: SLING-1850
URL: https://issues.apache.org/jira/browse/SLING-1850
Project: Sling
Issue
[
https://issues.apache.org/jira/browse/SLING-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-1850.
--
Resolution: Fixed
Reverted the early-error-handling-abort change introduce in
See
https://hudson.apache.org/hudson/job/sling-trunk-1.5/org.apache.sling$org.apache.sling.launchpad.testing/935/
See https://hudson.apache.org/hudson/job/sling-trunk-1.5/935/changes
Hi Felix,
compilationDone is now triggered in my environment.
At some point I saw that the compilationDone event is triggered for Dim.
This gave me a chance to find out how this is all suppose to work.
o Problem one:
I added the new JSDT-based debugger to the listener of the global
See
https://hudson.apache.org/hudson/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/622/
See https://hudson.apache.org/hudson/job/sling-trunk-1.6/622/changes
10 matches
Mail list logo