Unable to find resource 'org.apache.sling:org.apache.sling.launchpad.base:jar:app:2.3.0' in repository central (http://repo1.maven.org/maven2)

Hi all, just checked out the latest sources from the trunk and tried to build Sling. Unfortunately it fails due to a missing (maven) artifact. The maven output follows: ... Downloading: http://repo1.maven.org/maven2/org/apache/sling/org.apache.sling.launchpad.base/2.3.0/org.apache.sling.launchpa

Re: Unable to find resource 'org.apache.sling:org.apache.sling.launchpad.base:jar:app:2.3.0' in repository central (http://repo1.maven.org/maven2)

Hi, On Wed, Feb 16, 2011 at 11:06 AM, Clemens Wyss wrote: > ...just checked out the latest sources from the trunk and tried to build > Sling. Unfortunately it fails due to a missing (maven) artifact. > The maven output follows: > ... > Downloading: > http://repo1.maven.org/maven2/org/apache/sli

AW: Unable to find resource 'org.apache.sling:org.apache.sling.launchpad.base:jar:app:2.3.0' in repository central (http://repo1.maven.org/maven2)

Thx! > -Ursprüngliche Nachricht- > Von: Bertrand Delacretaz [mailto:bdelacre...@apache.org] > Gesendet: Mittwoch, 16. Februar 2011 11:15 > An: dev@sling.apache.org > Betreff: Re: Unable to find resource > 'org.apache.sling:org.apache.sling.launchpad.base:jar:app:2.3.0' in repository > cent

Hudson build is back to normal : sling-trunk-1.6 #776

See

[jira] Created: (SLING-1982) Potential deadlock if job manager is restarted

Potential deadlock if job manager is restarted -- Key: SLING-1982 URL: https://issues.apache.org/jira/browse/SLING-1982 Project: Sling Issue Type: Bug Components: Extensions Affects V

[jira] Commented: (SLING-1982) Potential deadlock if job manager is restarted

[ https://issues.apache.org/jira/browse/SLING-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995252#comment-12995252 ] Carsten Ziegeler commented on SLING-1982: - I moved the queue clean up out of the s

Hudson build is back to normal : sling-trunk-1.5 #1088

See

RE: JUnit Sling patch

I'm fine with doing it for all renderers. I started with HTML because that's the type I use the most. As for the output, I think leaving it on for all sounds right. I don't even think we would need to truncate it. If a user wants to output a novel that's their prerogative. -Original

[jira] Updated: (SLING-1890) JCR Explorer - improvements

[ https://issues.apache.org/jira/browse/SLING-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Müller updated SLING-1890: --- Fix Version/s: Sling Explorer 1.0.2 > JCR Explorer - improvements > --- > >

[jira] Updated: (SLING-1723) jQuery JCR Explorer - step 2

[ https://issues.apache.org/jira/browse/SLING-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Müller updated SLING-1723: --- Fix Version/s: (was: Sling Explorer 1.0.2) Sling Explorer 1.0.4 > jQuery JCR E

Re: Integration tests failing

On 15.02.11 21:02, "Alexander Klimetschek" wrote: >the integration tests fail for me. In the trunk I do > >> cd launchpad/integration-tests >> mvn test -Dtest=PostServlet* I got it running in the meantime (thanks to Bertrand). The above is not enough, you need to do: (1) start the sling testing

Hudson build became unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #778

See

Hudson build became unstable: sling-trunk-1.6 #778

See

[jira] Commented: (SLING-1939) wrong character encoding for compiled JSP scripts

[ https://issues.apache.org/jira/browse/SLING-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995403#comment-12995403 ] Julian Sedding commented on SLING-1939: --- As a workaround you can include <%@page pag

[jira] Created: (SLING-1983) Post servlet: Patching multi-value properties

Post servlet: Patching multi-value properties - Key: SLING-1983 URL: https://issues.apache.org/jira/browse/SLING-1983 Project: Sling Issue Type: New Feature Components: Servlets

Re: Integration tests failing

On Wed, Feb 16, 2011 at 5:58 PM, Alexander Klimetschek wrote: > ...you need to do: > > (1) start the sling testing instance > > cd launchpad/testing > mvn clean > mvn launchpad:run > > (2) in a separate shell, run the integration tests > > cd launchpad/integration-tests > mvn test -Dtest=**/*Test

[jira] Updated: (SLING-1983) Post servlet: Patching multi-value properties

[ https://issues.apache.org/jira/browse/SLING-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-1983: - Attachment: SLING-1983.patch This patch will add @Patch support as described. No

Re: [POST servlet] Patching multi-value properties

On 27.01.11 15:11, "Alexander Klimetschek" wrote: >I'd like to propose an extension to the Sling POST servlet. I created http://issues.apache.org/jira/browse/SLING-1983 for this, and attached a patch, which - as a side-effect - simplifies the rather complex set property logic in the post servlet