Re: [VOTE] Apache Sling Launchpad Base 2.5.0 and Apache Sling Scripting Console 1.0.0
Apologies, I should have guessed that. - the .s the staged artifacts check out ok, So I'm +1 Ian On 4 March 2013 17:53, Carsten Ziegeler cziege...@apache.org wrote: Ups, nice typo... Correct url is, without the dots: https://repository.apache.org/content/repositories/orgapachesling-309 Regards Carsten 2013/3/3 Ian Boston i...@tfd.co.uk: Hi, At the moment I get The server has not found anything matching the request URI You can get technical details here. Please continue your visit at our home page. When I go to: https://repository.apache.org/content/repositories/orgapachesling-3.0.9/ In principal I am +1 but I would like to check out the release. Is the URL correct ? Ian On 4 March 2013 04:31, Carsten Ziegeler cziege...@apache.org wrote: Anyone else? 2013/3/1 Felix Meschberger fmesc...@adobe.com: +1 Regards Felix Am 27.02.2013 um 11:28 schrieb Carsten Ziegeler: Hi, this vote is about a long outstanding release of launchpad base and a new module, the scripting console So please vote for: Launchpad Base 2.5.0 https://issues.apache.org/jira/browse/SLING/fixforversion/12321244 Scripting Console 1.0.0 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-3.0.9/ 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 3.0.9 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This vote will be open for 72 hours. Regards Carsten -- Carsten Ziegeler cziege...@apache.org -- Felix Meschberger | Principal Scientist | Adobe -- Carsten Ziegeler cziege...@apache.org -- Carsten Ziegeler cziege...@apache.org
[VOTE RESULT] Apache Sling Launchpad Base 2.5.0 and Apache Sling Scripting Console 1.0.0
The vote for Apache Sling Launchpad Base 2.5.0 and Apache Sling Scripting Console 1.0.0 passed with four binding +1 votes from Ian Boston, Mike Müller, Felix Meschberger, and Carsten Ziegeler - no other votes have been cast I'll continue with the release process Thanks everyone for voting Regards Carsten -- Carsten Ziegeler cziege...@apache.org
[jira] [Created] (SLING-2768) Broken link in launchpad-base's pom.xml
Lukas Eder created SLING-2768: - Summary: Broken link in launchpad-base's pom.xml Key: SLING-2768 URL: https://issues.apache.org/jira/browse/SLING-2768 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Base 2.5.0 Reporter: Lukas Eder Priority: Trivial Attachments: sling-launchpad-base-pom.xml.patch The pom.xml of the Launchpad Base project references an obsolete Wiki page. Please see the attached patch for a fix -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2768) Broken link in launchpad-base's pom.xml
[ https://issues.apache.org/jira/browse/SLING-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Eder updated SLING-2768: -- Attachment: sling-launchpad-base-pom.xml.patch Broken link in launchpad-base's pom.xml --- Key: SLING-2768 URL: https://issues.apache.org/jira/browse/SLING-2768 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Base 2.5.0 Reporter: Lukas Eder Priority: Trivial Attachments: sling-launchpad-base-pom.xml.patch The pom.xml of the Launchpad Base project references an obsolete Wiki page. Please see the attached patch for a fix -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Monitoring and Statistics
Hi, On Fri, Mar 1, 2013 at 9:12 PM, Ian Boston i...@tfd.co.uk wrote: ...I am not really certain of the value of this work any more, so I am not going to do anything further, unless there is a strong demand Note that FELIX-3152 provides jmx extensions for the Felix web console - for some reason that hasn't been committed yet, but I just tested it and it works with the Sling trunk and does provide some JMX-to-json conversion, dunno if that would work for your needs. -Bertrand
[jira] [Resolved] (SLING-2768) Broken link in launchpad-base's pom.xml
[ https://issues.apache.org/jira/browse/SLING-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-2768. Resolution: Fixed Assignee: Bertrand Delacretaz The canonical documentation page is actually http://sling.apache.org/site/the-sling-launchpad.html now, I have fixed this in revision 1452225, thanks very much for spotting this error! Broken link in launchpad-base's pom.xml --- Key: SLING-2768 URL: https://issues.apache.org/jira/browse/SLING-2768 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Base 2.5.0 Reporter: Lukas Eder Assignee: Bertrand Delacretaz Priority: Trivial Attachments: sling-launchpad-base-pom.xml.patch The pom.xml of the Launchpad Base project references an obsolete Wiki page. Please see the attached patch for a fix -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2768) Broken link in launchpad-base's pom.xml
[ https://issues.apache.org/jira/browse/SLING-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-2768: --- Fix Version/s: Launchpad Base 2.5.2 Broken link in launchpad-base's pom.xml --- Key: SLING-2768 URL: https://issues.apache.org/jira/browse/SLING-2768 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Base 2.5.0 Reporter: Lukas Eder Assignee: Bertrand Delacretaz Priority: Trivial Fix For: Launchpad Base 2.5.2 Attachments: sling-launchpad-base-pom.xml.patch The pom.xml of the Launchpad Base project references an obsolete Wiki page. Please see the attached patch for a fix -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2768) Broken link in launchpad-base's pom.xml
[ https://issues.apache.org/jira/browse/SLING-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13592091#comment-13592091 ] Lukas Eder commented on SLING-2768: --- Yes, you're right. I've noticed that there were static and wiki pages, containing similar content. Thanks for fixing this Broken link in launchpad-base's pom.xml --- Key: SLING-2768 URL: https://issues.apache.org/jira/browse/SLING-2768 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Base 2.5.0 Reporter: Lukas Eder Assignee: Bertrand Delacretaz Priority: Trivial Fix For: Launchpad Base 2.5.2 Attachments: sling-launchpad-base-pom.xml.patch The pom.xml of the Launchpad Base project references an obsolete Wiki page. Please see the attached patch for a fix -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Monitoring and Statistics
On 4 March 2013 20:44, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, On Fri, Mar 1, 2013 at 9:12 PM, Ian Boston i...@tfd.co.uk wrote: ...I am not really certain of the value of this work any more, so I am not going to do anything further, unless there is a strong demand Note that FELIX-3152 provides jmx extensions for the Felix web console - for some reason that hasn't been committed yet, but I just tested it and it works with the Sling trunk and does provide some JMX-to-json conversion, dunno if that would work for your needs. Looks like it will, and it supports a large number of OpenTypes. I assume it will make it into a Felix release at some point. Ian -Bertrand
Build failed in Jenkins: sling-trunk-1.6 #1585
See https://builds.apache.org/job/sling-trunk-1.6/1585/ -- Failed to access build log hudson.util.IOException2: remote file operation failed: /home/hudson/hudson-slave/workspace/sling-trunk-1.6 at hudson.remoting.Channel@1a41ef78:ubuntu2 at hudson.FilePath.act(FilePath.java:861) at hudson.FilePath.act(FilePath.java:838) at hudson.FilePath.toURI(FilePath.java:966) at hudson.tasks.MailSender.createFailureMail(MailSender.java:279) at hudson.tasks.MailSender.getMail(MailSender.java:154) at hudson.tasks.MailSender.execute(MailSender.java:100) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.cleanUp(MavenModuleSetBuild.java:964) at hudson.model.Run.execute(Run.java:1613) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:494) at hudson.remoting.Request.call(Request.java:129) at hudson.remoting.Channel.call(Channel.java:672) at hudson.FilePath.act(FilePath.java:854) ... 10 more Caused by: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Channel$CloseCommand.execute(Channel.java:850) at hudson.remoting.Channel$2.handle(Channel.java:435) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command close created at at hudson.remoting.Command.init(Command.java:56) at hudson.remoting.Channel$CloseCommand.init(Channel.java:844) at hudson.remoting.Channel$CloseCommand.init(Channel.java:842) at hudson.remoting.Channel.close(Channel.java:909) at hudson.remoting.Channel.close(Channel.java:892) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:849) ... 2 more
Upcoming Releases
Hi, I plan to cut new releases of some of our core bundles, including API, JCR Resource, Resource Resolver, Engine, and Servlet Resolver. Looking at the list of open issues I think there aren't any urgend things to add to these releases, so I would just move open issues to the next version. However, if you think that something really needs to go into one of those modules, now is the time to work on this :) Regards Carsten -- Carsten Ziegeler cziege...@apache.org
[jira] [Created] (SLING-2769) Broken sample: post-servlet-extensions
Lukas Eder created SLING-2769: - Summary: 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 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SLING-2211) Potential infinite loop in the :copy operation of the POST servlet
[ https://issues.apache.org/jira/browse/SLING-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-2211. Resolution: Duplicate Assignee: Bertrand Delacretaz This has been fixed in SLING-2517, the above requests fail with javax.jcr.RepositoryException: Cannot copy ancestor /foo to descendant /foo Potential infinite loop in the :copy operation of the POST servlet -- Key: SLING-2211 URL: https://issues.apache.org/jira/browse/SLING-2211 Project: Sling Issue Type: Bug Components: Servlets Affects Versions: Servlets Post 2.0.2, Servlets Post 2.0.4, Servlets Post 2.1.0 Reporter: Jukka Zitting Assignee: Bertrand Delacretaz The following puts Sling into a loop that will only end when an OutOfMemoryError is caused by a too large transient space: $ curl -u admin:admin -F x=y http://localhost:8080/foo $ curl -u admin:admin -F :operation=copy -F :dest=/foo/bar http://localhost:8080/foo The solution would be to either fail early with such recursive copies or to use the JCR Workspace.copy() operation or a similar mechanism that copies only previously persisted content, so that the recursion within the transient space is avoided. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SLING-81) Add write-support to Javascript API for JCR
[
https://issues.apache.org/jira/browse/SLING-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-81.
--
Resolution: Won't Fix
As we haven't touched this for a while, closing won't fix. We'll reopen if
needed.
Add write-support to Javascript API for JCR
---
Key: SLING-81
URL: https://issues.apache.org/jira/browse/SLING-81
Project: Sling
Issue Type: Sub-task
Components: Servlets
Reporter: Lars Trieloff
The current Javascript API is good at reading data from the repository, but
has not yet a working implementation of assignments like
node.mimetype = text/plain a.k.a node[mimetype] = text/plain
node[members] = [bertrand, lars];
node[childnode] = {mimetype: text/plain, text: bla bla bla}
The first example should call node.setProperty(mimetype, text/plain);
The second example should call node.setProperty(members, new String[]
{bertrand, lars});
The third example should either set the properties of the child node
childnode or of the node referenced in a property called childnode.
This should also allow for nesting of properties,
node[childnode] = {mimetype: text/plain, text: bla bla bla,
childnode: {mimetype : text/plain }}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SLING-292) µjax Post Servlet does not use correct HTTP status codes
[ https://issues.apache.org/jira/browse/SLING-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-292. --- Resolution: Won't Fix µjax Post Servlet is long gone, marking won't fix. µjax Post Servlet does not use correct HTTP status codes Key: SLING-292 URL: https://issues.apache.org/jira/browse/SLING-292 Project: Sling Issue Type: Bug Components: Servlets Reporter: Lars Trieloff The µjax Post Servlet does not use correct HTTP status codes when trying to write nodes without permissions. Expected status code is 403 (forbidden), if no user is logged in (no credentials in the request), status code 401 might be more appropriate -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SLING-592) add SNS (Same Name Siblings) support
[ https://issues.apache.org/jira/browse/SLING-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-592. --- Resolution: Won't Fix Marking won't fix - we want to discourage use of same-name siblings, and this hasn't been touched in quite a while. add SNS (Same Name Siblings) support Key: SLING-592 URL: https://issues.apache.org/jira/browse/SLING-592 Project: Sling Issue Type: Improvement Components: Servlets Reporter: Oliver Lietz support SNS to simplify adding content without a single unique (meaningful) property -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SLING-258) ujax.js should define useful constants
[ https://issues.apache.org/jira/browse/SLING-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-258. --- Resolution: Won't Fix ujax.js is long gone, marking won't fix ujax.js should define useful constants -- Key: SLING-258 URL: https://issues.apache.org/jira/browse/SLING-258 Project: Sling Issue Type: Improvement Components: Servlets Reporter: Bertrand Delacretaz Priority: Minor Constants like ujax:delete which can be useful in javascript code should be defined in ujax.js -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SLING-2532) sendRedirect in the SlingAllMethodsServlet doesn't work properly
[
https://issues.apache.org/jira/browse/SLING-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-2532.
Resolution: Won't Fix
Resolving won't fix, this is more a question for the users list than a Sling
issue.
sendRedirect in the SlingAllMethodsServlet doesn't work properly
Key: SLING-2532
URL: https://issues.apache.org/jira/browse/SLING-2532
Project: Sling
Issue Type: Bug
Components: Servlets
Environment: Windows 7, Sling 6
Reporter: Chris Papademos
Labels: logout, redirect, sendRedirect, servlet
Im trying to enable the user to delete his own account by sending a get
Request to /satlab/user/delete.
First Im trying to log him out, by sending a redirect to
/system/sling.logout.html
I also tried:
Session session = request.getResourceResolver().adaptTo(Session.class);
session.logout();
but this doesnt seem to work. Am I doing something wrong? Or is that a bug?
@Override
protected void doGet(SlingHttpServletRequest request,
SlingHttpServletResponse response) throws
ServletException,
IOException {
response.sendRedirect(/system/sling/logout.html);
String userID = request.getParameter(userID);
System.out.println(userID);
UserUtility.removePrivateFolder(userID);
UserUtility.removeUser(userID);
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (SLING-2769) Broken sample: post-servlet-extensions
[ https://issues.apache.org/jira/browse/SLING-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz reassigned SLING-2769: -- Assignee: Bertrand Delacretaz 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SLING-2769) Broken sample: post-servlet-extensions
[ https://issues.apache.org/jira/browse/SLING-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-2769. Resolution: Fixed Fixed in revision 1452252, the bundle now starts on Sling launchpad 6. Note that this wouldn't be needed for trunk as the org.apache.sling.jcr.jcr-wrapper bundle exports javax.jcr,version=1.1.0 Building Sling from trunk should work, if not please give us more details about what fails. 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [Adapter] Make AdapterManager.getAdapter transitive operation
On 03.03.2013, at 00:05, Miroslav Smiljanic smmiros...@gmail.com wrote: Currently if A adapts to [B, D], and B adapts to [C], adapter manager will not adapt A to C even if it is potentially possible. AdapterManager.getAdapter method has to be called twice. I have done some code modifications and made operation transitive. Do you think that it would be worth to add this new capability to AdapterManagerImpl? That sounds like a bit too much magic to me, I think it's better if devs are forced to explicitly adapt things one at a time Do you have a use case? Cheers, Alex
[jira] [Commented] (SLING-2769) Broken sample: post-servlet-extensions
[ https://issues.apache.org/jira/browse/SLING-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13592129#comment-13592129 ] Lukas Eder commented on SLING-2769: --- Great, thanks for fixing the OSGi import. I'll create a new issue for the failing trunk build, with more info... 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (SLING-2770) Building Launchpad from trunk fails due to unresolvable SNAPSHOT dependencies
Lukas Eder created SLING-2770: - Summary: Building Launchpad from trunk fails due to unresolvable SNAPSHOT dependencies Key: SLING-2770 URL: https://issues.apache.org/jira/browse/SLING-2770 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Reporter: Lukas Eder Building Launchpad from trunk fails as there seem to be some SNAPSHOT versions missing from the Apache snapshot repositories. Below is the output from a mvn install command (-X -e output attached in a file): SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Apache Sling Launchpad Application Builder 7-SNAPSHOT [INFO] [WARNING] The POM for org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.servlets.resolver:jar:2.2.3-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.jcr.resource:jar:2.2.5-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.scripting.jsp:jar:2.0.27-SNAPSHOT is missing, no dependency information available [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.804s [INFO] Finished at: Mon Mar 04 12:21:02 CET 2013 [INFO] Final Memory: 10M/81M [INFO] [ERROR] Failed to execute goal on project org.apache.sling.launchpad: Could not resolve dependencies for project org.apache.sling:org.apache.sling.launchpad:war:7-SNAPSHOT: The following artifacts could not be resolved: org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT, org.apache.sling:org.apache.sling.servlets.resolver:jar:2.2.3-SNAPSHOT, org.apache.sling:org.apache.sling.jcr.resource:jar:2.2.5-SNAPSHOT, org.apache.sling:org.apache.sling.scripting.jsp:jar:2.0.27-SNAPSHOT: Failure to find org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT in http://repository.apache.org/snapshots was cached in the local repository, resolution will not be reattempted until the update interval of apache.snapshots has elapsed or updates are forced - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2770) Building Launchpad from trunk fails due to unresolvable SNAPSHOT dependencies
[ https://issues.apache.org/jira/browse/SLING-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Eder updated SLING-2770: -- Attachment: mvn-install-X-e.txt Maven debug and error output Building Launchpad from trunk fails due to unresolvable SNAPSHOT dependencies - Key: SLING-2770 URL: https://issues.apache.org/jira/browse/SLING-2770 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Reporter: Lukas Eder Attachments: mvn-install-X-e.txt Building Launchpad from trunk fails as there seem to be some SNAPSHOT versions missing from the Apache snapshot repositories. Below is the output from a mvn install command (-X -e output attached in a file): SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Apache Sling Launchpad Application Builder 7-SNAPSHOT [INFO] [WARNING] The POM for org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.servlets.resolver:jar:2.2.3-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.jcr.resource:jar:2.2.5-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.scripting.jsp:jar:2.0.27-SNAPSHOT is missing, no dependency information available [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.804s [INFO] Finished at: Mon Mar 04 12:21:02 CET 2013 [INFO] Final Memory: 10M/81M [INFO] [ERROR] Failed to execute goal on project org.apache.sling.launchpad: Could not resolve dependencies for project org.apache.sling:org.apache.sling.launchpad:war:7-SNAPSHOT: The following artifacts could not be resolved: org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT, org.apache.sling:org.apache.sling.servlets.resolver:jar:2.2.3-SNAPSHOT, org.apache.sling:org.apache.sling.jcr.resource:jar:2.2.5-SNAPSHOT, org.apache.sling:org.apache.sling.scripting.jsp:jar:2.0.27-SNAPSHOT: Failure to find org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT in http://repository.apache.org/snapshots was cached in the local repository, resolution will not be reattempted until the update interval of apache.snapshots has elapsed or updates are forced - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (SLING-2769) Broken sample: post-servlet-extensions
[ https://issues.apache.org/jira/browse/SLING-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13592129#comment-13592129 ] Lukas Eder edited comment on SLING-2769 at 3/4/13 11:24 AM: Great, thanks for fixing the OSGi import. I'll create a new issue for the failing trunk build, with more info... https://issues.apache.org/jira/browse/SLING-2770 was (Author: lukas.eder): Great, thanks for fixing the OSGi import. I'll create a new issue for the failing trunk build, with more info... 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2770) Building Launchpad from trunk fails due to unresolvable SNAPSHOT dependencies
[ https://issues.apache.org/jira/browse/SLING-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Eder updated SLING-2770: -- Attachment: mvn-install-X-e.txt Building Launchpad from trunk fails due to unresolvable SNAPSHOT dependencies - Key: SLING-2770 URL: https://issues.apache.org/jira/browse/SLING-2770 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Reporter: Lukas Eder Attachments: mvn-install-X-e.txt Building Launchpad from trunk fails as there seem to be some SNAPSHOT versions missing from the Apache snapshot repositories. Below is the output from a mvn install command (-X -e output attached in a file): SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Apache Sling Launchpad Application Builder 7-SNAPSHOT [INFO] [WARNING] The POM for org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.servlets.resolver:jar:2.2.3-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.jcr.resource:jar:2.2.5-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.scripting.jsp:jar:2.0.27-SNAPSHOT is missing, no dependency information available [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.804s [INFO] Finished at: Mon Mar 04 12:21:02 CET 2013 [INFO] Final Memory: 10M/81M [INFO] [ERROR] Failed to execute goal on project org.apache.sling.launchpad: Could not resolve dependencies for project org.apache.sling:org.apache.sling.launchpad:war:7-SNAPSHOT: The following artifacts could not be resolved: org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT, org.apache.sling:org.apache.sling.servlets.resolver:jar:2.2.3-SNAPSHOT, org.apache.sling:org.apache.sling.jcr.resource:jar:2.2.5-SNAPSHOT, org.apache.sling:org.apache.sling.scripting.jsp:jar:2.0.27-SNAPSHOT: Failure to find org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT in http://repository.apache.org/snapshots was cached in the local repository, resolution will not be reattempted until the update interval of apache.snapshots has elapsed or updates are forced - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SLING-2770) Building Launchpad from trunk fails due to unresolvable SNAPSHOT dependencies
[ https://issues.apache.org/jira/browse/SLING-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Eder updated SLING-2770: -- Attachment: (was: mvn-install-X-e.txt) Building Launchpad from trunk fails due to unresolvable SNAPSHOT dependencies - Key: SLING-2770 URL: https://issues.apache.org/jira/browse/SLING-2770 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Reporter: Lukas Eder Attachments: mvn-install-X-e.txt Building Launchpad from trunk fails as there seem to be some SNAPSHOT versions missing from the Apache snapshot repositories. Below is the output from a mvn install command (-X -e output attached in a file): SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Apache Sling Launchpad Application Builder 7-SNAPSHOT [INFO] [WARNING] The POM for org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.servlets.resolver:jar:2.2.3-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.jcr.resource:jar:2.2.5-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.scripting.jsp:jar:2.0.27-SNAPSHOT is missing, no dependency information available [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.804s [INFO] Finished at: Mon Mar 04 12:21:02 CET 2013 [INFO] Final Memory: 10M/81M [INFO] [ERROR] Failed to execute goal on project org.apache.sling.launchpad: Could not resolve dependencies for project org.apache.sling:org.apache.sling.launchpad:war:7-SNAPSHOT: The following artifacts could not be resolved: org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT, org.apache.sling:org.apache.sling.servlets.resolver:jar:2.2.3-SNAPSHOT, org.apache.sling:org.apache.sling.jcr.resource:jar:2.2.5-SNAPSHOT, org.apache.sling:org.apache.sling.scripting.jsp:jar:2.0.27-SNAPSHOT: Failure to find org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT in http://repository.apache.org/snapshots was cached in the local repository, resolution will not be reattempted until the update interval of apache.snapshots has elapsed or updates are forced - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Build on empty Maven local repo: launchpad-plugin does not find launchpad.base
Hi, After removing $HOME/.m2/repository/org/apache/sling, mvn install at the top of the sling codebase says: The project org.apache.sling:org.apache.sling.launchpad.testing:7-SNAPSHOT has 1 error [ERROR] Unresolveable build extension: Plugin org.apache.sling:maven-launchpad-plugin:2.1.2 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.sling:org.apache.sling.launchpad.base:jar:2.5.1-SNAPSHOT, org.apache.sling:org.apache.sling.launchpad.base:jar:app:2.5.1-SNAPSHOT: ... but the launchpad/testing dependency:tree correctly includes org.apache.sling:org.apache.sling.launchpad.base:jar:app:2.5.1-SNAPSHOT:compile Does the launchpad plugin dependency resolution happen before the actual build and cause this error? The workaround is to build launchpad/base manually first, but IMO the build should work on an empty local Maven repo. SLING-2770 look related but it's not the exact same problem. -Bertrand
[jira] [Commented] (SLING-2770) Building Launchpad from trunk fails due to unresolvable SNAPSHOT dependencies
[ https://issues.apache.org/jira/browse/SLING-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13592142#comment-13592142 ] Bertrand Delacretaz commented on SLING-2770: We should fix that of course, but in the meantime you might be able to work around this by building the corresponding modules manually first. All the Sling core modules are found in the bundles folder, and you can search names like org.apache.sling.resourceresolver in their pom.xml to find where which module is. Building Launchpad from trunk fails due to unresolvable SNAPSHOT dependencies - Key: SLING-2770 URL: https://issues.apache.org/jira/browse/SLING-2770 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Reporter: Lukas Eder Attachments: mvn-install-X-e.txt Building Launchpad from trunk fails as there seem to be some SNAPSHOT versions missing from the Apache snapshot repositories. Below is the output from a mvn install command (-X -e output attached in a file): SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Apache Sling Launchpad Application Builder 7-SNAPSHOT [INFO] [WARNING] The POM for org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.servlets.resolver:jar:2.2.3-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.jcr.resource:jar:2.2.5-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.scripting.jsp:jar:2.0.27-SNAPSHOT is missing, no dependency information available [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.804s [INFO] Finished at: Mon Mar 04 12:21:02 CET 2013 [INFO] Final Memory: 10M/81M [INFO] [ERROR] Failed to execute goal on project org.apache.sling.launchpad: Could not resolve dependencies for project org.apache.sling:org.apache.sling.launchpad:war:7-SNAPSHOT: The following artifacts could not be resolved: org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT, org.apache.sling:org.apache.sling.servlets.resolver:jar:2.2.3-SNAPSHOT, org.apache.sling:org.apache.sling.jcr.resource:jar:2.2.5-SNAPSHOT, org.apache.sling:org.apache.sling.scripting.jsp:jar:2.0.27-SNAPSHOT: Failure to find org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT in http://repository.apache.org/snapshots was cached in the local repository, resolution will not be reattempted until the update interval of apache.snapshots has elapsed or updates are forced - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [Adapter] Make AdapterManager.getAdapter transitive operation
Hi Am 04.03.2013 um 12:16 schrieb Alexander Klimetschek: On 03.03.2013, at 00:05, Miroslav Smiljanic smmiros...@gmail.com wrote: Currently if A adapts to [B, D], and B adapts to [C], adapter manager will not adapt A to C even if it is potentially possible. AdapterManager.getAdapter method has to be called twice. I have done some code modifications and made operation transitive. Do you think that it would be worth to add this new capability to AdapterManagerImpl? That sounds like a bit too much magic to me, I think it's better if devs are forced to explicitly adapt things one at a time Agreed. Regards Felix Do you have a use case? Cheers, Alex -- Felix Meschberger | Principal Scientist | Adobe
RE: Build on empty Maven local repo: launchpad-plugin does not find launchpad.base
Hi Bertrand, (snip) Does the launchpad plugin dependency resolution happen before the actual build and cause this error? The workaround is to build launchpad/base manually first, but IMO the build should work on an empty local Maven repo. SLING-2770 look related but it's not the exact same problem. -Bertrand Building plugin and non-plugin modules depending on each other in a reactor seems to be a weak point in Maven right now. It's not the exact same issue, but seems related MNG-1911: Building plugins with extensions in a reactor fails https://jira.codehaus.org/browse/MNG-1911 Robert
[jira] [Commented] (SLING-2770) Building Launchpad from trunk fails due to unresolvable SNAPSHOT dependencies
[ https://issues.apache.org/jira/browse/SLING-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13592148#comment-13592148 ] Lukas Eder commented on SLING-2770: --- You're right of course, that is one option. That way, I got the Launchpad Builder running. Did I maybe miss some Maven option that allows to trigger those depending builds automatically? Or is that going to be part of the fix? Anyway, thanks for your help! Building Launchpad from trunk fails due to unresolvable SNAPSHOT dependencies - Key: SLING-2770 URL: https://issues.apache.org/jira/browse/SLING-2770 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Reporter: Lukas Eder Attachments: mvn-install-X-e.txt Building Launchpad from trunk fails as there seem to be some SNAPSHOT versions missing from the Apache snapshot repositories. Below is the output from a mvn install command (-X -e output attached in a file): SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Apache Sling Launchpad Application Builder 7-SNAPSHOT [INFO] [WARNING] The POM for org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.servlets.resolver:jar:2.2.3-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.jcr.resource:jar:2.2.5-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.scripting.jsp:jar:2.0.27-SNAPSHOT is missing, no dependency information available [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.804s [INFO] Finished at: Mon Mar 04 12:21:02 CET 2013 [INFO] Final Memory: 10M/81M [INFO] [ERROR] Failed to execute goal on project org.apache.sling.launchpad: Could not resolve dependencies for project org.apache.sling:org.apache.sling.launchpad:war:7-SNAPSHOT: The following artifacts could not be resolved: org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT, org.apache.sling:org.apache.sling.servlets.resolver:jar:2.2.3-SNAPSHOT, org.apache.sling:org.apache.sling.jcr.resource:jar:2.2.5-SNAPSHOT, org.apache.sling:org.apache.sling.scripting.jsp:jar:2.0.27-SNAPSHOT: Failure to find org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT in http://repository.apache.org/snapshots was cached in the local repository, resolution will not be reattempted until the update interval of apache.snapshots has elapsed or updates are forced - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2770) Building Launchpad from trunk fails due to unresolvable SNAPSHOT dependencies
[ https://issues.apache.org/jira/browse/SLING-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13592149#comment-13592149 ] Bertrand Delacretaz commented on SLING-2770: Note also that I don't get the same errors if building against a local Maven repo that has no previous Sling stuff, the following works for me without anything special in my Maven settings.xml: cd top of the Sling source code tree mv $HOME/.m2/repository/org/apache/sling /tmp/keep-it-around cd launchpad/base/ mvn clean install cd - mvn clean install Having to build launchpad/base first shouldn't be needed, but I don't get the missing modules that you get. Tested on macosx with java version 1.6.0_37 and Apache Maven 3.0.3 Building Launchpad from trunk fails due to unresolvable SNAPSHOT dependencies - Key: SLING-2770 URL: https://issues.apache.org/jira/browse/SLING-2770 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Reporter: Lukas Eder Attachments: mvn-install-X-e.txt Building Launchpad from trunk fails as there seem to be some SNAPSHOT versions missing from the Apache snapshot repositories. Below is the output from a mvn install command (-X -e output attached in a file): SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Apache Sling Launchpad Application Builder 7-SNAPSHOT [INFO] [WARNING] The POM for org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.servlets.resolver:jar:2.2.3-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.jcr.resource:jar:2.2.5-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.scripting.jsp:jar:2.0.27-SNAPSHOT is missing, no dependency information available [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.804s [INFO] Finished at: Mon Mar 04 12:21:02 CET 2013 [INFO] Final Memory: 10M/81M [INFO] [ERROR] Failed to execute goal on project org.apache.sling.launchpad: Could not resolve dependencies for project org.apache.sling:org.apache.sling.launchpad:war:7-SNAPSHOT: The following artifacts could not be resolved: org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT, org.apache.sling:org.apache.sling.servlets.resolver:jar:2.2.3-SNAPSHOT, org.apache.sling:org.apache.sling.jcr.resource:jar:2.2.5-SNAPSHOT, org.apache.sling:org.apache.sling.scripting.jsp:jar:2.0.27-SNAPSHOT: Failure to find org.apache.sling:org.apache.sling.resourceresolver:jar:1.0.5-SNAPSHOT in http://repository.apache.org/snapshots was cached in the local repository, resolution will not be reattempted until the update interval of apache.snapshots has elapsed or updates are forced - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Resource Access Tags
Hi Dan
Am 03.03.2013 um 01:58 schrieb Dan Klco:
Felix,
I agree with the package naming. For the short name of the TLD, should it be
something like 'sling-resource' or something shorter, such as 'sr'?
Personally I lean towards the shorter option. WDYT?
Ah naming ;-)
sr sounds not too bad. I would have chose resource out of my belly. I agree
sling-resource is probably too long.
I'll create a patch for separating the Resource Access code into another
directory. Should it be created under:
http://svn.apache.org/repos/asf/sling/trunk/bundles/scripting/jsp-resource-taglib
or
http://svn.apache.org/repos/asf/sling/trunk/contrib/scripting/jsp-resource-taglib
I think we should promote these tags to be used and thus include them with the
launchpad release and thus place them into the bundles (and not contrib) area.
What do others think ?
Regards
Felix
Thanks,
Dan
-Original Message-
From: Felix Meschberger [mailto:fmesc...@adobe.com]
Sent: Tuesday, February 26, 2013 5:19 AM
To: dev@sling.apache.org
Subject: Re: Resource Access Tags
Hi,
Am 26.02.2013 um 05:04 schrieb Dan Klco:
Felix,
I like the idea of creating a separate Resource API tag library. I think
there's enough functionality there to justify it and it may or may not be
something needed for every Sling installation and would reduce the number of
dependencies in the core Taglib. What would be a good namespace for the
Resource API tags? 'sr' or 'resource'?
I would imagine that this would be a bundle like
o.a.s.scripting.jsp.taglib.resource. WDYT ?
Regards
Felix
Thanks,
Dan
-Original Message-
From: Felix Meschberger [mailto:fmesc...@adobe.com]
Sent: Monday, February 25, 2013 12:03 PM
To: dev@sling.apache.org
Subject: Re: Resource Access Tags
Hi Dan
Thank you very much. Glancing over it, this looks fine -- a deeper review is
welcome.
Yet, I wonder whether we should add those tags and EL functions to the
existing JSP taglib or whether we should create a Resource API specific tag
library ?
WDYT ?
Regards
Felix
Am 22.02.2013 um 14:26 schrieb Dan Klco:
All,
I've made some additional contributions around the resource access tags,
based on SLING-1500https://issues.apache.org/jira/browse/SLING-1500, which
had some nice features including:
* New FindResources tag, for invoking the
resourceResolver.findResources functionality
* Updated: GetResources tag, adds the ability to specify a base
resource under which to retrieve a relative resource
* New EL function adaptTo: adding the ability to adapt adaptables in
EL functions
* New EL function findResources: enable invoking the
resourceResolver.findResources functionality EL functions
* New EL function getRelativeResource: enables finding resources by
a relative path in EL functions
The patch also contains jUnit tests for these new tags and functions.
I was also looking through the old issues, and I believe
SLING-577https://issues.apache.org/jira/browse/SLING-577 can be closed, as
Tobias points out you can bind a ValueMap to the page context and access
properties on it using EL functions, e.g.:
pageContext.setAttribute(myProps,aValueMap);
${myProps.name} - ${myProps['sling:resourceType']}
Finally, I was wondering what the process would be for getting Sling Taglib
2.1.9 released? Is there anything else required before it gets released or
anything I can do to help the process?
Thanks,
Dan
From: Dan Klco
Sent: Wednesday, December 05, 2012 3:48 PM
To: dev@sling.apache.orgmailto:dev@sling.apache.org
Subject: Resource Access Tags
All,
I was wondering if there was any interest in adding the Resource access tags
I provided into the Sling Taglib. The idea behind these tags is to provide
a faculty for accessing some of the most common functionality in the Sling
Resource API without having to use Scriplet.
The tags include the following:
* getResource - get a resource by path
* listChildren - invoke the listChildren method, useful if
SLING-2641 is not in place
* adapt - adapts adaptables to other object types
* getProperty - allows you to get properties from ValueMaps with
defaults and object casting
The patches for this functionality and a page describing the Sling TLDs,
including what tags are available in each version of the Sling TLD are on
this issue:
https://issues.apache.org/jira/browse/SLING-2648
Thanks,
Dan Klco
Senior Staff Engineer, Adobe WEM / Day CQ5 San Ramon, CA / Dayton, OH
http://www.sixdimensions.com/
Cell (937) 231-3050
Office (937) 343-1326
Fax (877) 510-5082
LinkedInhttp://www.linkedin.com/in/klcodanr |
@KlcoDanRhttps://twitter.com/klcodanr
People. Deliver. Progress.
--
Felix Meschberger | Principal Scientist | Adobe
-
No virus found in this message.
Checked by AVG - www.avg.com
Re: [jira] [Created] (SLING-2762) AbstractSlingRepository#login violates JCR spec
Hi,
Am 01.03.2013 um 17:29 schrieb Angela Schreiber:
hi felix
that makes sense. in general i would suggest to consistently use
GuestCredentials and get rid of the jr-core-null workaround that
in fact relies on an comfortable but somewhat incorrect
implementation detail...
Not having GuestCredentials, our use of the anonymous credentials was in fact
done to prevent using the jr-core-null sideeffect. But GuestCredentials is
better for sure.
hope that helps
Sure does ;-)
Regards
Felix
angela
On 3/1/13 11:29 AM, Felix Meschberger wrote:
Hi
Yes, we assume this under the backwards compatibility umbrella. IIRC
Jackrabbit supported the null-argument in this way, too. So we just made it
explicit.
What we might want to change, though, is to use JCR 2 GuestCredentials
instead of doing our own anonmous login stuff and thus get rid of the
PluggableLoginModule for anonnyous access.
we could also improve a bit by checking for an access control context:
if (credentials == null) {
if (hasAccessControlContext() hasSubject()) {
// assume external authentication
} else {
// assume backwards compatibility anon login
credentials = new GuestCredentials();
}
}
WDYT ?
Regards
Felix
Am 01.03.2013 um 10:43 schrieb Antonio Sanso (JIRA):
Antonio Sanso created SLING-2762:
Summary: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA
administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
Felix Meschberger | Principal Scientist | Adobe
--
Felix Meschberger | Principal Scientist | Adobe
Re: Resource Access Tags
On Mon, Mar 4, 2013 at 4:30 AM, Felix Meschberger fmesc...@adobe.com wrote: ... sr sounds not too bad. I would have chose resource out of my belly. I agree sling-resource is probably too long Maybe res ? I don't do much JSP so I don't know if it's already used though. -Bertrand
Re: [RT] ResourceMetadata
2013/3/4 Felix Meschberger fmesc...@adobe.com: Hi, I have been looking into this some time ago. And I am also somewhat unhappy with the read/write nature of the ResourceMetadata. While I think in general we can make the ResourceMetadata read-only, we have a problem with code like: resource.getResourceMetadata().setResolutionPathInfo(rpi); which is in ResourceResolverImpl.resolveInternal (line 805). This would break. Yepp. We could see, whether it would be possible to make the ResourceMetadata read-only after resource resolution has completed, e.g. ResourceMetadata.lock(). But I am not really convinced. Yes, that's why I suggest that the resource resolver calls this method before returning the resource object. I am also not sure, what client application we would break with this change ? We will never know - so far I don't know any code putting stuff in here outside of the resource resolver. What happens in the Sling Launchpad Testing build if this would be read-only ? I couldn't find a reference to metadata in that module Carsten Regards Felix Am 01.03.2013 um 17:48 schrieb Carsten Ziegeler: Hi, while looking into some issues, I realized that ResourceMetadata is not only extending a HashMap (which makes handling easier), but we have absolutely no information if this map can be changed by client code or is a read-only map. I think we should add this to the documentation and make this read-only. We could either just document it or add a make read-only method to ResourceMetadata which is called by the resource resolver before the resource object is returned to the client code. But I think we should not allow client code to change/add/remove to ResourceMetadata. WDYT Regards Carsten -- Carsten Ziegeler cziege...@apache.org -- Felix Meschberger | Principal Scientist | Adobe -- Carsten Ziegeler cziege...@apache.org
Re: [RT] ResourceMetadata
On Mon, Mar 4, 2013 at 5:24 AM, Felix Meschberger fmesc...@adobe.com wrote: ...We could see, whether it would be possible to make the ResourceMetadata read-only after resource resolution has completed, e.g. ResourceMetadata.lock(). But I am not really convinced Maybe wrap it in a ReadOnlyResourceMetadataWrapper, once resolution is done? Looks cleaner than a lock() or setReadyOnly() method to me. ...I am also not sure, what client application we would break with this change ? What happens in the Sling Launchpad Testing build if this would be read-only ?... IMO there's no reason to change ResourceMetadata once a resource has been setup, so if any tests break we should rather fix them. I don't remember touching it in tests that I wrote. -Bertrand
Re: [Adapter] Make AdapterManager.getAdapter transitive operation
Hi Alex, Felix Thanks for sharing your thoughts. The real magic was to implement cache of adapter factory descriptors, indexed by adaptable and adapter, and to maintain that. It works really well btw. Proposed implementation change would just query that cache more that once, what is currently done. On Mon, Mar 4, 2013 at 12:59 PM, Felix Meschberger fmesc...@adobe.comwrote: Hi Am 04.03.2013 um 12:16 schrieb Alexander Klimetschek: On 03.03.2013, at 00:05, Miroslav Smiljanic smmiros...@gmail.com wrote: Currently if A adapts to [B, D], and B adapts to [C], adapter manager will not adapt A to C even if it is potentially possible. AdapterManager.getAdapter method has to be called twice. I have done some code modifications and made operation transitive. Do you think that it would be worth to add this new capability to AdapterManagerImpl? That sounds like a bit too much magic to me, I think it's better if devs are forced to explicitly adapt things one at a time Agreed. Regards Felix Do you have a use case? Cheers, Alex -- Felix Meschberger | Principal Scientist | Adobe -- Best regards, Miroslav
Re: [Adapter] Make AdapterManager.getAdapter transitive operation
On Mon, Mar 4, 2013 at 5:38 AM, Miroslav Smiljanic smmiros...@gmail.com wrote: ...Proposed implementation change would just query that cache more that once, what is currently done Yes, but from the user's point of view there's the additional magic of a transitive chain of adapters. I agree with others that that's too much magic - the adapter pattern potentially creates non-transparent code (when abused by adapting apples to oranges), if it's transitive the risk is even higher. -Bertrand
Re: Resource Access Tags
Hi,
I might be missing something obvious, but what is the driver to put these in a
separate bundle?
Thanks,
Justin
On Feb 25, 2013, at 12:02 PM, Felix Meschberger fmesc...@adobe.com wrote:
Hi Dan
Thank you very much. Glancing over it, this looks fine -- a deeper review is
welcome.
Yet, I wonder whether we should add those tags and EL functions to the
existing JSP taglib or whether we should create a Resource API specific tag
library ?
WDYT ?
Regards
Felix
Am 22.02.2013 um 14:26 schrieb Dan Klco:
All,
I’ve made some additional contributions around the resource access tags,
based on SLING-1500https://issues.apache.org/jira/browse/SLING-1500, which
had some nice features including:
• New FindResources tag, for invoking the
resourceResolver.findResources functionality
• Updated: GetResources tag, adds the ability to specify a base
resource under which to retrieve a relative resource
• New EL function adaptTo: adding the ability to adapt adaptables in
EL functions
• New EL function findResources: enable invoking the
resourceResolver.findResources functionality EL functions
• New EL function getRelativeResource: enables finding resources by a
relative path in EL functions
The patch also contains jUnit tests for these new tags and functions.
I was also looking through the old issues, and I believe
SLING-577https://issues.apache.org/jira/browse/SLING-577 can be closed, as
Tobias points out you can bind a ValueMap to the page context and access
properties on it using EL functions, e.g.:
pageContext.setAttribute(“myProps”,aValueMap);
${myProps.name} - ${myProps[‘sling:resourceType’]}
Finally, I was wondering what the process would be for getting Sling Taglib
2.1.9 released? Is there anything else required before it gets released or
anything I can do to help the process?
Thanks,
Dan
From: Dan Klco
Sent: Wednesday, December 05, 2012 3:48 PM
To: dev@sling.apache.orgmailto:dev@sling.apache.org
Subject: Resource Access Tags
All,
I was wondering if there was any interest in adding the Resource access tags
I provided into the Sling Taglib. The idea behind these tags is to provide a
faculty for accessing some of the most common functionality in the Sling
Resource API without having to use Scriplet.
The tags include the following:
• getResource – get a resource by path
• listChildren – invoke the listChildren method, useful if SLING-2641
is not in place
• adapt – adapts adaptables to other object types
• getProperty – allows you to get properties from ValueMaps with
defaults and object casting
The patches for this functionality and a page describing the Sling TLDs,
including what tags are available in each version of the Sling TLD are on
this issue:
https://issues.apache.org/jira/browse/SLING-2648
Thanks,
Dan Klco
Senior Staff Engineer, Adobe WEM / Day CQ5
San Ramon, CA / Dayton, OH
http://www.sixdimensions.com/
Cell (937) 231-3050
Office (937) 343-1326
Fax (877) 510-5082
LinkedInhttp://www.linkedin.com/in/klcodanr |
@KlcoDanRhttps://twitter.com/klcodanr
People. Deliver. Progress.
--
Felix Meschberger | Principal Scientist | Adobe
[jira] [Commented] (SLING-2698) Add a minimal resource access gate
[ https://issues.apache.org/jira/browse/SLING-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13592231#comment-13592231 ] Mike Müller commented on SLING-2698: I commited a first shot of the API interface an implementation in r1452322. At the moment it^s implemented for read rights of whole resources. Add a minimal resource access gate -- Key: SLING-2698 URL: https://issues.apache.org/jira/browse/SLING-2698 Project: Sling Issue Type: New Feature Components: ResourceResolver Reporter: Mike Müller Assignee: Mike Müller Fix For: Resource Resolver 1.1.0 Adding a minmal resource access gate as discussed in [1]. First step is to define the API interface and a minimal implementation which allows to define READ access (rest of CRUD can follow later) [1] http://markmail.org/thread/4ctczoiy533tquyl -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2698) Add a minimal resource access gate
[ https://issues.apache.org/jira/browse/SLING-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13592239#comment-13592239 ] Bertrand Delacretaz commented on SLING-2698: I don't see any tests in revision 1452322, did I miss something? As that's in the Sling core, good test coverage is required IMO. Add a minimal resource access gate -- Key: SLING-2698 URL: https://issues.apache.org/jira/browse/SLING-2698 Project: Sling Issue Type: New Feature Components: ResourceResolver Reporter: Mike Müller Assignee: Mike Müller Fix For: Resource Resolver 1.1.0 Adding a minmal resource access gate as discussed in [1]. First step is to define the API interface and a minimal implementation which allows to define READ access (rest of CRUD can follow later) [1] http://markmail.org/thread/4ctczoiy533tquyl -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2698) Add a minimal resource access gate
[ https://issues.apache.org/jira/browse/SLING-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13592242#comment-13592242 ] Julian Sedding commented on SLING-2698: --- I had a quick look at the implementation and there are three things that worry me: * The implementation is in the resourceresolver bundle and therefore not optional * Checking permissions using regular expressions seems troublesome to me for performance considerations. While rendering a moderately complex website, a lot of RR#getResource() calls are made, each of which would trigger a regexp evaluation. Would a String#startsWith() call be enough? This should definitely be backed by performance tests. * Implementing AccessGates using a ResourceDecorator seems pretty insecure, because the resource can easily be unwrapped (intentionally or by accident). We had this issue recently in the context of the Resource#isResourceType() checks (see SLING-2739). Add a minimal resource access gate -- Key: SLING-2698 URL: https://issues.apache.org/jira/browse/SLING-2698 Project: Sling Issue Type: New Feature Components: ResourceResolver Reporter: Mike Müller Assignee: Mike Müller Fix For: Resource Resolver 1.1.0 Adding a minmal resource access gate as discussed in [1]. First step is to define the API interface and a minimal implementation which allows to define READ access (rest of CRUD can follow later) [1] http://markmail.org/thread/4ctczoiy533tquyl -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [Adapter] Make AdapterManager.getAdapter transitive operation
2013/3/4 Bertrand Delacretaz bdelacre...@apache.org: On Mon, Mar 4, 2013 at 5:38 AM, Miroslav Smiljanic smmiros...@gmail.com wrote: ...Proposed implementation change would just query that cache more that once, what is currently done Yes, but from the user's point of view there's the additional magic of a transitive chain of adapters. I agree with others that that's too much magic - the adapter pattern potentially creates non-transparent code (when abused by adapting apples to oranges), if it's transitive the risk is even higher. Apart from this too much magic, I guess the implementation might really have a negative impact on performance unless you limit the transitive search to one level. Regards Carsten -- Carsten Ziegeler cziege...@apache.org
[jira] [Commented] (SLING-2698) Add a minimal resource access gate
[ https://issues.apache.org/jira/browse/SLING-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13592265#comment-13592265 ] Bertrand Delacretaz commented on SLING-2698: I agree with Julian, having that functionality in a separate bundle would be much better. As I've said in list discussions, I'm wary of people trusting this functionality too much for security, and I don't want us to support this as a security feature as we already have security elsewhere. Putting this in a separate bundle helps make that distinction, and if that exposes a need for additional extension points in the resource resolver that might be a good thing. Mike, do you see a way of moving this to a separate bundle? Add a minimal resource access gate -- Key: SLING-2698 URL: https://issues.apache.org/jira/browse/SLING-2698 Project: Sling Issue Type: New Feature Components: ResourceResolver Reporter: Mike Müller Assignee: Mike Müller Fix For: Resource Resolver 1.1.0 Adding a minmal resource access gate as discussed in [1]. First step is to define the API interface and a minimal implementation which allows to define READ access (rest of CRUD can follow later) [1] http://markmail.org/thread/4ctczoiy533tquyl -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Resource Access Tags
Hi,
Am 04.03.2013 um 15:10 schrieb Justin Edelson:
Hi,
I might be missing something obvious, but what is the driver to put these in
a separate bundle?
Separation of concern ? The current tag lib is about include/forward mostly -
hence request processing logic.
The new tags are around accessing resources - hence not really directly related
to request processing logic.
Regards
Felix
Thanks,
Justin
On Feb 25, 2013, at 12:02 PM, Felix Meschberger fmesc...@adobe.com wrote:
Hi Dan
Thank you very much. Glancing over it, this looks fine -- a deeper review is
welcome.
Yet, I wonder whether we should add those tags and EL functions to the
existing JSP taglib or whether we should create a Resource API specific tag
library ?
WDYT ?
Regards
Felix
Am 22.02.2013 um 14:26 schrieb Dan Klco:
All,
I’ve made some additional contributions around the resource access tags,
based on SLING-1500https://issues.apache.org/jira/browse/SLING-1500, which
had some nice features including:
• New FindResources tag, for invoking the
resourceResolver.findResources functionality
• Updated: GetResources tag, adds the ability to specify a base
resource under which to retrieve a relative resource
• New EL function adaptTo: adding the ability to adapt adaptables in
EL functions
• New EL function findResources: enable invoking the
resourceResolver.findResources functionality EL functions
• New EL function getRelativeResource: enables finding resources by
a relative path in EL functions
The patch also contains jUnit tests for these new tags and functions.
I was also looking through the old issues, and I believe
SLING-577https://issues.apache.org/jira/browse/SLING-577 can be closed, as
Tobias points out you can bind a ValueMap to the page context and access
properties on it using EL functions, e.g.:
pageContext.setAttribute(“myProps”,aValueMap);
${myProps.name} - ${myProps[‘sling:resourceType’]}
Finally, I was wondering what the process would be for getting Sling Taglib
2.1.9 released? Is there anything else required before it gets released or
anything I can do to help the process?
Thanks,
Dan
From: Dan Klco
Sent: Wednesday, December 05, 2012 3:48 PM
To: dev@sling.apache.orgmailto:dev@sling.apache.org
Subject: Resource Access Tags
All,
I was wondering if there was any interest in adding the Resource access tags
I provided into the Sling Taglib. The idea behind these tags is to provide
a faculty for accessing some of the most common functionality in the Sling
Resource API without having to use Scriplet.
The tags include the following:
• getResource – get a resource by path
• listChildren – invoke the listChildren method, useful if
SLING-2641 is not in place
• adapt – adapts adaptables to other object types
• getProperty – allows you to get properties from ValueMaps with
defaults and object casting
The patches for this functionality and a page describing the Sling TLDs,
including what tags are available in each version of the Sling TLD are on
this issue:
https://issues.apache.org/jira/browse/SLING-2648
Thanks,
Dan Klco
Senior Staff Engineer, Adobe WEM / Day CQ5
San Ramon, CA / Dayton, OH
http://www.sixdimensions.com/
Cell (937) 231-3050
Office (937) 343-1326
Fax (877) 510-5082
LinkedInhttp://www.linkedin.com/in/klcodanr |
@KlcoDanRhttps://twitter.com/klcodanr
People. Deliver. Progress.
--
Felix Meschberger | Principal Scientist | Adobe
--
Felix Meschberger | Principal Scientist | Adobe
Re: Resource Access Tags
Hi,
On Mon, Mar 4, 2013 at 10:12 AM, Felix Meschberger fmesc...@adobe.comwrote:
Hi,
Am 04.03.2013 um 15:10 schrieb Justin Edelson:
Hi,
I might be missing something obvious, but what is the driver to put
these in a separate bundle?
Separation of concern ? The current tag lib is about include/forward
mostly - hence request processing logic.
The new tags are around accessing resources - hence not really directly
related to request processing logic.
But including and forwarding *resources* and *scripts* both of which I
would consider to be core Sling. It doesn't make sense to me to have a
separate taglib than the sling taglib and seems like a
real inconvenience to developers to have to include two different taglib
directives and on deployers to deploy two separate bundles.
If we had, for example, event framework-specific JSP tags, I could see
those going in a separate taglib, but this stuff is at the heart of what
Sling is.
Regards,
Justin
Regards
Felix
Thanks,
Justin
On Feb 25, 2013, at 12:02 PM, Felix Meschberger fmesc...@adobe.com
wrote:
Hi Dan
Thank you very much. Glancing over it, this looks fine -- a deeper
review is welcome.
Yet, I wonder whether we should add those tags and EL functions to the
existing JSP taglib or whether we should create a Resource API specific tag
library ?
WDYT ?
Regards
Felix
Am 22.02.2013 um 14:26 schrieb Dan Klco:
All,
I’ve made some additional contributions around the resource access
tags, based on SLING-1500https://issues.apache.org/jira/browse/SLING-1500,
which had some nice features including:
• New FindResources tag, for invoking the
resourceResolver.findResources functionality
• Updated: GetResources tag, adds the ability to specify a base
resource under which to retrieve a relative resource
• New EL function adaptTo: adding the ability to adapt
adaptables in EL functions
• New EL function findResources: enable invoking the
resourceResolver.findResources functionality EL functions
• New EL function getRelativeResource: enables finding
resources by a relative path in EL functions
The patch also contains jUnit tests for these new tags and functions.
I was also looking through the old issues, and I believe SLING-577
https://issues.apache.org/jira/browse/SLING-577 can be closed, as Tobias
points out you can bind a ValueMap to the page context and access
properties on it using EL functions, e.g.:
pageContext.setAttribute(“myProps”,aValueMap);
${myProps.name} - ${myProps[‘sling:resourceType’]}
Finally, I was wondering what the process would be for getting Sling
Taglib 2.1.9 released? Is there anything else required before it gets
released or anything I can do to help the process?
Thanks,
Dan
From: Dan Klco
Sent: Wednesday, December 05, 2012 3:48 PM
To: dev@sling.apache.orgmailto:dev@sling.apache.org
Subject: Resource Access Tags
All,
I was wondering if there was any interest in adding the Resource access
tags I provided into the Sling Taglib. The idea behind these tags is to
provide a faculty for accessing some of the most common functionality in
the Sling Resource API without having to use Scriplet.
The tags include the following:
• getResource – get a resource by path
• listChildren – invoke the listChildren method, useful if
SLING-2641 is not in place
• adapt – adapts adaptables to other object types
• getProperty – allows you to get properties from ValueMaps
with defaults and object casting
The patches for this functionality and a page describing the Sling
TLDs, including what tags are available in each version of the Sling TLD
are on this issue:
https://issues.apache.org/jira/browse/SLING-2648
Thanks,
Dan Klco
Senior Staff Engineer, Adobe WEM / Day CQ5
San Ramon, CA / Dayton, OH
http://www.sixdimensions.com/
Cell (937) 231-3050
Office (937) 343-1326
Fax (877) 510-5082
LinkedInhttp://www.linkedin.com/in/klcodanr | @KlcoDanR
https://twitter.com/klcodanr
People. Deliver. Progress.
--
Felix Meschberger | Principal Scientist | Adobe
--
Felix Meschberger | Principal Scientist | Adobe
[jira] [Created] (SLING-2771) mvn validate doesn't work if local Maven repo is empty
Bertrand Delacretaz created SLING-2771: -- Summary: mvn validate doesn't work if local Maven repo is empty Key: SLING-2771 URL: https://issues.apache.org/jira/browse/SLING-2771 Project: Sling Issue Type: Bug Components: General Environment: macosx with java version 1.6.0_37 and Apache Maven 3.0.5 Reporter: Bertrand Delacretaz Priority: Minor The workaround is to build launchpad/base first, and the cause seems to be https://jira.codehaus.org/browse/MNG-1911 $ cd sling $ mv $HOME/.m2/repository/org/apache/sling /tmp/keep-it-somewhere $ mvn validate INFO] Scanning for projects... [WARNING] The POM for org.apache.sling:org.apache.sling.launchpad.base:jar:2.5.1-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.launchpad.base:jar:app:2.5.1-SNAPSHOT is missing, no dependency information available [ERROR] The build could not read 1 project - [Help 1] [ERROR] [ERROR] The project org.apache.sling:org.apache.sling.launchpad.testing:7-SNAPSHOT (/Users/bert/workspace/apache/sling/launchpad/testing/pom.xml) has 1 error [ERROR] Unresolveable build extension: Plugin org.apache.sling:maven-launchpad-plugin:2.1.2 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.sling:org.apache.sling.launchpad.base:jar:2.5.1-SNAPSHOT, org.apache.sling:org.apache.sling.launchpad.base:jar:app:2.5.1-SNAPSHOT... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [Adapter] Make AdapterManager.getAdapter transitive operation
Hi Carsten, Apart from this too much magic, I guess the implementation might really have a negative impact on performance unless you limit the transitive search to one level. Yes, it has complexity of tree traversal, and idea was to limit look up to certain number of levels. But I guess that we got enough no go replies :) -- Best regards, Miroslav
[jira] [Resolved] (SLING-2771) mvn validate doesn't work if local Maven repo is empty
[ https://issues.apache.org/jira/browse/SLING-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-2771. Resolution: Won't Fix Assignee: Bertrand Delacretaz Deploying the launchpad/base snapshot to the Apache snapshots Maven repository works around the issue, mvn clean install now works with a local Maven repo that doesn't have any sling artifacts initially. Marking this won't fix for now, there's probably nothing we can do on our side besides deploying such snapshots to work around the issue. mvn validate doesn't work if local Maven repo is empty -- Key: SLING-2771 URL: https://issues.apache.org/jira/browse/SLING-2771 Project: Sling Issue Type: Bug Components: General Environment: macosx with java version 1.6.0_37 and Apache Maven 3.0.5 Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Priority: Minor The workaround is to build launchpad/base first, and the cause seems to be https://jira.codehaus.org/browse/MNG-1911 $ cd sling $ mv $HOME/.m2/repository/org/apache/sling /tmp/keep-it-somewhere $ mvn validate INFO] Scanning for projects... [WARNING] The POM for org.apache.sling:org.apache.sling.launchpad.base:jar:2.5.1-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.launchpad.base:jar:app:2.5.1-SNAPSHOT is missing, no dependency information available [ERROR] The build could not read 1 project - [Help 1] [ERROR] [ERROR] The project org.apache.sling:org.apache.sling.launchpad.testing:7-SNAPSHOT (/Users/bert/workspace/apache/sling/launchpad/testing/pom.xml) has 1 error [ERROR] Unresolveable build extension: Plugin org.apache.sling:maven-launchpad-plugin:2.1.2 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.sling:org.apache.sling.launchpad.base:jar:2.5.1-SNAPSHOT, org.apache.sling:org.apache.sling.launchpad.base:jar:app:2.5.1-SNAPSHOT... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2771) mvn validate doesn't work if local Maven repo is empty
[ https://issues.apache.org/jira/browse/SLING-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13592307#comment-13592307 ] Justin Edelson commented on SLING-2771: --- Agreed. The other thing we can do is not depend upon a SNAPSHOT version of launchpad.base. mvn validate doesn't work if local Maven repo is empty -- Key: SLING-2771 URL: https://issues.apache.org/jira/browse/SLING-2771 Project: Sling Issue Type: Bug Components: General Environment: macosx with java version 1.6.0_37 and Apache Maven 3.0.5 Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Priority: Minor The workaround is to build launchpad/base first, and the cause seems to be https://jira.codehaus.org/browse/MNG-1911 $ cd sling $ mv $HOME/.m2/repository/org/apache/sling /tmp/keep-it-somewhere $ mvn validate INFO] Scanning for projects... [WARNING] The POM for org.apache.sling:org.apache.sling.launchpad.base:jar:2.5.1-SNAPSHOT is missing, no dependency information available [WARNING] The POM for org.apache.sling:org.apache.sling.launchpad.base:jar:app:2.5.1-SNAPSHOT is missing, no dependency information available [ERROR] The build could not read 1 project - [Help 1] [ERROR] [ERROR] The project org.apache.sling:org.apache.sling.launchpad.testing:7-SNAPSHOT (/Users/bert/workspace/apache/sling/launchpad/testing/pom.xml) has 1 error [ERROR] Unresolveable build extension: Plugin org.apache.sling:maven-launchpad-plugin:2.1.2 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.sling:org.apache.sling.launchpad.base:jar:2.5.1-SNAPSHOT, org.apache.sling:org.apache.sling.launchpad.base:jar:app:2.5.1-SNAPSHOT... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Resource Access Tags
On Mon, Mar 4, 2013 at 7:26 AM, Justin Edelson jus...@justinedelson.com wrote: ...It doesn't make sense to me to have a separate taglib than the sling taglib and seems like a real inconvenience to developers to have to include two different taglib directives and on deployers to deploy two separate bundles I agree - at the OSGi level it would make sense to have two separate bundles, but from the JSP user's perspective that's not good, a single taglib is better. -Bertrand
[jira] [Commented] (SLING-2698) Add a minimal resource access gate
[ https://issues.apache.org/jira/browse/SLING-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13592326#comment-13592326 ] Mike Müller commented on SLING-2698: To be clear here: This is a first shot not the definitive implementation. I wanted to share this as soon as possible. - Yes, we need tests for this new service. Help is very welcome here, I haven't wrote any integration tests (which I think are needed here?) for sling by now... but by now - If no ResourceAccessGate is registered absolutely nothing changes: ResourceAccessGateTracker keeps track if a ResourceGateAccess is registered and only if at least one service is registered the AccessGateResourceDecorator is instantiated and registered as a service. - I know that regexp are not very fast, but regexp should be allowed, when using ResourceAccessGate to make it as flexible as possible. My idea is, that if we ran into performance problems, maybe a cache of often used paths can help. - To implement the whole service in a separate bundle is maybe not a good idea. We would need extension points for each operation (CRUD) and also to implement ResourceAccessGate#sanitizeQuery. - We can overwrite getResource() on the wrapper. The resource can not be unwrapped then, but - and Julian is right there - the wrapped resource can be adapted to some object... Further thoughts see the discussion unter [1] (important: It is not a replacement of ACLs!) [1] http://markmail.org/thread/4ctczoiy533tquyl Add a minimal resource access gate -- Key: SLING-2698 URL: https://issues.apache.org/jira/browse/SLING-2698 Project: Sling Issue Type: New Feature Components: ResourceResolver Reporter: Mike Müller Assignee: Mike Müller Fix For: Resource Resolver 1.1.0 Adding a minmal resource access gate as discussed in [1]. First step is to define the API interface and a minimal implementation which allows to define READ access (rest of CRUD can follow later) [1] http://markmail.org/thread/4ctczoiy533tquyl -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SLING-2698) Add a minimal resource access gate
[ https://issues.apache.org/jira/browse/SLING-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13592380#comment-13592380 ] Carsten Ziegeler commented on SLING-2698: - Thanks Mike for the first implementation, I think from an API pov (sling api) this is fine - however we might move this into a separate package as this service is implemented by different bundles as a resource resolver or a resource provider. We currently have the problem, when changing the resource resolver interface, the package version increases and we have to rerelease all resource provider implementations as that interface happens to be in the same package. We can't change this for old stuff, but we can account for this with new interfaces. It's good that this has no impact if no ResourcAccessGate is registered - I'm not sure about regexps either, but if they turn out to be a performance problem, I guess this is solvable later on. While it would be nice to have the implementation in a separate package, I think we shouldn't add hooks all over the place into the resource resolver implementation. This would open up a can of worms. I'm wondering if we could find some tricky way of wrapping the current resource resolver with an AccessGateAware resource resolver? (or actually it's the factory we have to wrap) Add a minimal resource access gate -- Key: SLING-2698 URL: https://issues.apache.org/jira/browse/SLING-2698 Project: Sling Issue Type: New Feature Components: ResourceResolver Reporter: Mike Müller Assignee: Mike Müller Fix For: Resource Resolver 1.1.0 Adding a minmal resource access gate as discussed in [1]. First step is to define the API interface and a minimal implementation which allows to define READ access (rest of CRUD can follow later) [1] http://markmail.org/thread/4ctczoiy533tquyl -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
