[jira] [Created] (SLING-3239) Upgrade to SCR 1.8.0
Robert Munteanu created SLING-3239: -- Summary: Upgrade to SCR 1.8.0 Key: SLING-3239 URL: https://issues.apache.org/jira/browse/SLING-3239 Project: Sling Issue Type: Task Components: Launchpad Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Launchpad Builder 7 SCR 1.8.0 has been released with numerous bug fixes and improvements ( see http://markmail.org/thread/yhsejwrjdqxvwugv). We should update, especially since it appears that SCR 1.6.0 is not viable for the topology bundle ( http://sling.markmail.org/thread/brmg2qj7zlgbqj3d#query:+page:1+mid:ts7mru6q6ukdez2k+state:results ) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SLING-3006) SlingServletResolver webconsole plugin uses custom URL decomposition code that can be wrong
[ https://issues.apache.org/jira/browse/SLING-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13818879#comment-13818879 ] Bertrand Delacretaz commented on SLING-3006: Good idea, I have added workaround info in http://svn.apache.org/r1540671 SlingServletResolver webconsole plugin uses custom URL decomposition code that can be wrong --- Key: SLING-3006 URL: https://issues.apache.org/jira/browse/SLING-3006 Project: Sling Issue Type: Bug Components: Servlets Affects Versions: Servlets Resolver 2.2.4 Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Priority: Minor Fix For: Servlets Resolver 2.2.6 Entering http://localhost:8080/libs/foo/content/something/formitems.json/image/vnd/xnd/knd.xml in the /system/console/servletresolver webconsole plugin does not produce the correct results as per the testDotsAroundSuffix() at [1] This is due to the plugin using its own DecomposedURL class which is a simplified version of the SlingRequestPathInfo class. For now, I'll add a warning to the plugin. [1] http://svn.apache.org/repos/asf/sling/trunk/bundles/engine/src/test/java/org/apache/sling/engine/impl/request/SlingRequestPathInfoTest.java -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SLING-3234) Sling buildbot setup
[ https://issues.apache.org/jira/browse/SLING-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13818887#comment-13818887 ] Bertrand Delacretaz commented on SLING-3234: The build doesn't start automatically after a commit, created INFRA-6987 for that. Sling buildbot setup Key: SLING-3234 URL: https://issues.apache.org/jira/browse/SLING-3234 Project: Sling Issue Type: Task Components: Testing Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Buildbot jobs have been setup for Sling in INFRA-6962; * http://ci.apache.org/builders/sling-trunk (triggered by commits) * http://ci.apache.org/builders/sling-trunk-oak (runs after sling-trunk) We'll use this issue to keep track of changes related to this buildbot setup, as we did with SLING-920 for our Jenkins builds. Builds can be started manually via IRC if needed, via #asftest. Talk to the sling-bot there, start with help force, status or commands. [1] https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/sling.conf -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (SLING-3240) Unable to run tests from launchpad/testing-war: launchpad/testing-war/src/main/config does not exist
Robert Munteanu created SLING-3240: -- Summary: Unable to run tests from launchpad/testing-war: launchpad/testing-war/src/main/config does not exist Key: SLING-3240 URL: https://issues.apache.org/jira/browse/SLING-3240 Project: Sling Issue Type: Bug Components: Testing Reporter: Robert Munteanu Fix For: Launchpad Testing 7 The launchpad/test-war project fails, apparently due to a missing configuration directory ( src/main/config ). However, once that directory is created the build still fails, since it fails to find the org.apache.sling.commons.testing.integration.HttpTest class. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SLING-3240) Unable to run tests from launchpad/testing-war: launchpad/testing-war/src/main/config does not exist
[ https://issues.apache.org/jira/browse/SLING-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3240: --- Attachment: build-failure-class-not-found.log build-failure-config-dir-not-found.log Attached log files for both of the issues described. Unable to run tests from launchpad/testing-war: launchpad/testing-war/src/main/config does not exist Key: SLING-3240 URL: https://issues.apache.org/jira/browse/SLING-3240 Project: Sling Issue Type: Bug Components: Testing Reporter: Robert Munteanu Fix For: Launchpad Testing 7 Attachments: build-failure-class-not-found.log, build-failure-config-dir-not-found.log The launchpad/test-war project fails, apparently due to a missing configuration directory ( src/main/config ). However, once that directory is created the build still fails, since it fails to find the org.apache.sling.commons.testing.integration.HttpTest class. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (SLING-3239) Upgrade to SCR 1.8.0
[ https://issues.apache.org/jira/browse/SLING-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3239. Resolution: Fixed Updated the bundle list in http://svn.apache.org/viewvc?view=revisionrevision=1540694 . Also updated various ITs to use the same version of the scr bundle, for consistency reasons. ITs are passing, with the notable exception from SLING-3240 . However, that is unrelated to this change. Upgrade to SCR 1.8.0 Key: SLING-3239 URL: https://issues.apache.org/jira/browse/SLING-3239 Project: Sling Issue Type: Task Components: Launchpad Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Launchpad Builder 7 SCR 1.8.0 has been released with numerous bug fixes and improvements ( see http://markmail.org/thread/yhsejwrjdqxvwugv). We should update, especially since it appears that SCR 1.6.0 is not viable for the topology bundle ( http://sling.markmail.org/thread/brmg2qj7zlgbqj3d#query:+page:1+mid:ts7mru6q6ukdez2k+state:results ) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SLING-3240) Unable to run tests from launchpad/testing-war: launchpad/testing-war/src/main/config does not exist
[ https://issues.apache.org/jira/browse/SLING-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13818930#comment-13818930 ] Bertrand Delacretaz commented on SLING-3240: I think the root cause of the src/main/config error is maven-launchpad-plugin not accepting a missing folder in recent versions. I had the same problem in launchpad/builder and worked around it for now, look for empty.config.directory in pom.xml Unable to run tests from launchpad/testing-war: launchpad/testing-war/src/main/config does not exist Key: SLING-3240 URL: https://issues.apache.org/jira/browse/SLING-3240 Project: Sling Issue Type: Bug Components: Testing Reporter: Robert Munteanu Fix For: Launchpad Testing 7 Attachments: build-failure-class-not-found.log, build-failure-config-dir-not-found.log The launchpad/test-war project fails, apparently due to a missing configuration directory ( src/main/config ). However, once that directory is created the build still fails, since it fails to find the org.apache.sling.commons.testing.integration.HttpTest class. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (SLING-3225) ModifyAceTest integration test fails with Oak: missing rep:write privilege
[ https://issues.apache.org/jira/browse/SLING-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-3225. Resolution: Fixed Assignee: Bertrand Delacretaz Test reactivated in revision 1540733, passes after upgrading to Oak 0.10. ModifyAceTest integration test fails with Oak: missing rep:write privilege --- Key: SLING-3225 URL: https://issues.apache.org/jira/browse/SLING-3225 Project: Sling Issue Type: Bug Components: Testing Reporter: Bertrand Delacretaz Assignee: Bertrand Delacretaz Priority: Minor In ModifyAceTest.testMergeAceForUserGrantAggregatePrivilegePartsAfterDenyAggregatePrivilege Expected privilege rep:write to be included in supplied list: [jcr:read, jcr:nodeTypeManagement, jcr:modifyAccessControl, jcr:versionManagement, jcr:write]) at org.apache.sling.launchpad.webapp.integrationtest.accessManager.ModifyAceTest.testMergeAceForUserGrantAggregatePrivilegePartsAfterDenyAggregatePrivilege(ModifyAceTest.java:986) Which looks related to SLING-3010 - but my knowledge of those modules is fairly limited, so before I spend too much time on digging down, hints or patches are welcome. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SLING-2788) Optionally run Sling on Apache OAK
[ https://issues.apache.org/jira/browse/SLING-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13818981#comment-13818981 ] Bertrand Delacretaz commented on SLING-2788: Upgraded to Oak 0.10 in http://svn.apache.org/r1540718 The upgrade fixed SLING-3225, no other changes to the integration tests. Optionally run Sling on Apache OAK -- Key: SLING-2788 URL: https://issues.apache.org/jira/browse/SLING-2788 Project: Sling Issue Type: Wish Components: General Reporter: Antonio Sanso Assignee: Ian Boston Attachments: fix.sed, junit4.sed It would be nice to have a runMode of Sling that runs on top of Apache OAK [0] [0] http://jackrabbit.apache.org/oak/ -- This message was sent by Atlassian JIRA (v6.1#6144)
release for org.apache.sling.commons.log
Hello, Could someone please cut a release for org.apache.sling.commons.log? There haven't been any releases since Aug. 26th and I'd like to have the fix for SLING-3045 [0] in the bundle. Thanks, Radu [0] - https://issues.apache.org/jira/browse/SLING-3045
Re: release for org.apache.sling.commons.log
Hi, On Mon, Nov 11, 2013 at 4:58 PM, Radu Cotescu r...@apache.org wrote: ...Could someone please cut a release for org.apache.sling.commons.log? There haven't been any releases since Aug. 26th and I'd like to have the fix for SLING-3045 [0] in the bundle Chetan, would that work for you or are you still working on that module? I've been using 3.0.3.SNAPSHOT in our integration tests a lot while working on SLING-2788 lately, and haven't seen issues since SLING-3189 was fixed. -Bertrand
Re: release for org.apache.sling.commons.log
Yup time to cut the release. Have some minor task to complete Would try to do that by this week end Chetan Mehrotra On Mon, Nov 11, 2013 at 9:41 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, On Mon, Nov 11, 2013 at 4:58 PM, Radu Cotescu r...@apache.org wrote: ...Could someone please cut a release for org.apache.sling.commons.log? There haven't been any releases since Aug. 26th and I'd like to have the fix for SLING-3045 [0] in the bundle Chetan, would that work for you or are you still working on that module? I've been using 3.0.3.SNAPSHOT in our integration tests a lot while working on SLING-2788 lately, and haven't seen issues since SLING-3189 was fixed. -Bertrand
[jira] [Commented] (SLING-3231) Not able to set multiple framework property via command line args
[
https://issues.apache.org/jira/browse/SLING-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13819797#comment-13819797
]
Chetan Mehrotra commented on SLING-3231:
Fine would go with {{-F}} option
[~fmeschbe] and [~cziegeler] Can you also have a look and comment. Would like
to commit it by tomorrow
Not able to set multiple framework property via command line args
-
Key: SLING-3231
URL: https://issues.apache.org/jira/browse/SLING-3231
Project: Sling
Issue Type: Bug
Components: Launchpad
Affects Versions: Launchpad Base 2.5.0
Reporter: Chetan Mehrotra
Priority: Minor
Attachments: SLING-3231.patch
Sling launchpad doc [1] mentions that multiple framework properties can be
specified via command line like -D n=v. For current implementation this
leads to saving of last pair only.
This appears to be a bug in parsing logic [2]. Patch to follow
[1]
http://sling.apache.org/documentation/the-sling-engine/the-sling-launchpad.html
[2] http://markmail.org/thread/dtlzmnrcid4v3esy
--
This message was sent by Atlassian JIRA
(v6.1#6144)
