[jira] [Updated] (SLING-6612) HTL/Sightly sometimes fails to recompile an updated Java POJO located in the repository

[Radu Cotescu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-6612:

Fix Version/s: Scripting HTL Engine 1.0.34

> HTL/Sightly sometimes fails to recompile an updated Java POJO located in the 
> repository
> ---
>
> Key: SLING-6612
> URL: https://issues.apache.org/jira/browse/SLING-6612
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting Sightly Engine 1.0.18
>Reporter: Vlad Bailescu
>Assignee: Radu Cotescu
>Priority: Critical
> Fix For: Scripting HTL Engine 1.0.34
>
> Attachments: SLING-6612-test.patch
>
>
> HTL/Sightly sometimes fails to recompile an updated Java POJO located in the 
> repository because the current implementation of the {{JavaUseProvider}} does 
> not take into account the timestamps of the {{.java}} and {{.class}} files 
> (and relies on {{ResourceChangeListener}} to track updates to the Java 
> classes in the repo).
> I have attached a patch with a test that reproduces the issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SLING-6633) [sightly] NumberFormat should support String-properties with number value

[Radu Cotescu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-6633:

Fix Version/s: Scripting HTL Java Compiler 1.0.10

> [sightly] NumberFormat should support String-properties with number value
> -
>
> Key: SLING-6633
> URL: https://issues.apache.org/jira/browse/SLING-6633
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Affects Versions: Scripting HTL Java Compiler 1.0.6
>Reporter: Feike Visser
>Assignee: Radu Cotescu
> Fix For: Scripting HTL Java Compiler 1.0.10
>
>
> When a node-property is a String-type, but contains a numeric value then 
> there should be done a best effort to do a casting.
> {code}
> ${ '#.00' @ 
> format=linkPage['root/product-grid-container/product-grid/childDepth']}
> {code}
> It the moment the numberFormat is displayed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SLING-6632) [sightly]NumberFormat is printed when format is empty

[Radu Cotescu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-6632:

Affects Version/s: Scripting HTL Engine 1.0.28

> [sightly]NumberFormat is printed when format is empty
> -
>
> Key: SLING-6632
> URL: https://issues.apache.org/jira/browse/SLING-6632
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting HTL Engine 1.0.28
>Reporter: Feike Visser
>Assignee: Radu Cotescu
> Fix For: Scripting HTL Engine 1.0.34
>
>
> I have the following code:
> {code}
> ${ '#.00' @ 
> format=linkPage['root/product-grid-container/product-grid/childDepth']}
> {code}
> Now #.00 is displayed when @ format is empty.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SLING-6633) [sightly] NumberFormat should support String-properties with number value

[Radu Cotescu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-6633:

Affects Version/s: Scripting HTL Java Compiler 1.0.6

> [sightly] NumberFormat should support String-properties with number value
> -
>
> Key: SLING-6633
> URL: https://issues.apache.org/jira/browse/SLING-6633
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Affects Versions: Scripting HTL Java Compiler 1.0.6
>Reporter: Feike Visser
>Assignee: Radu Cotescu
>
> When a node-property is a String-type, but contains a numeric value then 
> there should be done a best effort to do a casting.
> {code}
> ${ '#.00' @ 
> format=linkPage['root/product-grid-container/product-grid/childDepth']}
> {code}
> It the moment the numberFormat is displayed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SLING-6632) [sightly]NumberFormat is printed when format is empty

[Radu Cotescu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-6632:

Fix Version/s: Scripting HTL Engine 1.0.34

> [sightly]NumberFormat is printed when format is empty
> -
>
> Key: SLING-6632
> URL: https://issues.apache.org/jira/browse/SLING-6632
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting HTL Engine 1.0.28
>Reporter: Feike Visser
>Assignee: Radu Cotescu
> Fix For: Scripting HTL Engine 1.0.34
>
>
> I have the following code:
> {code}
> ${ '#.00' @ 
> format=linkPage['root/product-grid-container/product-grid/childDepth']}
> {code}
> Now #.00 is displayed when @ format is empty.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (SLING-6633) [sightly] NumberFormat should support String-properties with number value

[Radu Cotescu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu reassigned SLING-6633:
---

Assignee: Radu Cotescu

> [sightly] NumberFormat should support String-properties with number value
> -
>
> Key: SLING-6633
> URL: https://issues.apache.org/jira/browse/SLING-6633
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Reporter: Feike Visser
>Assignee: Radu Cotescu
>
> When a node-property is a String-type, but contains a numeric value then 
> there should be done a best effort to do a casting.
> {code}
> ${ '#.00' @ 
> format=linkPage['root/product-grid-container/product-grid/childDepth']}
> {code}
> It the moment the numberFormat is displayed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SLING-6632) [sightly]NumberFormat is printed when format is empty

[Radu Cotescu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-6632:

Component/s: Scripting

> [sightly]NumberFormat is printed when format is empty
> -
>
> Key: SLING-6632
> URL: https://issues.apache.org/jira/browse/SLING-6632
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Reporter: Feike Visser
>Assignee: Radu Cotescu
>
> I have the following code:
> {code}
> ${ '#.00' @ 
> format=linkPage['root/product-grid-container/product-grid/childDepth']}
> {code}
> Now #.00 is displayed when @ format is empty.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (SLING-6592) File System Content File Parser

[Konrad Windszus (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905546#comment-15905546
 ] 

Konrad Windszus edited comment on SLING-6592 at 3/10/17 6:49 PM:
-

maybe {{resourcedeserializer}}? The important part is not whether the source is 
a file or an input stream but rather the output format, which is a resource.


was (Author: kwin):
maybe {{resourcedeserializer}}?

> File System Content File Parser
> ---
>
> Key: SLING-6592
> URL: https://issues.apache.org/jira/browse/SLING-6592
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: File System Content File Parser 1.0.0
>
>
> for different usecases around file system resource provider and sling mocks 
> (see related tickets) we need to parse content structures from files in the 
> file system, e.g. in JSON format or JCR XML format.
> we should put this code in a new commons library so it can be reused from the 
> different projects.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SLING-6592) File System Content File Parser

[Konrad Windszus (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905546#comment-15905546
 ] 

Konrad Windszus commented on SLING-6592:


maybe {{resourcedeserializer}}?

> File System Content File Parser
> ---
>
> Key: SLING-6592
> URL: https://issues.apache.org/jira/browse/SLING-6592
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: File System Content File Parser 1.0.0
>
>
> for different usecases around file system resource provider and sling mocks 
> (see related tickets) we need to parse content structures from files in the 
> file system, e.g. in JSON format or JCR XML format.
> we should put this code in a new commons library so it can be reused from the 
> different projects.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (SLING-6592) File System Content File Parser

[Konrad Windszus (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905530#comment-15905530
 ] 

Konrad Windszus edited comment on SLING-6592 at 3/10/17 6:40 PM:
-

{{contentfileparser}} feels a bit redundant. I would rather go for 
{{fileparser}} only then. After all files do IMHO always contain content.


was (Author: kwin):
{{contentfileparser}} feels a bit redundant. I would rather go for 
{{fileparser}} only then.

> File System Content File Parser
> ---
>
> Key: SLING-6592
> URL: https://issues.apache.org/jira/browse/SLING-6592
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: File System Content File Parser 1.0.0
>
>
> for different usecases around file system resource provider and sling mocks 
> (see related tickets) we need to parse content structures from files in the 
> file system, e.g. in JSON format or JCR XML format.
> we should put this code in a new commons library so it can be reused from the 
> different projects.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SLING-6592) File System Content File Parser

[Konrad Windszus (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905530#comment-15905530
 ] 

Konrad Windszus commented on SLING-6592:


{{contentfileparser}} feels a bit redundant. I would rather go for 
{{fileparser}} only then.

> File System Content File Parser
> ---
>
> Key: SLING-6592
> URL: https://issues.apache.org/jira/browse/SLING-6592
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: File System Content File Parser 1.0.0
>
>
> for different usecases around file system resource provider and sling mocks 
> (see related tickets) we need to parse content structures from files in the 
> file system, e.g. in JSON format or JCR XML format.
> we should put this code in a new commons library so it can be reused from the 
> different projects.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SLING-6502) JSP: java.lang.VerifyError (Bad type on operand stack)

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-6502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905521#comment-15905521
 ] 

Oliver Lietz commented on SLING-6502:
-

Switched back to Apache Tomcat 6.0.14 JSP and EL API 
([r1786406|https://svn.apache.org/r1786406]) and using wrappers (SLING-6548 and 
SLING-6549) in Launchpad ([r1786409|https://svn.apache.org/r1786409]).

> JSP: java.lang.VerifyError (Bad type on operand stack)
> --
>
> Key: SLING-6502
> URL: https://issues.apache.org/jira/browse/SLING-6502
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting JSP 2.2.6
> Environment: Apache Karaf 4.1.0-SNAPSHOT (Pax Web 6.0.2)
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Scripting JSP 2.2.8
>
> Attachments: apis.patch
>
>
> {{org.apache.sling.scripting.jsp}} embeds {{jsp-api}} and {{el-api}} from 
> Apache Tomcat ({{6.0.14}}) which causes this error.
> {noformat}
> [...]
> [httpclient.wire.header] : << "HTTP/1.1 500 Server Error[\r][\n]"
> [httpclient.wire.header] : << "Content-Type: text/html;charset=utf-8[\r][\n]"
> [httpclient.wire.header] : << "Transfer-Encoding: chunked[\r][\n]"
> [httpclient.wire.header] : << "Server: Jetty(9.3.15.v20161220)[\r][\n]"
> [httpclient.wire.header] : << "[\r][\n]"
> [httpclient.wire.content] : << "B"
> [httpclient.wire.content] : << "5"
> [httpclient.wire.content] : << "1"
> [httpclient.wire.content] : << "[\r]"
> [httpclient.wire.content] : << "[\n]"
> [httpclient.wire.content] : << "[\n]"
> [httpclient.wire.content] : << "java.lang.VerifyError: Bad type on operand 
> stack[\n]"
> [httpclient.wire.content] : << "Exception Details:[\n]"
> [httpclient.wire.content] : << "  Location:[\n]"
> [httpclient.wire.content] : << "
> org/apache/sling/scripting/jsp/jasper/runtime/JspApplicationContextImpl.createELResolver()Ljavax/el/ELResolver;
>  @28: invokevirtual[\n]"
> [httpclient.wire.content] : << "  Reason:[\n]"
> [httpclient.wire.content] : << "Type 
> javax/servlet/jsp/el/ImplicitObjectELResolver (current frame, 
> stack[1]) is not assignable to javax/el/ELResolver[\n]"
> [httpclient.wire.content] : << "  Current Frame:[\n]"
> [httpclient.wire.content] : << "bci: @28[\n]"
> [httpclient.wire.content] : << "flags: { }[\n]"
> [httpclient.wire.content] : << "locals: { 
> org/apache/sling/scripting/jsp/jasper/runtime/JspApplicationContextImpl,
>  javax/el/CompositeELResolver }[\n]"
> [httpclient.wire.content] : << "stack: { 
> javax/el/CompositeELResolver, 
> javax/servlet/jsp/el/ImplicitObjectELResolver }[\n]"
> [httpclient.wire.content] : << "  Bytecode:[\n]"
> [httpclient.wire.content] : << "0x000: 2a04 b500 062a b400 1dc7 0080 
> bb00 1e59[\n]"
> [httpclient.wire.content] : << "0x010: b700 1f4c 2bbb 0020 59b7 0021 
> b600 222a[\n]"
> [httpclient.wire.content] : << "0x020: b400 05b9 0023 0100 4d2c b900 
> 2401 0099[\n]"
> [httpclient.wire.content] : << "0x030: 0013 2b2c b900 2501 00c0 0026 
> b600 22a7[\n]"
> [httpclient.wire.content] : << "0x040: ffea 2bbb 0027 59b7 0028 b600 
> 222b bb00[\n]"
> [httpclient.wire.content] : << "0x050: 2959 b700 2ab6 0022 2bbb 002b 
> 59b7 002c[\n]"
> [httpclient.wire.content] : << "0x060: b600 222b bb00 2d59 b700 2eb6 
> 0022 2bbb[\n]"
> [httpclient.wire.content] : << "0x070: 002f 59b7 0030 b600 222b bb00 
> 3159 b700[\n]"
> [httpclient.wire.content] : << "0x080: 32b6 0022 2a2b b500 1d2a b400 
> 1db0 [\n]"
> [httpclient.wire.content] : << "  Stackmap Table:[\n]"
> [httpclient.wire.content] : << "
> append_frame(@41,Object[#112],Object[#113])[\n]"
> [httpclient.wire.content] : << "chop_frame(@66,1)[\n]"
> [httpclient.wire.content] : << "chop_frame(@137,1)[\n]"
> [httpclient.wire.content] : << "[\n]"
> [httpclient.wire.content] : << "[\n]"
> [...]
> {noformat}
> {noformat}
> java.lang.VerifyError: Bad type on operand stack
> Exception Details:
>   Location:
> 
> org/apache/sling/scripting/jsp/jasper/runtime/JspApplicationContextImpl.createELResolver()Ljavax/el/ELResolver;
>  @28: invokevirtual
>   Reason:
> Type javax/servlet/jsp/el/ImplicitObjectELResolver (current 
> frame, stack[1]) is not assignable to javax/el/ELResolver
>   Current Frame:
> bci: @28
> flags: { }
> locals: { 
> org/apache/sling/scripting/jsp/jasper/runtime/JspApplicationContextImpl,
>  javax/el/CompositeELResolver }
> stack: { javax/el/CompositeELResolver, 
> javax/servlet/jsp/el/ImplicitObjectELResolver }
>   Bytecode:
> 0x000: 2a04 b500 062a b400 1dc7 0080 bb00 1e59
> 0x010: b700 1f4c 2bbb 0020 59b7 0021 b600 222a
> 0x020: b400 05b9 0023 0100 4d2c b900 2401 0099
> 0x030: 0013 2b2c b900 2501 00c0 0026 b600 22a7
> 

[jira] [Resolved] (SLING-6549) Provide bundle wrapping Apache Tomcat 6.0.14 EL API

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz resolved SLING-6549.
-
Resolution: Done

[r1786401|https://svn.apache.org/r1786401]

> Provide bundle wrapping Apache Tomcat 6.0.14 EL API
> ---
>
> Key: SLING-6549
> URL: https://issues.apache.org/jira/browse/SLING-6549
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Scripting EL API Wrapper 1.0.0
>
>
> fragment for {{javax.el}} (EL API)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (SLING-6548) Provide bundle wrapping Apache Tomcat 6.0.14 JSP API

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz resolved SLING-6548.
-
Resolution: Done

[r1786399|https://svn.apache.org/r1786399]

> Provide bundle wrapping Apache Tomcat 6.0.14 JSP API
> 
>
> Key: SLING-6548
> URL: https://issues.apache.org/jira/browse/SLING-6548
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Scripting JSP API Wrapper 1.0.0
>
>
> fragment for {{javax.servlet.jsp}} (Servlet JSP API)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (SLING-6548) Provide framework extension fragment for Servlet JSP API

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz reassigned SLING-6548:
---

Assignee: Oliver Lietz

> Provide framework extension fragment for Servlet JSP API
> 
>
> Key: SLING-6548
> URL: https://issues.apache.org/jira/browse/SLING-6548
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Scripting JSP API Wrapper 1.0.0
>
>
> fragment for {{javax.servlet.jsp}} (Servlet JSP API)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SLING-6548) Provide bundle wrapping Apache Tomcat 6.0.14 JSP API

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-6548:

Summary: Provide bundle wrapping Apache Tomcat 6.0.14 JSP API  (was: 
Provide framework extension fragment for Servlet JSP API)

> Provide bundle wrapping Apache Tomcat 6.0.14 JSP API
> 
>
> Key: SLING-6548
> URL: https://issues.apache.org/jira/browse/SLING-6548
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Scripting JSP API Wrapper 1.0.0
>
>
> fragment for {{javax.servlet.jsp}} (Servlet JSP API)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (SLING-6549) Provide framework extension fragment for EL API

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz reassigned SLING-6549:
---

Assignee: Oliver Lietz

> Provide framework extension fragment for EL API
> ---
>
> Key: SLING-6549
> URL: https://issues.apache.org/jira/browse/SLING-6549
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Scripting EL API Wrapper 1.0.0
>
>
> fragment for {{javax.el}} (EL API)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SLING-6549) Provide bundle wrapping Apache Tomcat 6.0.14 EL API

[Oliver Lietz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz updated SLING-6549:

Summary: Provide bundle wrapping Apache Tomcat 6.0.14 EL API  (was: Provide 
framework extension fragment for EL API)

> Provide bundle wrapping Apache Tomcat 6.0.14 EL API
> ---
>
> Key: SLING-6549
> URL: https://issues.apache.org/jira/browse/SLING-6549
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Scripting EL API Wrapper 1.0.0
>
>
> fragment for {{javax.el}} (EL API)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SLING-6549) Provide framework extension fragment for EL API

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905487#comment-15905487
 ] 

Oliver Lietz commented on SLING-6549:
-

Instead of providing fragments and using existing JSP and EL API bundles in 
Launchpad (standalone and WAR), providing wrapper bundles for Apache Tomcat 
6.0.14 JSP and EL API and using those is the smallest change possible. 
Scripting JSP will then use Apache Tomcat JSP and EL API as before. That means 
just 2 additional bundles for Launchpad, but freedom to use different ones. 
Changing this issue accordingly.

> Provide framework extension fragment for EL API
> ---
>
> Key: SLING-6549
> URL: https://issues.apache.org/jira/browse/SLING-6549
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Oliver Lietz
> Fix For: Scripting EL API Wrapper 1.0.0
>
>
> fragment for {{javax.el}} (EL API)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SLING-6548) Provide framework extension fragment for Servlet JSP API

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905486#comment-15905486
 ] 

Oliver Lietz commented on SLING-6548:
-

Instead of providing fragments and using existing JSP and EL API bundles in 
Launchpad (standalone and WAR), providing wrapper bundles for Apache Tomcat 
6.0.14 JSP and EL API and using those is the smallest change possible. 
Scripting JSP will then use Apache Tomcat JSP and EL API as before. That means 
just 2 additional bundles for Launchpad, but freedom to use different ones. 
Changing this issue accordingly.

> Provide framework extension fragment for Servlet JSP API
> 
>
> Key: SLING-6548
> URL: https://issues.apache.org/jira/browse/SLING-6548
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Oliver Lietz
> Fix For: Scripting JSP API Wrapper 1.0.0
>
>
> fragment for {{javax.servlet.jsp}} (Servlet JSP API)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SLING-6592) File System Content File Parser

[Stefan Seifert (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905474#comment-15905474
 ] 

Stefan Seifert commented on SLING-6592:
---

yes, this is true, we do not need the "fs" prefix.

what about {{contentfileparser}}. after all it's handling formats designed for 
storage in files.

> File System Content File Parser
> ---
>
> Key: SLING-6592
> URL: https://issues.apache.org/jira/browse/SLING-6592
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: File System Content File Parser 1.0.0
>
>
> for different usecases around file system resource provider and sling mocks 
> (see related tickets) we need to parse content structures from files in the 
> file system, e.g. in JSON format or JCR XML format.
> we should put this code in a new commons library so it can be reused from the 
> different projects.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SLING-6592) File System Content File Parser

[Konrad Windszus (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905454#comment-15905454
 ] 

Konrad Windszus commented on SLING-6592:


I think this module is not really bound to a filesystem, but can also act on 
{{InputStreams}} being provided from arbitrary sources. Maybe we should rename 
the module to something not mentioning the filesystem at all. I would propose 
{{contentparser}} instead of {{fscontentparser}}.
[~sseif...@pro-vision.de] WDYT?

> File System Content File Parser
> ---
>
> Key: SLING-6592
> URL: https://issues.apache.org/jira/browse/SLING-6592
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: File System Content File Parser 1.0.0
>
>
> for different usecases around file system resource provider and sling mocks 
> (see related tickets) we need to parse content structures from files in the 
> file system, e.g. in JSON format or JCR XML format.
> we should put this code in a new commons library so it can be reused from the 
> different projects.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6634) Use new FS Content Provider module in ContentLoader

[Konrad Windszus (JIRA)]

Konrad Windszus created SLING-6634:
--

 Summary: Use new FS Content Provider module in ContentLoader
 Key: SLING-6634
 URL: https://issues.apache.org/jira/browse/SLING-6634
 Project: Sling
  Issue Type: Bug
  Components: JCR
Affects Versions: JCR ContentLoader 2.1.10
Reporter: Konrad Windszus


With the new module being added with SLING-6592 it should be easy to add 
FileVault XML support to the JCR Contentloader.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SLING-6537) Filesystem Resource Provider: Support "mounting" content resources from FileVault JCR XML files

[Stefan Seifert (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905425#comment-15905425
 ] 

Stefan Seifert commented on SLING-6537:
---

configuration has changed a bit - final version ist documented here:
https://sling.apache.org/documentation/bundles/accessing-filesystem-resources-extensions-fsresource.html

> Filesystem Resource Provider: Support "mounting" content resources from 
> FileVault JCR XML files
> ---
>
> Key: SLING-6537
> URL: https://issues.apache.org/jira/browse/SLING-6537
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: File System Resource Provider 1.3.0, File System 
> Resource Provider 2.0.0
>
>
> it would be nice if the filesystem resource provider does not only support 
> serving binary files and folders, but also arbitrary resources stored in 
> FileVault JCR XML files in the folder hierarchy which are normally packaged 
> and uploaded.
> is is necessary to explicitly switch this feature on per configuration, 
> because it may be desired to directly serve the JSON and XML files as binary 
> files in some cases.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SLING-6622) maven-sling-plugin: Add "fsmount" and "fsunmount" goals

[Stefan Seifert (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-6622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905427#comment-15905427
 ] 

Stefan Seifert commented on SLING-6622:
---

documentation: http://sling.apache.org/components/maven-sling-plugin/

> maven-sling-plugin: Add "fsmount" and "fsunmount" goals
> ---
>
> Key: SLING-6622
> URL: https://issues.apache.org/jira/browse/SLING-6622
> Project: Sling
>  Issue Type: New Feature
>  Components: Tooling
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: Maven Sling Plugin 2.2.0
>
>
> the feature to add osgi configurations for the file system resource provider 
> is quite hidden with the optional "mountByFs" property from the 
> install/uninstall goals.
> we should additionally add two explicit goals "fsmount" and "fsunmount" 
> allowing to add or remove these configs without installing/uninstalling the 
> bundle at the same time.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SLING-6440) Filesystem Resource Provider: Support "mounting" content resources from JSON files

[Stefan Seifert (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-6440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905424#comment-15905424
 ] 

Stefan Seifert commented on SLING-6440:
---

configuration has changed a bit - final version ist documented here:
https://sling.apache.org/documentation/bundles/accessing-filesystem-resources-extensions-fsresource.html

> Filesystem Resource Provider: Support "mounting" content resources from JSON 
> files
> --
>
> Key: SLING-6440
> URL: https://issues.apache.org/jira/browse/SLING-6440
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
> Fix For: File System Resource Provider 1.3.0, File System 
> Resource Provider 2.0.0
>
>
> it would be nice if the filesystem resource provider does not only support 
> serving binary files and folders, but also arbitrary resources stored in 
> .json files in the folder hierarchy which are normally extracted when 
> installing the bundle with sling-initial-content.
> is is necessary to explicitly switch this feature on per configuration, 
> because it may be desired to directly serve the JSON files as binary files in 
> some cases.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SLING-6633) [sightly] NumberFormat should support String-properties with number value

[Feike Visser (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Feike Visser updated SLING-6633:

Issue Type: Improvement  (was: Bug)

> [sightly] NumberFormat should support String-properties with number value
> -
>
> Key: SLING-6633
> URL: https://issues.apache.org/jira/browse/SLING-6633
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Reporter: Feike Visser
>
> When a node-property is a String-type, but contains a numeric value then 
> there should be done a best effort to do a casting.
> {code}
> ${ '#.00' @ 
> format=linkPage['root/product-grid-container/product-grid/childDepth']}
> {code}
> It the moment the numberFormat is displayed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6633) [sightly] NumberFormat should support String-properties with number value

[Feike Visser (JIRA)]

Feike Visser created SLING-6633:
---

 Summary: [sightly] NumberFormat should support String-properties 
with number value
 Key: SLING-6633
 URL: https://issues.apache.org/jira/browse/SLING-6633
 Project: Sling
  Issue Type: Bug
  Components: Scripting
Reporter: Feike Visser


When a node-property is a String-type, but contains a numeric value then there 
should be done a best effort to do a casting.

{code}
${ '#.00' @ 
format=linkPage['root/product-grid-container/product-grid/childDepth']}
{code}

It the moment the numberFormat is displayed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (SLING-6632) [sightly]NumberFormat is printed when format is empty

[Radu Cotescu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu reassigned SLING-6632:
---

Assignee: Radu Cotescu

> [sightly]NumberFormat is printed when format is empty
> -
>
> Key: SLING-6632
> URL: https://issues.apache.org/jira/browse/SLING-6632
> Project: Sling
>  Issue Type: Bug
>Reporter: Feike Visser
>Assignee: Radu Cotescu
>
> I have the following code:
> {code}
> ${ '#.00' @ 
> format=linkPage['root/product-grid-container/product-grid/childDepth']}
> {code}
> Now #.00 is displayed when @ format is empty.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

RE: Maven plugin documentation

[Stefan Seifert]

>On Fri, Mar 10, 2017 at 9:58 AM, Stefan Seifert 
>wrote:
>> ...step 4 and 5 are not correct currently...
>
>I have restored your previous steps 4. and 5. , should be ok now at
>http://sling.apache.org/documentation/development/release-management.html
>
>-Bertrand

thanks!

stefan

Re: Maven plugin documentation

[Bertrand Delacretaz]

On Fri, Mar 10, 2017 at 9:58 AM, Stefan Seifert  wrote:
> Bertrand wrote:
>>Also, now when publishing the site via Apache CMS,
>>https://cms.apache.org/sling/publish?diff=1 shows lots of removed
>>files...

> ...I detected that in felix-site a file 'content/extpaths.txt' exists which 
> exactly
> defines this folder as "externall controlled" and keeps it intact on cms 
> publishing...

Ok, I have created https://issues.apache.org/jira/browse/INFRA-13644 about this.

-Bertrand

Re: Maven plugin documentation

[Bertrand Delacretaz]

On Fri, Mar 10, 2017 at 9:58 AM, Stefan Seifert  wrote:
> ...step 4 and 5 are not correct currently...

I have restored your previous steps 4. and 5. , should be ok now at
http://sling.apache.org/documentation/development/release-management.html

-Bertrand

Re: Maven plugin documentation

[Bertrand Delacretaz]

On Fri, Mar 10, 2017 at 9:58 AM, Stefan Seifert  wrote:
> ...step 4 and 5 are not correct currently.
> the 'scm-publish:publish-scm' goal directly commits the generated 
> documentation to a path
> https://svn.apache.org/repos/infra/websites/production/sling/content/component/-archives/-LATEST..

argh...so that's why my test was committed there ;-)

I'll fix that and the documentation now.

-Bertrand

[jira] [Updated] (SLING-6632) [sightly]NumberFormat is printed when format is empty

[Feike Visser (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Feike Visser updated SLING-6632:

Summary: [sightly]NumberFormat is printed when format is empty  (was: 
Number)

> [sightly]NumberFormat is printed when format is empty
> -
>
> Key: SLING-6632
> URL: https://issues.apache.org/jira/browse/SLING-6632
> Project: Sling
>  Issue Type: Bug
>Reporter: Feike Visser
>
> I have the following code:
> {code}
> ${ '#.00' @ 
> format=linkPage['root/product-grid-container/product-grid/childDepth']}
> {code}
> Now #.00 is displayed when @ format is empty.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SLING-6632) Number

[Feike Visser (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Feike Visser updated SLING-6632:

Description: 
I have the following code:

{code}
${ '#.00' @ 
format=linkPage['root/product-grid-container/product-grid/childDepth']}
{code}

Now #.00 is displayed when @ format is empty.

> Number
> --
>
> Key: SLING-6632
> URL: https://issues.apache.org/jira/browse/SLING-6632
> Project: Sling
>  Issue Type: Bug
>Reporter: Feike Visser
>
> I have the following code:
> {code}
> ${ '#.00' @ 
> format=linkPage['root/product-grid-container/product-grid/childDepth']}
> {code}
> Now #.00 is displayed when @ format is empty.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6632) Number

[Feike Visser (JIRA)]

Feike Visser created SLING-6632:
---

 Summary: Number
 Key: SLING-6632
 URL: https://issues.apache.org/jira/browse/SLING-6632
 Project: Sling
  Issue Type: Bug
Reporter: Feike Visser






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SLING-6631) upgrade Sling Datasource extension to latest Tomcat JDBC

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu updated SLING-6631:
---
Fix Version/s: DataSource Provider 1.0.4

> upgrade Sling Datasource extension to latest Tomcat JDBC
> 
>
> Key: SLING-6631
> URL: https://issues.apache.org/jira/browse/SLING-6631
> Project: Sling
>  Issue Type: Task
>  Components: Extensions
>Reporter: Julian Reschke
>Assignee: Robert Munteanu
>Priority: Minor
> Fix For: DataSource Provider 1.0.4
>
>
> {noformat}
> Index: pom.xml
> ===
> --- pom.xml (Revision 1786291)
> +++ pom.xml (Arbeitskopie)
> @@ -138,7 +138,7 @@
>  
>org.apache.tomcat
>tomcat-jdbc
> -  7.0.72
> +  7.0.75
>
>  
>org.apache.tomcat
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (SLING-6631) upgrade Sling Datasource extension to latest Tomcat JDBC

[Robert Munteanu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Munteanu resolved SLING-6631.

Resolution: Fixed
  Assignee: Robert Munteanu

Applied in [r1786324|https://svn.apache.org/r1786324], thanks for the patch!

> upgrade Sling Datasource extension to latest Tomcat JDBC
> 
>
> Key: SLING-6631
> URL: https://issues.apache.org/jira/browse/SLING-6631
> Project: Sling
>  Issue Type: Task
>  Components: Extensions
>Reporter: Julian Reschke
>Assignee: Robert Munteanu
>Priority: Minor
>
> {noformat}
> Index: pom.xml
> ===
> --- pom.xml (Revision 1786291)
> +++ pom.xml (Arbeitskopie)
> @@ -138,7 +138,7 @@
>  
>org.apache.tomcat
>tomcat-jdbc
> -  7.0.72
> +  7.0.75
>
>  
>org.apache.tomcat
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

RE: Maven plugin documentation

[Stefan Seifert]

>I have slightly reworded the instructions at the end of
>http://sling.apache.org/documentation/development/release-management.html
>, could you cross-check?

step 4 and 5 are not correct currently.
the 'scm-publish:publish-scm' goal directly commits the generated documentation 
to a path
https://svn.apache.org/repos/infra/websites/production/sling/content/component/-archives/-LATEST

so it's already in svn, and from there it has to be renamed (or moved) to 
'-archives/-' *and* to a folder 
'' (which already exists with the old docs, so the old has to be 
removed first resulting in a replace). the site html should not be svn-imported 
again, because then it's duplicated in the svn history. the process is 
described here [1]. i do not know why the publish-scm plugin does not do this 
steps automatically.

the other changes are fine.


>Also, now when publishing the site via Apache CMS,
>https://cms.apache.org/sling/publish?diff=1 shows lots of removed
>files under content/components/htl-maven-plugin (probably the whole
>folder), could that be related to what you did?
>
>http://sling.apache.org/components/ looks ok to me, the
>htl-maven-plugin folder is still there after CMS publishing - but this
>makes the publish diff unusable. I can have a closer look but maybe
>you understand what happened based on your changes?

this is strange, not sure why this happens.
when starting testing the publication of the documtation I had the problem that 
new updates to the cms site completely removed the "components" folder. then I 
detected that in felix-site a file 'content/extpaths.txt' exists which exactly 
defines this folder as "externall controlled" and keeps it intact on cms 
publishing. so there is no longer a conflict and i thought all is fine. i have 
no idea what the effect on this diff view is. it is happing on felix site as 
well [2]. unfortunately i have no deeper knowledge on this svn-based cms 
publishing features.

stefan


[1] 
http://maven.apache.org/developers/website/deploy-component-reference-documentation.html
[2] https://cms.apache.org/felix/publish?diff=1

Re: [VOTE] Apache Sling Repoinit JCR 1.1.4

[Bertrand Delacretaz]

On Thu, Mar 9, 2017 at 7:19 PM, Oliver Lietz  wrote:
> ...Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1662/ ...

Thank you very much for taking care of these changes and +1 for the release of

SHA1(org.apache.sling.jcr.repoinit-1.1.4-source-release.zip)
= 00ee7fecffc70540ad4aa5eb6f2fc619c306efdc

checked signatures, svn tag and build.

-Bertrand

Re: Maven plugin documentation

[Bertrand Delacretaz]

Hi Stefan,

On Fri, Mar 10, 2017 at 1:25 AM, Stefan Seifert  wrote:
> ...inspired by the process used by the felix maven-bundle-plugin i've set up 
> the same for the three most important sling plugins...

Great, thanks for this!

I have slightly reworded the instructions at the end of
http://sling.apache.org/documentation/development/release-management.html
, could you cross-check?

Also, now when publishing the site via Apache CMS,
https://cms.apache.org/sling/publish?diff=1 shows lots of removed
files under content/components/htl-maven-plugin (probably the whole
folder), could that be related to what you did?

http://sling.apache.org/components/ looks ok to me, the
htl-maven-plugin folder is still there after CMS publishing - but this
makes the publish diff unusable. I can have a closer look but maybe
you understand what happened based on your changes?

-Bertrand