[GitHub] sling pull request #213: SLING-6780 - org.apache.sling.scripting.sightly.js....
Github user vladbailescu closed the pull request at: https://github.com/apache/sling/pull/213 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request #213: SLING-6780 - org.apache.sling.scripting.sightly.js....
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/213 SLING-6780 - org.apache.sling.scripting.sightly.js.provider does not ⦠â¦declare an version range for org.mozilla.javascript import * Added dependency to org.apache.sling.scripting.javascript You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling issue/SLING-6780 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/213.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #213 commit 21891430ea2b3af8d860db44009a393bfa7de738 Author: vladbailescu <baile...@adobe.com> Date: 2017-04-12T14:56:54Z SLING-6780 - org.apache.sling.scripting.sightly.js.provider does not declare an version range for org.mozilla.javascript import * Added dependency to org.apache.sling.scripting.javascript --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request #197: SLING-6428 - DateFormat is printed when date-value ...
Github user vladbailescu closed the pull request at: https://github.com/apache/sling/pull/197 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request #197: SLING-6428 - DateFormat is printed when date-value ...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/197 SLING-6428 - DateFormat is printed when date-value is empty * Updated TCK to include tests for empty/undefined formatting input values * Updated implementation to return empty when formatting input is null/undefined * Added missing javadocs You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling issue/SLING-6428 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/197.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #197 commit 8295230ff8472366f07e938ec81fe75f05ab8ca3 Author: vladbailescu <baile...@adobe.com> Date: 2017-01-09T15:07:19Z SLING-6428 - DateFormat is printed when date-value is empty * Updated TCK to include tests for empty/undefined formatting input values * Updated implementation to return empty when formatting input is null/undefined * Added missing javadocs --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request #196: SLING-6445 - HTL scripts do not compile on Windows ...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/196 SLING-6445 - HTL scripts do not compile on Windows if the compiler needs to generate any warnings * Improved error/warning line and column computation to take into account any possible line separator * Added test cases and files with different line separators * Added PowerMockito dependency to be able to mock System#lineSeparator static method You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling issue/SLING-6445 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/196.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #196 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request #191: Added implementation for date and number formatting...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/191 Added implementation for date and number formatting to HTL * SLING-6102 - Adding formatter to HTL/Sightly dates ⦠* SLING-6140 - Adding number formatting to Sightly/HTL You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling format-multiple Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/191.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #191 commit 6927a1e48e9d0ab229edb668d2beb78c7dcda5c3 Author: vladbailescu <baile...@adobe.com> Date: 2016-11-25T20:40:02Z SLING-6102 - Adding formatter to HTL/Sightly dates SLING-6140 - Adding number formatting to Sightly/HTL * Updated HTL compiler and filters, adapted tests * Updated formatting extension * Added some convenience methods to RuntimeObjectModel * Updated TCK reference * Added some sample translations for locale verification commit b593e42f25b80df12785e8e3c83b1f2a6fa37e64 Author: vladbailescu <baile...@adobe.com> Date: 2016-11-30T12:16:53Z SLING-6102 - Adding formatter to HTL/Sightly dates SLING-6140 - Adding number formatting to Sightly/HTL * Updated constants visibility and usage commit aaa77609edf3c6fd39ccdeda405ed45d33fddc66 Author: vladbailescu <baile...@adobe.com> Date: 2016-12-12T17:32:00Z SLING-6102 - Adding formatter to HTL/Sightly dates SLING-6140 - Adding number formatting to Sightly/HTL * Updated performance tests to include date formatting --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request #151: SLING-5813 - Allow a Resource to be used as a Sight...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/151 SLING-5813 - Allow a Resource to be used as a Sightly Use-Object with data-sly-use * Added a new UseProvider for Resource objects * Added tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling SLING-5813_Resource_data-sly-use Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/151.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #151 commit 89fb8a6410b8f5523b38cb7426189c0d8d0d7458 Author: vladbailescu <baile...@adobe.com> Date: 2016-02-16T16:00:53Z SLING-5813 - Allow a Resource to be used as a Sightly Use-Object with data-sly-use * Added a new UseProvider for Resource objects * Added tests --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request #150: SLING-5811 - Properly handle actual Resource's in S...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/150 SLING-5811 - Properly handle actual Resource's in Sightly data-sly-resource * Added handling for actual Resource objects in data-sly-resource * Added tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling SLING-5811_Resource_data-sly-resource Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/150.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #150 commit 6ee525fdb6b1fee7ae35003802653e0785ea0eaf Author: vladbailescu <baile...@adobe.com> Date: 2016-06-28T09:00:42Z SLING-5811 - Properly handle actual Resource's in Sightly data-sly-resource * Added handling for actual Resource objects in data-sly-resource * Added tests --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request #149: SlingSLING-5812 - Add option to include attributes ...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/149 SlingSLING-5812 - Add option to include attributes in request scope for Sightly data-sly-request and data-sly-include * Added new option named requestAttributes to allow setting specific attributes on data-sly-request and data-sly-include * Added tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling SLING-5812_request_attributes Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/149.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #149 commit 4d9009574647248a47f7693c7d47addea8dcc4ad Author: vladbailescu <baile...@adobe.com> Date: 2016-06-27T13:56:43Z SlingSLING-5812 - Add option to include attributes in request scope for Sightly data-sly-request and data-sly-include * Added new option named requestAttributes to allow setting specific attributes on data-sly-request and data-sly-include * Added tests --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4957 - Sightly RenderContextImpl contain...
Github user vladbailescu closed the pull request at: https://github.com/apache/sling/pull/101 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4957 - Sightly RenderContextImpl contain...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/101 SLING-4957 - Sightly RenderContextImpl contains utility methods that don't belong there - Moved utility methods from RenderContextImpl to RenderUtils - Made methods static - Removed unnecessary passing of renderContext just for utility methods You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling SLING-4957_refactor_RenderContextImpl Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/101.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #101 commit a2dcfd43f37c5f3c1032df395a101a9a834ef09c Author: vladbailescu <baile...@adobe.com> Date: 2015-08-19T08:20:25Z SLING-4957 - Sightly RenderContextImpl contains utility methods that don't belong there - Moved utility methods from RenderContextImpl to RenderUtils - Made methods static - Removed unnecessary passing of renderContext just for utility methods commit 0e818da0e22354cf599b5672906d59034b82abc5 Author: vladbailescu <baile...@adobe.com> Date: 2015-09-03T14:21:27Z SLING-4957 - Sightly RenderContextImpl contains utility methods that don't belong there - Moved utility methods from RenderContextImpl to RenderUtils - Made methods static - Removed unnecessary passing of renderContext just for utility methods --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4562 - Sightly: Allow passing of custom ...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/82 SLING-4562 - Sightly: Allow passing of custom options to the I18n extension - Changed the I18nFilter to pass all options to the extension call - Changed the I18nRuntimeExtension to extract locale and hint for the options map You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling SLING-4562_custom_i18n_options Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/82.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #82 commit 107f631fd21cfef4a47537ed66d06694e8e8bdc3 Author: vladbailescu baile...@adobe.com Date: 2015-04-01T18:36:10Z SLING-4562 - Sightly: Allow passing of custom options to the I18n extension - Changed the I18nFilter to pass all options to the extension call - Changed the I18nRuntimeExtension to extract locale and hint for the options map --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4557 - Add JSON and XML validation to th...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/81 SLING-4557 - Add JSON and XML validation to the XSS Protection API - Added validator methods to the API - Added JSON validation implementation using Apache Commons JSON - Added XML validation implementation using SAX - Added unit tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling SLING-4557_json_xml_validation Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/81.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #81 commit 3f910b2f90d5705d53cde31cc264c4c098c91eea Author: vladbailescu baile...@adobe.com Date: 2015-03-31T14:16:19Z SLING-4557 - Add JSON and XML validation to the XSS Protection API - Added validator methods to the API - Added JSON validation implementation using Apache Commons JSON - Added XML validation implementation using SAX - Added unit tests --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4525 - XSS protection path mangling issu...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/80 SLING-4525 - XSS protection path mangling issue - Added proper encoding for colons in query string - Added testcases based on Georg Koester's patch You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling SLING-4525_xss_protection_colon Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/80.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #80 commit 75a326cae99a54de76652e97076bdeba465e65df Author: vladbailescu baile...@adobe.com Date: 2015-03-30T09:13:51Z SLING-4525 - XSS protection path mangling issue - Added proper encoding for colons in query string - Added testcases based on Georg Koester's patch --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4546 - Sightly: Improper handling of ext...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/77 SLING-4546 - Sightly: Improper handling of extension and selectors by data-sly-resource - Improved selector extraction for resource path (taking extensions into consideration) - Added selectors from path or parent to dispatcher options so they will no longer be ignored - Updated testing content and integration tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling SLING-4546_improper_extension_selectors_in_data-sly-resource Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/77.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #77 commit 6b4e0ec1ab1a38c771e0da3e8e86e3e4bcdca1f5 Author: vladbailescu baile...@adobe.com Date: 2015-03-25T14:55:19Z SLING-4546 - Sightly: Improper handling of extension and selectors by data-sly-resource - Improved selector extraction for resource path (taking extensions into consideration) - Added selectors from path or parent to dispatcher options so they will no longer be ignored - Updated testing content and integration tests --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4499 - Sightly: Parsing errors should no...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/71 SLING-4499 - Sightly: Parsing errors should not show up in console/stdout * Added custom error listener to the Lexer as well, as per Sam Harwell's suggestion: http://stackoverflow.com/a/18137301/831507 * Updated the error listener to also accept Lexer recognizers. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling SLING-4499_sightly_parsing_errors Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/71.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #71 commit 93636dbd58935c903920e5e18876bf61184ce8a6 Author: vladbailescu baile...@adobe.com Date: 2015-03-13T14:34:16Z SLING-4499 - Sightly: Parsing errors should not show up in console/stdout Added custom error listener to the Lexer as well, as per Sam Harwell's suggestion: http://stackoverflow.com/a/18137301/831507 Updated the error listener to also accept Lexer recognizers. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4493 Sightly: Create performance tests
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/70 SLING-4493 Sightly: Create performance tests Added: - Sightly performance testing content and scripts - Test suite for JSP, JSP-EL, Sightly Java Use API and Sightly JS Use API You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling SLING-4493_sightly_performance_tests Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/70.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #70 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4494 - Performance: update performance t...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/69 SLING-4494 - Performance: update performance test framework to allow comparison of results Performance testing features which allow us to not only log tests run time but also compare them and fail in case a certain threshold ratio is surpassed. Added: - Annotations for reference method and performance threshold - Deferred results logging to allow for comparison after all tests ran - Analysis of performance against reference method and threshold enforcement You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling SLING-4494_performance_framework_update Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/69.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #69 commit c065f663b5cbc46518972281939b231429180f19 Author: vladbailescu baile...@adobe.com Date: 2015-03-11T15:04:02Z @trivial Converted mixed tabs and spaces indentation to spaces commit 7732f003aef962c21e66eb819190521e04cb7f06 Author: vladbailescu baile...@adobe.com Date: 2015-03-11T15:16:43Z SLING-4494 - Performance: update performance test framework to allow comparison of results Performance testing features which allow us to not only log tests run time but also compare them and fail in case a certain threshold ratio is surpassed. Added: - Annotations for reference method and performance threshold - Deferred results logging to allow for comparison after all tests ran - Analysis of performance against reference method and threshold enforcement --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4093 Added performance tests to compare ...
Github user vladbailescu closed the pull request at: https://github.com/apache/sling/pull/61 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4489 - Sightly: Hyphenated identifiers c...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/68 SLING-4489 - Sightly: Hyphenated identifiers cause a compilation exception in Sightly generated Java classes Added hyphen checks and parsing exception throwing. Added integration tests. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling SLING-4489-Sightly-Hyphenated-identifiers Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/68.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #68 commit 2786d22c3263c58990dc71aa486e90457eb8065e Author: vladbailescu baile...@adobe.com Date: 2015-03-10T14:24:33Z SLING-4489 - Sightly: Hyphenated identifiers cause a compilation exception in Sightly generated Java classes Added hyphen checks and parsing exception throwing. Added integration tests. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4484 - XSS POM references wrong scm URLs
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/67 SLING-4484 - XSS POM references wrong scm URLs Updated URLs to point to correct location. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling SLING-4484-XSS-POM-references-wrong-scm-URLs Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/67.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #67 commit 3af7540b410f8aa26abe6ad0a10142e90059bd0b Author: vladbailescu baile...@adobe.com Date: 2015-03-09T12:11:18Z SLING-4484 - XSS POM references wrong scm URLs Updated URLs to point to correct location. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4484 - XSS POM references wrong scm URLs
Github user vladbailescu closed the pull request at: https://github.com/apache/sling/pull/67 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4483 - Sightly: data-sly-resource does n...
Github user vladbailescu closed the pull request at: https://github.com/apache/sling/pull/66 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4483 - Sightly: data-sly-resource does n...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/66 SLING-4483 - Sightly: data-sly-resource does not properly resolve relative paths Prepended current resource path to relative paths to make sure normalization doesn't break the paths. The same approach is used by sling:include ../ You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling SLING-4483-sightly-resource-relative-paths Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/66.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #66 commit 9728f8ae36001c174fa9ae74a9a6ac17e0979df9 Author: vladbailescu baile...@adobe.com Date: 2015-03-09T11:39:34Z SLING-4483 - Sightly: data-sly-resource does not properly resolve relative paths Prepended current resource path to relative paths to make sure normalization doesn't break the paths. The same approach is used by sling:include ../ --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4428 - Sightly: scriptComment and styleC...
Github user vladbailescu closed the pull request at: https://github.com/apache/sling/pull/65 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4428 - Sightly: scriptComment and styleC...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/65 SLING-4428 - Sightly: scriptComment and styleComment contexts are not doing anything Added support for multiline comment validation in XSS API. Added implementation and test. Added styleComment context to Sightly. Added proper validation for scriptComment and styleComment contexts. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling SLING-4428-Sightly-scriptComment-styleComment Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/65.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #65 commit 3b08e403a684ee393ce0321e9e1fe918b9e397e5 Author: vladbailescu baile...@adobe.com Date: 2015-02-17T14:12:52Z SLING-4428 - Sightly: scriptComment and styleComment contexts are not doing anything Added support for multiline comment validation in XSS API. Added implementation and test. commit f3b88492ea32d97ca25b1547226e579b7072e564 Author: vladbailescu baile...@adobe.com Date: 2015-02-17T14:13:54Z SLING-4428 - Sightly: scriptComment and styleComment contexts are not doing anything Added styleComment context. Added proper validation for scriptComment and styleComment contexts. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4093 Added performance tests to compare ...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/61 SLING-4093 Added performance tests to compare JSP and Sighlty Changes: - Added test content - Made improvements to performance module to allow results comparison and test failures if a threshold ratio is surpassed - ITs for Sightly performance - @trivial formatting changes (separate commit) You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling sightlyperf Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/61.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #61 commit 174e045371301ee9ce9e7a2a33598bed57378159 Author: vladbailescu baile...@adobe.com Date: 2015-01-27T08:56:58Z Added Sightly performance testing content and scripts commit e4adb0c8238da0b208369abf17f363c8c60a6515 Author: vladbailescu baile...@adobe.com Date: 2015-01-30T12:26:40Z Merge branch 'trunk' of github.com:apache/sling into sightlyperf commit d963d9dab9d3dbc3819f2ba05ba54821d592532c Author: vladbailescu baile...@adobe.com Date: 2015-02-03T10:13:48Z Merge branch 'trunk' of github.com:apache/sling into sightlyperf commit a4eb4ae5a2e8b00ac70bd4b6943123a69d498dd2 Author: vladbailescu baile...@adobe.com Date: 2015-02-03T10:22:41Z @trivial Converted mixed tabs and spaces indentation to spaces commit 236da69cac9fa6c795e52b80f059214cf2a897fa Author: vladbailescu baile...@adobe.com Date: 2015-02-03T15:46:43Z SLING-4093 Comparative performance testing features which allow us to not only log tests run time but also compare them and fail in case a certain threshold ratio is surpassed. Added. - Annotations for reference method and performance threshold - Deferred results logging to allow for comparison after all tests ran - Analysis of performance against reference method and threshold enforcement commit 16c4b2cf35cf3e450928794cf28354e3e36169b4 Author: vladbailescu baile...@adobe.com Date: 2015-02-03T15:53:33Z SLING-4093 Added performance testing for Sightly: - Added test suite for JSP, JSP-EL, Sightly Java Use API and Sightly JS Use API commit d50621fe5117b6cce6ba7cf597c48b47e1770169 Author: vladbailescu baile...@adobe.com Date: 2015-02-03T15:53:55Z Merge branch 'trunk' of github.com:apache/sling into sightlyperf --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4177 - Added escaping for styleString co...
Github user vladbailescu closed the pull request at: https://github.com/apache/sling/pull/52 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4177 - Added escaping for styleString co...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/52 SLING-4177 - Added escaping for styleString context * added a new method for style string escaping to XSS API * added implementation and tests * added string escaping in Sightly for styleString context You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling SLING-4177-styleString-context-escaping Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/52.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #52 commit a836590e972831b4ac57c2b690b1be757ddcc32d Author: vladbailescu baile...@adobe.com Date: 2014-12-03T14:48:29Z SLING-4177 - Added escaping for styleString context * added a new method for style string escaping to XSS API * added implementation and tests * added string escaping in Sightly for styleString context --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4177 - Added escaping for styleString co...
Github user vladbailescu closed the pull request at: https://github.com/apache/sling/pull/46 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4177 - Added escaping for styleString co...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/46 SLING-4177 - Added escaping for styleString context * added a new method for style string escaping to XSS API * added implementation (using OWASP encoder) and tests * added string escaping in Sightly for styleString context You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling SLING-4177-escape-stylestring Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/46.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #46 commit 53938e14a860bfd46b1dabbbcba168ae5517a04b Author: vladbailescu baile...@adobe.com Date: 2014-11-20T11:43:20Z SLING-4177 - Added escaping for styleString context * added a new method for style string escaping to XSS API * added implementation and tests * added string escaping in Sightly for styleString context --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] sling pull request: SLING-4176 - Added validation/filtering for St...
GitHub user vladbailescu opened a pull request: https://github.com/apache/sling/pull/38 SLING-4176 - Added validation/filtering for StyleToken context You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladbailescu/sling Sightly-StyleToken-context-is-doing-nothing Alternatively you can review and apply these changes as the patch at: https://github.com/apache/sling/pull/38.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #38 commit e9b7ba0ef09ef3a7f409f6bca71b1911fe2e5065 Author: vladbailescu baile...@adobe.com Date: 2014-11-17T14:00:12Z SLING-4176 - Added validation/filtering for StyleToken context --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
