Build failed in Jenkins: sling-samples-1.5 #235

2011-07-26 Thread Apache Jenkins Server 
See 

Changes:

[enorman] SLING-2159 fix custom-login-form sample

[enorman] SLING-2159 fix custom-login-form sample

--
Started by an SCM change
Building remotely on ubuntu1
Updating http://svn.apache.org/repos/asf/sling/trunk/samples
D custom-login-form/src/main/resources/org/apache/sling/formauth
A custom-login-form/src/main/resources/org/apache/sling/auth
A custom-login-form/src/main/resources/org/apache/sling/auth/form
A custom-login-form/src/main/resources/org/apache/sling/auth/form/impl
AU
custom-login-form/src/main/resources/org/apache/sling/auth/form/impl/custom_login.html
U custom-login-form/pom.xml
At revision 1151345
ERROR: Ignore Problem expanding maven opts macros 
org.jenkinsci.plugins.tokenmacro.TokenMacro
Found mavenVersion 2.2.1 from file 
jar:file:/home/hudson/tools/maven/apache-maven-2.2.1/lib/maven-2.2.1-uber.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties
[locks-and-latches] Checking to see if we really have the locks
[locks-and-latches] Have all the locks, build can start
Parsing POMs
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
ERROR: Failed to parse POMs
hudson.util.IOException2: remote file operation failed: 
 at 
hudson.remoting.Channel@d02420d:ubuntu1
at hudson.FilePath.act(FilePath.java:754)
at hudson.FilePath.act(FilePath.java:740)
at 
hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:817)
at 
hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:617)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:429)
at hudson.model.Run.run(Run.java:1374)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:467)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:145)
Caused by: hudson.remoting.ProxyException: 
hudson.maven.MavenModuleSetBuild$MavenExecutionException: 
org.apache.maven.project.ProjectBuildingException: Some problems were 
encountered while processing the POMs:
[FATAL] Non-resolvable parent POM: Could not find artifact 
org.apache.sling:sling:pom:11-SNAPSHOT and 'parent.relativePath' points at 
wrong local POM @ line 12, column 11

at 
hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1327)
at 
hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1110)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:1979)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:270)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: hudson.remoting.ProxyException: 
org.apache.maven.project.ProjectBuildingException: Some problems were 
encountered while processing the POMs:
[FATAL] Non-resolvable parent POM: Could not find artifact 
org.apache.sling:sling:pom:11-SNAPSHOT and 'parent.relativePath' points at 
wrong local POM @ line 12, column 11

at 
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:339)
at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:360)
at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:330)
at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:321)
at 
hudson.maven.MavenModuleSetBuild$PomParser.readChilds(MavenModuleSetBuild.java:1381)
at 
hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1288)
... 11 more

[jira] [Resolved] (SLING-2143) SlingPostServlet ImportOperation :content parameter overrides _charset_ parameter with system default encoding

2011-07-26 Thread Eric Norman (JIRA) 

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

Eric Norman resolved SLING-2143.


   Resolution: Fixed
Fix Version/s: Servlets Post 2.1.2

fixed in r1150269.  Please verify when you have some free time.

> SlingPostServlet ImportOperation :content parameter overrides _charset_ 
> parameter with system default encoding
> --
>
> Key: SLING-2143
> URL: https://issues.apache.org/jira/browse/SLING-2143
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Post 2.1.0
> Environment: OS: Windows 2k8, Windows 7
> Web Servers: Tomcat 6
> Sling 6
>Reporter: Stephen Sanchez
>Assignee: Eric Norman
> Fix For: Servlets Post 2.1.2
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> The ImportOperation on the SlingPostServlet (2.1.0 to Trunk) does not support 
> encoding specified in the form _charset_ parameter on a POST request. 
> REPRODUCTION STEPS:
> Create a POST request using the SlingPostServlet and ImportOperation:
> curl -F":operation=import" -F"_charset_=UTF-8" -F":contentType=json" 
> -F":replace=true" -F":replaceProperties=true" -F":content={'latin':'øµå', 
> 'chinese':'玄牛'}" http://admin:admin@localhost:8080
> PROPOSED SOLUTION:
> In ImportOperation.java, line 137 (as of 2.1.0 tag):
> contentStream = new ByteArrayInputStream(content.getBytes());
> This line will take the :content parameter on a request, properly encoded 
> (ex. UTF-8) and get the bytes using system-level encoding. This causes all 
> unicode characters in the content to be encoded, on windows, with the wrong 
> encoding. 
> The simple fix, which resolves the issue and allows UTF-8 encoding across all 
> operating systems:
> contentStream = new ByteArrayInputStream(content.getBytes("UTF-8"));
> My proposed fix, is to support the form parameter _charset_, since :content 
> is a parameter on the form in the post request:
> RequestParameter encodingParam = request.getRequestParameter("_charset_");
> byte[] contentBytes;
> if (encodingParam != null && encodingParam.getString() != null) {
>   contentBytes = content.getBytes(encodingParam.getString());
> } else {
>   contentBytes = content.getBytes();
> }
> contentStream = new ByteArrayInputStream(contentBytes);

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (SLING-2159) The custom-login-form sample doesn't work anymore

2011-07-26 Thread Eric Norman (JIRA) 

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

Eric Norman resolved SLING-2159.


Resolution: Fixed

fixed in r1151337

> The custom-login-form sample doesn't work anymore
> -
>
> Key: SLING-2159
> URL: https://issues.apache.org/jira/browse/SLING-2159
> Project: Sling
>  Issue Type: Bug
>  Components: Samples
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Minor
>
> 1. Move the custom_login.html resource to the org/apache/sling/auth/form/impl 
> folder
> 2. Change the fragment-host to: org.apache.sling.auth.form

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (SLING-2159) The custom-login-form sample doesn't work anymore

2011-07-26 Thread Eric Norman (JIRA) 

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

Eric Norman reassigned SLING-2159:
--

Assignee: Eric Norman

> The custom-login-form sample doesn't work anymore
> -
>
> Key: SLING-2159
> URL: https://issues.apache.org/jira/browse/SLING-2159
> Project: Sling
>  Issue Type: Bug
>  Components: Samples
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Minor
>
> 1. Move the custom_login.html resource to the org/apache/sling/auth/form/impl 
> folder
> 2. Change the fragment-host to: org.apache.sling.auth.form

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (SLING-2159) The custom-login-form sample doesn't work anymore

2011-07-26 Thread Eric Norman (JIRA) 
The custom-login-form sample doesn't work anymore
-

 Key: SLING-2159
 URL: https://issues.apache.org/jira/browse/SLING-2159
 Project: Sling
  Issue Type: Bug
  Components: Samples
Reporter: Eric Norman
Priority: Minor


1. Move the custom_login.html resource to the org/apache/sling/auth/form/impl 
folder
2. Change the fragment-host to: org.apache.sling.auth.form


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SLING-2158) JsonSerialization: Add new ":order" JSON array to transport child node ordering when needed

2011-07-26 Thread Tobias Bocanegra (JIRA) 

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

Tobias Bocanegra updated SLING-2158:


Summary: JsonSerialization: Add new ":order" JSON array to transport child 
node ordering when needed  (was: JsonSerialization: Add new ":oder" JSON array 
to transport child node ordering when needed)

> JsonSerialization: Add new ":order" JSON array to transport child node 
> ordering when needed
> ---
>
> Key: SLING-2158
> URL: https://issues.apache.org/jira/browse/SLING-2158
> Project: Sling
>  Issue Type: New Feature
>  Components: Servlets
>Reporter: Tobias Bocanegra
>Priority: Minor
>
> as discussed in:
> http://mail-archives.apache.org/mod_mbox/sling-dev/201104.mbox/%3cbanlktimau-cv5fhyyrx-z5ktn4afmfq...@mail.gmail.com%3E
> i suggest to add a new array property containing the child node names to the 
> default JSON renderer if 'requested' with an 'order' selector.
> i would include the child node names also on the end of the depth limit. this 
> allows to get the child node names without the need to load them with a 
> deeper request:
> eg:
> GET /content/en.0.order.json would return:
> {
> "title": "Hello, world",
> ":oder": ["sub1", "sub2"]
> }

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (SLING-2158) JsonSerialization: Add new ":oder" JSON array to transport child node ordering when needed

2011-07-26 Thread Tobias Bocanegra (JIRA) 
JsonSerialization: Add new ":oder" JSON array to transport child node ordering 
when needed
--

 Key: SLING-2158
 URL: https://issues.apache.org/jira/browse/SLING-2158
 Project: Sling
  Issue Type: New Feature
  Components: Servlets
Reporter: Tobias Bocanegra
Priority: Minor


as discussed in:

http://mail-archives.apache.org/mod_mbox/sling-dev/201104.mbox/%3cbanlktimau-cv5fhyyrx-z5ktn4afmfq...@mail.gmail.com%3E

i suggest to add a new array property containing the child node names to the 
default JSON renderer if 'requested' with an 'order' selector.
i would include the child node names also on the end of the depth limit. this 
allows to get the child node names without the need to load them with a deeper 
request:

eg:

GET /content/en.0.order.json would return:

{
"title": "Hello, world",
":oder": ["sub1", "sub2"]
}





--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-1137) Support hierarchical child node creation from SlingPostServlet

2011-07-26 Thread Justin Edelson (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071160#comment-13071160
 ] 

Justin Edelson commented on SLING-1137:
---

duplicate of SLING-1504

> Support hierarchical child node creation from SlingPostServlet
> --
>
> Key: SLING-1137
> URL: https://issues.apache.org/jira/browse/SLING-1137
> Project: Sling
>  Issue Type: Improvement
>  Components: Servlets
>Reporter: Mark Baker
>Priority: Minor
>
> The default node creation functionality on "/" terminated paths via the 
> SlingPostServlet doesn't scale very well as it only supports creation of 
> nodes immediately under the targeted path.  So, for example, when using this 
> via a CQ form to capture form responses in the repository, a site can 
> potentially have thousands of child nodes, leading to well known performance 
> problems.
> I think it would be useful to offer an option for the servlet to save a 
> hierarchy of nodes, perhaps via the common convention of using the first 4 
> characters of the would-be node id to create a 2 level hierarchy.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (SLING-1137) Support hierarchical child node creation from SlingPostServlet

2011-07-26 Thread Justin Edelson (JIRA) 

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

Justin Edelson resolved SLING-1137.
---

Resolution: Duplicate

> Support hierarchical child node creation from SlingPostServlet
> --
>
> Key: SLING-1137
> URL: https://issues.apache.org/jira/browse/SLING-1137
> Project: Sling
>  Issue Type: Improvement
>  Components: Servlets
>Reporter: Mark Baker
>Priority: Minor
>
> The default node creation functionality on "/" terminated paths via the 
> SlingPostServlet doesn't scale very well as it only supports creation of 
> nodes immediately under the targeted path.  So, for example, when using this 
> via a CQ form to capture form responses in the repository, a site can 
> potentially have thousands of child nodes, leading to well known performance 
> problems.
> I think it would be useful to offer an option for the servlet to save a 
> hierarchy of nodes, perhaps via the common convention of using the first 4 
> characters of the would-be node id to create a 2 level hierarchy.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (SLING-2157) Make the framework logger level configurable

2011-07-26 Thread Carsten Ziegeler (JIRA) 
Make the framework logger level configurable


 Key: SLING-2157
 URL: https://issues.apache.org/jira/browse/SLING-2157
 Project: Sling
  Issue Type: Improvement
  Components: Launchpad
Affects Versions: Launchpad Base 2.3.0
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
 Fix For: Launchpad Base 2.3.2


Currently the framework and launchpad app logger always log with log level 
ERROR which makes it impossible to see INFO or DEBUG messages for troubleshoting

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira