[jira] [Resolved] (SLING-2328) Error in DOAP

[Justin Edelson (Resolved) (JIRA)]

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

Justin Edelson resolved SLING-2328.
---

Resolution: Fixed
  Assignee: Justin Edelson

fixed in r1213936

> Error in DOAP
> -
>
> Key: SLING-2328
> URL: https://issues.apache.org/jira/browse/SLING-2328
> Project: Sling
>  Issue Type: Bug
> Environment: 
> http://svn.apache.org/repos/asf/sling/site/doap/sling-doap.rdf
>Reporter: Sebb
>Assignee: Justin Edelson
>
> The DOAP file has:
>   http://sling.apache.org";>
> Sling
> However, the name should be
> Apache Sling

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (SLING-2328) Error in DOAP

[Sebb (Created) (JIRA)]

Error in DOAP
-

 Key: SLING-2328
 URL: https://issues.apache.org/jira/browse/SLING-2328
 Project: Sling
  Issue Type: Bug
 Environment: 
http://svn.apache.org/repos/asf/sling/site/doap/sling-doap.rdf
Reporter: Sebb


The DOAP file has:

  http://sling.apache.org";>
Sling

However, the name should be

Apache Sling


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Build failed in Jenkins: sling-trunk-1.5 #1482

[Apache Jenkins Server]

See 

Changes:

[justin] SLING-2251 - fixing IT (thanks to Troy Caldwell for the patch!)

--
[...truncated 16325 lines...]
---
There are no tests to run.

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results[INFO] Checking unresolved references to 
org.codehaus.mojo.signature:java15:1.0

[INFO] 
[INFO] --- animal-sniffer-maven-plugin:1.7:check (default) @ 
org.apache.sling.testing.samples.integrationtests ---
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ 
org.apache.sling.testing.samples.integrationtests ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-java) @ 
org.apache.sling.testing.samples.integrationtests ---
[JENKINS] Archiving 

 to 
/home/hudson/hudson/jobs/sling-trunk-1.5/modules/org.apache.sling$org.apache.sling.testing.samples.integrationtests/builds/2011-12-13_19-11-22/archive/org.apache.sling/org.apache.sling.testing.samples.integrationtests/1.0.7-SNAPSHOT/org.apache.sling.testing.samples.integrationtests-1.0.7-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
/home/hudson/hudson/jobs/sling-trunk-1.5/modules/org.apache.sling$org.apache.sling.testing.samples.integrationtests/builds/2011-12-13_19-11-22/archive/org.apache.sling/org.apache.sling.testing.samples.integrationtests/1.0.7-SNAPSHOT/org.apache.sling.testing.samples.integrationtests-1.0.7-SNAPSHOT.jar
ignoring exception during new ExecutedMojo null
[INFO] 
[INFO] --- maven-source-plugin:2.1.2:jar (attach-sources) @ 
org.apache.sling.testing.samples.integrationtests ---
[INFO] META-INF already added, skipping
[INFO] META-INF/LICENSE already added, skipping
[INFO] META-INF/NOTICE already added, skipping
[INFO] META-INF/DEPENDENCIES already added, skipping
[INFO] Building jar: 

[INFO] META-INF already added, skipping
[INFO] META-INF/LICENSE already added, skipping
[INFO] META-INF/NOTICE already added, skipping
[INFO] META-INF/DEPENDENCIES already added, skipping
[INFO] 
[INFO] --- maven-failsafe-plugin:2.7.2:integration-test (integration-test) @ 
org.apache.sling.testing.samples.integrationtests ---
[INFO] Failsafe report directory: 


---
 T E S T S
---
Running org.apache.sling.testing.samples.integrationtests.http.OsgiConsoleTest
8 [main] INFO 
org.apache.sling.testing.samples.integrationtests.http.OsgiConsoleTest - Server 
base URL=http://localhost:53723
18 [main] INFO org.apache.sling.testing.tools.jarexec.JarExecutor - Executable 
jar options: -p 53723
18 [main] INFO org.apache.sling.testing.tools.jarexec.JarExecutor - Executing 
java -Xmx512m -jar 

 -p 53723
21 [main] INFO org.apache.sling.testing.tools.sling.TimeoutsProvider - Timeout 
factor set to 1.0 from system property sling.testing.timeout.multiplier
21 [main] INFO 
org.apache.sling.testing.samples.integrationtests.http.OsgiConsoleTest - Will 
wait up to 60 seconds for server to become ready
23 [main] INFO 
org.apache.sling.testing.samples.integrationtests.http.OsgiConsoleTest - 
Checking that GET requests return expected content (timeout=60 seconds): 
[/:script src="system/sling.js", 
/.explorer.html:href="/libs/sling/explorer/css/explorer.css", 
/sling-test/sling/sling-test.html:Sling client library tests]
13.12.2011 19:54:25.262 *INFO* [main] Setting sling.home=sling (default)
13.12.2011 19:54:25.262 *INFO* [main] Starting Sling in sling 
(
13.12.2011 19:54:25.267 *INFO* [main] Checking launcher JAR in folder sling
13.12.2011 19:54:25.278 *INFO* [main] Installing new launcher: 
jar:
 2.3.0 (org.apache.sling.launchpad.base.jar.1323806065277)
13.12.2011 19:54:25.282 *INFO* [main] Loading launche

Build failed in Jenkins: sling-trunk-1.5 » Apache Sling Sample Integration Tests #1482

[Apache Jenkins Server]

See 


--
ignoring exception during new ExecutedMojo null
[INFO] 
[INFO] --- maven-source-plugin:2.1.2:jar (attach-sources) @ 
org.apache.sling.testing.samples.failingtests ---
[INFO] META-INF already added, skipping
[INFO] META-INF/LICENSE already added, skipping
[INFO] META-INF/NOTICE already added, skipping
[INFO] META-INF/DEPENDENCIES already added, skipping
[INFO] Building jar: 
/home/jenkins/jenkins-slave/workspace/sling-trunk-1.5/trunk/testing/samples/failing-tests/target/org.apache.sling.testing.samples.failingtests-1.0.7-SNAPSHOT-sources.jar
[INFO] META-INF already added, skipping
[INFO] META-INF/LICENSE already added, skipping
[INFO] META-INF/NOTICE already added, skipping
[INFO] META-INF/DEPENDENCIES already added, skipping
[INFO] [INFO] Checking legal files in: 
org.apache.sling.testing.samples.failingtests-1.0.7-SNAPSHOT.jar
[INFO] Checking legal files in: 
org.apache.sling.testing.samples.failingtests-1.0.7-SNAPSHOT-sources.jar

[INFO] --- ianal-maven-plugin:1.0-alpha-1:verify-legal-files (default) @ 
org.apache.sling.testing.samples.failingtests ---
[INFO] [INFO] Installing 
/home/jenkins/jenkins-slave/workspace/sling-trunk-1.5/trunk/testing/samples/failing-tests/target/org.apache.sling.testing.samples.failingtests-1.0.7-SNAPSHOT.jar
 to 
/home/jenkins/.m2/repository/org/apache/sling/org.apache.sling.testing.samples.failingtests/1.0.7-SNAPSHOT/org.apache.sling.testing.samples.failingtests-1.0.7-SNAPSHOT.jar
[INFO] Installing 
/home/jenkins/jenkins-slave/workspace/sling-trunk-1.5/trunk/testing/samples/failing-tests/pom.xml
 to 
/home/jenkins/.m2/repository/org/apache/sling/org.apache.sling.testing.samples.failingtests/1.0.7-SNAPSHOT/org.apache.sling.testing.samples.failingtests-1.0.7-SNAPSHOT.pom
[INFO] Installing 
/home/jenkins/jenkins-slave/workspace/sling-trunk-1.5/trunk/testing/samples/failing-tests/target/org.apache.sling.testing.samples.failingtests-1.0.7-SNAPSHOT-sources.jar
 to 
/home/jenkins/.m2/repository/org/apache/sling/org.apache.sling.testing.samples.failingtests/1.0.7-SNAPSHOT/org.apache.sling.testing.samples.failingtests-1.0.7-SNAPSHOT-sources.jar

[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
org.apache.sling.testing.samples.failingtests ---
[INFO] Local OBR update disabled (enable with -DobrRepository)
[INFO] 
[INFO] --- maven-bundle-plugin:2.0.1:install (default-install) @ 
org.apache.sling.testing.samples.failingtests ---
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/sling/org.apache.sling.testing.samples.failingtests/1.0.7-SNAPSHOT/maven-metadata.xml
[INFO] 
[INFO] --- maven-deploy-plugin:2.5:deploy (default-deploy) @ 
org.apache.sling.testing.samples.failingtests ---
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/sling/org.apache.sling.testing.samples.failingtests/1.0.7-SNAPSHOT/maven-metadata.xml
 (2 KB at 6.8 KB/sec)
Uploading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/sling/org.apache.sling.testing.samples.failingtests/1.0.7-SNAPSHOT/org.apache.sling.testing.samples.failingtests-1.0.7-20111213.195406-249.jar
Uploaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/sling/org.apache.sling.testing.samples.failingtests/1.0.7-SNAPSHOT/org.apache.sling.testing.samples.failingtests-1.0.7-20111213.195406-249.jar
 (11 KB at 40.4 KB/sec)
Uploading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/sling/org.apache.sling.testing.samples.failingtests/1.0.7-SNAPSHOT/org.apache.sling.testing.samples.failingtests-1.0.7-20111213.195406-249.pom
Uploaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/sling/org.apache.sling.testing.samples.failingtests/1.0.7-SNAPSHOT/org.apache.sling.testing.samples.failingtests-1.0.7-20111213.195406-249.pom
 (4 KB at 26.6 KB/sec)
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/sling/org.apache.sling.testing.samples.failingtests/maven-metadata.xml
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/sling/org.apache.sling.testing.samples.failingtests/maven-metadata.xml
 (361 B at 2.0 KB/sec)
Uploading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/sling/org.apache.sling.testing.samples.failingtests/1.0.7-SNAPSHOT/maven-metadata.xml
Uploaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/sling/org.apache.sling.testing.samples.failingtests/1.0.7-SNAPSHOT/maven-metadata.xml
 (2 KB at 6.6 KB/sec)
Uploading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/sling/org.apache.sling.testing.samples.failingtests/maven-metadata.xml
Uploaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/sling/org.apache.sling.testing.samples.failingt

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

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.6 #1154

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.5 » Apache Sling Launchpad Testing WAR version #1481

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.5 » Apache Sling Launchpad Testing #1481

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.5 » Apache Sling Installer Integration Tests #1481

[Apache Jenkins Server]

See 

[jira] [Commented] (SLING-2251) RedirectServlet should create relative Location headers as often as possible

[Justin Edelson (Commented) (JIRA)]

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

Justin Edelson commented on SLING-2251:
---

applied IT patch in r1213782. Thanks for the patch!

> RedirectServlet should create relative Location headers as often as possible
> 
>
> Key: SLING-2251
> URL: https://issues.apache.org/jira/browse/SLING-2251
> Project: Sling
>  Issue Type: Improvement
>  Components: Servlets
>Affects Versions: Servlets Get 2.1.2
>Reporter: Alexander Klimetschek
> Attachments: SLING-2251-VanityPathTest.patch, SLING-2251.patch
>
>
> SLING-1965 (more specifically 
> http://svn.apache.org/viewvc?view=revision&revision=903175 ) changed the 
> redirect servlet so that it _always_ generates an absolute location header. 
> The issue does not give much reasoning for that.
> The problem is that this breaks cases where a Sling server is run behind a 
> proxy (which does not or cannot rewrite the Location header), as the redirect 
> ("http://localhost:8080/some/path";) might not match the externally visible 
> domain (e.g. "https://my.domain.com";). Also, the schema is fixed (e.g. might 
> switch external https back to http).
> A solution would be to generate absolute URLs only if a resource resolver 
> mapping (/etc/map) includes an explicit domain and thus generates an absolute 
> URL. For all other cases, relative URLs should be generated. AFAICS, this was 
> the case before SLING-1965.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2251) RedirectServlet should create relative Location headers as often as possible

[Alexander Klimetschek (Commented) (JIRA)]

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

Alexander Klimetschek commented on SLING-2251:
--

@Antonio: It's already committed :-)

Could someone fix the integration tests (Troy provided a patch already) and 
resolve + close this bug? Thanks!

> RedirectServlet should create relative Location headers as often as possible
> 
>
> Key: SLING-2251
> URL: https://issues.apache.org/jira/browse/SLING-2251
> Project: Sling
>  Issue Type: Improvement
>  Components: Servlets
>Affects Versions: Servlets Get 2.1.2
>Reporter: Alexander Klimetschek
> Attachments: SLING-2251-VanityPathTest.patch, SLING-2251.patch
>
>
> SLING-1965 (more specifically 
> http://svn.apache.org/viewvc?view=revision&revision=903175 ) changed the 
> redirect servlet so that it _always_ generates an absolute location header. 
> The issue does not give much reasoning for that.
> The problem is that this breaks cases where a Sling server is run behind a 
> proxy (which does not or cannot rewrite the Location header), as the redirect 
> ("http://localhost:8080/some/path";) might not match the externally visible 
> domain (e.g. "https://my.domain.com";). Also, the schema is fixed (e.g. might 
> switch external https back to http).
> A solution would be to generate absolute URLs only if a resource resolver 
> mapping (/etc/map) includes an explicit domain and thus generates an absolute 
> URL. For all other cases, relative URLs should be generated. AFAICS, this was 
> the case before SLING-1965.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SLING-2251) RedirectServlet should create relative Location headers as often as possible

[Antonio Sanso (Commented) (JIRA)]

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

Antonio Sanso commented on SLING-2251:
--

+1

> RedirectServlet should create relative Location headers as often as possible
> 
>
> Key: SLING-2251
> URL: https://issues.apache.org/jira/browse/SLING-2251
> Project: Sling
>  Issue Type: Improvement
>  Components: Servlets
>Affects Versions: Servlets Get 2.1.2
>Reporter: Alexander Klimetschek
> Attachments: SLING-2251-VanityPathTest.patch, SLING-2251.patch
>
>
> SLING-1965 (more specifically 
> http://svn.apache.org/viewvc?view=revision&revision=903175 ) changed the 
> redirect servlet so that it _always_ generates an absolute location header. 
> The issue does not give much reasoning for that.
> The problem is that this breaks cases where a Sling server is run behind a 
> proxy (which does not or cannot rewrite the Location header), as the redirect 
> ("http://localhost:8080/some/path";) might not match the externally visible 
> domain (e.g. "https://my.domain.com";). Also, the schema is fixed (e.g. might 
> switch external https back to http).
> A solution would be to generate absolute URLs only if a resource resolver 
> mapping (/etc/map) includes an explicit domain and thus generates an absolute 
> URL. For all other cases, relative URLs should be generated. AFAICS, this was 
> the case before SLING-1965.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Jenkins build is still unstable: sling-trunk-1.6 #1153

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing WAR version #1153

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.5 #1480

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.5 » Apache Sling Launchpad Testing WAR version #1480

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.5 » Apache Sling Launchpad Testing #1480

[Apache Jenkins Server]

See 

[jira] [Resolved] (SLING-2289) Implement generic retry mechanism

[Carsten Ziegeler (Resolved) (JIRA)]

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

Carsten Ziegeler resolved SLING-2289.
-

Resolution: Fixed

Implemented in revision 1213634

> Implement generic retry mechanism
> -
>
> Key: SLING-2289
> URL: https://issues.apache.org/jira/browse/SLING-2289
> Project: Sling
>  Issue Type: New Feature
>  Components: Installer
>Affects Versions: Installer Core 3.2.2
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Installer Core 3.2.4
>
>
> Currently, if a task fails it is retried over and over again which basically 
> is kind of an endless loop.
> However, if between two retries nothing has changed, it is most likely that a 
> retry is failing again. We have some basic code for bundle handling, but this 
> is a) tied to bundles, b) not reusable, and c) not working perfectly.
> Instead we should come up with a generic mechanism for retries - a task 
> should signal that it want's to be retried. In addition we need a 
> notification mechanism which notifies the installer to retry something, e.g. 
> a service listening for bundle events would notify the installer each time a 
> bundle event has occurred etc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira