Build failed in Hudson: sling-contrib-1.5 #443

2010-04-25 Thread Apache Hudson Server 
See 

--
[...truncated 7058 lines...]






]
org.apache.sling.commons.testing.integration.HttpStatusCodeException: Expected 
status code 302 for POST, got 404, 
URL=http://localhost:59638/org.apache.sling.launchpad.contrib-testing-4-SNAPSHOT/WaitForSlingStartup/1272252100384,
 Content=[


Error 404 

HTTP ERROR: 404NOT_FOUND
RequestURI=/org.apache.sling.launchpad.contrib-testing-4-SNAPSHOT/WaitForSlingStartup/1272252100384http://jetty.mortbay.org/";>Powered by Jetty://  
  






















]
org.apache.sling.commons.testing.integration.HttpStatusCodeException: Expected 
status code 302 for POST, got 404, 
URL=http://localhost:59638/org.apache.sling.launchpad.contrib-testing-4-SNAPSHOT/WaitForSlingStartup/1272252100902,
 Content=[


Error 404 

HTTP ERROR: 404NOT_FOUND
RequestURI=/org.apache.sling.launchpad.contrib-testing-4-SNAPSHOT/WaitForSlingStartup/1272252100902http://jetty.mortbay.org/";>Powered by Jetty://  
  






















]
org.apache.sling.commons.testing.integration.HttpStatusCodeException: Expected 
status code 302 for POST, got 404, 
URL=http://localhost:59638/org.apache.sling.launchpad.contrib-testing-4-SNAPSHOT/WaitForSlingStartup/1272252101422,
 Content=[


Error 404 

HTTP ERROR: 404NOT_FOUND
RequestURI=/org.apache.sling.launchpad.contrib-testing-4-SNAPSHOT/WaitForSlingStartup/1272252101422http://jetty.mortbay.org/";>Powered by Jetty://  
  






















]
org.apache.sling.commons.testing.integration.HttpStatusCodeException: Expected 
status code 302 for POST, got 404, 
URL=http://localhost:59638/org.apache.sling.launchpad.contrib-testing-4-SNAPSHOT/WaitForSlingStartup/1272252101942,
 Content=[


Error 404 

HTTP ERROR: 404NOT_FOUND
RequestURI=/org.apache.sling.launchpad.contrib-testing-4-SNAPSHOT/WaitForSlingStartup/1272252101942http://jetty.mortbay.org/";>Powered by Jetty://

Build failed in Hudson: sling-contrib-1.5 » Apache Sling Launchpad Contrib Testing #443

2010-04-25 Thread Apache Hudson Server 
See 


--
[...truncated 3480 lines...]












]
org.apache.sling.commons.testing.integration.HttpStatusCodeException: Expected 
status code 302 for POST, got 404, 
URL=http://localhost:59638/org.apache.sling.launchpad.contrib-testing-4-SNAPSHOT/WaitForSlingStartup/1272252100384,
 Content=[


Error 404 

HTTP ERROR: 404NOT_FOUND
RequestURI=/org.apache.sling.launchpad.contrib-testing-4-SNAPSHOT/WaitForSlingStartup/1272252100384http://jetty.mortbay.org/";>Powered by Jetty://  
  






















]
org.apache.sling.commons.testing.integration.HttpStatusCodeException: Expected 
status code 302 for POST, got 404, 
URL=http://localhost:59638/org.apache.sling.launchpad.contrib-testing-4-SNAPSHOT/WaitForSlingStartup/1272252100902,
 Content=[


Error 404 

HTTP ERROR: 404NOT_FOUND
RequestURI=/org.apache.sling.launchpad.contrib-testing-4-SNAPSHOT/WaitForSlingStartup/1272252100902http://jetty.mortbay.org/";>Powered by Jetty://  
  






















]
org.apache.sling.commons.testing.integration.HttpStatusCodeException: Expected 
status code 302 for POST, got 404, 
URL=http://localhost:59638/org.apache.sling.launchpad.contrib-testing-4-SNAPSHOT/WaitForSlingStartup/1272252101422,
 Content=[


Error 404 

HTTP ERROR: 404NOT_FOUND
RequestURI=/org.apache.sling.launchpad.contrib-testing-4-SNAPSHOT/WaitForSlingStartup/1272252101422http://jetty.mortbay.org/";>Powered by Jetty://  
  






















]
org.apache.sling.commons.testing.integration.HttpStatusCodeException: Expected 
status code 302 for POST,

Hudson build is back to stable : sling-trunk-1.6 #388

2010-04-25 Thread Apache Hudson Server 
See

Hudson build is back to stable : sling-tr unk-1.6 » Apache Sling Event Support #388

2010-04-25 Thread Apache Hudson Server 
See

Re: Build fails, wrong version for maven-launchpad-plugin?

2010-04-25 Thread Eric Norman 
Yeah, I think you are right.  I just ran into the same issue doing a clean
build.  I've updated the version number in r937907.  Try syncing to that to
see if it works better for you.

Regards,
Eric

On Sun, Apr 25, 2010 at 11:53 AM, Pontus Amberg wrote:

> Currently the trunk contains a /parent/pom.xml that specifies version
> "2.0.5-SNAPSHOT" for "maven-launchpad-plugin". The version in
> /maven/maven-launchpad-plugin/pom.xml is "2.0.7-SNAPSHOT". Is the version in
> /parent/pom.xml wrong?
>
> /Pontus
>
>
>

Build fails, wrong version for maven-launchpad-plugin?

2010-04-25 Thread Pontus Amberg 
Currently the trunk contains a /parent/pom.xml that specifies version 
"2.0.5-SNAPSHOT" for "maven-launchpad-plugin". The version in 
/maven/maven-launchpad-plugin/pom.xml is "2.0.7-SNAPSHOT". Is the 
version in /parent/pom.xml wrong?


/Pontus

[jira] Updated: (SLING-1501) JSONResponse doesn't set the status code on the response

2010-04-25 Thread Simon Gaeremynck (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Gaeremynck updated SLING-1501:


Attachment: jsonresponse.patch

Sets the status in JSONresponse
Adds in a test case to check for a proper statuscode

> JSONResponse doesn't set the status code on the response
> 
>
> Key: SLING-1501
> URL: https://issues.apache.org/jira/browse/SLING-1501
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Post 2.0.6
>Reporter: Simon Gaeremynck
> Fix For: Servlets Post 2.0.6
>
> Attachments: jsonresponse.patch
>
>
> When  we are doing POST operations we use the Accept header set to 
> application/json so we get a json response back.
> However, when an operation fails for some reason, there is no status code set 
> on the response. (It is defined in the json response itself though).
> This patch should set a status code.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (SLING-1501) JSONResponse doesn't set the status code on the response

2010-04-25 Thread Simon Gaeremynck (JIRA) 
JSONResponse doesn't set the status code on the response


 Key: SLING-1501
 URL: https://issues.apache.org/jira/browse/SLING-1501
 Project: Sling
  Issue Type: Bug
  Components: Servlets
Affects Versions: Servlets Post 2.0.6
Reporter: Simon Gaeremynck
 Fix For: Servlets Post 2.0.6
 Attachments: jsonresponse.patch

When  we are doing POST operations we use the Accept header set to 
application/json so we get a json response back.
However, when an operation fails for some reason, there is no status code set 
on the response. (It is defined in the json response itself though).
This patch should set a status code.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (SLING-1500) Patch Submission: Expression Language (EL) Functions for JSP Taglib

2010-04-25 Thread Mark Adamcin (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Adamcin updated SLING-1500:


Priority: Minor  (was: Major)

Probably not worthy of 'major' priority.

> Patch Submission: Expression Language (EL) Functions for JSP Taglib
> ---
>
> Key: SLING-1500
> URL: https://issues.apache.org/jira/browse/SLING-1500
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Affects Versions: Scripting JSP-Taglib 2.0.6
>Reporter: Mark Adamcin
>Priority: Minor
> Attachments: add-files.zip, taglib11.tld.patch
>
>
> I've noticed that the Sling Resource API is not very accessible for tag- and 
> EL-focused JSP development. In order to promote readable JSP code, I created 
> a set of static methods to implement commonly-used ResourceResolver methods 
> as well as to expose the rather useful ResourceUtil methods as EL functions. 
> The functions use ResourceWrappers to work around the isse 
> https://issues.apache.org/jira/browse/SLING-1414 where the Resource.getPath() 
> method is inaccessible in EL for JcrNodeResource objects.
> I've found these taglib functions to be very useful for Day CQ5 development, 
> so I thought I'd offer to contribute them to the project.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.