[jira] [Commented] (SLING-3542) Use commons compiler (instead of embedding own jdt compiler)

[ https://issues.apache.org/jira/browse/SLING-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987838#comment-13987838 ] Carsten Ziegeler commented on SLING-3542: - I've committed a first version using th

[jira] [Created] (SLING-3542) Use commons compiler (instead of embedding own jdt compiler)

Carsten Ziegeler created SLING-3542: --- Summary: Use commons compiler (instead of embedding own jdt compiler) Key: SLING-3542 URL: https://issues.apache.org/jira/browse/SLING-3542 Project: Sling

[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-tabpanel&focusedCommentId=13987734#comment-13987734 ] Bertrand Delacretaz commented on SLING-3540: The benefit of using the post ser

[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 curre

[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 > -

[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 Ass

[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-tabpanel&focusedCommentId=13987726#comment-13987726 ] Robert Munteanu commented on SLING-3540: The discussion above seemed to be blocked

[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-tabpanel&focusedCommentId=13987721#comment-13987721 ] Carsten Ziegeler commented on SLING-3405: - I've also updated the commons compiler

[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-tabpanel&focusedCommentId=13987717#comment-13987717 ] Carsten Ziegeler commented on SLING-3405: - It seems that version requires Java 6 a

[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-tabpanel&focusedCommentId=13987714#comment-13987714 ] Carsten Ziegeler commented on SLING-3405: - I've replaced the compiler with a versi

[jira] [Updated] (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:all-tabpanel ] Carsten Ziegeler updated SLING-3405: Fix Version/s: (was: Scripting Java 2.0.8) Commons Compiler 2.1.2 >

[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-tabpanel&focusedCommentId=13987709#comment-13987709 ] Robert Munteanu commented on SLING-3538: Fixed IT for the servlet archetype in ht

Build failed in Jenkins: sling-trunk-1.6 #2111

See Changes: [olli] [maven-release-plugin] prepare for next development iteration [olli] [maven-release-plugin] prepare release org.apache.sling.jcr.contentloader-2.1.8 [cziegeler] SLING-3523 : ResourceResolverImpl.mangleNamespace an

Re: Build failed in Jenkins: sling-trunk-1.6 » Sling Servlet Archetype #2111

I forgot to adjust the ITs, will fix now. On Fri, May 2, 2014 at 4:49 PM, Apache Jenkins Server wrote: > See > > > Changes: > > [rombert] SLING-3538 - Maven archetypes should use the same port a

[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-tabpanel&focusedCommentId=13987707#comment-13987707 ] Konrad Windszus commented on SLING-3540: http://apache-sling.73963.n3.nabble.com/I

Build failed in Jenkins: sling-trunk-1.6 » Sling Servlet Archetype #2111

See Changes: [rombert] SLING-3538 - Maven archetypes should use the same port as the default launchpad port -- [INFO]

[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=revision&revision=1591905 > S

[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-tabpanel&focusedCommentId=13987701#comment-13987701 ] Bertrand Delacretaz commented on SLING-3540: The best would be for maven-sling

[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

[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 Proje

[jira] [Updated] (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:all-tabpanel ] Carsten Ziegeler updated SLING-3405: Fix Version/s: Scripting Java 2.0.8 Scripting JSP 2.0.30 > SLING2094Test

[jira] [Resolved] (SLING-3486) Configuration changes like jasper.trimSpaces only work after cleaning /var/classes and bundle restart

[ https://issues.apache.org/jira/browse/SLING-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3486. - Resolution: Fixed > Configuration changes like jasper.trimSpaces only work after cleaning

[VOTE] Release Apache Sling JCR ContentLoader 2.1.8

Hi, We solved 3 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12322442/ Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1057/ You can use this UNIX script to download the release and verify the signatures: http://svn.apac

[jira] [Resolved] (SLING-2757) Support Java 8 as a platform

[ https://issues.apache.org/jira/browse/SLING-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-2757. - Resolution: Won't Fix Fix Version/s: (was: Launchpad Base 2.5.2) It seems the

[jira] [Updated] (SLING-2757) Support Java 8 as a platform

[ https://issues.apache.org/jira/browse/SLING-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2757: Fix Version/s: (was: Launchpad Base 2.5.4) Launchpad Base 2.5.2 > Su

[jira] [Commented] (SLING-3529) Move startup handling to a separate bundle

[ https://issues.apache.org/jira/browse/SLING-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987646#comment-13987646 ] Carsten Ziegeler commented on SLING-3529: - I totally agree that depending on start

[jira] [Updated] (SLING-3529) Move startup handling to a separate bundle

[ https://issues.apache.org/jira/browse/SLING-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3529: Fix Version/s: Launchpad Impl 1.0.0 > Move startup handling to a separate bundle >

Re: Archetype versions in Jira

Great, thanks (again) On Fri, May 2, 2014 at 3:13 PM, Carsten Ziegeler wrote: > Done > > Carsten > > > 2014-04-30 17:40 GMT+02:00 Robert Munteanu : > >> Hm, I forgot about another version. Can you please also add a release >> version for the org.apache.sling.tooling.support.install ( Apache >> Sl

[VOTE] Release Apache Sling Tooling Support Install 1.0.0

Hi, We solved 1 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12326819 There are no outstanding issues: Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1056/ You can use this UNIX script to download the release and verify

[jira] [Assigned] (SLING-3523) ResourceResolverImpl.mangleNamespace and unmangleNamespaces behave differently

[ https://issues.apache.org/jira/browse/SLING-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-3523: --- Assignee: Carsten Ziegeler > ResourceResolverImpl.mangleNamespace and unmangleNamespa

[jira] [Commented] (SLING-3523) ResourceResolverImpl.mangleNamespace and unmangleNamespaces behave differently

[ https://issues.apache.org/jira/browse/SLING-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987633#comment-13987633 ] Carsten Ziegeler commented on SLING-3523: - I've committed a potential fix to the p

[jira] [Resolved] (SLING-3504) SlingHttpServletResponseImpl.encodeXXX methods always add context path

[ https://issues.apache.org/jira/browse/SLING-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3504. - Resolution: Fixed > SlingHttpServletResponseImpl.encodeXXX methods always add context pat

[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

Re: Archetype versions in Jira

Done Carsten 2014-04-30 17:40 GMT+02:00 Robert Munteanu : > Hm, I forgot about another version. Can you please also add a release > version for the org.apache.sling.tooling.support.install ( Apache > Sling Tooling Support Install ) bundle from tooling/support/install ? > I'd like to cut a relea

[jira] [Commented] (SLING-3114) DefaultContentImporter should guard against a closed InputStream on system view imports

[ https://issues.apache.org/jira/browse/SLING-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987619#comment-13987619 ] Oliver Lietz commented on SLING-3114: - https://github.com/oliverlietz/sling-tests/tree

[jira] [Commented] (SLING-3114) DefaultContentImporter should guard against a closed InputStream on system view imports

[ https://issues.apache.org/jira/browse/SLING-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987617#comment-13987617 ] Oliver Lietz commented on SLING-3114: - Fixed in r1591877 as described above (same beha

[jira] [Resolved] (SLING-3114) DefaultContentImporter should guard against a closed InputStream on system view imports

[ https://issues.apache.org/jira/browse/SLING-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-3114. - Resolution: Fixed > DefaultContentImporter should guard against a closed InputStream on system >

[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 Arch

[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=revision&revision=1591865 > S

[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 I

[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=revision&revision=1591859 > M

[jira] [Created] (SLING-3538) Maven archetypes should use the same port as the default launchpad port

Robert Munteanu created SLING-3538: -- Summary: 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: Sl