[jira] [Commented] (SLING-2798) Apache Cassandra backend for Sling: GSoC2013 Project
[ https://issues.apache.org/jira/browse/SLING-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13850757#comment-13850757 ] Robert Munteanu commented on SLING-2798: Two comments here: 1. The code was donated, but still not included in the source repo. What is missing to make this happen? 2. [~bdelacretaz] mentioned Cassandra testing. We can use the Cassandra Maven plugin ( http://mojo.codehaus.org/cassandra-maven-plugin/ ) to set up integrations tests. But maybe we can get the first point solved :-) Apache Cassandra backend for Sling: GSoC2013 Project Key: SLING-2798 URL: https://issues.apache.org/jira/browse/SLING-2798 Project: Sling Issue Type: Bug Components: Samples Reporter: Ian Boston Labels: cassandra, gsoc, gsoc2013, java, osgi, sling Attachments: Sling Cassandra backend Architecture.jpg, cassandra-backend-for-sling.tar.gz This is a proposal for GSoC2013: create an Resource Provider that allows resources stored in Apache Cassandra to be exposed as Sling Resources. Resources[1] are the basic building blocks of Sling. ResourceProviders[2] allow data sources to be added to the core ResourceProvider within Sling allowing those data sources to provide Resources at pre-determined locations in the resource tree. To put it in more familiar terms, implementing and adding a Resource provider is like mounting or mapping a network drive. A more recent addition to the facilities available in Sling include updatable ResourceProviders. Apache Cassandra[3] is a column database (NoSQL) which aims to provide linear scalability to web scale. It is used by many of the best known names on the internet. Initially this will provide read only resource access, but if there is time in the project will allow read write access to a cassandra cluster. Advanced Java skills are required, some knowledge of OSGi, Sling, Cassandra will be valuable. The following pages give more information about GSoC @apache: * http://www.google-melange.com/gsoc/homepage/google/gsoc2013 * http://community.apache.org/gsoc.html * http://s.apache.org/gsoc2013ideas 1 http://sling.apache.org/site/resources.html 2 http://sling.apache.org/apidocs/sling6/org/apache/sling/api/resource/ResourceProvider.html 3 http://cassandra.apache.org/ -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (SLING-3286) Remove plugin version overrides from poms
[ https://issues.apache.org/jira/browse/SLING-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13853872#comment-13853872 ] Robert Munteanu commented on SLING-3286: Opened FELIX-4364 regarding the maven-bundle-plugin behaviour change. Remove plugin version overrides from poms - Key: SLING-3286 URL: https://issues.apache.org/jira/browse/SLING-3286 Project: Sling Issue Type: Task Reporter: Robert Munteanu Assignee: Robert Munteanu Multiple modules specify their own versions instead of picking up the one from the parent pom. For consistency and for making sure that we always get the upgrades, all these modules should have the same versions. Situations where this isn't possible should be clearly documented in the pom. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (SLING-3307) Updated launchpad bundle list is not reflected after upgrade
Robert Munteanu created SLING-3307: -- Summary: Updated launchpad bundle list is not reflected after upgrade Key: SLING-3307 URL: https://issues.apache.org/jira/browse/SLING-3307 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Installer 1.2.2 Reporter: Robert Munteanu This is a follow-up bug report for http://markmail.org/thread/6us2jyrkcz6wjwxr . I've run into a bug when trying to update an existing Sling launchad to add a new bundle. The steps I've taken were: * Create a launchpad ( using the maven-launchpad-plugin ) and executed the jar file * Updated the bundle list to include a new bundle and executed the jar file on top of the existing launchpad directory The end result was that the new bundle was not deployed. Digging in the code a bit, I've noticed that the upgrade goes well if I force the startup mode to update. The sling/conf/launchpad_timestamp.txt exists and is valid. It seems that the StartupManager.getSelfTimeStamp() method does not get the correct timestamp: * looks for the last-modified date of the jar loading StartupManager.class - org.apache.sling.launchpad.base.jar * looks for the last-modified date of the jar loading LaunchpadContentProvider.class - still org.apache.sling.launchpad.base.jar * looks for the last-modified date of all the bundles from sling/startup folder The problem is that at this point, the new/modified bundles are not present in the sling/startup folder, so they are not taken into account. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (SLING-3307) Updated launchpad bundle list is not reflected after upgrade
[ https://issues.apache.org/jira/browse/SLING-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13862914#comment-13862914 ] Robert Munteanu commented on SLING-3307: I've attached [^SLING-3307-repro.zip|a sample maven project] which demonstrates the steps I took and ended up with the launchpad not being updated. The archive contains a README.md file which shows step-by-step instructions. Updated launchpad bundle list is not reflected after upgrade Key: SLING-3307 URL: https://issues.apache.org/jira/browse/SLING-3307 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Installer 1.2.2 Reporter: Robert Munteanu Attachments: SLING-3307-repro.zip This is a follow-up bug report for http://markmail.org/thread/6us2jyrkcz6wjwxr . I've run into a bug when trying to update an existing Sling launchad to add a new bundle. The steps I've taken were: * Create a launchpad ( using the maven-launchpad-plugin ) and executed the jar file * Updated the bundle list to include a new bundle and executed the jar file on top of the existing launchpad directory The end result was that the new bundle was not deployed. Digging in the code a bit, I've noticed that the upgrade goes well if I force the startup mode to update. The sling/conf/launchpad_timestamp.txt exists and is valid. It seems that the StartupManager.getSelfTimeStamp() method does not get the correct timestamp: * looks for the last-modified date of the jar loading StartupManager.class - org.apache.sling.launchpad.base.jar * looks for the last-modified date of the jar loading LaunchpadContentProvider.class - still org.apache.sling.launchpad.base.jar * looks for the last-modified date of all the bundles from sling/startup folder The problem is that at this point, the new/modified bundles are not present in the sling/startup folder, so they are not taken into account. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (SLING-3307) Updated launchpad bundle list is not reflected after upgrade
[ https://issues.apache.org/jira/browse/SLING-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3307: --- Attachment: SLING-3307-repro.zip Updated launchpad bundle list is not reflected after upgrade Key: SLING-3307 URL: https://issues.apache.org/jira/browse/SLING-3307 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Installer 1.2.2 Reporter: Robert Munteanu Attachments: SLING-3307-repro.zip This is a follow-up bug report for http://markmail.org/thread/6us2jyrkcz6wjwxr . I've run into a bug when trying to update an existing Sling launchad to add a new bundle. The steps I've taken were: * Create a launchpad ( using the maven-launchpad-plugin ) and executed the jar file * Updated the bundle list to include a new bundle and executed the jar file on top of the existing launchpad directory The end result was that the new bundle was not deployed. Digging in the code a bit, I've noticed that the upgrade goes well if I force the startup mode to update. The sling/conf/launchpad_timestamp.txt exists and is valid. It seems that the StartupManager.getSelfTimeStamp() method does not get the correct timestamp: * looks for the last-modified date of the jar loading StartupManager.class - org.apache.sling.launchpad.base.jar * looks for the last-modified date of the jar loading LaunchpadContentProvider.class - still org.apache.sling.launchpad.base.jar * looks for the last-modified date of all the bundles from sling/startup folder The problem is that at this point, the new/modified bundles are not present in the sling/startup folder, so they are not taken into account. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (SLING-2393) Update Post Servlet Documentation for patch operation
[ https://issues.apache.org/jira/browse/SLING-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894311#comment-13894311 ] Robert Munteanu commented on SLING-2393: [~alexander.klimetschek] - that would be http://svn.apache.org/repos/asf/sling/site/trunk/content/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.mdtext . Update Post Servlet Documentation for patch operation - Key: SLING-2393 URL: https://issues.apache.org/jira/browse/SLING-2393 Project: Sling Issue Type: Task Components: Servlets Affects Versions: Servlets Post 2.1.0 Reporter: Felix Meschberger Add documentation to http://sling.apache.org/site/manipulating-content-the-slingpostservlet-servletspost.html with information on patch operation (see SLING-1983) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (SLING-2393) Update Post Servlet Documentation for patch operation
[ https://issues.apache.org/jira/browse/SLING-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-2393: --- Component/s: (was: Servlets) Documentation Affects Version/s: (was: Servlets Post 2.1.0) Update Post Servlet Documentation for patch operation - Key: SLING-2393 URL: https://issues.apache.org/jira/browse/SLING-2393 Project: Sling Issue Type: Task Components: Documentation Reporter: Felix Meschberger Assignee: Robert Munteanu Attachments: SLING-2393.patch Add documentation to http://sling.apache.org/site/manipulating-content-the-slingpostservlet-servletspost.html with information on patch operation (see SLING-1983) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (SLING-2393) Update Post Servlet Documentation for patch operation
[ https://issues.apache.org/jira/browse/SLING-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-2393. Resolution: Fixed Patch applied in http://svn.apache.org/r1565846 , thanks! The changes are now live at http://sling.apache.org/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html#patch . Update Post Servlet Documentation for patch operation - Key: SLING-2393 URL: https://issues.apache.org/jira/browse/SLING-2393 Project: Sling Issue Type: Task Components: Documentation Reporter: Felix Meschberger Assignee: Robert Munteanu Attachments: SLING-2393.patch Add documentation to http://sling.apache.org/site/manipulating-content-the-slingpostservlet-servletspost.html with information on patch operation (see SLING-1983) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (SLING-3447) Improve documentation of sling
[ https://issues.apache.org/jira/browse/SLING-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13930496#comment-13930496 ] Robert Munteanu commented on SLING-3447: [~bond_] - contributions for documentation are more than welcome :-) I suggest that you open independent Jira issues for each issue that you find. Improve documentation of sling -- Key: SLING-3447 URL: https://issues.apache.org/jira/browse/SLING-3447 Project: Sling Issue Type: Improvement Components: Documentation Reporter: Ravi Teja Labels: documentation I'm expecting something on the lines of # http://grails.org/doc/latest/guide/introduction.html # http://docs.spring.io/spring/docs/current/spring-framework-reference/html/ I will also help you build the documentation as I'm learning about Sling. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3447) Improve documentation of sling
[ https://issues.apache.org/jira/browse/SLING-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13931536#comment-13931536 ] Robert Munteanu commented on SLING-3447: The sling web site is open source, all the content is in the ASF SVN at https://svn.apache.org/repos/asf/sling/site/trunk/content/ . As for starting to contribute, you should attach your contributions to this Jira ticket. The site is formatted in markdown, and it's best if you submit SVN diffs. If that's not feasible, just attach whole files and I'll try to merge them. Improve documentation of sling -- Key: SLING-3447 URL: https://issues.apache.org/jira/browse/SLING-3447 Project: Sling Issue Type: Improvement Components: Documentation Reporter: Ravi Teja Labels: documentation I'm expecting something on the lines of # http://grails.org/doc/latest/guide/introduction.html # http://docs.spring.io/spring/docs/current/spring-framework-reference/html/ I will also help you build the documentation as I'm learning about Sling. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3447) Improve documentation of sling
[ https://issues.apache.org/jira/browse/SLING-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13931590#comment-13931590 ] Robert Munteanu commented on SLING-3447: There's a lot of discussion around where to host code, but I can definitely say that we will be hosting the code on the ASF infrastructure for the foreseeable future. There is some effort to get github mirrors up and running - the sling project has its own github mirror and AFAIK you can even submit pull requests - https://github.com/apache/sling . But that's not done for the website yet. Improve documentation of sling -- Key: SLING-3447 URL: https://issues.apache.org/jira/browse/SLING-3447 Project: Sling Issue Type: Improvement Components: Documentation Reporter: Ravi Teja Labels: documentation I'm expecting something on the lines of # http://grails.org/doc/latest/guide/introduction.html # http://docs.spring.io/spring/docs/current/spring-framework-reference/html/ I will also help you build the documentation as I'm learning about Sling. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3447) Add more Source and CI links to sidebar
[ https://issues.apache.org/jira/browse/SLING-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13936295#comment-13936295 ] Robert Munteanu commented on SLING-3447: [~bond_] - sorry for dropping the ball on the patch and thanks to Justin for applying it :-) To give you a bit more detail, we don't open up issues which are very large in scope, like 'Improve documentation', 'Increase usability' or 'Make development simpler'. While these may be overarching themes in our development, it's hard to say when they are 'done', and as such the risks are to have bugs which * are open for a very long time, with no clear outcome * have very mixed discussions on such bugs, due to the many issues they can affect So I'd invite you to open up bugs for individual issues, and if you feel that there are larger issues to discuss, post on the mailing lists. Thanks, and thanks again for the patch. Add more Source and CI links to sidebar --- Key: SLING-3447 URL: https://issues.apache.org/jira/browse/SLING-3447 Project: Sling Issue Type: Improvement Components: Documentation Reporter: Ravi Teja Assignee: Justin Edelson Labels: documentation Attachments: sidenav.diff I'm expecting something on the lines of # http://grails.org/doc/latest/guide/introduction.html # http://docs.spring.io/spring/docs/current/spring-framework-reference/html/ I will also help you build the documentation as I'm learning about Sling. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-920) Sling Jenkins setup
[
https://issues.apache.org/jira/browse/SLING-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13948086#comment-13948086
]
Robert Munteanu commented on SLING-920:
---
Updated sling-trunk-1.6 and sling-trunk-1.7 to fix job execution. Previously,
they would fail with
{code}FATAL: Failed to install
http://archive.apache.org/dist/maven/binaries/apache-maven-3.0.4-bin.zip to
/home/hudson/tools/maven/apache-maven-3.0.4{code}
This was previously discussed on bui...@apache.org, but I don't have the link
at hand.
Sling Jenkins setup
---
Key: SLING-920
URL: https://issues.apache.org/jira/browse/SLING-920
Project: Sling
Issue Type: Task
Components: Testing
Reporter: Bertrand Delacretaz
Use this issue to record changes to the Hudson continuous environment setup
at http://hudson.zones.apache.org/hudson/view/Sling/
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (SLING-3491) Standalone Launchpad Testing does not start on trunk
Robert Munteanu created SLING-3491: -- Summary: Standalone Launchpad Testing does not start on trunk Key: SLING-3491 URL: https://issues.apache.org/jira/browse/SLING-3491 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Reporter: Robert Munteanu Assignee: Carsten Ziegeler Fix For: Launchpad Builder 7 When starting the standalone launchpad it can fail with the error below. Whether or not you see this depends a little on the version of org.apache.felix.http.jetty that you have in your local .m2 directory. This is caused by the fact that in org.apache.felix.http.jetty version 2.3 the API bundles have been split off. The error is: 19.03.2014 16:17:59.128 *ERROR* [FelixStartLevel] ERROR: Error starting slinginstall:org.apache.felix.http.jetty-2.3.0-R1570612.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.felix.http.jetty [5]: Unable to resolve 5.0: missing requirement [5.0] osgi.wiring.package; ((osgi.wiring.package=javax.servlet)(version=3.0.0)(!(version=4.0.0 org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.felix.http.jetty [5]: Unable to resolve 5.0: missing requirement [5.0] osgi.wiring.package; ((osgi.wiring.package=javax.servlet)(version=3.0.0)(!(version=4.0.0))) 19.03.2014 16:17:59.128 *ERROR* [FelixStartLevel] at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3962) 19.03.2014 16:17:59.128 *ERROR* [FelixStartLevel] at org.apache.felix.framework.Felix.startBundle(Felix.java:2025) 19.03.2014 16:17:59.128 *ERROR* [FelixStartLevel] at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1279) 19.03.2014 16:17:59.128 *ERROR* [FelixStartLevel] at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304) 19.03.2014 16:17:59.128 *ERROR* [FelixStartLevel] at java.lang.Thread.run(Thread.java:695) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3491) Standalone Launchpad Testing does not start on trunk
[ https://issues.apache.org/jira/browse/SLING-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3491: --- Description: The fix from SLING-3468 needs to be applied to the launchpad/testing project as well. (was: When starting the standalone launchpad it can fail with the error below. Whether or not you see this depends a little on the version of org.apache.felix.http.jetty that you have in your local .m2 directory. This is caused by the fact that in org.apache.felix.http.jetty version 2.3 the API bundles have been split off. The error is: 19.03.2014 16:17:59.128 *ERROR* [FelixStartLevel] ERROR: Error starting slinginstall:org.apache.felix.http.jetty-2.3.0-R1570612.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.felix.http.jetty [5]: Unable to resolve 5.0: missing requirement [5.0] osgi.wiring.package; ((osgi.wiring.package=javax.servlet)(version=3.0.0)(!(version=4.0.0 org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.felix.http.jetty [5]: Unable to resolve 5.0: missing requirement [5.0] osgi.wiring.package; ((osgi.wiring.package=javax.servlet)(version=3.0.0)(!(version=4.0.0))) 19.03.2014 16:17:59.128 *ERROR* [FelixStartLevel] at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3962) 19.03.2014 16:17:59.128 *ERROR* [FelixStartLevel] at org.apache.felix.framework.Felix.startBundle(Felix.java:2025) 19.03.2014 16:17:59.128 *ERROR* [FelixStartLevel] at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1279) 19.03.2014 16:17:59.128 *ERROR* [FelixStartLevel] at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304) 19.03.2014 16:17:59.128 *ERROR* [FelixStartLevel] at java.lang.Thread.run(Thread.java:695)) Standalone Launchpad Testing does not start on trunk Key: SLING-3491 URL: https://issues.apache.org/jira/browse/SLING-3491 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Reporter: Robert Munteanu Assignee: Carsten Ziegeler Fix For: Launchpad Builder 7 The fix from SLING-3468 needs to be applied to the launchpad/testing project as well. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3491) Standalone Launchpad Testing does not start on trunk
[ https://issues.apache.org/jira/browse/SLING-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3491. Resolution: Fixed Assignee: Robert Munteanu (was: Carsten Ziegeler) Fixed in http://svn.apache.org/r1584648 Standalone Launchpad Testing does not start on trunk Key: SLING-3491 URL: https://issues.apache.org/jira/browse/SLING-3491 Project: Sling Issue Type: Bug Components: Launchpad Affects Versions: Launchpad Builder 7 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Launchpad Builder 7 The fix from SLING-3468 needs to be applied to the launchpad/testing project as well. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3405) SLING2094Test and ServerSideScriptsTest fail with java 8: JSP compiler does not find java.util.Arrays or java.lang.CharSequence
[
https://issues.apache.org/jira/browse/SLING-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13959985#comment-13959985
]
Robert Munteanu commented on SLING-3405:
Compilation of that sample class works fine now with [org.eclipse.jdt.core
3.9.1.v20130905-0837|http://search.maven.org/#artifactdetails\|org.eclipse.tycho\|org.eclipse.jdt.core\|3.9.1.v20130905-0837\|jar]
and a Java 8 runtime.
Nevertheless, I have no idea where to add this new JDT compiler jar ; {{mvn
dependency:tree}} mentions nothing about org.eclipse.jdt.core in
bundles/scripting/jsp . I actually made the change in contrib/commons/compiler
before realising that the issue is rooted somewhere else.
SLING2094Test and ServerSideScriptsTest fail with java 8: JSP compiler does
not find java.util.Arrays or java.lang.CharSequence
---
Key: SLING-3405
URL: https://issues.apache.org/jira/browse/SLING-3405
Project: Sling
Issue Type: Bug
Components: Scripting, Testing
Reporter: Bertrand Delacretaz
Priority: Minor
Attachments: jasper-upgrade.patch
Running the launchpad/integration-tests SLING2094Test fails due to a
compilation error for the test script [1]: Unable to compile class for JSP,
the import java.util.Arrays cannot be resolved.
[1]
https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/resources/integration-test/issues/sling2094/sling2094.jsp
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (SLING-3405) SLING2094Test and ServerSideScriptsTest fail with java 8: JSP compiler does not find java.util.Arrays or java.lang.CharSequence
[ https://issues.apache.org/jira/browse/SLING-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960001#comment-13960001 ] Robert Munteanu commented on SLING-3405: I see, thanks. SLING2094Test and ServerSideScriptsTest fail with java 8: JSP compiler does not find java.util.Arrays or java.lang.CharSequence --- Key: SLING-3405 URL: https://issues.apache.org/jira/browse/SLING-3405 Project: Sling Issue Type: Bug Components: Scripting, Testing Reporter: Bertrand Delacretaz Priority: Minor Attachments: jasper-upgrade.patch Running the launchpad/integration-tests SLING2094Test fails due to a compilation error for the test script [1]: Unable to compile class for JSP, the import java.util.Arrays cannot be resolved. [1] https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/resources/integration-test/issues/sling2094/sling2094.jsp -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3405) SLING2094Test and ServerSideScriptsTest fail with java 8: JSP compiler does not find java.util.Arrays or java.lang.CharSequence
[ https://issues.apache.org/jira/browse/SLING-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960004#comment-13960004 ] Robert Munteanu commented on SLING-3405: By looking at https://tomcat.apache.org/whichversion.html , I can see that the latest Tomcat version is 6.0.39, and since the attached [^jasper-upgrade.patch] does not work, it's clear that we must look into the 7.x stream at least. There are two issues here: * Tomcat 7 requires Java 6 at least. That shouldn't be too much of a problem, as Java 5 is long EOLed * There are no published jasper-jdt artifacts for Tomcat 7. Not sure why that is, I need to look a bit deeper SLING2094Test and ServerSideScriptsTest fail with java 8: JSP compiler does not find java.util.Arrays or java.lang.CharSequence --- Key: SLING-3405 URL: https://issues.apache.org/jira/browse/SLING-3405 Project: Sling Issue Type: Bug Components: Scripting, Testing Reporter: Bertrand Delacretaz Priority: Minor Attachments: jasper-upgrade.patch Running the launchpad/integration-tests SLING2094Test fails due to a compilation error for the test script [1]: Unable to compile class for JSP, the import java.util.Arrays cannot be resolved. [1] https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/resources/integration-test/issues/sling2094/sling2094.jsp -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3405) SLING2094Test and ServerSideScriptsTest fail with java 8: JSP compiler does not find java.util.Arrays or java.lang.CharSequence
[
https://issues.apache.org/jira/browse/SLING-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960021#comment-13960021
]
Robert Munteanu commented on SLING-3405:
{quote}I have been thinking of actually removing the Java Compiler from both
the JSP and the Compiler support bundles and just install the Eclipse JDT
compiler bundle in Sling. WDYT ?{quote}
That sounds good to me. The jsp scripting support bundle should keep working,
as the JDT bundle has changed in a compatible way ( still at 3.x ).
SLING2094Test and ServerSideScriptsTest fail with java 8: JSP compiler does
not find java.util.Arrays or java.lang.CharSequence
---
Key: SLING-3405
URL: https://issues.apache.org/jira/browse/SLING-3405
Project: Sling
Issue Type: Bug
Components: Scripting, Testing
Reporter: Bertrand Delacretaz
Priority: Minor
Attachments: jasper-upgrade.patch
Running the launchpad/integration-tests SLING2094Test fails due to a
compilation error for the test script [1]: Unable to compile class for JSP,
the import java.util.Arrays cannot be resolved.
[1]
https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/resources/integration-test/issues/sling2094/sling2094.jsp
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (SLING-3494) Launchpad Testing WAR tests fail due to a CNFE
Robert Munteanu created SLING-3494: -- Summary: Launchpad Testing WAR tests fail due to a CNFE Key: SLING-3494 URL: https://issues.apache.org/jira/browse/SLING-3494 Project: Sling Issue Type: Bug Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Launchpad Testing 7 --- T E S T S --- Running org.apache.sling.launchpad.testing.TestAll Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.579 sec FAILURE! initializationError(org.apache.sling.launchpad.testing.TestAll) Time elapsed: 0.007 sec ERROR! java.lang.NoClassDefFoundError: org/apache/sling/commons/testing/integration/HttpTest at java.lang.ClassLoader.defineClass1(Native Method) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3494) Launchpad Testing WAR tests fail due to a CNFE
[ https://issues.apache.org/jira/browse/SLING-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3494. Resolution: Fixed Fixed in http://svn.apache.org/r1584906 Launchpad Testing WAR tests fail due to a CNFE -- Key: SLING-3494 URL: https://issues.apache.org/jira/browse/SLING-3494 Project: Sling Issue Type: Bug Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Launchpad Testing 7 --- T E S T S --- Running org.apache.sling.launchpad.testing.TestAll Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.579 sec FAILURE! initializationError(org.apache.sling.launchpad.testing.TestAll) Time elapsed: 0.007 sec ERROR! java.lang.NoClassDefFoundError: org/apache/sling/commons/testing/integration/HttpTest at java.lang.ClassLoader.defineClass1(Native Method) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-920) Sling Jenkins setup
[ https://issues.apache.org/jira/browse/SLING-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13961218#comment-13961218 ] Robert Munteanu commented on SLING-920: --- Updated all Sling jobs to use Maven 3.0.5 . This seems to fix SVN polling for now ( see INFRA-7536 ). Sling Jenkins setup --- Key: SLING-920 URL: https://issues.apache.org/jira/browse/SLING-920 Project: Sling Issue Type: Task Components: Testing Reporter: Bertrand Delacretaz Use this issue to record changes to the Hudson continuous environment setup at http://hudson.zones.apache.org/hudson/view/Sling/ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SLING-3495) TopologyTest.testLargeTopologyWithHub failures on Jenkins
Robert Munteanu created SLING-3495: -- Summary: TopologyTest.testLargeTopologyWithHub failures on Jenkins Key: SLING-3495 URL: https://issues.apache.org/jira/browse/SLING-3495 Project: Sling Issue Type: Bug Components: Extensions Reporter: Robert Munteanu TopologyTest.testLargeTopologyWithHub has failed in the last testing run for both sling-trunk-1.6 and sling-trunk-1.7 . The errors are -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3495) TopologyTest.testLargeTopologyWithHub failures on Jenkins
[ https://issues.apache.org/jira/browse/SLING-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3495: --- Attachment: TopologyTest.testLargeTopologyWithHub-failure-sling-trunk-1.7.txt TopologyTest.testLargeTopologyWithHub-failure-sling-trunk-1.6.txt TopologyTest.testLargeTopologyWithHub failures on Jenkins - Key: SLING-3495 URL: https://issues.apache.org/jira/browse/SLING-3495 Project: Sling Issue Type: Bug Components: Extensions Reporter: Robert Munteanu Attachments: TopologyTest.testLargeTopologyWithHub-failure-sling-trunk-1.6.txt, TopologyTest.testLargeTopologyWithHub-failure-sling-trunk-1.7.txt TopologyTest.testLargeTopologyWithHub has failed in the last testing run for both sling-trunk-1.6 and sling-trunk-1.7 . The errors are -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3495) TopologyTest.testLargeTopologyWithHub failures on Jenkins
[ https://issues.apache.org/jira/browse/SLING-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3495: --- Description: TopologyTest.testLargeTopologyWithHub has failed in the last testing run for both sling-trunk-1.6 [1] and sling-trunk-1.7 [2] . The errors are attached, in case the build results will expire. [1]: https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/lastBuild/org.apache.sling$org.apache.sling.discovery.impl/testReport/org.apache.sling.discovery.impl.topology/TopologyTest/testLargeTopologyWithHub/ [2]: https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/lastBuild/org.apache.sling$org.apache.sling.discovery.impl/testReport/org.apache.sling.discovery.impl.topology/TopologyTest/testLargeTopologyWithHub/ was: TopologyTest.testLargeTopologyWithHub has failed in the last testing run for both sling-trunk-1.6 ( [build 2086|https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/lastBuild/org.apache.sling$org.apache.sling.discovery.impl/testReport/org.apache.sling.discovery.impl.topology/TopologyTest/testLargeTopologyWithHub/] ) and sling-trunk-1.7 ( [build 457|https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/lastBuild/org.apache.sling$org.apache.sling.discovery.impl/testReport/org.apache.sling.discovery.impl.topology/TopologyTest/testLargeTopologyWithHub/] ) . The errors are attached, in case the build results will expire. TopologyTest.testLargeTopologyWithHub failures on Jenkins - Key: SLING-3495 URL: https://issues.apache.org/jira/browse/SLING-3495 Project: Sling Issue Type: Bug Components: Extensions Reporter: Robert Munteanu Attachments: TopologyTest.testLargeTopologyWithHub-failure-sling-trunk-1.6.txt, TopologyTest.testLargeTopologyWithHub-failure-sling-trunk-1.7.txt TopologyTest.testLargeTopologyWithHub has failed in the last testing run for both sling-trunk-1.6 [1] and sling-trunk-1.7 [2] . The errors are attached, in case the build results will expire. [1]: https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/lastBuild/org.apache.sling$org.apache.sling.discovery.impl/testReport/org.apache.sling.discovery.impl.topology/TopologyTest/testLargeTopologyWithHub/ [2]: https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/lastBuild/org.apache.sling$org.apache.sling.discovery.impl/testReport/org.apache.sling.discovery.impl.topology/TopologyTest/testLargeTopologyWithHub/ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3495) TopologyTest.testLargeTopologyWithHub failures on Jenkins
[ https://issues.apache.org/jira/browse/SLING-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3495: --- Description: TopologyTest.testLargeTopologyWithHub has failed in the last testing run for both sling-trunk-1.6 ( [build 2086|https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/lastBuild/org.apache.sling$org.apache.sling.discovery.impl/testReport/org.apache.sling.discovery.impl.topology/TopologyTest/testLargeTopologyWithHub/] ) and sling-trunk-1.7 ( [build 457|https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/lastBuild/org.apache.sling$org.apache.sling.discovery.impl/testReport/org.apache.sling.discovery.impl.topology/TopologyTest/testLargeTopologyWithHub/] ) . The errors are attached, in case the build results will expire. was: TopologyTest.testLargeTopologyWithHub has failed in the last testing run for both sling-trunk-1.6 and sling-trunk-1.7 . The errors are TopologyTest.testLargeTopologyWithHub failures on Jenkins - Key: SLING-3495 URL: https://issues.apache.org/jira/browse/SLING-3495 Project: Sling Issue Type: Bug Components: Extensions Reporter: Robert Munteanu Attachments: TopologyTest.testLargeTopologyWithHub-failure-sling-trunk-1.6.txt, TopologyTest.testLargeTopologyWithHub-failure-sling-trunk-1.7.txt TopologyTest.testLargeTopologyWithHub has failed in the last testing run for both sling-trunk-1.6 ( [build 2086|https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/lastBuild/org.apache.sling$org.apache.sling.discovery.impl/testReport/org.apache.sling.discovery.impl.topology/TopologyTest/testLargeTopologyWithHub/] ) and sling-trunk-1.7 ( [build 457|https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/lastBuild/org.apache.sling$org.apache.sling.discovery.impl/testReport/org.apache.sling.discovery.impl.topology/TopologyTest/testLargeTopologyWithHub/] ) . The errors are attached, in case the build results will expire. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3495) TopologyTest.testLargeTopologyWithHub failures on Jenkins
[ https://issues.apache.org/jira/browse/SLING-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3495: --- Affects Version/s: Discovery Impl 1.0.6 TopologyTest.testLargeTopologyWithHub failures on Jenkins - Key: SLING-3495 URL: https://issues.apache.org/jira/browse/SLING-3495 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Discovery Impl 1.0.6 Reporter: Robert Munteanu Attachments: TopologyTest.testLargeTopologyWithHub-failure-sling-trunk-1.6.txt, TopologyTest.testLargeTopologyWithHub-failure-sling-trunk-1.7.txt TopologyTest.testLargeTopologyWithHub has failed in the last testing run for both sling-trunk-1.6 [1] and sling-trunk-1.7 [2] . The errors are attached, in case the build results will expire. [1]: https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/lastBuild/org.apache.sling$org.apache.sling.discovery.impl/testReport/org.apache.sling.discovery.impl.topology/TopologyTest/testLargeTopologyWithHub/ [2]: https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/lastBuild/org.apache.sling$org.apache.sling.discovery.impl/testReport/org.apache.sling.discovery.impl.topology/TopologyTest/testLargeTopologyWithHub/ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SLING-3515) New sling bundle project wizard fails - java.lang.NoSuchMethodError
Robert Munteanu created SLING-3515: -- Summary: New sling bundle project wizard fails - java.lang.NoSuchMethodError Key: SLING-3515 URL: https://issues.apache.org/jira/browse/SLING-3515 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Priority: Critical Fix For: Sling Eclipse IDE 1.0.0 I think this is related to m2e/Maven runtime changes. I'm using m2e 1.5.0 with embedded Maven 3.2.1 . -- Error Details -- Date: Thu Apr 24 14:26:16 EEST 2014 Message: org.apache.maven.DefaultMaven.newRepositorySession(Lorg/apache/maven/execution/MavenExecutionRequest;)Lorg/sonatype/aether/RepositorySystemSession; Severity: Error Product: Eclipse 2.0.2.20140224- (org.eclipse.epp.package.java.product) Plugin: org.apache.sling.ide.eclipse-m2e-ui Session Data: eclipse.buildId=4.3.2.M20140221-1700 java.version=1.7.0_51 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.java.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.java.product Exception Stack Trace: java.lang.NoSuchMethodError: org.apache.maven.DefaultMaven.newRepositorySession(Lorg/apache/maven/execution/MavenExecutionRequest;)Lorg/sonatype/aether/RepositorySystemSession; at org.apache.sling.ide.eclipse.m2e.EmbeddedArchetypeInstaller.installArchetype(EmbeddedArchetypeInstaller.java:108) at org.apache.sling.ide.eclipse.ui.wizards.np.NewSlingBundleWizard.installArchetypes(NewSlingBundleWizard.java:57) at org.apache.sling.ide.eclipse.ui.wizards.np.ChooseArchetypeWizardPage$6.run(ChooseArchetypeWizardPage.java:204) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3102) Inconsistent behaviour when loading archetypes in new Sling bundle project wizard
[ https://issues.apache.org/jira/browse/SLING-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3102. Resolution: Fixed Fixed in http://svn.apache.org/viewvc?view=revisionrevision=1589686 Inconsistent behaviour when loading archetypes in new Sling bundle project wizard - Key: SLING-3102 URL: https://issues.apache.org/jira/browse/SLING-3102 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 The archetype selection wizard has an inconsistent behaviour - sometimes only the 'embedded' archetype is shown - sometimes the 'embedded' archetype and the 1.0 versions are shown However, I can't get the 1.0.1-SNAPSHOT archetype version, which is supposedly installed by us, to show. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3515) New sling bundle project wizard fails - java.lang.NoSuchMethodError
[ https://issues.apache.org/jira/browse/SLING-3515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3515: --- Assignee: Robert Munteanu New sling bundle project wizard fails - java.lang.NoSuchMethodError --- Key: SLING-3515 URL: https://issues.apache.org/jira/browse/SLING-3515 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Priority: Critical Fix For: Sling Eclipse IDE 1.0.0 I think this is related to m2e/Maven runtime changes. I'm using m2e 1.5.0 with embedded Maven 3.2.1 . -- Error Details -- Date: Thu Apr 24 14:26:16 EEST 2014 Message: org.apache.maven.DefaultMaven.newRepositorySession(Lorg/apache/maven/execution/MavenExecutionRequest;)Lorg/sonatype/aether/RepositorySystemSession; Severity: Error Product: Eclipse 2.0.2.20140224- (org.eclipse.epp.package.java.product) Plugin: org.apache.sling.ide.eclipse-m2e-ui Session Data: eclipse.buildId=4.3.2.M20140221-1700 java.version=1.7.0_51 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.java.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.java.product Exception Stack Trace: java.lang.NoSuchMethodError: org.apache.maven.DefaultMaven.newRepositorySession(Lorg/apache/maven/execution/MavenExecutionRequest;)Lorg/sonatype/aether/RepositorySystemSession; at org.apache.sling.ide.eclipse.m2e.EmbeddedArchetypeInstaller.installArchetype(EmbeddedArchetypeInstaller.java:108) at org.apache.sling.ide.eclipse.ui.wizards.np.NewSlingBundleWizard.installArchetypes(NewSlingBundleWizard.java:57) at org.apache.sling.ide.eclipse.ui.wizards.np.ChooseArchetypeWizardPage$6.run(ChooseArchetypeWizardPage.java:204) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SLING-3520) Consolidate archetype plugin versions in a parent pom
Robert Munteanu created SLING-3520: -- Summary: Consolidate archetype plugin versions in a parent pom Key: SLING-3520 URL: https://issues.apache.org/jira/browse/SLING-3520 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Reporter: Robert Munteanu Assignee: Robert Munteanu Currently all plugin versions used in generated archetypes are maintained in each pom. This makes it difficult to update the used versions, and many archetypes now have outdated plugin versions. To make maintenance easier, we should create an archetype parent which centralises these settings. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3520) Consolidate archetype plugin versions in a parent pom
[ https://issues.apache.org/jira/browse/SLING-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3520: --- Attachment: SLING-3520-1.patch Attached a [^proposed patch|SLING-3520-1.patch] which shows how this can be done for a the bundle archetype. If this is agreed on, I will extend this approach for all archetypes and all interesting plugin versions and cut a first release of the archetype parent pom. Consolidate archetype plugin versions in a parent pom - Key: SLING-3520 URL: https://issues.apache.org/jira/browse/SLING-3520 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Reporter: Robert Munteanu Assignee: Robert Munteanu Attachments: SLING-3520-1.patch Currently all plugin versions used in generated archetypes are maintained in each pom. This makes it difficult to update the used versions, and many archetypes now have outdated plugin versions. To make maintenance easier, we should create an archetype parent which centralises these settings. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (SLING-3520) Consolidate archetype plugin versions in a parent pom
[ https://issues.apache.org/jira/browse/SLING-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13980782#comment-13980782 ] Robert Munteanu edited comment on SLING-3520 at 4/25/14 8:03 AM: - Attached [^SLING-3520-1.patch] which shows how this can be done for the bundle archetype. If this is agreed on, I will extend this approach for all archetypes and all interesting plugin versions and cut a first release of the archetype parent pom. _Edit_: fix link to attachment was (Author: rombert): Attached a [^proposed patch|SLING-3520-1.patch] which shows how this can be done for a the bundle archetype. If this is agreed on, I will extend this approach for all archetypes and all interesting plugin versions and cut a first release of the archetype parent pom. Consolidate archetype plugin versions in a parent pom - Key: SLING-3520 URL: https://issues.apache.org/jira/browse/SLING-3520 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Reporter: Robert Munteanu Assignee: Robert Munteanu Attachments: SLING-3520-1.patch Currently all plugin versions used in generated archetypes are maintained in each pom. This makes it difficult to update the used versions, and many archetypes now have outdated plugin versions. To make maintenance easier, we should create an archetype parent which centralises these settings. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3515) New sling bundle project wizard fails - java.lang.NoSuchMethodError
[ https://issues.apache.org/jira/browse/SLING-3515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3515. Resolution: Fixed Fixed in http://svn.apache.org/viewvc?view=revisionrevision=1589998 Additional cleanups in http://svn.apache.org/viewvc?view=revisionrevision=158 The code is really ugly now, using reflection. If/when we decide to drop Maven 3.0.x support, we can clean this up. New sling bundle project wizard fails - java.lang.NoSuchMethodError --- Key: SLING-3515 URL: https://issues.apache.org/jira/browse/SLING-3515 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Priority: Critical Fix For: Sling Eclipse IDE 1.0.0 I think this is related to m2e/Maven runtime changes. I'm using m2e 1.5.0 with embedded Maven 3.2.1 . -- Error Details -- Date: Thu Apr 24 14:26:16 EEST 2014 Message: org.apache.maven.DefaultMaven.newRepositorySession(Lorg/apache/maven/execution/MavenExecutionRequest;)Lorg/sonatype/aether/RepositorySystemSession; Severity: Error Product: Eclipse 2.0.2.20140224- (org.eclipse.epp.package.java.product) Plugin: org.apache.sling.ide.eclipse-m2e-ui Session Data: eclipse.buildId=4.3.2.M20140221-1700 java.version=1.7.0_51 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.java.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.java.product Exception Stack Trace: java.lang.NoSuchMethodError: org.apache.maven.DefaultMaven.newRepositorySession(Lorg/apache/maven/execution/MavenExecutionRequest;)Lorg/sonatype/aether/RepositorySystemSession; at org.apache.sling.ide.eclipse.m2e.EmbeddedArchetypeInstaller.installArchetype(EmbeddedArchetypeInstaller.java:108) at org.apache.sling.ide.eclipse.ui.wizards.np.NewSlingBundleWizard.installArchetypes(NewSlingBundleWizard.java:57) at org.apache.sling.ide.eclipse.ui.wizards.np.ChooseArchetypeWizardPage$6.run(ChooseArchetypeWizardPage.java:204) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SLING-3159) Never try to install bundles if the support bundle is not installed
[ https://issues.apache.org/jira/browse/SLING-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-3159: -- Assignee: Robert Munteanu Never try to install bundles if the support bundle is not installed --- Key: SLING-3159 URL: https://issues.apache.org/jira/browse/SLING-3159 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Priority: Critical Fix For: Sling Eclipse IDE 1.0.0 As a user, if I check 'Install bundles directly from local directory' but do not install the support bundle, when trying to deploy I bundle I get a success message ( the POST is successful ) but the bundle is not deployed. I only get a hint on the servers view that the status is 404. I should be prompted that the support bundle is not installed and asked to install it. Or maybe the bundle should be automatically installed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3520) Consolidate archetype plugin versions in a parent pom
[ https://issues.apache.org/jira/browse/SLING-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13984203#comment-13984203 ] Robert Munteanu commented on SLING-3520: Attached a second revision of the patch, which makes minimal changes to the archetype to make it build with no warnings. Consolidate archetype plugin versions in a parent pom - Key: SLING-3520 URL: https://issues.apache.org/jira/browse/SLING-3520 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Reporter: Robert Munteanu Assignee: Robert Munteanu Attachments: SLING-3520-1.patch, SLING-3520-2.patch Currently all plugin versions used in generated archetypes are maintained in each pom. This makes it difficult to update the used versions, and many archetypes now have outdated plugin versions. To make maintenance easier, we should create an archetype parent which centralises these settings. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3520) Consolidate archetype plugin versions in a parent pom
[ https://issues.apache.org/jira/browse/SLING-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3520: --- Attachment: SLING-3520-2.patch Consolidate archetype plugin versions in a parent pom - Key: SLING-3520 URL: https://issues.apache.org/jira/browse/SLING-3520 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Reporter: Robert Munteanu Assignee: Robert Munteanu Attachments: SLING-3520-1.patch, SLING-3520-2.patch Currently all plugin versions used in generated archetypes are maintained in each pom. This makes it difficult to update the used versions, and many archetypes now have outdated plugin versions. To make maintenance easier, we should create an archetype parent which centralises these settings. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SLING-3530) Update plugin versions used by the Maven archetypes
Robert Munteanu created SLING-3530: -- Summary: Update plugin versions used by the Maven archetypes Key: SLING-3530 URL: https://issues.apache.org/jira/browse/SLING-3530 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Initial Content Archetype 1.0.0, Launchpad Standalone Archetype 1.0.0, Launchpad Webapp Archetype 1.0.0, Servlet Archetype 1.0.0, Bundle Archetype 1.0.0, JCRInstall Bundle Archetype 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu Plugin version changes scr plugin : 1.13.0 - 1.16.0 bundle plugin : 2.0.1 - 2.4.0 compiler plugin: 2.3.2 - 3.1 sling plugin : 2.0.4-incubator - 2.1.0 launchpad plugin: 2.0.10 - 2.3.0 Dependency version changes scr annotations: 1.9.0 - 1.9.8 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3530) Update plugin versions used by the Maven archetypes
[ https://issues.apache.org/jira/browse/SLING-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3530: --- Fix Version/s: Initial Content Archetype 1.0.2 Servlet Archetype 1.0.2 Update plugin versions used by the Maven archetypes --- Key: SLING-3530 URL: https://issues.apache.org/jira/browse/SLING-3530 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Servlet Archetype 1.0.0, Bundle Archetype 1.0.0, JCRInstall Bundle Archetype 1.0.0, Launchpad Webapp Archetype 1.0.0, Launchpad Standalone Archetype 1.0.0, Initial Content Archetype 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Servlet Archetype 1.0.2, Initial Content Archetype 1.0.2 Plugin version changes scr plugin : 1.13.0 - 1.16.0 bundle plugin : 2.0.1 - 2.4.0 compiler plugin: 2.3.2 - 3.1 sling plugin : 2.0.4-incubator - 2.1.0 launchpad plugin: 2.0.10 - 2.3.0 Dependency version changes scr annotations: 1.9.0 - 1.9.8 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3530) Update plugin versions used by the Maven archetypes
[ https://issues.apache.org/jira/browse/SLING-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3530. Resolution: Fixed Parent pom updated in http://svn.apache.org/viewvc?view=revisionrevision=1591296 Update plugin versions used by the Maven archetypes --- Key: SLING-3530 URL: https://issues.apache.org/jira/browse/SLING-3530 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Servlet Archetype 1.0.0, Bundle Archetype 1.0.0, JCRInstall Bundle Archetype 1.0.0, Launchpad Webapp Archetype 1.0.0, Launchpad Standalone Archetype 1.0.0, Initial Content Archetype 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Servlet Archetype 1.0.2, Initial Content Archetype 1.0.2 Plugin version changes scr plugin : 1.13.0 - 1.16.0 bundle plugin : 2.0.1 - 2.4.0 compiler plugin: 2.3.2 - 3.1 sling plugin : 2.0.4-incubator - 2.1.0 launchpad plugin: 2.0.10 - 2.3.0 Dependency version changes scr annotations: 1.9.0 - 1.9.8 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SLING-3531) Update java version used by archetypes to 6
Robert Munteanu created SLING-3531: -- Summary: Update java version used by archetypes to 6 Key: SLING-3531 URL: https://issues.apache.org/jira/browse/SLING-3531 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Servlet Archetype 1.0.0, Bundle Archetype 1.0.0, JCRInstall Bundle Archetype 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Servlet Archetype 1.0.2 The java-based archetypes use Java 5 by default. Moving to Java 6 is a safe move for all consumers. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3531) Update java version used by archetypes to 6
[ https://issues.apache.org/jira/browse/SLING-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3531. Resolution: Fixed Fixed in http://svn.apache.org/viewvc?view=revisionrevision=1591305 Update java version used by archetypes to 6 --- Key: SLING-3531 URL: https://issues.apache.org/jira/browse/SLING-3531 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Servlet Archetype 1.0.0, Bundle Archetype 1.0.0, JCRInstall Bundle Archetype 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Servlet Archetype 1.0.2 The java-based archetypes use Java 5 by default. Moving to Java 6 is a safe move for all consumers. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SLING-3532) Move sling plugin configuration out of the autoInstallBundle profile
Robert Munteanu created SLING-3532: -- Summary: Move sling plugin configuration out of the autoInstallBundle profile Key: SLING-3532 URL: https://issues.apache.org/jira/browse/SLING-3532 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Servlet Archetype 1.0.0, Bundle Archetype 1.0.0, JCRInstall Bundle Archetype 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Servlet Archetype 1.0.2 The maven-sling-plugin is configured completely inside a profile block. This means that it's not available for 'regular' executions, e.g. mvn sling:install . The fix is simple - move the plugin configuration to the plugins section, and only bind the execution in the profile. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3532) Move sling plugin configuration out of the autoInstallBundle profile
[ https://issues.apache.org/jira/browse/SLING-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3532: --- Fix Version/s: JCRInstall Bundle Archetype 1.0.2 Bundle Archetype 1.0.2 Move sling plugin configuration out of the autoInstallBundle profile Key: SLING-3532 URL: https://issues.apache.org/jira/browse/SLING-3532 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Servlet Archetype 1.0.0, Bundle Archetype 1.0.0, JCRInstall Bundle Archetype 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Servlet Archetype 1.0.2, Bundle Archetype 1.0.2, JCRInstall Bundle Archetype 1.0.2 The maven-sling-plugin is configured completely inside a profile block. This means that it's not available for 'regular' executions, e.g. mvn sling:install . The fix is simple - move the plugin configuration to the plugins section, and only bind the execution in the profile. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3531) Update java version used by archetypes to 6
[ https://issues.apache.org/jira/browse/SLING-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3531: --- Fix Version/s: JCRInstall Bundle Archetype 1.0.2 Bundle Archetype 1.0.2 Update java version used by archetypes to 6 --- Key: SLING-3531 URL: https://issues.apache.org/jira/browse/SLING-3531 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Servlet Archetype 1.0.0, Bundle Archetype 1.0.0, JCRInstall Bundle Archetype 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Servlet Archetype 1.0.2, Bundle Archetype 1.0.2, JCRInstall Bundle Archetype 1.0.2 The java-based archetypes use Java 5 by default. Moving to Java 6 is a safe move for all consumers. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3531) Update java version used by archetypes to 6
[ https://issues.apache.org/jira/browse/SLING-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3531: --- Fix Version/s: Archetype Parent Version 1 Update java version used by archetypes to 6 --- Key: SLING-3531 URL: https://issues.apache.org/jira/browse/SLING-3531 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Servlet Archetype 1.0.0, Bundle Archetype 1.0.0, JCRInstall Bundle Archetype 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Servlet Archetype 1.0.2, Bundle Archetype 1.0.2, JCRInstall Bundle Archetype 1.0.2, Archetype Parent Version 1 The java-based archetypes use Java 5 by default. Moving to Java 6 is a safe move for all consumers. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3520) Consolidate archetype plugin versions in a parent pom
[ https://issues.apache.org/jira/browse/SLING-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3520: --- Fix Version/s: Archetype Parent Version 1 Consolidate archetype plugin versions in a parent pom - Key: SLING-3520 URL: https://issues.apache.org/jira/browse/SLING-3520 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Archetype Parent Version 1 Attachments: SLING-3520-1.patch, SLING-3520-2.patch Currently all plugin versions used in generated archetypes are maintained in each pom. This makes it difficult to update the used versions, and many archetypes now have outdated plugin versions. To make maintenance easier, we should create an archetype parent which centralises these settings. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3520) Consolidate archetype plugin versions in a parent pom
[ https://issues.apache.org/jira/browse/SLING-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985592#comment-13985592 ] Robert Munteanu commented on SLING-3520: Added first cut of the parent pom at http://svn.apache.org/viewvc?view=revisionrevision=1591280 Consolidate archetype plugin versions in a parent pom - Key: SLING-3520 URL: https://issues.apache.org/jira/browse/SLING-3520 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Archetype Parent Version 1 Attachments: SLING-3520-1.patch, SLING-3520-2.patch Currently all plugin versions used in generated archetypes are maintained in each pom. This makes it difficult to update the used versions, and many archetypes now have outdated plugin versions. To make maintenance easier, we should create an archetype parent which centralises these settings. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3530) Update plugin versions used by the Maven archetypes
[ https://issues.apache.org/jira/browse/SLING-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3530: --- Fix Version/s: Archetype Parent Version 1 Launchpad Standalone Archetype 1.0.2 Launchpad Webapp Archetype 1.0.2 JCRInstall Bundle Archetype 1.0.2 Bundle Archetype 1.0.2 Update plugin versions used by the Maven archetypes --- Key: SLING-3530 URL: https://issues.apache.org/jira/browse/SLING-3530 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Servlet Archetype 1.0.0, Bundle Archetype 1.0.0, JCRInstall Bundle Archetype 1.0.0, Launchpad Webapp Archetype 1.0.0, Launchpad Standalone Archetype 1.0.0, Initial Content Archetype 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Servlet Archetype 1.0.2, Bundle Archetype 1.0.2, JCRInstall Bundle Archetype 1.0.2, Launchpad Webapp Archetype 1.0.2, Launchpad Standalone Archetype 1.0.2, Initial Content Archetype 1.0.2, Archetype Parent Version 1 Plugin version changes scr plugin : 1.13.0 - 1.16.0 bundle plugin : 2.0.1 - 2.4.0 compiler plugin: 2.3.2 - 3.1 sling plugin : 2.0.4-incubator - 2.1.0 launchpad plugin: 2.0.10 - 2.3.0 Dependency version changes scr annotations: 1.9.0 - 1.9.8 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (SLING-3531) Update java version used by archetypes to 6
[ https://issues.apache.org/jira/browse/SLING-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985561#comment-13985561 ] Robert Munteanu edited comment on SLING-3531 at 4/30/14 3:01 PM: - Fixed in http://svn.apache.org/viewvc?view=revisionrevision=1591330 was (Author: rombert): Fixed in http://svn.apache.org/viewvc?view=revisionrevision=1591305 Update java version used by archetypes to 6 --- Key: SLING-3531 URL: https://issues.apache.org/jira/browse/SLING-3531 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Servlet Archetype 1.0.0, Bundle Archetype 1.0.0, JCRInstall Bundle Archetype 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Servlet Archetype 1.0.2, Bundle Archetype 1.0.2, JCRInstall Bundle Archetype 1.0.2, Archetype Parent Version 1 The java-based archetypes use Java 5 by default. Moving to Java 6 is a safe move for all consumers. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3520) Consolidate archetype plugin versions in a parent pom
[ https://issues.apache.org/jira/browse/SLING-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3520. Resolution: Fixed Archetype projects will be fixed in a follow-up commit, marking this as done for the release. Consolidate archetype plugin versions in a parent pom - Key: SLING-3520 URL: https://issues.apache.org/jira/browse/SLING-3520 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Archetype Parent Version 1 Attachments: SLING-3520-1.patch, SLING-3520-2.patch Currently all plugin versions used in generated archetypes are maintained in each pom. This makes it difficult to update the used versions, and many archetypes now have outdated plugin versions. To make maintenance easier, we should create an archetype parent which centralises these settings. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3538) Maven archetypes should use the same port as the default launchpad port
[ https://issues.apache.org/jira/browse/SLING-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3538. Resolution: Fixed Fixed in http://svn.apache.org/viewvc?view=revisionrevision=1591859 Maven archetypes should use the same port as the default launchpad port --- Key: SLING-3538 URL: https://issues.apache.org/jira/browse/SLING-3538 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Servlet Archetype 1.0.0, Bundle Archetype 1.0.0, JCRInstall Bundle Archetype 1.0.0, Initial Content Archetype 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Servlet Archetype 1.0.2, Bundle Archetype 1.0.2, JCRInstall Bundle Archetype 1.0.2, Initial Content Archetype 1.0.2 The Maven archetypes should be usable out-of-the-box with a Sling launchpad. Right now deploying archetypes fails since the maven-sling-plugin is configured with port - which we typically use for integration tests - but the sling launchpad start by default on port 8080. I think more people would use port 8080 rather than , so we should use that in our archetypes by default. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SLING-3539) SimpleDSComponent from archetypes does nothing by default
Robert Munteanu created SLING-3539: -- Summary: SimpleDSComponent from archetypes does nothing by default Key: SLING-3539 URL: https://issues.apache.org/jira/browse/SLING-3539 Project: Sling Issue Type: Bug Components: Maven Plugins and Archetypes Affects Versions: JCRInstall Bundle Archetype 1.0.0, Bundle Archetype 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Bundle Archetype 1.0.2, JCRInstall Bundle Archetype 1.0.2 The SimpleDSComponent generated by the bundle archetypes is registered as a Runnable, but it is not immediate. Therefore, it is never invoked. Since using immediate components is not a good practice, I'll change the components to be scheduled jobs, so that they actually output something in the log. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3539) SimpleDSComponent from archetypes does nothing by default
[ https://issues.apache.org/jira/browse/SLING-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3539. Resolution: Fixed Fixed in http://svn.apache.org/viewvc?view=revisionrevision=1591865 SimpleDSComponent from archetypes does nothing by default - Key: SLING-3539 URL: https://issues.apache.org/jira/browse/SLING-3539 Project: Sling Issue Type: Bug Components: Maven Plugins and Archetypes Affects Versions: Bundle Archetype 1.0.0, JCRInstall Bundle Archetype 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Bundle Archetype 1.0.2, JCRInstall Bundle Archetype 1.0.2 The SimpleDSComponent generated by the bundle archetypes is registered as a Runnable, but it is not immediate. Therefore, it is never invoked. Since using immediate components is not a good practice, I'll change the components to be scheduled jobs, so that they actually output something in the log. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3532) Move sling plugin configuration out of the autoInstallBundle profile
[ https://issues.apache.org/jira/browse/SLING-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3532: --- Affects Version/s: Initial Content Archetype 1.0.0 Fix Version/s: Initial Content Archetype 1.0.2 Move sling plugin configuration out of the autoInstallBundle profile Key: SLING-3532 URL: https://issues.apache.org/jira/browse/SLING-3532 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Servlet Archetype 1.0.0, Bundle Archetype 1.0.0, JCRInstall Bundle Archetype 1.0.0, Initial Content Archetype 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Servlet Archetype 1.0.2, Bundle Archetype 1.0.2, JCRInstall Bundle Archetype 1.0.2, Initial Content Archetype 1.0.2 The maven-sling-plugin is configured completely inside a profile block. This means that it's not available for 'regular' executions, e.g. mvn sling:install . The fix is simple - move the plugin configuration to the plugins section, and only bind the execution in the profile. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3019) Provide a mechanism to install a bundle based on a directory
[
https://issues.apache.org/jira/browse/SLING-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-3019.
Resolution: Fixed
Fix Version/s: Tooling Support Install 1.0.0
I consider this fixed. We can always file follow-up issues if needed, but right
now I prefer closing and cutting a first release.
Provide a mechanism to install a bundle based on a directory
Key: SLING-3019
URL: https://issues.apache.org/jira/browse/SLING-3019
Project: Sling
Issue Type: New Feature
Components: IDE
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: Tooling Support Install 1.0.0
With an IDE integration and incremental builds, it would be great to have a
mechanism to install/update a bundle based on the output directory of a
project.
I'll start with a prototype of a bundle which receives post requests
containing the path of a local directory. The servlet will then either
install or update the bundle from that directory
For this to work, the scr descriptor files of a project should go into a
bundle. So configure the scr plugin like this:
plugin
groupIdorg.apache.felix/groupId
artifactIdmaven-scr-plugin/artifactId
configuration
outputDirectory${project.build.directory}/classes/outputDirectory
/configuration
/plugin
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (SLING-3540) JCR Install bundle plugin can not be installed on an out-of-the-box launchpad
Robert Munteanu created SLING-3540:
--
Summary: JCR Install bundle plugin can not be installed on an
out-of-the-box launchpad
Key: SLING-3540
URL: https://issues.apache.org/jira/browse/SLING-3540
Project: Sling
Issue Type: Bug
Components: Maven Plugins and Archetypes
Affects Versions: JCRInstall Bundle Archetype 1.0.0
Reporter: Robert Munteanu
{code}[INFO] Installing Bundle
com.example.jcrbundle(/home/rmuntean/tmp/jcrbundle/target/jcrbundle-1.0-SNAPSHOT.jar)
to http://localhost:8080/libs/sling/install via PUT
[ERROR] Installation failed, cause: Conflict{code}
The reason is that the default Sling launchpad does not have a
/libs/sling/install directory structure out of the box. The workaround is to
create it, e.g. with curl
{code}
curl -u admin:admin -X MKCOL http://localhost:8080/libs
curl -u admin:admin -X MKCOL http://localhost:8080/libs/sling
curl -u admin:admin -X MKCOL http://localhost:8080/libs/sling/install
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (SLING-3541) Standalone Launchpad Archetype fails to start due to random selection of jarWebSupport
Robert Munteanu created SLING-3541:
--
Summary: Standalone Launchpad Archetype fails to start due to
random selection of jarWebSupport
Key: SLING-3541
URL: https://issues.apache.org/jira/browse/SLING-3541
Project: Sling
Issue Type: Bug
Components: Maven Plugins and Archetypes
Affects Versions: Launchpad Standalone Archetype 1.0.0
Reporter: Robert Munteanu
Assignee: Robert Munteanu
Fix For: Launchpad Standalone Archetype 1.0.2
After generating an archetype it fails to start
{code}
[INFO] --- maven-launchpad-plugin:2.3.0:run (default-cli) @ launchpad ---
[INFO] Using bundle list file from
/home/ADOBENET/rmuntean/.m2/repository/org/apache/sling/org.apache.sling.launchpad/6/org.apache.sling.launchpad-6-bundlelist.xml
[INFO] HTTP server port: 8080
INFO: Command file absent or older than last execution timestamp, nothing to
execute (/home/ADOBENET/rmuntean/tmp/launchpad/sling/sling_bootstrap.txt)
INFO: Ignoring
/home/ADOBENET/rmuntean/tmp/launchpad/sling/startup/1/org.apache.sling.commons.log-2.1.2.jar:
More recent version already installed
INFO: Ignoring
/home/ADOBENET/rmuntean/tmp/launchpad/sling/startup/1/org.apache.felix.http.jetty-2.3.0-R1579739.jar:
More recent version already installed
INFO: Ignoring
/home/ADOBENET/rmuntean/tmp/launchpad/sling/startup/1/org.apache.felix.http.jetty-2.2.2.jar:
More recent version already installed
INFO: Using timestamp from
file:/home/ADOBENET/rmuntean/.m2/repository/org/apache/sling/maven-launchpad-plugin/2.3.0/maven-launchpad-plugin-2.3.0.jar.
INFO: Using timestamp from
file:/home/ADOBENET/rmuntean/.m2/repository/org/apache/sling/maven-launchpad-plugin/2.3.0/maven-launchpad-plugin-2.3.0.jar.
INFO: Using timestamp from
/home/ADOBENET/rmuntean/tmp/launchpad/sling/startup/1/org.apache.sling.commons.log-2.1.2.jar.
INFO: Final self timestamp: 1399037235000.
INFO: Started startup handler with target start level=35, and expected bundle
count=3
INFO: Startup progress 1/3
INFO: Startup progress 1/3
ERROR: Bundle org.apache.felix.http.jetty [2]: Error starting
slinginstall:org.apache.felix.http.jetty-2.3.0-R1579739.jar
(org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.felix.http.jetty [2]: Unable to resolve 2.0: missing requirement
[2.0] package; ((package=javax.servlet)(version=3.0.0)(!(version=4.0.0
org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.felix.http.jetty [2]: Unable to resolve 2.0: missing requirement
[2.0] package; ((package=javax.servlet)(version=3.0.0)(!(version=4.0.0)))
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3443)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1727)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1156)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:744)
{code}
We should set the org.apache.felix.http.jetty bundle version to the one
expected by the configured defaultBundleList.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (SLING-3541) Standalone Launchpad Archetype fails to start due to random selection of jarWebSupport
[
https://issues.apache.org/jira/browse/SLING-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-3541.
Resolution: Fixed
Fixed in http://svn.apache.org/viewvc?view=revisionrevision=1591905
Standalone Launchpad Archetype fails to start due to random selection of
jarWebSupport
--
Key: SLING-3541
URL: https://issues.apache.org/jira/browse/SLING-3541
Project: Sling
Issue Type: Bug
Components: Maven Plugins and Archetypes
Affects Versions: Launchpad Standalone Archetype 1.0.0
Reporter: Robert Munteanu
Assignee: Robert Munteanu
Fix For: Launchpad Standalone Archetype 1.0.2
After generating an archetype it fails to start
{code}
[INFO] --- maven-launchpad-plugin:2.3.0:run (default-cli) @ launchpad ---
[INFO] Using bundle list file from
/home/ADOBENET/rmuntean/.m2/repository/org/apache/sling/org.apache.sling.launchpad/6/org.apache.sling.launchpad-6-bundlelist.xml
[INFO] HTTP server port: 8080
INFO: Command file absent or older than last execution timestamp, nothing to
execute (/home/ADOBENET/rmuntean/tmp/launchpad/sling/sling_bootstrap.txt)
INFO: Ignoring
/home/ADOBENET/rmuntean/tmp/launchpad/sling/startup/1/org.apache.sling.commons.log-2.1.2.jar:
More recent version already installed
INFO: Ignoring
/home/ADOBENET/rmuntean/tmp/launchpad/sling/startup/1/org.apache.felix.http.jetty-2.3.0-R1579739.jar:
More recent version already installed
INFO: Ignoring
/home/ADOBENET/rmuntean/tmp/launchpad/sling/startup/1/org.apache.felix.http.jetty-2.2.2.jar:
More recent version already installed
INFO: Using timestamp from
file:/home/ADOBENET/rmuntean/.m2/repository/org/apache/sling/maven-launchpad-plugin/2.3.0/maven-launchpad-plugin-2.3.0.jar.
INFO: Using timestamp from
file:/home/ADOBENET/rmuntean/.m2/repository/org/apache/sling/maven-launchpad-plugin/2.3.0/maven-launchpad-plugin-2.3.0.jar.
INFO: Using timestamp from
/home/ADOBENET/rmuntean/tmp/launchpad/sling/startup/1/org.apache.sling.commons.log-2.1.2.jar.
INFO: Final self timestamp: 1399037235000.
INFO: Started startup handler with target start level=35, and expected bundle
count=3
INFO: Startup progress 1/3
INFO: Startup progress 1/3
ERROR: Bundle org.apache.felix.http.jetty [2]: Error starting
slinginstall:org.apache.felix.http.jetty-2.3.0-R1579739.jar
(org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.felix.http.jetty [2]: Unable to resolve 2.0: missing requirement
[2.0] package; ((package=javax.servlet)(version=3.0.0)(!(version=4.0.0
org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.felix.http.jetty [2]: Unable to resolve 2.0: missing requirement
[2.0] package; ((package=javax.servlet)(version=3.0.0)(!(version=4.0.0)))
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3443)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1727)
at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1156)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:744)
{code}
We should set the org.apache.felix.http.jetty bundle version to the one
expected by the configured defaultBundleList.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (SLING-3538) Maven archetypes should use the same port as the default launchpad port
[ https://issues.apache.org/jira/browse/SLING-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13987709#comment-13987709 ] Robert Munteanu commented on SLING-3538: Fixed IT for the servlet archetype in http://svn.apache.org/viewvc?view=revisionrevision=1591908 Maven archetypes should use the same port as the default launchpad port --- Key: SLING-3538 URL: https://issues.apache.org/jira/browse/SLING-3538 Project: Sling Issue Type: Improvement Components: Maven Plugins and Archetypes Affects Versions: Servlet Archetype 1.0.0, Bundle Archetype 1.0.0, JCRInstall Bundle Archetype 1.0.0, Initial Content Archetype 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Servlet Archetype 1.0.2, Bundle Archetype 1.0.2, JCRInstall Bundle Archetype 1.0.2, Initial Content Archetype 1.0.2 The Maven archetypes should be usable out-of-the-box with a Sling launchpad. Right now deploying archetypes fails since the maven-sling-plugin is configured with port - which we typically use for integration tests - but the sling launchpad start by default on port 8080. I think more people would use port 8080 rather than , so we should use that in our archetypes by default. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3540) JCR Install bundle plugin can not be installed on an out-of-the-box launchpad
[
https://issues.apache.org/jira/browse/SLING-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13987726#comment-13987726
]
Robert Munteanu commented on SLING-3540:
The discussion above seemed to be blocked at the point of whether we should use
webdav to create the intermediate nodes or the Sling Post Servlet. I for one
don't have a strong opinion ( we already use the WebDAV servlet when usePut is
true ), but if someone (still) thinks the distinction is important it would be
good to hear.
JCR Install bundle plugin can not be installed on an out-of-the-box launchpad
-
Key: SLING-3540
URL: https://issues.apache.org/jira/browse/SLING-3540
Project: Sling
Issue Type: Bug
Components: Maven Plugins and Archetypes
Affects Versions: JCRInstall Bundle Archetype 1.0.0
Reporter: Robert Munteanu
{code}[INFO] Installing Bundle
com.example.jcrbundle(/home/rmuntean/tmp/jcrbundle/target/jcrbundle-1.0-SNAPSHOT.jar)
to http://localhost:8080/libs/sling/install via PUT
[ERROR] Installation failed, cause: Conflict{code}
The reason is that the default Sling launchpad does not have a
/libs/sling/install directory structure out of the box. The workaround is to
create it, e.g. with curl
{code}
curl -u admin:admin -X MKCOL http://localhost:8080/libs
curl -u admin:admin -X MKCOL http://localhost:8080/libs/sling
curl -u admin:admin -X MKCOL http://localhost:8080/libs/sling/install
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (SLING-3054) Archetypes should use correct port
[ https://issues.apache.org/jira/browse/SLING-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3054: --- Component/s: (was: Maven Plugins and Archetypes) Documentation Assignee: Robert Munteanu Thanks for the patch! I've applied it partially, as I have already made some changes as part of SLING-3538, before noticing your patch. Archetypes should use correct port --- Key: SLING-3054 URL: https://issues.apache.org/jira/browse/SLING-3054 Project: Sling Issue Type: Bug Components: Documentation Reporter: Andrew Savory Assignee: Robert Munteanu Priority: Minor Attachments: SLING-3054.diff Based on http://sling.markmail.org/thread/pbgefv6kztbqxzt6 the preferred or expected port for Sling to run on is 8080. The archetypes by default set the port to which means that 'mvn -PautoInstallBundle install' on an archetype-generated project will fail. The fix is to update the archetypes to use the correct port. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3054) Archetypes should use correct port
[ https://issues.apache.org/jira/browse/SLING-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3054. Resolution: Fixed Archetypes should use correct port --- Key: SLING-3054 URL: https://issues.apache.org/jira/browse/SLING-3054 Project: Sling Issue Type: Bug Components: Documentation Reporter: Andrew Savory Assignee: Robert Munteanu Priority: Minor Attachments: SLING-3054.diff Based on http://sling.markmail.org/thread/pbgefv6kztbqxzt6 the preferred or expected port for Sling to run on is 8080. The archetypes by default set the port to which means that 'mvn -PautoInstallBundle install' on an archetype-generated project will fail. The fix is to update the archetypes to use the correct port. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SLING-3107) initial-content archetype does not reflect current practices
[ https://issues.apache.org/jira/browse/SLING-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-3107: -- Assignee: (was: Robert Munteanu) initial-content archetype does not reflect current practices Key: SLING-3107 URL: https://issues.apache.org/jira/browse/SLING-3107 Project: Sling Issue Type: Bug Components: Maven Plugins and Archetypes Affects Versions: Initial Content Archetype 1.0.2 Reporter: Andrew Savory Priority: Minor Attachments: SLING-3107.diff The initial content archetype has a number of deficiencies: - it uses xml rather than the more modern json format for content - the layout of initial projects doesn't match the most recent sample apps -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3159) Never try to install bundles if the support bundle is not installed
[ https://issues.apache.org/jira/browse/SLING-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3159. Resolution: Fixed Fixed in http://svn.apache.org/viewvc?view=revisionrevision=1592478 Never try to install bundles if the support bundle is not installed --- Key: SLING-3159 URL: https://issues.apache.org/jira/browse/SLING-3159 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Priority: Critical Fix For: Sling Eclipse IDE 1.0.0 As a user, if I check 'Install bundles directly from local directory' but do not install the support bundle, when trying to deploy I bundle I get a success message ( the POST is successful ) but the bundle is not deployed. I only get a hint on the servers view that the status is 404. I should be prompted that the support bundle is not installed and asked to install it. Or maybe the bundle should be automatically installed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SLING-3074) Repository, SerializationManager - make stateful based on RepositoryInfo
[ https://issues.apache.org/jira/browse/SLING-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-3074: -- Assignee: Robert Munteanu Repository, SerializationManager - make stateful based on RepositoryInfo Key: SLING-3074 URL: https://issues.apache.org/jira/browse/SLING-3074 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 Currently the Repository interface has a setRepositoryInfo method which is used to configure the repository in use. From a thread safety point of view, this is dangerous and will most likely result in problems when multiple repositories are used. The SerializationManager follows a similar pattern with the init/destroy methods. The DS components in use should rather be RepositoryFactory and SerializationManagerFactory, and implementations should invoke the factory methods on them, supplying the required arguments. Also, the SerializationManager is currently very slow since it has to mount a VaultFileSystem for each operation. Making the Repository and SerializationManager stateful will help with this. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3074) Repository, SerializationManager - make stateful based on RepositoryInfo
[ https://issues.apache.org/jira/browse/SLING-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3074. Resolution: Fixed * Introduced RepositoryFactory in http://svn.apache.org/viewvc?view=revisionrevision=r1592510 * Removed stale TODO in http://svn.apache.org/viewvc?view=revisionrevision=1592513 - no need to change SerializationManager Repository, SerializationManager - make stateful based on RepositoryInfo Key: SLING-3074 URL: https://issues.apache.org/jira/browse/SLING-3074 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 Currently the Repository interface has a setRepositoryInfo method which is used to configure the repository in use. From a thread safety point of view, this is dangerous and will most likely result in problems when multiple repositories are used. The SerializationManager follows a similar pattern with the init/destroy methods. The DS components in use should rather be RepositoryFactory and SerializationManagerFactory, and implementations should invoke the factory methods on them, supplying the required arguments. Also, the SerializationManager is currently very slow since it has to mount a VaultFileSystem for each operation. Making the Repository and SerializationManager stateful will help with this. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SLING-3153) Sling project overlay conflicts with the version control overlay
[ https://issues.apache.org/jira/browse/SLING-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-3153: -- Assignee: Robert Munteanu Sling project overlay conflicts with the version control overlay Key: SLING-3153 URL: https://issues.apache.org/jira/browse/SLING-3153 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 Attachments: java-faceted-project-decoration.png, screenshot.png The 'S' overlay which is present on Sling projects conflicts with the Version control overlay, as defined in the [Eclipse UI guidelines|http://wiki.eclipse.org/User_Interface_Guidelines] - search for 'Version Control'. As such , I think we should find a different way of decorating Sling projects, or even remove the decorator altogether. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-2635) [Tooling] Logging framework for Slingclipse
[ https://issues.apache.org/jira/browse/SLING-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13989473#comment-13989473 ] Robert Munteanu commented on SLING-2635: [~asanso] - do you plan to work on this in the near future? If not, I can wrap up this task for the 1.0 release. [Tooling] Logging framework for Slingclipse --- Key: SLING-2635 URL: https://issues.apache.org/jira/browse/SLING-2635 Project: Sling Issue Type: Improvement Components: IDE Reporter: Antonio Sanso Assignee: Antonio Sanso Fix For: Sling Eclipse IDE 1.0.0 Attachments: SLING-2635.diff We need a Logging framework for Slingclipse. I see two options at the moment: - using a log framework as SLF4J logger or other similar - using the embedded Eclipse logging framework -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3153) Sling project overlay conflicts with the version control overlay
[ https://issues.apache.org/jira/browse/SLING-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3153. Resolution: Fixed Since no other proposal popped up, I removed the overlay in http://svn.apache.org/viewvc?view=revisionrevision=1592516 Sling project overlay conflicts with the version control overlay Key: SLING-3153 URL: https://issues.apache.org/jira/browse/SLING-3153 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 Attachments: java-faceted-project-decoration.png, screenshot.png The 'S' overlay which is present on Sling projects conflicts with the Version control overlay, as defined in the [Eclipse UI guidelines|http://wiki.eclipse.org/User_Interface_Guidelines] - search for 'Version Control'. As such , I think we should find a different way of decorating Sling projects, or even remove the decorator altogether. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SLING-3544) Integration tests running against a live Sling Launchpad instance
Robert Munteanu created SLING-3544: -- Summary: Integration tests running against a live Sling Launchpad instance Key: SLING-3544 URL: https://issues.apache.org/jira/browse/SLING-3544 Project: Sling Issue Type: Improvement Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 There are lots of moving parts - and still quite some bugs - when it comes to transporting content to/from a Sling instance. It would be helpful to create a test harness which validates that the way we transport/read/write/filter content is correct. This will then help when fixing the various bugs we have related to content sync. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SLING-2635) [Tooling] Logging framework for Slingclipse
[ https://issues.apache.org/jira/browse/SLING-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-2635: -- Assignee: Robert Munteanu (was: Antonio Sanso) OK them, assigning to myself. [Tooling] Logging framework for Slingclipse --- Key: SLING-2635 URL: https://issues.apache.org/jira/browse/SLING-2635 Project: Sling Issue Type: Improvement Components: IDE Reporter: Antonio Sanso Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 Attachments: SLING-2635.diff We need a Logging framework for Slingclipse. I see two options at the moment: - using a log framework as SLF4J logger or other similar - using the embedded Eclipse logging framework -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3551) Content sync does not propagate mixin types
[
https://issues.apache.org/jira/browse/SLING-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-3551:
---
Description:
Assume that we have a full coverage aggregate as follows:
{code}
?xml version=1.0 encoding=UTF-8?
jcr:root xmlns:sling=http://sling.apache.org/jcr/sling/1.0;
xmlns:vlt=http://www.day.com/jcr/vault/1.0;
xmlns:jcr=http://www.jcp.org/jcr/1.0;
jcr:mixinTypes=[mix:language]
jcr:primaryType=nt:folder
jcr:language=en
message
jcr:primaryType=sling:MessageEntry
sling:key=message
sling:value=Message
/message
error
jcr:primaryType=sling:MessageEntry
sling:key=error
sling:value=Error
/error
warning
jcr:primaryType=sling:MessageEntry
sling:key=warning
sling:value=Warning
/warning
/jcr:root
{code}
When synced to the repo this will fail with the following message
{quote}{noformat}!MESSAGE Failed publishing JcrResult[ success:false,
exception: org.apache.sling.ide.transport.RepositoryException -
javax.jcr.nodetype.ConstraintViolationException: no matching property
definition found for {http://www.jcp.org/jcr/1.0}language]{noformat}{quote}
The reason is that the jcr:mixinTypes property is protected, and therefore
skipped. We need to handle this explicitly.
was:
Assume that we have a full coverage aggregate as follows:
{code}
?xml version=1.0 encoding=UTF-8?
jcr:root xmlns:sling=http://sling.apache.org/jcr/sling/1.0;
xmlns:vlt=http://www.day.com/jcr/vault/1.0;
xmlns:jcr=http://www.jcp.org/jcr/1.0;
jcr:mixinTypes=[mix:language]
jcr:primaryType=nt:folder
jcr:language=en
message
jcr:primaryType=sling:MessageEntry
sling:key=message
sling:value=Message
/message
error
jcr:primaryType=sling:MessageEntry
sling:key=error
sling:value=Error
/error
warning
jcr:primaryType=sling:MessageEntry
sling:key=warning
sling:value=Warning
/warning
/jcr:root
{code}
When synced to the repo this will fail with the following message
{quote}!MESSAGE Failed publishing JcrResult[ success:false, exception:
org.apache.sling.ide.transport.RepositoryException -
javax.jcr.nodetype.ConstraintViolationException: no matching property
definition found for {http://www.jcp.org/jcr/1.0}language]{quote}
The reason is that the jcr:mixinTypes property is protected, and therefore
skipped. We need to handle this explicitly.
Content sync does not propagate mixin types
---
Key: SLING-3551
URL: https://issues.apache.org/jira/browse/SLING-3551
Project: Sling
Issue Type: Bug
Reporter: Robert Munteanu
Assignee: Robert Munteanu
Fix For: Sling Eclipse IDE 1.0.0
Assume that we have a full coverage aggregate as follows:
{code}
?xml version=1.0 encoding=UTF-8?
jcr:root xmlns:sling=http://sling.apache.org/jcr/sling/1.0;
xmlns:vlt=http://www.day.com/jcr/vault/1.0;
xmlns:jcr=http://www.jcp.org/jcr/1.0;
jcr:mixinTypes=[mix:language]
jcr:primaryType=nt:folder
jcr:language=en
message
jcr:primaryType=sling:MessageEntry
sling:key=message
sling:value=Message
/message
error
jcr:primaryType=sling:MessageEntry
sling:key=error
sling:value=Error
/error
warning
jcr:primaryType=sling:MessageEntry
sling:key=warning
sling:value=Warning
/warning
/jcr:root
{code}
When synced to the repo this will fail with the following message
{quote}{noformat}!MESSAGE Failed publishing JcrResult[ success:false,
exception: org.apache.sling.ide.transport.RepositoryException -
javax.jcr.nodetype.ConstraintViolationException: no matching property
definition found for {http://www.jcp.org/jcr/1.0}language]{noformat}{quote}
The reason is that the jcr:mixinTypes property is protected, and therefore
skipped. We need to handle this explicitly.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (SLING-3544) Integration tests running against a live Sling Launchpad instance
[ https://issues.apache.org/jira/browse/SLING-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3544. Resolution: Fixed * http://svn.apache.org/viewvc?view=revisionrevision=1593274 added a ContentDeploymentTest * http://svn.apache.org/viewvc?view=revisionrevision=1593275 removing hardcoding of repository urls * http://svn.apache.org/viewvc?view=revisionrevision=1593276 add a a RepositoryAccessor helper * http://svn.apache.org/viewvc?view=revisionrevision=1593277 use a Poller for operations which are timing-sensitive With these final changes the task can be considered complete. Integration tests running against a live Sling Launchpad instance - Key: SLING-3544 URL: https://issues.apache.org/jira/browse/SLING-3544 Project: Sling Issue Type: Improvement Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 There are lots of moving parts - and still quite some bugs - when it comes to transporting content to/from a Sling instance. It would be helpful to create a test harness which validates that the way we transport/read/write/filter content is correct. This will then help when fixing the various bugs we have related to content sync. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-2635) [Tooling] Logging framework for Slingclipse
[ https://issues.apache.org/jira/browse/SLING-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13993560#comment-13993560 ] Robert Munteanu commented on SLING-2635: Added references to the Sling console and the tracing page at https://cwiki.apache.org/confluence/display/SLING/Sling+IDE+tooling+User+Guide#SlingIDEtoolingUserGuide-Troubleshooting . [Tooling] Logging framework for Slingclipse --- Key: SLING-2635 URL: https://issues.apache.org/jira/browse/SLING-2635 Project: Sling Issue Type: Improvement Components: IDE Reporter: Antonio Sanso Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 Attachments: SLING-2635.diff We need a Logging framework for Slingclipse. I see two options at the moment: - using a log framework as SLF4J logger or other similar - using the embedded Eclipse logging framework -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3117) Node order changes made in .content.xml files are not persisted
[ https://issues.apache.org/jira/browse/SLING-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3117: --- Assignee: Robert Munteanu Node order changes made in .content.xml files are not persisted --- Key: SLING-3117 URL: https://issues.apache.org/jira/browse/SLING-3117 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 If the node supports orderable child nodes we should reoder the child nodes to follow the order in the .content.xml file. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-2635) [Tooling] Logging framework for Slingclipse
[ https://issues.apache.org/jira/browse/SLING-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13993559#comment-13993559 ] Robert Munteanu commented on SLING-2635: * http://svn.apache.org/viewvc?view=revisionrevision=1593531 - added API + impl for logging/debugging in org.apache.sling.ide.eclipse.core.debug * http://svn.apache.org/viewvc?view=revisionrevision=1593532 - remove duplicate tracer from resource-impl * http://svn.apache.org/viewvc?view=revisionrevision=1593533 - add tracing to eclipse-ui * http://svn.apache.org/viewvc?view=revisionrevision=1593534 - remove stray System.out from eclipse-test * http://svn.apache.org/viewvc?view=revisionrevision=1593535 - contribute to the platform tracing page [Tooling] Logging framework for Slingclipse --- Key: SLING-2635 URL: https://issues.apache.org/jira/browse/SLING-2635 Project: Sling Issue Type: Improvement Components: IDE Reporter: Antonio Sanso Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 Attachments: SLING-2635.diff We need a Logging framework for Slingclipse. I see two options at the moment: - using a log framework as SLF4J logger or other similar - using the embedded Eclipse logging framework -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3116) Node structures serialized to a .content.xml file do not propagate deletions
[
https://issues.apache.org/jira/browse/SLING-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-3116.
Resolution: Fixed
* http://svn.apache.org/viewvc?view=revisionrevision=1593959 implemented +
added IT
* http://svn.apache.org/viewvc?view=revisionrevision=1593960 improved generics
usage in Poller
Node structures serialized to a .content.xml file do not propagate deletions
Key: SLING-3116
URL: https://issues.apache.org/jira/browse/SLING-3116
Project: Sling
Issue Type: Bug
Components: IDE
Reporter: Robert Munteanu
Assignee: Robert Munteanu
Fix For: Sling Eclipse IDE 1.0.0
Assume that a .content.xml file like the one below changes by
- removing the parent-1 node OR
- removing the child-1-2 node
We need to persist these deletions into the repository.
However, we need to be careful to propagate these only for full coverage
nodes.
{code}
?xml version=1.0 encoding=UTF-8?
jcr:root xmlns:sling=http://sling.apache.org/jcr/sling/1.0;
xmlns:vlt=http://www.day.com/jcr/vault/1.0;
xmlns:jcr=http://www.jcp.org/jcr/1.0;
jcr:mixinTypes=[vlt:FullCoverage]
jcr:primaryType=sling:Folder
jcr:title=Full coverage parent
parent-1
jcr:primaryType=sling:Folder
jcr:title=Parent 1
child-1-1
jcr:primaryType=sling:Folder
jcr:title=Child 1-1/
child-1-2
jcr:primaryType=sling:Folder
jcr:title=Child 1-2/
/parent-1
parent-2
jcr:primaryType=sling:Folder
jcr:title=Parent 2
child-2-1
jcr:primaryType=sling:Folder
jcr:title=Child 2-1/
child-2-2
jcr:primaryType=sling:Folder
jcr:title=Child 2-2/
/parent-2
/jcr:root
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (SLING-3552) Update minimum requirement to Eclipse Kepler
Robert Munteanu created SLING-3552: -- Summary: Update minimum requirement to Eclipse Kepler Key: SLING-3552 URL: https://issues.apache.org/jira/browse/SLING-3552 Project: Sling Issue Type: Task Components: IDE Affects Versions: Sling Eclipse IDE 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu To make use of enhanced APIs, we should set up a baseline with Eclipse Kepler. This should also be noted in the user guide. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3116) Node structures serialized to a .content.xml file do not propagate deletions
[
https://issues.apache.org/jira/browse/SLING-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995180#comment-13995180
]
Robert Munteanu commented on SLING-3116:
* http://svn.apache.org/viewvc?view=revisionrevision=1594005 fixed regression
when deploying file-like or folder-like nodes
Node structures serialized to a .content.xml file do not propagate deletions
Key: SLING-3116
URL: https://issues.apache.org/jira/browse/SLING-3116
Project: Sling
Issue Type: Bug
Components: IDE
Reporter: Robert Munteanu
Assignee: Robert Munteanu
Fix For: Sling Eclipse IDE 1.0.0
Assume that a .content.xml file like the one below changes by
- removing the parent-1 node OR
- removing the child-1-2 node
We need to persist these deletions into the repository.
However, we need to be careful to propagate these only for full coverage
nodes.
{code}
?xml version=1.0 encoding=UTF-8?
jcr:root xmlns:sling=http://sling.apache.org/jcr/sling/1.0;
xmlns:vlt=http://www.day.com/jcr/vault/1.0;
xmlns:jcr=http://www.jcp.org/jcr/1.0;
jcr:mixinTypes=[vlt:FullCoverage]
jcr:primaryType=sling:Folder
jcr:title=Full coverage parent
parent-1
jcr:primaryType=sling:Folder
jcr:title=Parent 1
child-1-1
jcr:primaryType=sling:Folder
jcr:title=Child 1-1/
child-1-2
jcr:primaryType=sling:Folder
jcr:title=Child 1-2/
/parent-1
parent-2
jcr:primaryType=sling:Folder
jcr:title=Parent 2
child-2-1
jcr:primaryType=sling:Folder
jcr:title=Child 2-1/
child-2-2
jcr:primaryType=sling:Folder
jcr:title=Child 2-2/
/parent-2
/jcr:root
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (SLING-3551) Content sync does not propagate mixin types
[
https://issues.apache.org/jira/browse/SLING-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13993870#comment-13993870
]
Robert Munteanu commented on SLING-3551:
* http://svn.apache.org/viewvc?view=revisionrevision=1593604 make
RepositoryUtils API so that it can be used by the eclipse test utils
* http://svn.apache.org/viewvc?view=revisionrevision=1593605 make the
RepositoryAccessor use JCR APIs when needed.
* http://svn.apache.org/viewvc?view=revisionrevision=1593606 add helpers.jcr
package for working with JCR data
* http://svn.apache.org/viewvc?view=revisionrevision=1593607 make the Poller
propagate the last caught error after a timeout
* http://svn.apache.org/viewvc?view=revisionrevision=1593608 sync mixin types
whenever a node is created or updated ( + test )
Content sync does not propagate mixin types
---
Key: SLING-3551
URL: https://issues.apache.org/jira/browse/SLING-3551
Project: Sling
Issue Type: Bug
Reporter: Robert Munteanu
Assignee: Robert Munteanu
Fix For: Sling Eclipse IDE 1.0.0
Assume that we have a full coverage aggregate as follows:
{code}
?xml version=1.0 encoding=UTF-8?
jcr:root xmlns:sling=http://sling.apache.org/jcr/sling/1.0;
xmlns:vlt=http://www.day.com/jcr/vault/1.0;
xmlns:jcr=http://www.jcp.org/jcr/1.0;
jcr:mixinTypes=[mix:language]
jcr:primaryType=nt:folder
jcr:language=en
message
jcr:primaryType=sling:MessageEntry
sling:key=message
sling:value=Message
/message
error
jcr:primaryType=sling:MessageEntry
sling:key=error
sling:value=Error
/error
warning
jcr:primaryType=sling:MessageEntry
sling:key=warning
sling:value=Warning
/warning
/jcr:root
{code}
When synced to the repo this will fail with the following message
{quote}!MESSAGE Failed publishing JcrResult[ success:false, exception:
org.apache.sling.ide.transport.RepositoryException -
javax.jcr.nodetype.ConstraintViolationException: no matching property
definition found for {http://www.jcp.org/jcr/1.0}language]{quote}
The reason is that the jcr:mixinTypes property is protected, and therefore
skipped. We need to handle this explicitly.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (SLING-3117) Node order changes made in .content.xml files are not persisted
[ https://issues.apache.org/jira/browse/SLING-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3117. Resolution: Fixed * http://svn.apache.org/viewvc?view=revisionrevision=1594002 added ChildrenNameMatcher * http://svn.apache.org/viewvc?view=revisionrevision=1594004 persist node order changes Node order changes made in .content.xml files are not persisted --- Key: SLING-3117 URL: https://issues.apache.org/jira/browse/SLING-3117 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 If the node supports orderable child nodes we should reoder the child nodes to follow the order in the .content.xml file. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3552) Update minimum requirement to Eclipse Kepler
[ https://issues.apache.org/jira/browse/SLING-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3552. Resolution: Fixed Fixed in http://svn.apache.org/viewvc?view=revisionrevision=1594203 Update minimum requirement to Eclipse Kepler Key: SLING-3552 URL: https://issues.apache.org/jira/browse/SLING-3552 Project: Sling Issue Type: Task Components: IDE Affects Versions: Sling Eclipse IDE 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu To make use of enhanced APIs, we should set up a baseline with Eclipse Kepler. This should also be noted in the user guide. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SLING-3555) Simpler target platform management with the target platform generator DSL
Robert Munteanu created SLING-3555: -- Summary: Simpler target platform management with the target platform generator DSL Key: SLING-3555 URL: https://issues.apache.org/jira/browse/SLING-3555 Project: Sling Issue Type: Improvement Components: IDE Reporter: Robert Munteanu Priority: Minor Fix For: Sling Eclipse IDE 1.0.2 Maintaining the target platform by hand is problematic - and we need to maintain two of them. The [Target Platform Definition DSL and Generator|https://github.com/mbarbero/fr.obeo.releng.targetplatform] should simplify this task. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SLING-3556) The Filter API should work on resources, not on filesystem-based paths
Robert Munteanu created SLING-3556: -- Summary: The Filter API should work on resources, not on filesystem-based paths Key: SLING-3556 URL: https://issues.apache.org/jira/browse/SLING-3556 Project: Sling Issue Type: Improvement Components: IDE Affects Versions: Sling Eclipse IDE 1.0.0 Reporter: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.2 Today the SlingLaunchpadBehaviour encapsulates lot of knowledge about what it takes to find out if a resource should be filtered or not ( also visited in the context of SLING-3112 ). This knowledge should be rooted in the Filter API, which currently takes paths. Instead, it should take a ResourceProxy instance, and delegate to the SerializationKindManager to see what the serialization policy is, so that it can determine the repository path. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-2651) [Tooling] manually trigger sync on files/directories
[ https://issues.apache.org/jira/browse/SLING-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-2651: --- Description: We should have the ability to update just a section of the local checkout, opposed to the whole project. [Tooling] manually trigger sync on files/directories - Key: SLING-2651 URL: https://issues.apache.org/jira/browse/SLING-2651 Project: Sling Issue Type: Improvement Components: IDE Reporter: Antonio Sanso Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 We should have the ability to update just a section of the local checkout, opposed to the whole project. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-2651) Manually trigger sync on files/directories
[ https://issues.apache.org/jira/browse/SLING-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-2651: --- Summary: Manually trigger sync on files/directories (was: Manually trigger import on files/directories) Manually trigger sync on files/directories -- Key: SLING-2651 URL: https://issues.apache.org/jira/browse/SLING-2651 Project: Sling Issue Type: Improvement Components: IDE Reporter: Antonio Sanso Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 We should be able to manually publish a subtree of content, as opposed to the sync happening in the background. One use case is where the auto-sync is disabled and the user only wants to publish the changes manually. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3552) Update minimum requirement to Eclipse Kepler
[ https://issues.apache.org/jira/browse/SLING-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996482#comment-13996482 ] Robert Munteanu commented on SLING-3552: Follow-up fix in http://svn.apache.org/viewvc?view=revisionrevision=1594241 ; due to API change in org.eclipse.jdt.debug Update minimum requirement to Eclipse Kepler Key: SLING-3552 URL: https://issues.apache.org/jira/browse/SLING-3552 Project: Sling Issue Type: Task Components: IDE Affects Versions: Sling Eclipse IDE 1.0.0 Reporter: Robert Munteanu Assignee: Robert Munteanu To make use of enhanced APIs, we should set up a baseline with Eclipse Kepler. This should also be noted in the user guide. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-2651) Manually trigger import on files/directories
[ https://issues.apache.org/jira/browse/SLING-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-2651: --- Summary: Manually trigger import on files/directories (was: [Tooling] manually trigger sync on files/directories ) Manually trigger import on files/directories Key: SLING-2651 URL: https://issues.apache.org/jira/browse/SLING-2651 Project: Sling Issue Type: Improvement Components: IDE Reporter: Antonio Sanso Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 We should be able to manually publish a subtree of content, as opposed to the sync happening in the background. One use case is where the auto-sync is disabled and the user only wants to publish the changes manually. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-2651) [Tooling] manually trigger sync on files/directories
[ https://issues.apache.org/jira/browse/SLING-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-2651: --- Description: We should be able to manually publish a subtree of content, as opposed to the sync happening in the background. One use case is where the auto-sync is disabled and the user only wants to publish the changes manually. (was: We should have the ability to update just a section of the local checkout, opposed to the whole project.) [Tooling] manually trigger sync on files/directories - Key: SLING-2651 URL: https://issues.apache.org/jira/browse/SLING-2651 Project: Sling Issue Type: Improvement Components: IDE Reporter: Antonio Sanso Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 We should be able to manually publish a subtree of content, as opposed to the sync happening in the background. One use case is where the auto-sync is disabled and the user only wants to publish the changes manually. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3556) The Filter API should work on resources, not on filesystem-based paths
[ https://issues.apache.org/jira/browse/SLING-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996465#comment-13996465 ] Robert Munteanu commented on SLING-3556: Attached [^SLING-3556-wip-1.patch], which shows how this API can look. The Filter API should work on resources, not on filesystem-based paths -- Key: SLING-3556 URL: https://issues.apache.org/jira/browse/SLING-3556 Project: Sling Issue Type: Improvement Components: IDE Affects Versions: Sling Eclipse IDE 1.0.0 Reporter: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.2 Attachments: SLING-3556-wip-1.patch Today the SlingLaunchpadBehaviour encapsulates lot of knowledge about what it takes to find out if a resource should be filtered or not ( also visited in the context of SLING-3112 ). This knowledge should be rooted in the Filter API, which currently takes paths. Instead, it should take a ResourceProxy instance, and delegate to the SerializationKindManager to see what the serialization policy is, so that it can determine the repository path. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3560) Never run project launches when publishing
[ https://issues.apache.org/jira/browse/SLING-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3560. Resolution: Duplicate Fix Version/s: (was: Sling Eclipse IDE 1.0.0) Oops, accidental double-submission Never run project launches when publishing -- Key: SLING-3560 URL: https://issues.apache.org/jira/browse/SLING-3560 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu The SlingLaunchpadBehaviour still runs project launches if they exist. I don't think that's needed anymore, as the content sync code should be good enough, and launches are reserved for other tasks. As such, we should remove that code. [~egli] - is there anything that I missed? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3559) Never run project launches when publishing
[ https://issues.apache.org/jira/browse/SLING-3559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997901#comment-13997901 ] Robert Munteanu commented on SLING-3559: It can work in theory, but in practice the user can set up the launch for different purposes. For instance, running unit tests :-) So there's no guarantee that we will get the result that we want. Also, bundles are not deployed anymore if the tooling support bundle is not installed, see SLING-3159 . Never run project launches when publishing -- Key: SLING-3559 URL: https://issues.apache.org/jira/browse/SLING-3559 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 The SlingLaunchpadBehaviour still runs project launches if they exist. I don't think that's needed anymore, as the content sync code should be good enough, and launches are reserved for other tasks. As such, we should remove that code. [~egli] - is there anything that I missed? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SLING-3556) The Filter API should work on resources, not on filesystem-based paths
[ https://issues.apache.org/jira/browse/SLING-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3556: --- Description: Today the SlingLaunchpadBehaviour encapsulates lot of knowledge about what it takes to find out if a resource should be filtered or not ( also visited in the context of SLING-3122 ). This knowledge should be rooted in the Filter API, which currently takes paths. Instead, it should take a ResourceProxy instance, and delegate to the SerializationKindManager to see what the serialization policy is, so that it can determine the repository path. was: Today the SlingLaunchpadBehaviour encapsulates lot of knowledge about what it takes to find out if a resource should be filtered or not ( also visited in the context of SLING-3112 ). This knowledge should be rooted in the Filter API, which currently takes paths. Instead, it should take a ResourceProxy instance, and delegate to the SerializationKindManager to see what the serialization policy is, so that it can determine the repository path. The Filter API should work on resources, not on filesystem-based paths -- Key: SLING-3556 URL: https://issues.apache.org/jira/browse/SLING-3556 Project: Sling Issue Type: Improvement Components: IDE Affects Versions: Sling Eclipse IDE 1.0.0 Reporter: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.2 Attachments: SLING-3556-wip-1.patch Today the SlingLaunchpadBehaviour encapsulates lot of knowledge about what it takes to find out if a resource should be filtered or not ( also visited in the context of SLING-3122 ). This knowledge should be rooted in the Filter API, which currently takes paths. Instead, it should take a ResourceProxy instance, and delegate to the SerializationKindManager to see what the serialization policy is, so that it can determine the repository path. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SLING-3122) Incorrect filtering for full coverage nodes
[ https://issues.apache.org/jira/browse/SLING-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-3122: -- Assignee: Robert Munteanu Incorrect filtering for full coverage nodes --- Key: SLING-3122 URL: https://issues.apache.org/jira/browse/SLING-3122 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 With the following filter ?xml version=1.0 encoding=UTF-8? workspaceFilter version=1.0 filter root=/content/slingDemo/ filter root=/apps/slingDemo/ filter root=/var/full-coverage/ /workspaceFilter changes to /var/full-coverage.xml not synced, were that is file corresponds to a node with full coverage present at /var/full-coverage -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SLING-3236) Unable to change node primary type once created
[ https://issues.apache.org/jira/browse/SLING-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3236. Resolution: Fixed Unable to change node primary type once created --- Key: SLING-3236 URL: https://issues.apache.org/jira/browse/SLING-3236 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 Consider the following scenario in a Sling content module: - folder is created in the project - folder is synced and created in the repo with a nt:folder primary type - a .content.xml file is added and the primary type set to sling:Folder At this point the the primary type is not updated in the repository and additional metadata is not updated. Originally reported by [~dsuess] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SLING-3081) Do not re-publish modules when starting the launchpad for the first time
[ https://issues.apache.org/jira/browse/SLING-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998100#comment-13998100 ] Robert Munteanu commented on SLING-3081: [~egli] - When SLING-2651 is fixed, I'm tempted to fix this one for 1.0.0 as well. The reason is that for external servers it's confusing to connect it to the workspace and instantly publish all the assigned modules. This can even take a long time for large modules ( think vlt ci every time you start Eclipse ... ) . Thoughts? Do not re-publish modules when starting the launchpad for the first time Key: SLING-3081 URL: https://issues.apache.org/jira/browse/SLING-3081 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.2 This results in unnecessary publishing activity. The right way is to provide a manual action to sync a sub-tree to ( or the whole module ) to the Launchpad. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SLING-3560) Never run project launches when publishing
Robert Munteanu created SLING-3560: -- Summary: Never run project launches when publishing Key: SLING-3560 URL: https://issues.apache.org/jira/browse/SLING-3560 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 The SlingLaunchpadBehaviour still runs project launches if they exist. I don't think that's needed anymore, as the content sync code should be good enough, and launches are reserved for other tasks. As such, we should remove that code. [~egli] - is there anything that I missed? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SLING-3116) Node structures serialized to a .content.xml file do not propagate deletions
[
https://issues.apache.org/jira/browse/SLING-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu reassigned SLING-3116:
--
Assignee: Robert Munteanu
Node structures serialized to a .content.xml file do not propagate deletions
Key: SLING-3116
URL: https://issues.apache.org/jira/browse/SLING-3116
Project: Sling
Issue Type: Bug
Components: IDE
Reporter: Robert Munteanu
Assignee: Robert Munteanu
Fix For: Sling Eclipse IDE 1.0.0
Assume that a .content.xml file like the one below changes by
- removing the parent-1 node OR
- removing the child-1-2 node
We need to persist these deletions into the repository.
However, we need to be careful to propagate these only for full coverage
nodes.
{code}
?xml version=1.0 encoding=UTF-8?
jcr:root xmlns:sling=http://sling.apache.org/jcr/sling/1.0;
xmlns:vlt=http://www.day.com/jcr/vault/1.0;
xmlns:jcr=http://www.jcp.org/jcr/1.0;
jcr:mixinTypes=[vlt:FullCoverage]
jcr:primaryType=sling:Folder
jcr:title=Full coverage parent
parent-1
jcr:primaryType=sling:Folder
jcr:title=Parent 1
child-1-1
jcr:primaryType=sling:Folder
jcr:title=Child 1-1/
child-1-2
jcr:primaryType=sling:Folder
jcr:title=Child 1-2/
/parent-1
parent-2
jcr:primaryType=sling:Folder
jcr:title=Parent 2
child-2-1
jcr:primaryType=sling:Folder
jcr:title=Child 2-1/
child-2-2
jcr:primaryType=sling:Folder
jcr:title=Child 2-2/
/parent-2
/jcr:root
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
