date:20131016

[jira] [Created] (SLING-3184) Create a job consumer to clean up the history

2013-10-16 Thread Carsten Ziegeler (JIRA)

Carsten Ziegeler created SLING-3184:
---

 Summary: Create a job consumer to clean up the history
 Key: SLING-3184
 URL: https://issues.apache.org/jira/browse/SLING-3184
 Project: Sling
  Issue Type: Improvement
  Components: Extensions
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
 Fix For: Extensions Event 3.3.0


As failed jobs are now put into the history, they are never removed from the 
resource tree. We should at least add a clean up consumer which could be 
configured to run periodically to clean up the history



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Re: failure running sling.extensions.event unit/integraiton tests on windows?

2013-10-16 Thread Carsten Ziegeler

I fixed one thing in the Classloading test which removes the started job
from the history...this shouldn't have an impact though

Could you please comment out line 222 in the Classloading test and retun
the tests, so hopefully this gives us a clue about what is going on.

Carsten


2013/10/17 Stefan Seifert 

> please note: i was not able to reproduce the problem after your last
> commits. perhaps the problem was fixed by accident.
> i tried it several times on two different machines.
> although we do not know why it seems to be solved now.
>
> stefan
>
> >-Original Message-
> >From: Carsten Ziegeler [mailto:cziege...@apache.org]
> >Sent: Wednesday, October 16, 2013 4:50 PM
> >To: dev@sling.apache.org
> >Subject: Re: failure running sling.extensions.event unit/integraiton
> tests on
> >windows?
> >
> >Yes, it seems to hang at that point as it doesn't get any jobs - I guess
> >the difference between windows and other machines is the order in which
> >test cases are executed. So it must be some previous test which does not
> >clean up correctly. Can you please find out from the logs which tests are
> >run before the HistoryTest?
> >
> >Carsten
>



-- 
Carsten Ziegeler
cziege...@apache.org

RE: failure running sling.extensions.event unit/integraiton tests on windows?

2013-10-16 Thread Stefan Seifert

please note: i was not able to reproduce the problem after your last commits. 
perhaps the problem was fixed by accident.
i tried it several times on two different machines.
although we do not know why it seems to be solved now.

stefan

>-Original Message-
>From: Carsten Ziegeler [mailto:cziege...@apache.org]
>Sent: Wednesday, October 16, 2013 4:50 PM
>To: dev@sling.apache.org
>Subject: Re: failure running sling.extensions.event unit/integraiton tests on
>windows?
>
>Yes, it seems to hang at that point as it doesn't get any jobs - I guess
>the difference between windows and other machines is the order in which
>test cases are executed. So it must be some previous test which does not
>clean up correctly. Can you please find out from the logs which tests are
>run before the HistoryTest?
>
>Carsten

[jira] [Commented] (SLING-3169) Job state and related enumerations

2013-10-16 Thread Stefan Seifert (JIRA)


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

Stefan Seifert commented on SLING-3169:
---

thanks!

> Job state and related enumerations
> --
>
> Key: SLING-3169
> URL: https://issues.apache.org/jira/browse/SLING-3169
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Extensions Event 3.3.0
>
>
> This is a follow up from SLING-3028 based on comments by Stefan Seifert:
> I find the enum name Job.JobType not ideal, because it does not stand of 
> a type but for a state of the job. But there is a JobState enum in the 
> consumer API package already.
> I find the enum and class names JobState and JobStatus in the consumer 
> package not ideal, because they do not stand for a state, but for a job 
> result.
>   



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Launchpad Testing #1983

2013-10-16 Thread Apache Jenkins Server

See

Jenkins build is back to stable : sling-trunk-1.6 #1983

2013-10-16 Thread Apache Jenkins Server

See

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

2013-10-16 Thread Apache Jenkins Server

See

[jira] [Commented] (SLING-3182) Filter out invalid alias values

2013-10-16 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler commented on SLING-3182:
-

Invalid aliases are ignored. An alias is considered invalid if it equals "..", 
"." or contains a /, # or ?
This is logged with log level warn

> Filter out invalid alias values
> ---
>
> Key: SLING-3182
> URL: https://issues.apache.org/jira/browse/SLING-3182
> Project: Sling
>  Issue Type: Improvement
>  Components: ResourceResolver
>Affects Versions: Resource Resolver 1.0.6
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.1.0
>
>
> Right now, the sling:alias property is used as is for reverse mapping and 
> isn't checked for invalid characters which will result in invalid links.
> We should filter those out and ignore the values



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Resolved] (SLING-3182) Filter out invalid alias values

2013-10-16 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler resolved SLING-3182.
-

Resolution: Fixed

> Filter out invalid alias values
> ---
>
> Key: SLING-3182
> URL: https://issues.apache.org/jira/browse/SLING-3182
> Project: Sling
>  Issue Type: Improvement
>  Components: ResourceResolver
>Affects Versions: Resource Resolver 1.0.6
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.1.0
>
>
> Right now, the sling:alias property is used as is for reverse mapping and 
> isn't checked for invalid characters which will result in invalid links.
> We should filter those out and ignore the values



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Jenkins build is unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #1982

2013-10-16 Thread Apache Jenkins Server

See

Jenkins build is unstable: sling-trunk-1.6 #1982

2013-10-16 Thread Apache Jenkins Server

See

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Sample Integration Tests #1982

2013-10-16 Thread Apache Jenkins Server

See

[jira] [Resolved] (SLING-3183) Add a configuration flag to disable sling vanity path handling

2013-10-16 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler resolved SLING-3183.
-

Resolution: Fixed

Added the flag in rev 1532814
(And also moved metatype information into the class file)

> Add a configuration flag to disable sling vanity path handling
> --
>
> Key: SLING-3183
> URL: https://issues.apache.org/jira/browse/SLING-3183
> Project: Sling
>  Issue Type: Improvement
>  Components: ResourceResolver
>Affects Versions: Resource Resolver 1.0.6
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.1.0
>
>
> If the sling vanity path feature is not used, it still adds some processing 
> overhead (search executed, observation listener etc.).
> We should add a global flag to disable it if it's not used



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Created] (SLING-3183) Add a configuration flag to disable sling vanity path handling

2013-10-16 Thread Carsten Ziegeler (JIRA)

Carsten Ziegeler created SLING-3183:
---

 Summary: Add a configuration flag to disable sling vanity path 
handling
 Key: SLING-3183
 URL: https://issues.apache.org/jira/browse/SLING-3183
 Project: Sling
  Issue Type: Improvement
  Components: ResourceResolver
Affects Versions: Resource Resolver 1.0.6
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
 Fix For: Resource Resolver 1.1.0


If the sling vanity path feature is not used, it still adds some processing 
overhead (search executed, observation listener etc.).
We should add a global flag to disable it if it's not used



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Created] (SLING-3182) Filter out invalid alias values

2013-10-16 Thread Carsten Ziegeler (JIRA)

Carsten Ziegeler created SLING-3182:
---

 Summary: Filter out invalid alias values
 Key: SLING-3182
 URL: https://issues.apache.org/jira/browse/SLING-3182
 Project: Sling
  Issue Type: Improvement
  Components: ResourceResolver
Affects Versions: Resource Resolver 1.0.6
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
 Fix For: Resource Resolver 1.1.0


Right now, the sling:alias property is used as is for reverse mapping and isn't 
checked for invalid characters which will result in invalid links.
We should filter those out and ignore the values



--
This message was sent by Atlassian JIRA
(v6.1#6144)

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

2013-10-16 Thread Apache Jenkins Server

See 

--
[...truncated 286 lines...]
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
Caused by: hudson.scm.subversion.UpdaterException: failed to perform svn update
... 15 more
Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT 
/repos/asf/!svn/vcc/default failed
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:379)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:364)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:708)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:335)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1289)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:837)
at 
org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:507)
at 
org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:364)
at 
org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:274)
at 
org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:27)
at 
org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:11)
at 
org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)
at 
org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:291)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:311)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387)
at 
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:157)
... 14 more
Caused by: svn: E175002: REPORT /repos/asf/!svn/vcc/default failed
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97)
... 33 more
Caused by: org.tmatesoft.svn.core.SVNException: svn: E204899: REPORT request 
failed on '/repos/asf/!svn/vcc/default'
svn: E204899: Cannot create new file 
'/home/hudson/jenkins-slave/workspace/sling-trunk-1.7/trunk/samples/espblog/src/main/java/org/apache/sling/samples/espblog/.svn/lock'
at 
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at 
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:748)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373)
... 32 more
Caused by: svn: E204899: REPORT request failed on '/repos/asf/!svn/vcc/default'
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97)
at org.tmatesoft.svn.core.SVNErrorMessage.wrap(SVNErrorMessage.java:407)
... 34 more
Caused by: svn: E204899: Cannot create new file 
'/home/hudson/jenkins-slave/workspace/sling-trunk-1.7/trunk/samples/espblog/src/main/java/org/apache/sling/samples/espblog/.svn/lock'
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:171)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:126)
at 
org.tmatesoft.svn.core.internal.wc.SVNFileUtil.createEmptyFile(SVNFileUtil.java:346)
at 
org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea14.createVersionedDirectory(SVNAdminArea14.java:1553)
at 
org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea16Factory.doCreateVersionedDirectory(SVNAdminArea16Factory.java:30)
at 
org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.createVersionedDirectory(SVNAdminAreaFactory.java:241)
at 
org.tmatesoft.svn.core.internal.wc.SVNWCManager.ensureAdminAreaExists(SVNWCManager.java:428)
at 
org.tmatesoft.svn.core.internal.wc.SVNUpdateEditor.addDir(SVNUpdateEditor.java:762)

Re: failure running sling.extensions.event unit/integraiton tests on windows?

2013-10-16 Thread Carsten Ziegeler

I just added an additional ine to the Classloading test removing stale
jobs, but I don't think that's the problem :( Apart from that I can't see
anything spurious in the test

Carsten


2013/10/16 Robert Munteanu 

> On Wed, Oct 16, 2013 at 5:55 PM, Stefan Seifert 
> wrote:
> > i was able to reproduce it in 2 of 3 tries with only two integration
> tests activated:
> > - ClassloadingTest
> > - HistoryTest
> >
> > running historytest or ClassloadingTest standalone worked.
> > running both (i assume ClassloadingTest did run first) did not work in 2
> of 3 tries.
>
> Seems to be related to
>
> SLING-2969: IT failure: ClassloadingTest.testSimpleClassloading fails
> intermitently
> https://issues.apache.org/jira/browse/SLING-2969
>
> Robert
>
> >
> > stefan
> >
> >>-Original Message-
> >>From: Carsten Ziegeler [mailto:cziege...@apache.org]
> >>Sent: Wednesday, October 16, 2013 4:50 PM
> >>To: dev@sling.apache.org
> >>Subject: Re: failure running sling.extensions.event unit/integraiton
> >>tests on windows?
> >>
> >>Yes, it seems to hang at that point as it doesn't get any jobs - I
> >>guess
> >>the difference between windows and other machines is the order in
> >>which
> >>test cases are executed. So it must be some previous test which does
> >>not
> >>clean up correctly. Can you please find out from the logs which tests
> >>are
> >>run before the HistoryTest?
> >>
> >>Carsten
>
>
>
> --
> Sent from my (old) computer
>



-- 
Carsten Ziegeler
cziege...@apache.org

[jira] [Resolved] (SLING-3169) Job state and related enumerations

2013-10-16 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler resolved SLING-3169.
-

Resolution: Fixed

I've added the above mentioned enum and implemented it

> Job state and related enumerations
> --
>
> Key: SLING-3169
> URL: https://issues.apache.org/jira/browse/SLING-3169
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Extensions Event 3.3.0
>
>
> This is a follow up from SLING-3028 based on comments by Stefan Seifert:
> I find the enum name Job.JobType not ideal, because it does not stand of 
> a type but for a state of the job. But there is a JobState enum in the 
> consumer API package already.
> I find the enum and class names JobState and JobStatus in the consumer 
> package not ideal, because they do not stand for a state, but for a job 
> result.
>   



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (SLING-3175) Make MediaRange parser linient to accept invalid Accept header generated by Oracle JDK HttpUrlConnection

2013-10-16 Thread Julian Reschke (JIRA)


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

Julian Reschke commented on SLING-3175:
---

Here's a test that demonstrates the Java problem:

{code}
package com.greenbytes.httptests;

import java.io.BufferedReader;
import java.io.IOException;
import java.io.InputStreamReader;
import java.net.InetSocketAddress;
import java.net.URL;
import java.net.URLConnection;

import sun.net.www.protocol.http.HttpURLConnection;

import com.sun.net.httpserver.HttpExchange;
import com.sun.net.httpserver.HttpHandler;
import com.sun.net.httpserver.HttpServer;

public class JavaAcceptHeader {

public static void main(String[] args) throws IOException {
InetSocketAddress address = new InetSocketAddress(8000);
HttpServer httpServer = HttpServer.create(address, 0);

HttpHandler echoAccept = new HttpHandler() {

public void handle(HttpExchange exchange) throws IOException {
byte[] response = 
exchange.getRequestHeaders().get("Accept").toString().getBytes();
exchange.sendResponseHeaders(HttpURLConnection.HTTP_OK, 
response.length);
exchange.getResponseBody().write(response);
exchange.close();
}
};
httpServer.createContext("/", echoAccept);
httpServer.start();

URL url = new URL("http://localhost:8000/";);
URLConnection conn = url.openConnection();
BufferedReader in = new BufferedReader(new 
InputStreamReader(conn.getInputStream()));
System.out.println(in.readLine());
httpServer.stop(0);
}
}
{code}

I have submitted a bug report to Oracle, let's see what happens.

> Make MediaRange parser linient to accept invalid Accept header generated by 
> Oracle JDK HttpUrlConnection
> 
>
> Key: SLING-3175
> URL: https://issues.apache.org/jira/browse/SLING-3175
> Project: Sling
>  Issue Type: Improvement
>  Components: Servlets
>Affects Versions: Servlets Post 2.3.2
>Reporter: Chetan Mehrotra
>Priority: Minor
> Attachments: SLING-3175.patch
>
>
> While making a call to Sling using Java URLConnection we get following 
> exception [1]. The root cause is due to parsing of invalid {{Accept}} header 
> being sent as part of request
> {noformat}
> Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
> {noformat}
> The problem here is that this header is added by JDK itself [0] and at times 
> its not possible to change the request property of URLConnection created by 
> third party library. Would be helpful to make Sling MediaRange parser more 
> linient
> [0] 
> http://hg.openjdk.java.net/jdk6/jdk6-gate/jdk/file/tip/src/share/classes/sun/net/www/protocol/http/HttpURLConnection.java
> [1] 15.10.2013 16:51:01.646 *WARN* [10.40.247.115 [1381836061645] POST 
> /rpc/protocol/model/rf HTTP/1.1] 
> org.apache.sling.servlets.post.impl.helper.MediaRangeList Error registering 
> media type  *; q=.2 java.lang.ArrayIndexOutOfBoundsException: 1
>   at 
> org.apache.sling.servlets.post.impl.helper.MediaRangeList$MediaRange.setType(MediaRangeList.java:237)
>   at 
> org.apache.sling.servlets.post.impl.helper.MediaRangeList$MediaRange.(MediaRangeList.java:191)
>   at 
> org.apache.sling.servlets.post.impl.helper.MediaRangeList.init(MediaRangeList.java:90)
>   at 
> org.apache.sling.servlets.post.impl.helper.MediaRangeList.(MediaRangeList.java:56)
>   at 
> org.apache.sling.servlets.post.impl.SlingPostServlet.createPostResponse(SlingPostServlet.java:279)
>   at 
> org.apache.sling.servlets.post.impl.SlingPostServlet.doPost(SlingPostServlet.java:185)



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Re: failure running sling.extensions.event unit/integraiton tests on windows?

2013-10-16 Thread Robert Munteanu

On Wed, Oct 16, 2013 at 5:55 PM, Stefan Seifert  wrote:
> i was able to reproduce it in 2 of 3 tries with only two integration tests 
> activated:
> - ClassloadingTest
> - HistoryTest
>
> running historytest or ClassloadingTest standalone worked.
> running both (i assume ClassloadingTest did run first) did not work in 2 of 3 
> tries.

Seems to be related to

SLING-2969: IT failure: ClassloadingTest.testSimpleClassloading fails
intermitently
https://issues.apache.org/jira/browse/SLING-2969

Robert

>
> stefan
>
>>-Original Message-
>>From: Carsten Ziegeler [mailto:cziege...@apache.org]
>>Sent: Wednesday, October 16, 2013 4:50 PM
>>To: dev@sling.apache.org
>>Subject: Re: failure running sling.extensions.event unit/integraiton
>>tests on windows?
>>
>>Yes, it seems to hang at that point as it doesn't get any jobs - I
>>guess
>>the difference between windows and other machines is the order in
>>which
>>test cases are executed. So it must be some previous test which does
>>not
>>clean up correctly. Can you please find out from the logs which tests
>>are
>>run before the HistoryTest?
>>
>>Carsten



-- 
Sent from my (old) computer

RE: failure running sling.extensions.event unit/integraiton tests on windows?

2013-10-16 Thread Stefan Seifert

i was able to reproduce it in 2 of 3 tries with only two integration tests 
activated:
- ClassloadingTest
- HistoryTest

running historytest or ClassloadingTest standalone worked.
running both (i assume ClassloadingTest did run first) did not work in 2 of 3 
tries.

stefan

>-Original Message-
>From: Carsten Ziegeler [mailto:cziege...@apache.org]
>Sent: Wednesday, October 16, 2013 4:50 PM
>To: dev@sling.apache.org
>Subject: Re: failure running sling.extensions.event unit/integraiton
>tests on windows?
>
>Yes, it seems to hang at that point as it doesn't get any jobs - I
>guess
>the difference between windows and other machines is the order in
>which
>test cases are executed. So it must be some previous test which does
>not
>clean up correctly. Can you please find out from the logs which tests
>are
>run before the HistoryTest?
>
>Carsten

Re: failure running sling.extensions.event unit/integraiton tests on windows?

2013-10-16 Thread Carsten Ziegeler

Yes, it seems to hang at that point as it doesn't get any jobs - I guess
the difference between windows and other machines is the order in which
test cases are executed. So it must be some previous test which does not
clean up correctly. Can you please find out from the logs which tests are
run before the HistoryTest?

Carsten


2013/10/16 Stefan Seifert 

> strange. i tried to isolate the problem by disabling all integration tests
> by added junit @Ignore annotation to them.
> the HistoryTest IT runs then fine.
> i startet adding/removing more integration tests and sometims it succeeds,
> sometimes not. perhaps a racing condition, or a cleanup issue of the
> integration tests.
>
> if it fails it takes a long time executing this step "Starting job queue
> test":
>
> ...
> 16.10.2013 13:23:27.352 *INFO* [Thread-102]
> org.apache.sling.event.impl.jobs.TopologyCapabilities Detected capabilities
> of 86db438e-86fa-43b2-85c2-62d22a12db6b :
> /,sling/test/history,sling/webconsole/test
> 16.10.2013 13:23:27.352 *INFO* [Thread-102]
> PAXEXAM-PROBE-914abd18-50d6-448f-82ca-29f27441a4cc Service [99]
> ServiceEvent REGISTERED
> 16.10.2013 13:23:29.342 *INFO* [Apache Sling Job Background Loader]
> org.apache.sling.event Service [QueueMBean for queue test,100] ServiceEvent
> REGISTERED
> 16.10.2013 13:23:29.342 *INFO* [Apache Sling Job Queue test]
> org.apache.sling.event.impl.jobs.queues.OrderedJobQueue.test Starting job
> queue test
>
> >> it hangs here for several minutes <<
>
> 16.10.2013 13:28:27.364 *INFO* [CM Event Dispatcher (Fire
> ConfigurationEvent:
> pid=org.apache.sling.event.jobs.QueueConfiguration.2be31a75-f846-4e17-a1b9-8482c5fcaed2)]
> org.apache.sling.event Service
> [org.apache.sling.event.jobs.QueueConfiguration.2be31a75-f846-4e17-a1b9-8482c5fcaed2,98]
> ServiceEvent UNREGISTERING
> 16.10.2013 13:28:27.364 *INFO* [main]
> PAXEXAM-PROBE-914abd18-50d6-448f-82ca-29f27441a4cc BundleEvent STOPPING
> 16.10.2013 13:28:27.364 *INFO* [main]
> PAXEXAM-PROBE-914abd18-50d6-448f-82ca-29f27441a4cc Service [73]
> ServiceEvent UNREGISTERING
> ...
>
> the failsafe report contains only this:
>
>
> ---
> Test set: org.apache.sling.event.it.HistoryTest
>
> ---
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 305.173
> sec <<< FAILURE!
> testHistory(org.apache.sling.event.it.HistoryTest)  Time elapsed: 305.163
> sec  <<< ERROR!
> java.lang.Exception: test timed out after 30 milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.sling.event.it.AbstractJobHandlingTest.sleep(AbstractJobHandlingTest.java:160)
> at
> org.apache.sling.event.it.HistoryTest.testHistory(HistoryTest.java:118)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
>
>
> stefan
>
> >-Original Message-
> >From: Carsten Ziegeler [mailto:cziege...@apache.org]
> >Sent: Wednesday, October 16, 2013 12:08 PM
> >To: dev@sling.apache.org
> >Subject: Re: failure running sling.extensions.event unit/integraiton
> >tests on windows?
> >
> >Hi,
> >
> >the tests run fine on my machine - it seems that in your case the loop
> >waits forever to get 10 finished jobs in the history.
> >Do you see any exception in the log output?
> >
> >Carsten
>



-- 
Carsten Ziegeler
cziege...@apache.org

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

2013-10-16 Thread Apache Jenkins Server

See

[jira] [Commented] (SLING-2769) Broken sample: post-servlet-extensions

2013-10-16 Thread Bertrand Delacretaz (JIRA)


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

Bertrand Delacretaz commented on SLING-2769:


The org.apache.sling.samples.simple-demo bundle, built from trunk, works for me 
when installed in a Sling instance built from the launchpad/builder trunk. 
Let's discuss on the Sling users list if you're still seeing this issue.

> Broken sample: post-servlet-extensions
> --
>
> Key: SLING-2769
> URL: https://issues.apache.org/jira/browse/SLING-2769
> Project: Sling
>  Issue Type: Bug
>  Components: Launchpad, Samples
>Affects Versions: Launchpad Base 2.5.0
>Reporter: Lukas Eder
>Assignee: Bertrand Delacretaz
>Priority: Minor
>
> I'm learning about Sling and I'm trying to build and run the Sling samples 
> within my Launchpad instance. For instance, I'm trying to run 
> "samples/post-servlet-extensions". However, it seems that this sample depends 
> on JCR 1.0, transitively, as I'm getting this error in the Sling Console, 
> after loading the bundle:
> Imported Packages javax.jcr,version=[1.0,2) -- Cannot be resolved
> The Launchpad (version 6), however includes JCR 2.0. Is this sample outdated? 
> How can this be fixed? Note:
> - I've tried upgrading the JCR dependency in ../../../parent/pom.xml before 
> building the samples (with mvn clean install) - without success
> - I've tried upgrading the sample's dependencies on 
> org.apache.sling.servlets.post from 2.0.4-incubator to 2.2.0 and on 
> org.apache.sling.jcr.resource from 2.0.6 to 2.2.4 - without success
> - I've tried building Sling from trunk - without success, as many artefacts 
> seem to be missing from the Apache SNAPSHOT repositories.
> I'm not having such issues with the "samples/urlfilter" sample



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Build failed in Jenkins: sling-trunk-1.6 #1981

2013-10-16 Thread Apache Jenkins Server

See 

Changes:

[cziegeler] SLING-3170 : Complex Job Result Structures

[cziegeler] SLING-3170 : Complex Job Result Structures

--
[...truncated 36582 lines...]
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.ResourceSuperTypeTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.NodetypeRenderingTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.IncludeTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.scripting.SlingJSPTaglibTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.scripting.StandaloneScriptExecutionTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.indexing.FullTextIndexingTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.InitialContentTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.PropertyRenderingTest
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.WebdavUploadTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.resourceprovider.PlanetsResourceProviderTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.DavExIntegrationTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.RangeStreamingTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.GetWithSuffixTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.ScriptBuiltinObjectsTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.HttpPingTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.NodeTypeBasedRenderingTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.auth.AuthenticationResponseCodeTest
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.ValueFromTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.ContentLoaderMiscPropertyTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.MkdirTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.accessManager.RemoveAcesTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.accessManager.PrivilegesInfoTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.accessManager.GetAclTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.accessManager.ModifyAceTest
Tests run: 15, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.ScriptBindingsValuesProviderTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.ExportedPackagesTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.RequestAttributeTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.JspIncludeTest
http://localhost:59663/JspIncludeTest/1381931018671/text_b_1381931018687_6
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.UploadFileTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.ResourceDecoratorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.ServerSideScriptsTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.CreateNodeTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.login.RedirectOnLogoutTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.login.RedirectOnLoginErrorTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.login.FormGenerationTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apac

Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Launchpad Testing #1981

2013-10-16 Thread Apache Jenkins Server

See 


--
[...truncated 600 lines...]
 T E S T S
---
Running org.apache.sling.launchpad.testing.TestAll
Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING2094Test
Checking if the required Sling services are started (timeout 300 seconds)...
(base URLs=http://localhost:59663 and http://localhost:59663; servlet context=)
Sling services seem to be started, continuing with integration tests.
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING2085Test
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING2617Test
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING2522Test
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING457Test
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING2082Test
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running org.apache.sling.launchpad.webapp.integrationtest.issues.SLING760Test
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingDefaultValuesTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostToRootTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletCopyTest
Tests run: 16, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletNopTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.ReferenceTypeHintTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletVersionableTest
Tests run: 25, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletAtCopyTest
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletMoveTest
Tests run: 15, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOrderTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostStatusTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletDeleteTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletAtMoveTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletAtDeleteTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingSessionInfoTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletUpdateTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletImportTest
Tests run: 19, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletPrivilegesUpdateTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletPatchTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingAutoPropertiesTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.CustomPostOperationTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingDateValuesTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletOutputContentTypeTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostServletCreateTest
Tests run: 16, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.post.PostResponseCreatorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
Running 
org.apache.sling.launchpad.webapp.integrationtest.servlets.resolution.PathsServletTest
Tests run:

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Sample Integration Tests #1981

2013-10-16 Thread Apache Jenkins Server

See

Re: failure running sling.extensions.event unit/integraiton tests on windows?

2013-10-16 Thread Bertrand Delacretaz

On Tue, Oct 15, 2013 at 10:30 PM, Stefan Seifert  wrote:
> ...running win7 64bit, java 1.7.0_17, maven 3.0.5
>
> any idea why this integration tests for sling event module fails when 
> building with "mvn clean install"?
> i assume they run on other platforms?...

Yes, they work for me (though integration tests take a lot of time,
total time 8 minutes in a debian VM on a 3-years old macbook), java
version 1.7.0_40, Debian 4.6.3-14.

And also at
https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.event/

-Bertrand

[jira] [Created] (SLING-3181) Use the *IT.java name pattern to separate between unit and integration tests

2013-10-16 Thread Bertrand Delacretaz (JIRA)

Bertrand Delacretaz created SLING-3181:
--

 Summary: Use the *IT.java name pattern to separate between unit 
and integration tests
 Key: SLING-3181
 URL: https://issues.apache.org/jira/browse/SLING-3181
 Project: Sling
  Issue Type: Improvement
  Components: Best practices
Reporter: Bertrand Delacretaz
Priority: Minor


When a module contains both unit and integration tests, naming integration test 
classes *IT allows the surefire and failsafe plugins to automatically select 
the right tests, without requiring pom configurations.

In the bundles/scripting/core module for example, the 
BindingsValuesProvidersByContextIT test is run in the integration-tests phase, 
and other tests in the test phase, based only on the test names:

src/test/java/org/apache/sling/scripting/core/impl/BindingsValuesProvidersByContextIT.java
src/test/java/org/apache/sling/scripting/core/impl/DummyScriptEngineFactory.java
src/test/java/org/apache/sling/scripting/core/impl/helper/ProtectedBindingsTest.java
src/test/java/org/apache/sling/scripting/core/impl/LogWriterTest.java
src/test/java/org/apache/sling/scripting/core/impl/ScriptEngineManagerFactoryTest.java




--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Resolved] (SLING-3170) Complex Job Result Structures

2013-10-16 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler resolved SLING-3170.
-

Resolution: Fixed

Ok, I'Ve added the remove event notification Thanks :)

> Complex Job Result Structures
> -
>
> Key: SLING-3170
> URL: https://issues.apache.org/jira/browse/SLING-3170
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Extensions Event 3.3.0
>
>
> This is a follow up from SLING-3028 based on comments by Stefan Seifert:
> we need a possible to store complex result structures in our jobs, e.g. a 
> subtree of nodes/resources with static and other process infos, definitely 
> too much for a single string. ok, we could build an JSON structure and pass 
> it over as log messages, but this would e really ugly hack. it would be 
> possible to store this structure in the job logic and have an own management 
> gui which can detect this additional result info by job id and display it. 
> but when thinking about a cluster of nodes where the job runs only on one 
> node it would be good to collect this job results centrally. i've not a 
> perfect idea for an API extension for this, perhaps we should create a 
> separate ticket for it.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

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

2013-10-16 Thread Apache Jenkins Server

See 

--
[...truncated 298 lines...]
Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT 
/repos/asf/!svn/vcc/default failed
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:379)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:364)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:708)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:335)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1289)
at 
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:837)
at 
org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:507)
at 
org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:364)
at 
org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:274)
at 
org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:27)
at 
org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:11)
at 
org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)
at 
org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:291)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:311)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387)
at 
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:157)
... 14 more
Caused by: svn: E175002: REPORT /repos/asf/!svn/vcc/default failed
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97)
... 33 more
Caused by: org.tmatesoft.svn.core.SVNException: svn: E204899: REPORT request 
failed on '/repos/asf/!svn/vcc/default'
svn: E204899: Cannot create new file 
'/home/hudson/jenkins-slave/workspace/sling-trunk-1.7/trunk/samples/espblog/src/main/java/org/apache/sling/samples/espblog/.svn/lock'
at 
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at 
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:748)
at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373)
... 32 more
Caused by: svn: E204899: REPORT request failed on '/repos/asf/!svn/vcc/default'
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97)
at org.tmatesoft.svn.core.SVNErrorMessage.wrap(SVNErrorMessage.java:407)
... 34 more
Caused by: svn: E204899: Cannot create new file 
'/home/hudson/jenkins-slave/workspace/sling-trunk-1.7/trunk/samples/espblog/src/main/java/org/apache/sling/samples/espblog/.svn/lock'
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:171)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:126)
at 
org.tmatesoft.svn.core.internal.wc.SVNFileUtil.createEmptyFile(SVNFileUtil.java:346)
at 
org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea14.createVersionedDirectory(SVNAdminArea14.java:1553)
at 
org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea16Factory.doCreateVersionedDirectory(SVNAdminArea16Factory.java:30)
at 
org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.createVersionedDirectory(SVNAdminAreaFactory.java:241)
at 
org.tmatesoft.svn.core.internal.wc.SVNWCManager.ensureAdminAreaExists(SVNWCManager.java:428)
at 
org.tmatesoft.svn.core.internal.wc.SVNUpdateEditor.addDir(SVNUpdateEditor.java:762)
at 
org.tmatesoft.svn.core.internal.wc.SVNCancellableEditor.addDir(SVNCancellableEditor.java:84)
at 
org.tmatesoft.svn.core.internal.io.dav.handlers.DAVEditorHandler.startElement(DAVEditorHandler.java:326)
at 
org.tmatesoft.svn.core.internal.io.dav.handlers.BasicDAVHandler.startElement(BasicDAVHandler.java:89)
at 
com.sun.org.apache.xerces.internal.parsers.AbstractSAXPars

RE: failure running sling.extensions.event unit/integraiton tests on windows?

2013-10-16 Thread Stefan Seifert

strange. i tried to isolate the problem by disabling all integration tests by 
added junit @Ignore annotation to them.
the HistoryTest IT runs then fine.
i startet adding/removing more integration tests and sometims it succeeds, 
sometimes not. perhaps a racing condition, or a cleanup issue of the 
integration tests.

if it fails it takes a long time executing this step "Starting job queue test":

...
16.10.2013 13:23:27.352 *INFO* [Thread-102] 
org.apache.sling.event.impl.jobs.TopologyCapabilities Detected capabilities of 
86db438e-86fa-43b2-85c2-62d22a12db6b : 
/,sling/test/history,sling/webconsole/test
16.10.2013 13:23:27.352 *INFO* [Thread-102] 
PAXEXAM-PROBE-914abd18-50d6-448f-82ca-29f27441a4cc Service [99] ServiceEvent 
REGISTERED
16.10.2013 13:23:29.342 *INFO* [Apache Sling Job Background Loader] 
org.apache.sling.event Service [QueueMBean for queue test,100] ServiceEvent 
REGISTERED
16.10.2013 13:23:29.342 *INFO* [Apache Sling Job Queue test] 
org.apache.sling.event.impl.jobs.queues.OrderedJobQueue.test Starting job queue 
test

>> it hangs here for several minutes <<

16.10.2013 13:28:27.364 *INFO* [CM Event Dispatcher (Fire ConfigurationEvent: 
pid=org.apache.sling.event.jobs.QueueConfiguration.2be31a75-f846-4e17-a1b9-8482c5fcaed2)]
 org.apache.sling.event Service 
[org.apache.sling.event.jobs.QueueConfiguration.2be31a75-f846-4e17-a1b9-8482c5fcaed2,98]
 ServiceEvent UNREGISTERING
16.10.2013 13:28:27.364 *INFO* [main] 
PAXEXAM-PROBE-914abd18-50d6-448f-82ca-29f27441a4cc BundleEvent STOPPING
16.10.2013 13:28:27.364 *INFO* [main] 
PAXEXAM-PROBE-914abd18-50d6-448f-82ca-29f27441a4cc Service [73] ServiceEvent 
UNREGISTERING
...

the failsafe report contains only this:

---
Test set: org.apache.sling.event.it.HistoryTest
---
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 305.173 sec <<< 
FAILURE!
testHistory(org.apache.sling.event.it.HistoryTest)  Time elapsed: 305.163 sec  
<<< ERROR!
java.lang.Exception: test timed out after 30 milliseconds
at java.lang.Thread.sleep(Native Method)
at 
org.apache.sling.event.it.AbstractJobHandlingTest.sleep(AbstractJobHandlingTest.java:160)
at 
org.apache.sling.event.it.HistoryTest.testHistory(HistoryTest.java:118)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)


stefan

>-Original Message-
>From: Carsten Ziegeler [mailto:cziege...@apache.org]
>Sent: Wednesday, October 16, 2013 12:08 PM
>To: dev@sling.apache.org
>Subject: Re: failure running sling.extensions.event unit/integraiton
>tests on windows?
>
>Hi,
>
>the tests run fine on my machine - it seems that in your case the loop
>waits forever to get 10 finished jobs in the history.
>Do you see any exception in the log output?
>
>Carsten

[jira] [Resolved] (SLING-3180) Failed deployment should fail the build by default

2013-10-16 Thread Robert Munteanu (JIRA)


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

Robert Munteanu resolved SLING-3180.


Resolution: Fixed

Fixed in http://svn.apache.org/r1532729

> Failed deployment should fail the build by default
> --
>
> Key: SLING-3180
> URL: https://issues.apache.org/jira/browse/SLING-3180
> Project: Sling
>  Issue Type: Improvement
>  Components: Maven Plugins and Archetypes
>Affects Versions: Maven Sling Plugin 2.1.0
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Maven Sling Plugin 2.1.2
>
>
> Even though we have added a failOnError attribute to the maven-sling-plugin 
> in SLING-2075, it defaults to false, for backwards compatibility reasons.
> However, this still leaves a lot of first-time setups silently broken by 
> default, and I see no real reason for which to leave this parameter by 
> default to false by default. As a matter of fact, I'd favour removing it 
> altogether and failing all the time, but that's a larger discussion.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Created] (SLING-3180) Failed deployment should fail the build by default

2013-10-16 Thread Robert Munteanu (JIRA)

Robert Munteanu created SLING-3180:
--

 Summary: Failed deployment should fail the build by default
 Key: SLING-3180
 URL: https://issues.apache.org/jira/browse/SLING-3180
 Project: Sling
  Issue Type: Improvement
  Components: Maven Plugins and Archetypes
Affects Versions: Maven Sling Plugin 2.1.0
Reporter: Robert Munteanu
Assignee: Robert Munteanu
 Fix For: Maven Sling Plugin 2.1.2


Even though we have added a failOnError attribute to the maven-sling-plugin in 
SLING-2075, it defaults to false, for backwards compatibility reasons.

However, this still leaves a lot of first-time setups silently broken by 
default, and I see no real reason for which to leave this parameter by default 
to false by default. As a matter of fact, I'd favour removing it altogether and 
failing all the time, but that's a larger discussion.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Re: failure running sling.extensions.event unit/integraiton tests on windows?

2013-10-16 Thread Carsten Ziegeler

Hi,

the tests run fine on my machine - it seems that in your case the loop
waits forever to get 10 finished jobs in the history.
Do you see any exception in the log output?

Carsten


2013/10/15 Stefan Seifert 

> running win7 64bit, java 1.7.0_17, maven 3.0.5
>
> any idea why this integration tests for sling event module fails when
> building with "mvn clean install"?
> i assume they run on other platforms?
>
> >>>
> Results :
>
> Tests in error:
>   testHistory(org.apache.sling.event.it.HistoryTest): test timed out after
> 30 milliseconds
>
> Tests run: 18, Failures: 0, Errors: 1, Skipped: 0
> <<<
>
> the other integration tests are running, but take quite a lot of time to
> complete.
>
> stefan
>



-- 
Carsten Ziegeler
cziege...@apache.org

Jenkins build is back to stable : sling-trunk-1.6 #1979

2013-10-16 Thread Apache Jenkins Server

See

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Installer Integration Tests #1979

2013-10-16 Thread Apache Jenkins Server

See

Jenkins build became unstable: sling-trunk-1.6 #1978

2013-10-16 Thread Apache Jenkins Server

See

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Installer Integration Tests #1978

2013-10-16 Thread Apache Jenkins Server

See

[jira] [Commented] (SLING-3169) Job state and related enumerations

2013-10-16 Thread Stefan Seifert (JIRA)


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

Stefan Seifert commented on SLING-3169:
---

from a job admin GUI perspective if find this a good solution to be sure what 
happened with the job exactly if it was not successful.

> Job state and related enumerations
> --
>
> Key: SLING-3169
> URL: https://issues.apache.org/jira/browse/SLING-3169
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Extensions Event 3.3.0
>
>
> This is a follow up from SLING-3028 based on comments by Stefan Seifert:
> I find the enum name Job.JobType not ideal, because it does not stand of 
> a type but for a state of the job. But there is a JobState enum in the 
> consumer API package already.
> I find the enum and class names JobState and JobStatus in the consumer 
> package not ideal, because they do not stand for a state, but for a job 
> result.
>   



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Comment Edited] (SLING-3169) Job state and related enumerations

2013-10-16 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler edited comment on SLING-3169 at 10/16/13 8:24 AM:
---

I could imagine the following enum:

enum JobState 
  QUEUED, // waiting in queue after adding or for restart after failing
  ACTIVE,   // job is currently processed
  SUCCEEDED,  // processing finished successfully
  STOPPED,  // processing was stopped by a user
  GIVEN_UP // number of retries reached
  ERROR  // processing signaled CANCELLED or throw an exception
  DROPPED // dropped due to queue configuration



[~sseif...@pro-vision.de] WDYT?


was (Author: cziegeler):
I could imagine the following enum:

enum JobState {
  QUEUED, // waiting in queue after adding or for restart after failing
  ACTIVE,   // job is currently processed
  SUCCEEDED,  // processing finished successfully
  STOPPED,  // processing was stopped by a user
  GIVEN_UP // number of retries reached
  ERROR  // processing signaled CANCELLED or throw an exception
  DROPPED // dropped due to queue configuration

};

[~sseif...@pro-vision.de] WDYT?

> Job state and related enumerations
> --
>
> Key: SLING-3169
> URL: https://issues.apache.org/jira/browse/SLING-3169
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Extensions Event 3.3.0
>
>
> This is a follow up from SLING-3028 based on comments by Stefan Seifert:
> I find the enum name Job.JobType not ideal, because it does not stand of 
> a type but for a state of the job. But there is a JobState enum in the 
> consumer API package already.
> I find the enum and class names JobState and JobStatus in the consumer 
> package not ideal, because they do not stand for a state, but for a job 
> result.
>   



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (SLING-3169) Job state and related enumerations

2013-10-16 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler commented on SLING-3169:
-

I could imagine the following enum:

enum JobState {
  QUEUED, // waiting in queue after adding or for restart after failing
  ACTIVE,   // job is currently processed
  SUCCEEDED,  // processing finished successfully
  STOPPED,  // processing was stopped by a user
  GIVEN_UP // number of retries reached
  ERROR  // processing signaled CANCELLED or throw an exception
  DROPPED // dropped due to queue configuration

};

[~sseif...@pro-vision.de] WDYT?

> Job state and related enumerations
> --
>
> Key: SLING-3169
> URL: https://issues.apache.org/jira/browse/SLING-3169
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Extensions Event 3.3.0
>
>
> This is a follow up from SLING-3028 based on comments by Stefan Seifert:
> I find the enum name Job.JobType not ideal, because it does not stand of 
> a type but for a state of the job. But there is a JobState enum in the 
> consumer API package already.
> I find the enum and class names JobState and JobStatus in the consumer 
> package not ideal, because they do not stand for a state, but for a job 
> result.
>   



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (SLING-3169) Job state and related enumerations

2013-10-16 Thread Stefan Seifert (JIRA)


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

Stefan Seifert commented on SLING-3169:
---

good solution for the ResultBuilder interface.

concerning the JobState: you are right. i think the enum names/method names are 
not fully intuitive for ones that have used similar states in other systems but 
with different meanings. so for the JobState from the job endinge POV the 
states are fine (although it had used FAILED instead of CANCELLED, but this is 
only my personal preference, i'm fine with CANCELLED as well). but now its in 
synch with the old JobResult enum from the JobConsumer interface, so it's at 
least consistent now.

together with the javadocs the methods in the ResultBuilder method should be 
clear now.

> Job state and related enumerations
> --
>
> Key: SLING-3169
> URL: https://issues.apache.org/jira/browse/SLING-3169
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Extensions Event 3.3.0
>
>
> This is a follow up from SLING-3028 based on comments by Stefan Seifert:
> I find the enum name Job.JobType not ideal, because it does not stand of 
> a type but for a state of the job. But there is a JobState enum in the 
> consumer API package already.
> I find the enum and class names JobState and JobStatus in the consumer 
> package not ideal, because they do not stand for a state, but for a job 
> result.
>   



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (SLING-2762) AbstractSlingRepository#login violates JCR spec

2013-10-16 Thread Felix Meschberger (JIRA)


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

Felix Meschberger commented on SLING-2762:
--

Linking to the generic issue implementing the preauthentication problem 
proposal 
(https://cwiki.apache.org/confluence/display/SLING/Solving+the+Authentication+Handler+Credential+Validation+Problem)

> AbstractSlingRepository#login violates JCR spec
> ---
>
> Key: SLING-2762
> URL: https://issues.apache.org/jira/browse/SLING-2762
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Reporter: Antonio Sanso
>
> AbstractSlingRepository#login seems to violate the javax.jcr.Repository spec.
> The API [0] says
> " If credentials is null, it is assumed that authentication is handled by a 
> mechanism external to the repository itself (for example, through the JAAS 
> framework) and that the repository implementation exists within a context 
> (for example, an application server) that allows it to handle authorization 
> of the request for access to the specified workspace."
> while the implementation looks like
> {code}
> ...
> if (credentials == null) {
> credentials = getAnonCredentials(this.anonUser);
> }
> ...
> {code}
> [0] 
> http://www.day.com/maven/jsr170/javadocs/jcr-2.0/javax/jcr/Repository.html#login%28javax.jcr.Credentials,%20java.lang.String%29



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Created] (SLING-3179) Implement solution to the Authentication Handler Credential Validation Problem

2013-10-16 Thread Felix Meschberger (JIRA)

Felix Meschberger created SLING-3179:


 Summary: Implement solution to the Authentication Handler 
Credential Validation Problem
 Key: SLING-3179
 URL: https://issues.apache.org/jira/browse/SLING-3179
 Project: Sling
  Issue Type: Bug
  Components: API, JCR, ResourceResolver
Affects Versions: Resource Resolver 1.0.6, API 2.4.2, JCR Base 2.1.2
Reporter: Felix Meschberger


The proposal [Solving the Authentication Handler Credential Validation 
Problem|https://cwiki.apache.org/confluence/display/SLING/Solving+the+Authentication+Handler+Credential+Validation+Problem]
 should be implemented.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Updated] (SLING-3169) Job state and related enumerations

2013-10-16 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler updated SLING-3169:


Summary: Job state and related enumerations  (was: Naming of Job related 
enumerations)

> Job state and related enumerations
> --
>
> Key: SLING-3169
> URL: https://issues.apache.org/jira/browse/SLING-3169
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Extensions Event 3.3.0
>
>
> This is a follow up from SLING-3028 based on comments by Stefan Seifert:
> I find the enum name Job.JobType not ideal, because it does not stand of 
> a type but for a state of the job. But there is a JobState enum in the 
> consumer API package already.
> I find the enum and class names JobState and JobStatus in the consumer 
> package not ideal, because they do not stand for a state, but for a job 
> result.
>   



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (SLING-3169) Naming of Job related enumerations

2013-10-16 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler commented on SLING-3169:
-

Thanks for the feedback [~sseif...@pro-vision.de]

I've now committed a slightly different solution:
ResultBuilder result();

public interface ResultBuilder {
ResultBuilder message(final String message);
JobExecutionResult succeeded();
JobExecutionResult failed();
JobExecutionResult failed(final long retryDelayInMs);
JobExecutionResult cancelled();
}

CANCELLED vs FAILED: a job consumer result is based on what the job consumer 
knows: it knows whether retrying the job does not make sense at all (CANCELLED) 
or whether the job could be retried (FAILED) (the names are maybe not perfect 
but that's what we picked :) ). When FAILED is signaled by the consumer, the 
job engine decides based on the queue configuration (number of retries) whether 
the job will be requeued or is marked as permanently FAILED. So a FAILED 
returned by the consumer either results in QUEUED or CANCELLED.
And based on SUCCESS, FAILED and CANCELLED we have the notification events 
right now.

Now for the enum JobState this is right now for consumers interested in the job 
state, we have right now:
enum JobType {
  QUEUED,
  ACTIVE,
  SUCCEEDED,
  CANCELLED
};
where SUCCEEDED and CANCELLED are final states and QUEUED, ACTIVE the states 
during queuing and processing.
The FAILED state can be detected, if the job is QUEUED or ACTIVE and the retry 
count is greather than 0 - but right now we can't detect why a job is in the 
CANCELLED state
So right now we don't distinguish between whether a job has been stopped by the 
user, was cancelled by the consumer, throw an exception etc.


> Naming of Job related enumerations
> --
>
> Key: SLING-3169
> URL: https://issues.apache.org/jira/browse/SLING-3169
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Extensions Event 3.3.0
>
>
> This is a follow up from SLING-3028 based on comments by Stefan Seifert:
> I find the enum name Job.JobType not ideal, because it does not stand of 
> a type but for a state of the job. But there is a JobState enum in the 
> consumer API package already.
> I find the enum and class names JobState and JobStatus in the consumer 
> package not ideal, because they do not stand for a state, but for a job 
> result.
>   



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Resolved] (SLING-3172) Job schedule name handling

2013-10-16 Thread Carsten Ziegeler (JIRA)


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

Carsten Ziegeler resolved SLING-3172.
-

Resolution: Fixed

I've dropped the name from the api for now, internally we use a uuid as the 
name to handle reschedule, unscheduling etc.

> Job schedule name handling
> --
>
> Key: SLING-3172
> URL: https://issues.apache.org/jira/browse/SLING-3172
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Stefan Seifert
>Assignee: Carsten Ziegeler
>Priority: Minor
> Fix For: Extensions Event 3.3.0
>
>
> follow-up from SLING-3028
> Q: JobBuilder.schedule - for what is the parameter "name" used? i does not 
> get its meaning from the javadocs. why is it required to make it unique?
> A: Schedule Name: each schedule gets a unique name to identify it and have a 
> way to update the schedule or unschedule it. The other option I see would be 
> to create a unique scheduling id when a new schedule is created and then use 
> this to reference it. But in that case the client needs to store this id 
> somewhere. If you think that this needs further enhancements or changes, 
> please open a separate ticket.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

[jira] [Commented] (SLING-3174) [Tooling] add 'new simple content/bundle project' wizards

2013-10-16 Thread Stefan Egli (JIRA)


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

Stefan Egli commented on SLING-3174:


[~rombert], are you referring to adding actions when creating a faceted project 
with a specific facet? I think we need both. For someone unfamiliar with 
Slingclipse it might help when there's an explicit "new sling content project" 
rather than that being hidden in the "new faceted project". wdyt?

> [Tooling] add 'new simple content/bundle project' wizards
> -
>
> Key: SLING-3174
> URL: https://issues.apache.org/jira/browse/SLING-3174
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Reporter: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> We should include 'new' wizards which create simple content/bundle projects. 
> The project would simply create a faceted project with the according facet 
> set and set any additional type specific properties (eg with content it would 
> create a jcr_root directory). Although these two wizards would do very 
> trivial tasks, IMO this will help users kickstart projects and get into the 
> mindset of slingclipse.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

49 matches

Mail list logo