Jenkins build is still unstable: sling-trunk-1.6 #2538
See https://builds.apache.org/job/sling-trunk-1.6/changes
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2538
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2538/
Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Installer Integration Tests #2538
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.installer.it/2538/
Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Installer Integration Tests #2539
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.installer.it/2539/
Jenkins build is still unstable: sling-trunk-1.6 #2539
See https://builds.apache.org/job/sling-trunk-1.6/changes
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2539
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2539/
Jenkins build became unstable: sling-trunk-1.8 » Apache Sling SlingRepository Integration Tests #201
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.jcr.repository.it-jackrabbit-oak/201/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling SlingRepository Integration Tests #911
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.jcr.repository.it-jackrabbit-oak/911/
Jenkins build is back to stable : sling-trunk-1.8 » Apache Sling SlingRepository Integration Tests #202
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.jcr.repository.it-jackrabbit-oak/202/
Jenkins build is unstable: sling-trunk-1.8 » Apache Sling Launchpad Base #202
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.launchpad.base/202/
Jenkins build is unstable: sling-trunk-1.8 #202
See https://builds.apache.org/job/sling-trunk-1.8/202/changes
Jenkins build is unstable: sling-trunk-1.8 » Apache Sling Launchpad Testing #202
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.launchpad.testing/202/
Jenkins build is back to stable : sling-trunk-1.8 » Apache Sling Installer Integration Tests #202
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.installer.it/202/
Jenkins build is unstable: sling-trunk-1.8 » Apache Sling Event Support #202
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/202/
[VOTE] Release Apache Sling Testing Resource Resolver Mock version 0.3.0
Hi, We solved 4 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12326159 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1131/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1131 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. stefan p.s. this is my first apache sling release, hopefully PGP signing etc. is all correct.
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2540
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2540/
Jenkins build is still unstable: sling-trunk-1.6 #2540
See https://builds.apache.org/job/sling-trunk-1.6/changes
[jira] [Created] (SLING-3974) Folders that contain two underscores in the name are not displayed
JBodkin created SLING-3974: -- Summary: Folders that contain two underscores in the name are not displayed Key: SLING-3974 URL: https://issues.apache.org/jira/browse/SLING-3974 Project: Sling Issue Type: Bug Components: IDE Affects Versions: Sling Eclipse IDE 1.0.2 Environment: Windows, Eclipse Luna Reporter: JBodkin The Sling Eclipse IDE plugin is unable to show folders which contain two underscores in the name. For example, these folders are not displayed upon refreshing the view when I create them in the location filesystem (.content.xml is contained inside) * _cq_template * _test_dialog -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build is still unstable: sling-trunk-1.8 » Apache Sling Launchpad Testing #203
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.launchpad.testing/203/
Jenkins build is back to stable : sling-trunk-1.8 » Apache Sling Launchpad Base #203
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.launchpad.base/203/
Jenkins build is back to stable : sling-trunk-1.8 » Apache Sling Event Support #203
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/203/
Jenkins build is unstable: sling-trunk-1.7 » Apache Sling Models Integration Tests #912
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.models.integration-tests/912/
Jenkins build is unstable: sling-trunk-1.7 » Apache Sling Launchpad Base #912
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.base/912/
Jenkins build is unstable: sling-trunk-1.7 #912
See https://builds.apache.org/job/sling-trunk-1.7/912/changes
Jenkins build is unstable: sling-trunk-1.7 » Apache Sling Sample Integration Tests #912
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.testing.samples.integrationtests/912/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling SlingRepository Integration Tests #912
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.jcr.repository.it-jackrabbit-oak/912/
Jenkins build is unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #912
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.impl/912/
Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling SlingRepository Integration Tests #913
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.jcr.repository.it-jackrabbit-oak/913/
Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Sample Integration Tests #913
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.testing.samples.integrationtests/913/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #913
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/913/
Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Launchpad Base #913
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.base/913/
Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Models Integration Tests #913
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.models.integration-tests/913/
Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #913
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.discovery.impl/913/
Jenkins build is still unstable: sling-trunk-1.7 #913
See https://builds.apache.org/job/sling-trunk-1.7/changes
Re: [VOTE] Release Apache Sling Testing Resource Resolver Mock version 0.3.0
+1 Signatures check out fine. Robert On Thu, Sep 25, 2014 at 12:22 PM, Stefan Seifert sseif...@pro-vision.de wrote: Hi, We solved 4 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12326159 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1131/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1131 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. stefan p.s. this is my first apache sling release, hopefully PGP signing etc. is all correct.
RE: [VOTE] Release Apache Sling Testing Resource Resolver Mock version 0.3.0
+1 Best regards mike -Original Message- From: Stefan Seifert [mailto:sseif...@pro-vision.de] Sent: Thursday, September 25, 2014 11:23 AM To: dev@sling.apache.org Subject: [VOTE] Release Apache Sling Testing Resource Resolver Mock version 0.3.0 Hi, We solved 4 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12326159 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1131/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1131 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. stefan p.s. this is my first apache sling release, hopefully PGP signing etc. is all correct.
[RESULT] [VOTE] Release Sling JSP Taglib version 2.2.4
Hi, The vote has passed with the following result : +1 (binding): Carsten Ziegeler, Robert Munteanu, Dan Klco and Oliver Lietz +1 (non binding): I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository.
[jira] [Updated] (SLING-3974) Folders that contain two underscores in the name are not displayed
[ https://issues.apache.org/jira/browse/SLING-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3974: --- Fix Version/s: Sling Eclipse IDE 1.0.4 Folders that contain two underscores in the name are not displayed -- Key: SLING-3974 URL: https://issues.apache.org/jira/browse/SLING-3974 Project: Sling Issue Type: Bug Components: IDE Affects Versions: Sling Eclipse IDE 1.0.2 Environment: Windows, Eclipse Luna Reporter: JBodkin Fix For: Sling Eclipse IDE 1.0.4 The Sling Eclipse IDE plugin is unable to show folders which contain two underscores in the name. For example, these folders are not displayed upon refreshing the view when I create them in the location filesystem (.content.xml is contained inside) * _cq_template * _test_dialog -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-3974) Folders that contain two underscores in the name are not displayed
[ https://issues.apache.org/jira/browse/SLING-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147787#comment-14147787 ] Robert Munteanu commented on SLING-3974: [~JBodkin] - thanks for the report. Just to confirm, this is about the Content Navigator view we contrbiute, not about the 'regular' file/folder view from Eclipse, right? Folders that contain two underscores in the name are not displayed -- Key: SLING-3974 URL: https://issues.apache.org/jira/browse/SLING-3974 Project: Sling Issue Type: Bug Components: IDE Affects Versions: Sling Eclipse IDE 1.0.2 Environment: Windows, Eclipse Luna Reporter: JBodkin Fix For: Sling Eclipse IDE 1.0.4 The Sling Eclipse IDE plugin is unable to show folders which contain two underscores in the name. For example, these folders are not displayed upon refreshing the view when I create them in the location filesystem (.content.xml is contained inside) * _cq_template * _test_dialog -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [PROPOSAL] Sightly donation to Apache Sling
Hi Carsten, I realised that I only half-answered your question. Ideally the TCK should be ready in 2, max. 3 weeks. As soon as we manage to push it to Maven Central it should be ready to be consumed in Sling. In parallel I'm working on a Sling bundle that should contain the TCK input scripts and a content structure that would allow running them as expected by the TCK such that we can test the Sling implementation. HTH, Radu On Tue, Sep 23, 2014 at 10:13 AM, Radu Cotescu r...@apache.org wrote: Hi Carsten, The specification will be available soon on GitHub [2] (matter of days). Until then the resource from [0] should give you an idea on how Sightly expressions look like and what plugins are available. Regards, Radu [2] - https://github.com/Adobe-Marketing-Cloud On Tue, Sep 23, 2014 at 7:07 AM, Carsten Ziegeler cziege...@apache.org wrote: Hi Radu, thanks for the offering. This definitely looks very interesting for Sling. Is the spec downloadable from somewhere? When do you think the test suite will be available? Regards Carsten 2014-09-22 10:59 GMT+02:00 Radu Cotescu r...@apache.org: Hello, On behalf of Adobe Systems Inc. I'd like to contribute two modules to Apache Sling: - org.apache.sling.scripting.sightly - org.apache.sling.xss Sightly is the new web templating language shipped with Adobe Experience Manager 6.0 [0]. Our contribution to Apache Sling is a Java-based implementation, fully compliant with the language's specification. However, the language's specification is and will be owned by Adobe. For Sightly's contextual-based automated XSS escaping feature we're also donating the org.apache.sling.xss bundle that provides two useful services meant to help escaping or filtering user-submitted content that might be prone to XSS attacks. While the XSS module contains a decent amount of unit tests, the Sightly implementation was tested using a proprietary (for now) UI testing framework. I'm currently working on porting those tests into a test runner that will be made available under an Apache License on Maven Central; this runner could easily be integrated into Sightly's build process in the near future. SLING-3959 [1] has been opened to track the donation progress and the bundles are attached there. If the Sling community finds this donation interesting we can carry on with the IP clearance. Thanks, Radu *Sightly Credits:* Senol Tas, Honwai Wong - initial language specification and implementation Gabriel Walt - product manager, language specification Marius Dănilă, Radu Cotescu, Sameer Charles - Java implementation and JavaScript Use-API support Cătălin Buzoiu - engineering manager Feike Visser, Florin Iordache - early adopters implementing projects with Sightly, who provided valuable feedback during Sightly's development process [0] - http://docs.adobe.com/content/docs/en/aem/6-0/develop/sightly.html [1] - *https://issues.apache.org/jira/browse/SLING-3959 https://issues.apache.org/jira/browse/SLING-3959* -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: Should we remove openid from Sling's launchpad?
On Wednesday 24 September 2014 16:03:28 Antonio Sanso wrote: On Sep 24, 2014, at 1:51 PM, Oliver Lietz apa...@oliverlietz.de wrote: On Wednesday 24 September 2014 11:13:59 Carsten Ziegeler wrote: Our launchpad currently contains openid support - which is old/not recommended to be used anymore. And maybe the implementation is also broken... So I think we should not have this in Sling-7 WDYT? +1 +1 for removing broken stuff, but we should come up with an alternative. Maybe Antonio can step in and help with OpenID Connect which he started in 2013 (I already did an update in my whiteboard space back in April to make it at least compile). I wish to. The thing that made me stop working on it is that I am not “happy” with the current LoginModulePlugin approach (since is not ideal). It would be really nice to finally tackle https://issues.apache.org/jira/browse/SLING-2623 that I consider a blocker if we really want to have something as OAuth or OpenIdConnect (or any form of third party authentication…) I have skimmend through SLING-2623... our latest org.apache.sling.jcr.jackrabbit.server bundle already exports all packages from embedded Jackrabbit 2.6.5. The Auth XING modules in contrib do third party authentication but require repository users - would be cool to (optionally) get rid of them. And we need to touch authentication anyway when switching to Oak, no? So let's tackle it. O. regards antonio O. Carsten
Re: [VOTE] Release Apache Sling Testing Resource Resolver Mock version 0.3.0
+1 2014-09-25 16:01 GMT+02:00 Mike Müller mike...@mysign.ch: +1 Best regards mike -Original Message- From: Stefan Seifert [mailto:sseif...@pro-vision.de] Sent: Thursday, September 25, 2014 11:23 AM To: dev@sling.apache.org Subject: [VOTE] Release Apache Sling Testing Resource Resolver Mock version 0.3.0 Hi, We solved 4 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12326159 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1131/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 1131 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. stefan p.s. this is my first apache sling release, hopefully PGP signing etc. is all correct. -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: [RT] Concistent model to describe an installation
I've talked with Bertrand yesterday during the adaptto and we agreed to use
the model approach and we also agreed on using YAML. I'll update the
current implementation and then we can discuss the details.
Carsten
2014-09-23 22:08 GMT+02:00 Carsten Ziegeler cziege...@apache.org:
Maybe I try to explain the basics of my idea again :)
Right now, we have the launchpad which is configured in many different
files, it's maven based and produces a runnable jar and a web application.
My primary goal is to have the possibility to define a single file
containing all the information.
The second goal is to split this description into different functional
parts, and the final result is aggregated by this.
And then, this description can be used by various tooling - so we can
still built a maven plugin on top of it that produces our launchpad. But we
can also build crankstart on top of it. But the same description file can
be used.
I hope this brief summary makes more sense :)
Now, in this sense, the model should be complete to get a runnable
installation. Therefore variables which are fed by environment variables
are not part of it. Of course you could simply specify such a variable in
the model, crankstart would work but the launchpad plugin would create
something unusable as actual values would be missing.
I'm also not sure, if explicit variables, like ENV:{mongodb.url} is the
way to go - this limits the control to very specific parts - namely only
those where such a variable is used. However, if no value is specified
there is no default value and if you want to override a different
configuration settings, you can't.
But I think that's an additional topic we should discuss. I would like to
talk about the first one first :)
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
[jira] [Commented] (SLING-3944) org.apache.sling.scripting.java bundle exports javax.inject package in wrong version
[ https://issues.apache.org/jira/browse/SLING-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147832#comment-14147832 ] Carsten Ziegeler commented on SLING-3944: - [~olli] I assume this can be set to resolved? org.apache.sling.scripting.java bundle exports javax.inject package in wrong version Key: SLING-3944 URL: https://issues.apache.org/jira/browse/SLING-3944 Project: Sling Issue Type: Bug Components: Scripting Affects Versions: Scripting Java 2.0.10 Reporter: Markus Haack Assignee: Oliver Lietz Priority: Critical Fix For: Scripting Java 2.0.12 The org.apache.sling.scripting.java bundle exports the package javax.inject in the version of the bundle, which is wrong and should be fixed. This can lead to bundle version problems for other bundles which depend on javax.inject in version [1.0,2) - the correct version (like Jersey Web Services libraries). Either export javax.inject with version 0.0.0 or even better with the correct version 1.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
RE: [PROPOSAL] Sightly donation to Apache Sling
a big +1 from my side, i'm very happy to see the sightly implementation becoming open source. some detail questions on the process: - i've had only a brief look at the sources, but if i understand correctly the org.apache.sling.scripting.sightly.zip/engine bundle contains both the sightly language implementation itself, as well as the integration with sling and the sling-specific sightly extensions (e.g. support for data-sly-resource). - would it not be better to separate this into different bundles - one for the language itself and one for the sling-specific extensions? - i've not seen the specification of sightly yet - does it contain the sling-specific extensions as well, or is it partitioned this way? - this would be the first time that the sling project does not only host the script language integration, but the script language implementation itself. are we as sling community prepared for it, and the best host for it? i do not want to put any stones in the way with this question, just to get the opinion of the community. stefan -Original Message- From: Radu Cotescu [mailto:r...@apache.org] Sent: Monday, September 22, 2014 11:00 AM To: Sling Dev Subject: [PROPOSAL] Sightly donation to Apache Sling Hello, On behalf of Adobe Systems Inc. I'd like to contribute two modules to Apache Sling: - org.apache.sling.scripting.sightly - org.apache.sling.xss Sightly is the new web templating language shipped with Adobe Experience Manager 6.0 [0]. Our contribution to Apache Sling is a Java-based implementation, fully compliant with the language's specification. However, the language's specification is and will be owned by Adobe. For Sightly's contextual-based automated XSS escaping feature we're also donating the org.apache.sling.xss bundle that provides two useful services meant to help escaping or filtering user-submitted content that might be prone to XSS attacks. While the XSS module contains a decent amount of unit tests, the Sightly implementation was tested using a proprietary (for now) UI testing framework. I'm currently working on porting those tests into a test runner that will be made available under an Apache License on Maven Central; this runner could easily be integrated into Sightly's build process in the near future. SLING-3959 [1] has been opened to track the donation progress and the bundles are attached there. If the Sling community finds this donation interesting we can carry on with the IP clearance. Thanks, Radu *Sightly Credits:* Senol Tas, Honwai Wong - initial language specification and implementation Gabriel Walt - product manager, language specification Marius Dănilă, Radu Cotescu, Sameer Charles - Java implementation and JavaScript Use-API support Cătălin Buzoiu - engineering manager Feike Visser, Florin Iordache - early adopters implementing projects with Sightly, who provided valuable feedback during Sightly's development process [0] - http://docs.adobe.com/content/docs/en/aem/6-0/develop/sightly.html [1] - *https://issues.apache.org/jira/browse/SLING-3959 https://issues.apache.org/jira/browse/SLING-3959*
Re: [PROPOSAL] Sightly donation to Apache Sling
Hi Stefan, On Thu, Sep 25, 2014 at 5:11 PM, Stefan Seifert sseif...@pro-vision.de wrote: ...this would be the first time that the sling project does not only host the script language integration, but the script language implementation itself. are we as sling community prepared for it, and the best host for it?... I haven't seen people interested in Sightly outside of the Sling/AEM community so far, so Sling sounds like the right community to host it for now. If Sightly grows its own community which is distinct from the Sling one over time, it can always move elsewhere later. -Bertrand
[jira] [Commented] (SLING-3575) upgrade Jackrabbit to 2.6.5
[ https://issues.apache.org/jira/browse/SLING-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147861#comment-14147861 ] Oliver Lietz commented on SLING-3575: - We still need to fix the test (SLING-897) for Oak and Jackrabbit 2.6.5. I had a short chat with [~mduerig], but I need to investigate further what fails here. upgrade Jackrabbit to 2.6.5 --- Key: SLING-3575 URL: https://issues.apache.org/jira/browse/SLING-3575 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR Jackrabbit Server 2.1.2 Reporter: Oliver Lietz Assignee: Oliver Lietz Fix For: JCR Jackrabbit Server 2.2.0 upgrade the embedded jackrabbit-core to 2.6.5 and lucene-core to 3.6.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-3944) org.apache.sling.scripting.java bundle exports javax.inject package in wrong version
[ https://issues.apache.org/jira/browse/SLING-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147863#comment-14147863 ] Oliver Lietz commented on SLING-3944: - Yes. I can do a new release tomorrow. org.apache.sling.scripting.java bundle exports javax.inject package in wrong version Key: SLING-3944 URL: https://issues.apache.org/jira/browse/SLING-3944 Project: Sling Issue Type: Bug Components: Scripting Affects Versions: Scripting Java 2.0.10 Reporter: Markus Haack Assignee: Oliver Lietz Priority: Critical Fix For: Scripting Java 2.0.12 The org.apache.sling.scripting.java bundle exports the package javax.inject in the version of the bundle, which is wrong and should be fixed. This can lead to bundle version problems for other bundles which depend on javax.inject in version [1.0,2) - the correct version (like Jersey Web Services libraries). Either export javax.inject with version 0.0.0 or even better with the correct version 1.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLING-3944) org.apache.sling.scripting.java bundle exports javax.inject package in wrong version
[ https://issues.apache.org/jira/browse/SLING-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-3944. - Resolution: Fixed r1625675 org.apache.sling.scripting.java bundle exports javax.inject package in wrong version Key: SLING-3944 URL: https://issues.apache.org/jira/browse/SLING-3944 Project: Sling Issue Type: Bug Components: Scripting Affects Versions: Scripting Java 2.0.10 Reporter: Markus Haack Assignee: Oliver Lietz Priority: Critical Fix For: Scripting Java 2.0.12 The org.apache.sling.scripting.java bundle exports the package javax.inject in the version of the bundle, which is wrong and should be fixed. This can lead to bundle version problems for other bundles which depend on javax.inject in version [1.0,2) - the correct version (like Jersey Web Services libraries). Either export javax.inject with version 0.0.0 or even better with the correct version 1.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jenkins build became unstable: sling-trunk-1.8 » Apache Sling Launchpad Base #204
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.launchpad.base/204/
Jenkins build is still unstable: sling-trunk-1.8 » Apache Sling Launchpad Testing #204
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.launchpad.testing/204/
Jenkins build is still unstable: sling-trunk-1.8 #204
See https://builds.apache.org/job/sling-trunk-1.8/changes
Jenkins build is back to stable : sling-contrib-1.6 » Apache Sling Replication Integration Tests #1269
See https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.it/1269/
How to use sling.servlet.resourceTypes
I am trying to map the sling.servlet.resourceTypes, so that the URL
requests can be handled by Spring MVC that is running inside Sling
container.
With the following Sling property 'sling.servlet.resourceTypes', sling not
able to map the request.
1. URL:
http://localhost:8080/content/slingspring/person/new
2. osgi:service-properties
entry key=sling.servlet.resourceTypes value=slingspring/person
/
entry key=sling.servlet.extensions
array
valuejson/value
valuehtml/value
valuejsp/value
/array
/entry
entry key=sling.servlet.methods
array
valueGET/value
valuePOST/value
/array
/entry
3.
Spring MVC is running inside Sling container:
@RequestMapping(value = /content/slingspring/person/new, method =
RequestMethod.GET)
public String showForm(ServletResponse servletResponse,
SlingHttpServletRequest slingRequest,
ResourceResolver resourceResolver) {
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2541
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2541/
Jenkins build is still unstable: sling-trunk-1.6 #2541
See https://builds.apache.org/job/sling-trunk-1.6/changes
Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Sample Integration Tests #914
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.testing.samples.integrationtests/914/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #914
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/914/
Jenkins build became unstable: sling-trunk-1.7 » Apache Sling SlingRepository Integration Tests #914
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.jcr.repository.it-jackrabbit-oak/914/
Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Launchpad Base #914
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.base/914/
Jenkins build is still unstable: sling-trunk-1.7 #914
See https://builds.apache.org/job/sling-trunk-1.7/changes
Jenkins build became unstable: sling-trunk-1.8 » Apache Sling Event Support #205
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/205/
Jenkins build is still unstable: sling-trunk-1.8 » Apache Sling Launchpad Testing #205
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.launchpad.testing/205/
Jenkins build is back to stable : sling-trunk-1.8 » Apache Sling Launchpad Base #205
See https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.launchpad.base/205/
Jenkins build is still unstable: sling-trunk-1.8 #205
See https://builds.apache.org/job/sling-trunk-1.8/changes
Jenkins build is still unstable: sling-trunk-1.7 #915
See https://builds.apache.org/job/sling-trunk-1.7/changes
Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Sample Integration Tests #915
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.testing.samples.integrationtests/915/
Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Models Integration Tests #915
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.models.integration-tests/915/
Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling SlingRepository Integration Tests #915
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.jcr.repository.it-jackrabbit-oak/915/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #915
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/915/
Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Base #915
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.base/915/
Re: How to use sling.servlet.resourceTypes
On 25.09.2014, at 08:48, Reetu reetu...@gmail.com wrote: I am trying to map the sling.servlet.resourceTypes, so that the URL requests can be handled by Spring MVC that is running inside Sling container. Why do you want to do that? I strongly assume this will create just more problems in the long term, if you have 2 very different frameworks fight over control. It might make sense if you need to integrate some existing code, but then I would try to embed the existing spring webapp via a bundle and keep the URLs between spring and sling separate. See also [1]. But for new stuff, use either sling or spring (and I'd argue for Sling :-)), but not both together. [1] http://dev.day.com/content/ddc/blog/2008/05/slingspringspling.html Cheers, Alex
Jenkins build is still unstable: sling-trunk-1.6 #2542
See https://builds.apache.org/job/sling-trunk-1.6/changes
Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2542
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2542/
[jira] [Closed] (SLING-3958) EL Function Name Mismatch
[ https://issues.apache.org/jira/browse/SLING-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Klco closed SLING-3958. --- EL Function Name Mismatch - Key: SLING-3958 URL: https://issues.apache.org/jira/browse/SLING-3958 Project: Sling Issue Type: Bug Components: Scripting Affects Versions: Scripting JSP-Taglib 2.2.2 Reporter: Dan Klco Assignee: Dan Klco Fix For: Scripting JSP-Taglib 2.2.4 The EL function 'encode' has a naming mismatch between the function name given in the TLD (encode) and the actual method name (escape) in the SlingFunctions class. This was missed due to there only being a unit test for this function, not an integration test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
