[jira] [Commented] (SLING-5135) Extend AbstractSlingRepositoryManager to whitelist loginAdministrative usage

[Antonio Sanso (JIRA)]

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

Antonio Sanso commented on SLING-5135:
--

[~bdelacretaz] those are good questions indeed. At the moment I opened this 
issue only to track the improvement and would not know the answers :p

> Extend AbstractSlingRepositoryManager to whitelist loginAdministrative usage
> 
>
> Key: SLING-5135
> URL: https://issues.apache.org/jira/browse/SLING-5135
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Reporter: Antonio Sanso
>
> {{AbstractSlingRepositoryManager}} contains a method that disable 
> loginAdministrative support
> {code}
> /**
>  * Returns whether to disable the
>  * {@code SlingRepository.loginAdministrative} method or not.
>  *
>  * @return {@code true} if {@code SlingRepository.loginAdministrative} is
>  * disabled.
>  */
> public final boolean isDisableLoginAdministrative() 
> {code}
> This is a global configuration. It would be nice to have an extension of such 
> mechanism that contains a white list of (few) legit usage of 
> {{loginAdministrative}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5135) Extend AbstractSlingRepositoryManager to whitelist loginAdministrative usage

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-5135:


How would you specify the legit usages? Based on which bundle is using the 
service? On the calling stack trace?

> Extend AbstractSlingRepositoryManager to whitelist loginAdministrative usage
> 
>
> Key: SLING-5135
> URL: https://issues.apache.org/jira/browse/SLING-5135
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Reporter: Antonio Sanso
>
> {{AbstractSlingRepositoryManager}} contains a method that disable 
> loginAdministrative support
> {code}
> /**
>  * Returns whether to disable the
>  * {@code SlingRepository.loginAdministrative} method or not.
>  *
>  * @return {@code true} if {@code SlingRepository.loginAdministrative} is
>  * disabled.
>  */
> public final boolean isDisableLoginAdministrative() 
> {code}
> This is a global configuration. It would be nice to have an extension of such 
> mechanism that contains a white list of (few) legit usage of 
> {{loginAdministrative}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-5135) Extend AbstractSlingRepositoryManager to whitelist loginAdministrative usage

[Antonio Sanso (JIRA)]

Antonio Sanso created SLING-5135:


 Summary: Extend AbstractSlingRepositoryManager to whitelist 
loginAdministrative usage
 Key: SLING-5135
 URL: https://issues.apache.org/jira/browse/SLING-5135
 Project: Sling
  Issue Type: Bug
  Components: JCR
Reporter: Antonio Sanso


{{AbstractSlingRepositoryManager}} contains a method that disable 
loginAdministrative support

{code}
/**
 * Returns whether to disable the
 * {@code SlingRepository.loginAdministrative} method or not.
 *
 * @return {@code true} if {@code SlingRepository.loginAdministrative} is
 * disabled.
 */
public final boolean isDisableLoginAdministrative() 
{code}

This is a global configuration. It would be nice to have an extension of such 
mechanism that contains a white list of (few) legit usage of 
{{loginAdministrative}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4873) Upgrade to Oak 1.3.2

[Robert Munteanu (JIRA)]

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

Robert Munteanu closed SLING-4873.
--

> Upgrade to Oak 1.3.2
> 
>
> Key: SLING-4873
> URL: https://issues.apache.org/jira/browse/SLING-4873
> Project: Sling
>  Issue Type: Improvement
>  Components: Launchpad, Oak
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: JCR Oak Server 1.0.0, Launchpad Karaf Features 0.2.0, 
> Launchpad Builder 8
>
>
> using unstable branch {{1.3}} should be noncritical as [Moving to 
> Oak|SLING-4528] is still work in progress



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4528) Moving to Oak

[Robert Munteanu (JIRA)]

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

Robert Munteanu closed SLING-4528.
--

> Moving to Oak
> -
>
> Key: SLING-4528
> URL: https://issues.apache.org/jira/browse/SLING-4528
> Project: Sling
>  Issue Type: Task
>  Components: Oak
>Reporter: Oliver Lietz
>  Labels: oak
> Fix For: JCR Oak Server 1.0.0
>
>
> _Apache Sling Oak Repository Server_ ({{org.apache.sling.jcr.oak.server}}) is 
> not released and contains some TODOs and {{JcrRepositoryHacks}}.
> What needs to be done for a first release, [~bdelacretaz] and [~mduerig]?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4696) Upgrade to Oak 1.2.2

[Robert Munteanu (JIRA)]

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

Robert Munteanu closed SLING-4696.
--

> Upgrade to Oak 1.2.2
> 
>
> Key: SLING-4696
> URL: https://issues.apache.org/jira/browse/SLING-4696
> Project: Sling
>  Issue Type: Improvement
>  Components: Launchpad, Oak
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: JCR Oak Server 1.0.0, Launchpad Builder 8
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313221=12331970
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313221=12332046



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4995) Upgrade to Oak 1.3.4

[Robert Munteanu (JIRA)]

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

Robert Munteanu closed SLING-4995.
--

> Upgrade to Oak 1.3.4
> 
>
> Key: SLING-4995
> URL: https://issues.apache.org/jira/browse/SLING-4995
> Project: Sling
>  Issue Type: Task
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
> Fix For: JCR Oak Server 1.0.0, Launchpad Karaf Features 0.2.0, 
> Launchpad Builder 8
>
>
> Oak 1.3.4 is the latest release



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4690) Use oak's OsgiRepository instead of JcrRepositoryHacks

[Robert Munteanu (JIRA)]

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

Robert Munteanu closed SLING-4690.
--

> Use oak's OsgiRepository instead of JcrRepositoryHacks
> --
>
> Key: SLING-4690
> URL: https://issues.apache.org/jira/browse/SLING-4690
> Project: Sling
>  Issue Type: Improvement
>  Components: Oak
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: JCR Oak Server 1.0.0
>
>
> Oak already provides a repository wrapper for usage in OSGi environments, so 
> we should no longer use our own JcrRepositoryHacks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4911) Upgrade to Oak 1.3.3

[Robert Munteanu (JIRA)]

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

Robert Munteanu closed SLING-4911.
--

> Upgrade to Oak 1.3.3
> 
>
> Key: SLING-4911
> URL: https://issues.apache.org/jira/browse/SLING-4911
> Project: Sling
>  Issue Type: Improvement
>  Components: Launchpad, Oak
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: JCR Oak Server 1.0.0, Launchpad Karaf Features 0.2.0, 
> Launchpad Builder 8
>
>
> * {{bundles/jcr/it-jackrabbit-oak/pom.xml}}
> * {{bundles/jcr/oak-server/pom.xml}}
> * {{launchpad/builder/src/main/provisioning/oak.txt}}
> * 
> {{contrib/launchpad/karaf/org.apache.sling.launchpad.karaf-features/src/main/feature/feature.xml}}
> SLING-4873



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-5104) Update to Oak 1.3.7

[Robert Munteanu (JIRA)]

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

Robert Munteanu closed SLING-5104.
--

> Update to Oak 1.3.7
> ---
>
> Key: SLING-5104
> URL: https://issues.apache.org/jira/browse/SLING-5104
> Project: Sling
>  Issue Type: Improvement
>  Components: Oak
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: JCR Oak Server 1.0.0
>
>
> This is the latest release in the 1.3.x stream, which we're using now.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4255) SLING2522Test IT fails

[Robert Munteanu (JIRA)]

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

Robert Munteanu closed SLING-4255.
--

> SLING2522Test IT fails
> --
>
> Key: SLING-4255
> URL: https://issues.apache.org/jira/browse/SLING-4255
> Project: Sling
>  Issue Type: Bug
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>  Labels: sling-IT
> Fix For: Adapter 2.1.6
>
>
> At https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6
> SLING2522Test.testThatServicesWhichLikeAdapterFactoriesArentShowInTheW
> Failing for the past 7 builds (Since Unstable#2862 )
> Expected status 200 for http://localhost:47139/system/console/adapters 
> ...
> expected:<200> but was:<500>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4258) JSON representation of Calendar values should preserve timezone

[Robert Munteanu (JIRA)]

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

Robert Munteanu closed SLING-4258.
--

> JSON representation of Calendar values should preserve timezone
> ---
>
> Key: SLING-4258
> URL: https://issues.apache.org/jira/browse/SLING-4258
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Affects Versions: Commons JSON 2.0.10
>Reporter: Santiago García Pimentel
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: Commons JSON 2.0.12
>
> Attachments: SLING-4258.patch
>
>
> Im currently doing some things with dates in Sling that involve timezones and 
> I find that the documentation regarding it is not particularly clear.
> according to 
> https://sling.apache.org/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html#date-properties
> several formats are defined. 
> I found that the only format that saves a provided timezone is the ISO8601 
> format, rest of them relies in a Date object, which does not have timezones. 
> Could this be clearly stated?
> Also, the ISO8601 parser is problematic. It relies on the Jackrabbit parser 
> which uses format "±-MM-DDThh:mm:ss.SSSTZD", but according to 
> http://www.w3.org/TR/NOTE-datetime the ISO format does not have milliseconds 
> on it ("SSS"). So it is very hard to find a way to keep the timezone 
> information (I had to dig through the code to figure it out)
> Could we please replace ISO8601 with the actual format 
> "±-MM-DDThh:mm:ss.SSSTZD" so it is clearer?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4958) add JMX MBean for Sling Servlet Filter

[Robert Munteanu (JIRA)]

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

Robert Munteanu closed SLING-4958.
--

> add JMX MBean for Sling Servlet Filter 
> ---
>
> Key: SLING-4958
> URL: https://issues.apache.org/jira/browse/SLING-4958
> Project: Sling
>  Issue Type: Improvement
>  Components: Engine
>Reporter: Antonio Sanso
>Assignee: Antonio Sanso
>Priority: Minor
> Fix For: Engine 2.4.4
>
> Attachments: SLING-4958-patch.txt
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4544) Performance: MessageFormat shouldn't be used for logging in SlingRequestProgressTracker

[Robert Munteanu (JIRA)]

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

Robert Munteanu closed SLING-4544.
--

> Performance: MessageFormat shouldn't be used for logging in 
> SlingRequestProgressTracker
> ---
>
> Key: SLING-4544
> URL: https://issues.apache.org/jira/browse/SLING-4544
> Project: Sling
>  Issue Type: Improvement
>  Components: Engine
>Affects Versions: Engine 2.4.0
>Reporter: Joel Richard
>Assignee: Tomek Rękawek
>  Labels: performance
> Fix For: Engine 2.4.4
>
> Attachments: SLING-4544.patch, Screen Shot 2015-03-25 at 10.42.05.png
>
>
> I am profiling an application where 1-5% of the rendering time is spent in 
> MessageFormat.format for SlingRequestProgressTracker.log (see attached 
> screenshot). Since the advanced capabilities of MessageFormat are not 
> required here, it should be rather easy to implement a utility which supports 
> \{x} as well but is much faster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[RESULT][VOTE] Release Apache Sling Adapter Manager Implementation 2.1.6

[Robert Munteanu]

Hi,

The vote has passed with the following result :

+1 (binding): Robert Munteanu, Stefan Egli, Carsten Ziegeler, Oliver
Lietz.

I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.

Robert

[jira] [Closed] (SLING-4563) Log start level number on STARTLEVEL CHANGED event

[Robert Munteanu (JIRA)]

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

Robert Munteanu closed SLING-4563.
--

> Log start level number on STARTLEVEL CHANGED event
> --
>
> Key: SLING-4563
> URL: https://issues.apache.org/jira/browse/SLING-4563
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Reporter: Alexander Klimetschek
>Assignee: Carsten Ziegeler
> Fix For: Commons Log Service 1.0.6
>
> Attachments: SLING-4563.patch
>
>
> Currently, the Sling logservice just logs that an osgi start level has 
> changed, without indicating which one:
> {noformat}
> ...org.apache.felix.framework FrameworkEvent STARTLEVEL CHANGED
> {noformat}
> This should include the current framework startlevel:
> {noformat}
> ...org.apache.felix.framework FrameworkEvent STARTLEVEL CHANGED to 14
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4804) Semicolon parameters are not passed to the resource resolver

[Robert Munteanu (JIRA)]

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

Robert Munteanu closed SLING-4804.
--

> Semicolon parameters are not passed to the resource resolver
> 
>
> Key: SLING-4804
> URL: https://issues.apache.org/jira/browse/SLING-4804
> Project: Sling
>  Issue Type: Bug
>  Components: Engine
>Affects Versions: Engine 2.4.2
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
>Priority: Minor
> Fix For: Engine 2.4.4
>
> Attachments: SLING-4804-2.patch, SLING-4804-3.patch, SLING-4804.patch
>
>
> SLING-848 provided a way to pass semicolon-separated parameters to the 
> resource provider. However, such parameters are removed from the 
> {{HttpServletRequest#getPathInfo()}}, which is used in the 
> {{RequestData#initResource()}} method to resolve the resource from the URI. 
> As a result, resource resolver and resource provider don't see the semicolon 
> parameters and can't use them.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4999) Check synchronization in RequestProcessorMBeanImpl

[Robert Munteanu (JIRA)]

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

Robert Munteanu closed SLING-4999.
--

> Check synchronization in RequestProcessorMBeanImpl
> --
>
> Key: SLING-4999
> URL: https://issues.apache.org/jira/browse/SLING-4999
> Project: Sling
>  Issue Type: Improvement
>  Components: Engine
>Affects Versions: Engine 2.4.2
>Reporter: Carsten Ziegeler
>Assignee: Robert Munteanu
> Fix For: Engine 2.4.4
>
> Attachments: 
> 0001-SLING-4999-Check-synchronization-in-RequestProcessor.patch
>
>
> Each and every request goes through RequestProcessorMBeanImpl#addRequestData 
> which is a synchronized block. I think this is a rather heavy bottleneck for 
> request processing.
> In addition, some of the methods which do additional calculation are sync'ed 
> (like getStandardDeviationDurationMsec) but others are not (like 
> getStandardDeviationPeakRecursionDepth). This seems a little bit arbitrary to 
> me



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4921) SlingMainServlet logs IOException at debug level only

[Robert Munteanu (JIRA)]

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

Robert Munteanu closed SLING-4921.
--

> SlingMainServlet logs IOException at debug level only
> -
>
> Key: SLING-4921
> URL: https://issues.apache.org/jira/browse/SLING-4921
> Project: Sling
>  Issue Type: Bug
>  Components: Engine
>Affects Versions: Engine 2.4.2
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: Engine 2.4.4
>
> Attachments: SLING-4921.patch, cae-stack-trace.txt
>
>
> The log level of IOException was reduced to DEBUG for SLING-3498, to avoid 
> polluting the logs with client disconnect exceptions, which are hard to 
> identify reliably.
> The downside is that this hides legit IOException from application code, as 
> debug logs are usually not enabled on production systems.
> We should find a better to way to separate client disconnects from 
> application-level IOException, and log the latter in the usual way.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[RESULT][VOTE] Release Apache Sling Jackrabbit UserManager Support 2.2.4

[Robert Munteanu]

Hi,

The vote has passed with the following result :

+1 (binding): Stefan Egli, Robert Munteanu, Antonio Sanso, Carsten
Ziegeler, Oliver Lietz

I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.

[RESULT][VOTE] Release Apache Sling JSON Library 2.0.12

[Robert Munteanu]

Hi,

The vote has passed with the following result :

+1 (binding): Robert Munteanu, Carsten Ziegeler, Stefan Egli, Oliver
Lietz.

I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.

Robert

[jira] [Closed] (SLING-3828) Hardcoded creation of SegmentNodeStoreService config makes it impossible to remove this configuration

[Robert Munteanu (JIRA)]

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

Robert Munteanu closed SLING-3828.
--

> Hardcoded creation of SegmentNodeStoreService config makes it impossible to 
> remove this configuration
> -
>
> Key: SLING-3828
> URL: https://issues.apache.org/jira/browse/SLING-3828
> Project: Sling
>  Issue Type: Bug
>  Components: Oak
>Reporter: David Bosschaert
>Assignee: Carsten Ziegeler
> Fix For: Launchpad Builder 7, JCR Oak Server 1.0.0
>
> Attachments: oak-server.diff
>
>
> The Activator in org.apache.sling.jcr.oak.server always creates a 
> configuration item with PID 
> org.apache.jackrabbit.oak.plugins.segment.SegmentNodeStoreService if it isn't 
> there. This means that if you delete this configuration, it will reappear on 
> restart.
> In some cases this configuration is undesirable, for example when running 
> with Mongo. Therefore it should be possible to delete it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-5105) Do not export org.apache.sling.oak.server

[Robert Munteanu (JIRA)]

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

Robert Munteanu closed SLING-5105.
--

> Do not export org.apache.sling.oak.server
> -
>
> Key: SLING-5105
> URL: https://issues.apache.org/jira/browse/SLING-5105
> Project: Sling
>  Issue Type: Bug
>  Components: Oak
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: JCR Oak Server 1.0.0
>
>
> The `org.apache.sling.oak.server` package is exported but it should not be. 
> Also there's a comment in the pom file which alludes to that
> {noformat}
> 
> org.apache.sling.oak.server.*
> 
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SLING-5118) Release engine 2.4.4

[Robert Munteanu (JIRA)]

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

Robert Munteanu resolved SLING-5118.

Resolution: Fixed

> Release engine 2.4.4
> 
>
> Key: SLING-5118
> URL: https://issues.apache.org/jira/browse/SLING-5118
> Project: Sling
>  Issue Type: Sub-task
>  Components: Launchpad
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>
> Rolling back to Engine 2.4.2 from 2.4.3-SNAPSHOT makes an IT fail:
> org.apache.sling.launchpad.webapp.integrationtest.VersionParameterTest.testVersionParameter
> We will release engine 2.4.4 and include it in Launchpad 8



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5135) Extend AbstractSlingRepositoryManager to whitelist loginAdministrative usage

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-5135:


Ok, it's good to know that you are aware of the issue ;-)

> Extend AbstractSlingRepositoryManager to whitelist loginAdministrative usage
> 
>
> Key: SLING-5135
> URL: https://issues.apache.org/jira/browse/SLING-5135
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Reporter: Antonio Sanso
>
> {{AbstractSlingRepositoryManager}} contains a method that disable 
> loginAdministrative support
> {code}
> /**
>  * Returns whether to disable the
>  * {@code SlingRepository.loginAdministrative} method or not.
>  *
>  * @return {@code true} if {@code SlingRepository.loginAdministrative} is
>  * disabled.
>  */
> public final boolean isDisableLoginAdministrative() 
> {code}
> This is a global configuration. It would be nice to have an extension of such 
> mechanism that contains a white list of (few) legit usage of 
> {{loginAdministrative}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[RESULT][VOTE] Release Apache Sling Oak Repository Server 1.0.0

[Robert Munteanu]

Hi,

The vote has passed with the following result :

+1 (binding): Robert Munteanu, Carsten Ziegeler, Stefan Egli, Oliver
Lietz.

I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.

Robert

[RESULT][VOTE] Release Apache Sling Engine Implementation 2.4.4

[Robert Munteanu]

Hi,

The vote has passed with the following result :

+1 (binding): Robert Munteanu, Stefan Egli, Antonio Sanso, Carsten Ziegeler, 
Oliver Lietz.

I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.

Robert

[RESULT][VOTE] Release Apache Sling OSGi LogService Implementation 1.0.6

[Robert Munteanu]

Hi,

The vote has passed with the following result :

+1 (binding): Robert Munteanu, Carsten Ziegeler, Stefan Egli .

I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.

Robert

[jira] [Resolved] (SLING-5109) Release commons.json 2.0.12

[Robert Munteanu (JIRA)]

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

Robert Munteanu resolved SLING-5109.

Resolution: Fixed

> Release commons.json 2.0.12
> ---
>
> Key: SLING-5109
> URL: https://issues.apache.org/jira/browse/SLING-5109
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Launchpad Builder 8
>
>
> org.apache.sling.launchpad.webapp.integrationtest.servlets.post.SlingDateValuesTest.testDateTimezones
>  fails since we reverted to the released version in the launchpad.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SLING-5113) Release commons.logservice 1.0.6

[Robert Munteanu (JIRA)]

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

Robert Munteanu resolved SLING-5113.

Resolution: Fixed

> Release commons.logservice 1.0.6
> 
>
> Key: SLING-5113
> URL: https://issues.apache.org/jira/browse/SLING-5113
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>
> IMO SLING-4563 is nice enough to warrant a release for Sling 8.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SLING-5110) Release adapter 2.1.6

[Robert Munteanu (JIRA)]

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

Robert Munteanu resolved SLING-5110.

Resolution: Fixed

> Release adapter 2.1.6
> -
>
> Key: SLING-5110
> URL: https://issues.apache.org/jira/browse/SLING-5110
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Launchpad Builder 8
>
>
> org.apache.sling.launchpad.webapp.integrationtest.issues.SLING2522Test.testThatServicesWhichLikeAdapterFactoriesArentShowInTheW
>  has started failing since we reverted to the released version in the 
> launchpad.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SLING-5112) Release jcr.webdav 2.3.2

[Robert Munteanu (JIRA)]

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

Robert Munteanu resolved SLING-5112.

Resolution: Fixed

> Release jcr.webdav 2.3.2
> 
>
> Key: SLING-5112
> URL: https://issues.apache.org/jira/browse/SLING-5112
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>
> Due to an IT added for SLING-4825 will release this module for Launchpad 8.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SLING-5100) Include latest release of Oak 1.3.x in the launchpad

[Robert Munteanu (JIRA)]

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

Robert Munteanu resolved SLING-5100.

Resolution: Fixed

> Include latest release of Oak 1.3.x in the launchpad
> 
>
> Key: SLING-5100
> URL: https://issues.apache.org/jira/browse/SLING-5100
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SLING-5111) Release jcr.jackrabbit.usermanager 2.2.4

[Robert Munteanu (JIRA)]

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

Robert Munteanu resolved SLING-5111.

Resolution: Fixed

> Release jcr.jackrabbit.usermanager 2.2.4
> 
>
> Key: SLING-5111
> URL: https://issues.apache.org/jira/browse/SLING-5111
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Launchpad Builder 8
>
>
> This contains required fixes for the Oak integration in the Launchpad -> 
> must-have for Sling 8 release.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[RESULT][VOTE] Release Apache Sling Simple WebDAV Access to repositories 2.3.2

[Robert Munteanu]

Hi,

The vote has passed with the following result :

+1 (binding): Robert Munteanu, Carsten Ziegeler, Stefan Egli, Oliver
Lietz.

I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.

Robert

[jira] [Closed] (SLING-5093) Remove UserAdmin and GroupAdmin settings from AuthorizablePrivilegesInfo

[Robert Munteanu (JIRA)]

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

Robert Munteanu closed SLING-5093.
--

> Remove UserAdmin and GroupAdmin settings from AuthorizablePrivilegesInfo
> 
>
> Key: SLING-5093
> URL: https://issues.apache.org/jira/browse/SLING-5093
> Project: Sling
>  Issue Type: Improvement
>Affects Versions: JCR Jackrabbit User Manager 2.2.2
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: JCR Jackrabbit User Manager 2.2.4
>
>
> As discussed on [dev@sling:Oak, Launchpad 8, Docker 
> |http://sling.markmail.org/thread/qijycb34kzyvmshw#query:+page:1+mid:za6zeobcai4vxuud+state:results]
> the GroupAdmin and UserAdmin configuration is no longer available on Oak and 
> should be retired, with the following 'implementation guidelines':
> - remove the metatype from the service exposing these parameters (
>  AuthorizablePrivilegesInfoImpl )
> - warn if a non-default value is found set for these properties
> - no longer take the properties into account
> - delete the ITs which exercise this functionality



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4976) Clarify handling of empty JCR workspace name in WebDAV URLs

[Robert Munteanu (JIRA)]

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

Robert Munteanu closed SLING-4976.
--

> Clarify handling of empty JCR workspace name in WebDAV URLs
> ---
>
> Key: SLING-4976
> URL: https://issues.apache.org/jira/browse/SLING-4976
> Project: Sling
>  Issue Type: Task
>  Components: Servlets
>Affects Versions: JCR Webdav 2.3.0
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: JCR Webdav 2.3.2
>
>
> The handling of an empty JCR workspace name in WebDAV URLs has changed 
> recently, I'll create an integration test that demonstrates the changes.
> _Update: the change in behavior is apparently caused by upgrading to 
> org.apache.felix.http.jetty/3.1.0, see SLING-4978_



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5136) [HApi] Add java HApi microdata client

[Andrei Dulvac (JIRA)]

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

Andrei Dulvac updated SLING-5136:
-
Attachment: SLING-5136.git.diff

Attached patch

> [HApi] Add java HApi microdata client
> -
>
> Key: SLING-5136
> URL: https://issues.apache.org/jira/browse/SLING-5136
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Andrei Dulvac
>Priority: Minor
>  Labels: PatchAvailable
> Attachments: SLING-5136.git.diff
>
>
> The hapi tools extension could make use of a java HTML and microdata client 
> to consume html markup annotated using HApi.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-5136) [HApi] Add java HApi microdata client

[Andrei Dulvac (JIRA)]

Andrei Dulvac created SLING-5136:


 Summary: [HApi] Add java HApi microdata client
 Key: SLING-5136
 URL: https://issues.apache.org/jira/browse/SLING-5136
 Project: Sling
  Issue Type: Improvement
  Components: Extensions
Reporter: Andrei Dulvac
Priority: Minor


The hapi tools extension could make use of a java HTML and microdata client to 
consume html markup annotated using HApi.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (SLING-5136) [HApi] Add java HApi microdata client

[Andrei Dulvac (JIRA)]

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

Andrei Dulvac edited comment on SLING-5136 at 10/12/15 4:44 PM:


Attached patch. Can be applied with: patch -p0 -i SLING-5136.git.diff


was (Author: andrei.dulvac):
Attached patch

> [HApi] Add java HApi microdata client
> -
>
> Key: SLING-5136
> URL: https://issues.apache.org/jira/browse/SLING-5136
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Andrei Dulvac
>Priority: Minor
>  Labels: PatchAvailable
> Attachments: SLING-5136.git.diff
>
>
> The hapi tools extension could make use of a java HTML and microdata client 
> to consume html markup annotated using HApi.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Handling credentials for non-apache services

[Bertrand Delacretaz]

On Mon, Oct 12, 2015 at 5:05 PM, Robert Munteanu  wrote:
> ...The login says 'ASF members' and after adding my credentials I get a
> 403 status, so this won't work for everyone

I've created https://issues.apache.org/jira/browse/INFRA-10578 to
request Sling PMC-only read/write access on
https://svn.apache.org/repos/private/pmc/sling/

-Bertrand

Re: [RESULT][VOTE] Release Apache Sling Scripting Sightly Engine 1.0.6, Apache Sling Scripting Sightly Models Use Provider 1.0.0, Apache Sling Scripting Sightly REPL 1.0.2, Apache Sling Scripting Sigh

[Robert Munteanu]

On Mon, 2015-10-12 at 13:01 +, Radu Cotescu wrote:
> @PMC, please move the artifacts to dist.

r10785, r10786, r10787, r10788.

Robert

Re: [RESULT] [VOTE] Release Apache Sling Testing OSGi Mock 1.6.0, Sling Mock 1.6.0, Sling Mock Jackrabbit 1.0.0, Sling Mock Oak 1.0.0

[Robert Munteanu]

On Fri, 2015-10-09 at 16:01 +0200, Stefan Seifert wrote:
> @any PMC member: please copy this release to the Sling dist
> directory.

r10792, r10793, r10794, r10795 .

Robert

[jira] [Closed] (SLING-4957) Sightly RenderContextImpl contains utility methods that don't belong there

[Radu Cotescu (JIRA)]

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

Radu Cotescu closed SLING-4957.
---

> Sightly RenderContextImpl contains utility methods that don't belong there
> --
>
> Key: SLING-4957
> URL: https://issues.apache.org/jira/browse/SLING-4957
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Affects Versions: Scripting Sightly Engine 1.0.2
>Reporter: Vlad Bailescu
>Assignee: Radu Cotescu
>Priority: Minor
> Fix For: Scripting Sightly Engine 1.0.6
>
> Attachments: sling-4957.patch
>
>
> The current implementation of Sightly's {{RenderContext}} contains a lot of 
> of utility methods 
> ([example|https://github.com/apache/sling/blob/90d2ed9e42deb144a7f6e1610871e72726cd810a/bundles/scripting/sightly/engine/src/main/java/org/apache/sling/scripting/sightly/impl/engine/runtime/RenderContextImpl.java#L142]).
> These are not related to the actual context and belong to an utility class. 
> They are also unrelated to a specific instance/state and should be made 
> static.
> Refactoring these out of {{RenderContextImpl}} will allow us to avoid 
> unnecessarily passing an object of this class to other parts of the code just 
> to use these utility methods 
> ([example|https://github.com/apache/sling/blob/90d2ed9e42deb144a7f6e1610871e72726cd810a/bundles/scripting/sightly/engine/src/main/java/org/apache/sling/scripting/sightly/impl/compiler/expression/node/BinaryOperator.java#L31]).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-5124) Optimise RenderUtils to avoid throwing exceptions when looking for object methods

[Radu Cotescu (JIRA)]

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

Radu Cotescu closed SLING-5124.
---

> Optimise RenderUtils to avoid throwing exceptions when looking for object 
> methods
> -
>
> Key: SLING-5124
> URL: https://issues.apache.org/jira/browse/SLING-5124
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Affects Versions: Scripting Sightly Engine 1.0.4
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Minor
> Fix For: Scripting Sightly Engine 1.0.6
>
>
> {{RenderUtils}} should be optimised to avoid throwing exceptions when looking 
> for object properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4671) Sightly does not render correctly when non-HTML resource cannot be found

[Radu Cotescu (JIRA)]

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

Radu Cotescu closed SLING-4671.
---

> Sightly does not render correctly when non-HTML resource cannot be found
> 
>
> Key: SLING-4671
> URL: https://issues.apache.org/jira/browse/SLING-4671
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting Sightly Engine 1.0.2
> Environment: Linux / OS X, Sling & Sightly Snapshot.
>Reporter: Chris Millar
>Assignee: Radu Cotescu
>Priority: Minor
> Fix For: Scripting Sightly Engine 1.0.6
>
>
> When creating /apps/sling/servlet/errorhander/404.html
> Sightly template is not rendered correctly for all 404s that are of a 
> different resource type.
> The following will result in the sightly template being dumped as plain text: 
> http://slick.millr.org/test
> If you browse to a page of the same resource type (html), Sightly renders 
> correctly:
> http://slick.millr.org/test.html
> Additionally, images attempt to render, even if they do not exist.
> http://slick.millr.org/test.jpg
> Using JSP, all URLs work as expected.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-5053) Add support for Enum comparison in Sightly scripts

[Radu Cotescu (JIRA)]

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

Radu Cotescu closed SLING-5053.
---

> Add support for Enum comparison in Sightly scripts
> --
>
> Key: SLING-5053
> URL: https://issues.apache.org/jira/browse/SLING-5053
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Affects Versions: Scripting Sightly Engine 1.0.4
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Minor
> Fix For: Scripting Sightly Engine 1.0.6
>
>
> Currently, in order to perform comparisons with enum values one needs to 
> write code similar to:
> {code:html}
>  data-sly-unwrap>${'Pending' @ i18n, locale=request.locale}   
> {code}
> This could be further simplified to:
> {code:html}
>  data-sly-unwrap>${'Pending' @ i18n, locale=request.locale}
> {code}
> for the cases when {{member.inviteStatus}} evaluates to an Enum constant.
> Enum comparison support has also been added to version 1.2 draft of the 
> Sightly Specification: 
> https://github.com/Adobe-Marketing-Cloud/sightly-spec/blob/1.2/SPECIFICATION.md#1142-comparison-operators



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4260) Sightly support for encoding for xml

[Radu Cotescu (JIRA)]

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

Radu Cotescu closed SLING-4260.
---

> Sightly support for encoding for xml
> 
>
> Key: SLING-4260
> URL: https://issues.apache.org/jira/browse/SLING-4260
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Affects Versions: Scripting Sightly Engine 1.0.2
>Reporter: Feike Visser
>Assignee: Radu Cotescu
> Fix For: Scripting Sightly Engine 1.0.6
>
>
> Currently this is not supported in Sightly:
> {noformat}
> ${ property @ context = 'xml' }
> {noformat}
> This should call the xssApi encode for XML.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5096) Deploy API documentation for Sling 8

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-5096:


Updated tooling/release/generate_javadoc_for_release.sh in 
https://svn.apache.org/r1708104

> Deploy API documentation for Sling 8
> 
>
> Key: SLING-5096
> URL: https://issues.apache.org/jira/browse/SLING-5096
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4713) Update Sightly REPL to display generated Java source code

[Radu Cotescu (JIRA)]

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

Radu Cotescu closed SLING-4713.
---

> Update Sightly REPL to display generated Java source code
> -
>
> Key: SLING-4713
> URL: https://issues.apache.org/jira/browse/SLING-4713
> Project: Sling
>  Issue Type: Bug
>Affects Versions: Scripting Sightly REPL 1.0.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Minor
> Fix For: Scripting Sightly REPL 1.0.2
>
>
> With the improvements provided by SLING-4692 and SLING-4693 generated Sightly 
> classes are generated to disk using the 
> {{org.apache.sling.commons.fsclassloader}} {{ClassLoaderWriter}} 
> implementation. Therefore, if the sources were generated, they should be 
> displayed by the Sightly REPL using the new disk location.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4734) Sightly should try to instantiate Sling Models first via SlingHttpServletRequest then via Resource and not the other way around

[Radu Cotescu (JIRA)]

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

Radu Cotescu closed SLING-4734.
---

> Sightly should try to instantiate Sling Models first via 
> SlingHttpServletRequest then via Resource and not the other way around
> ---
>
> Key: SLING-4734
> URL: https://issues.apache.org/jira/browse/SLING-4734
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Affects Versions: Scripting Sightly Models Use Provider 1.0.0
>Reporter: Konrad Windszus
> Fix For: Scripting Sightly Models Use Provider 1.0.0
>
>
> Currently the {{JavaUseProvider}} first tries to instantiate Sling Models via 
> the {{Resource}} then via the {{SlingHttpServletRequest}}. I would argue that 
> the inverse order makes more sense, because more injections are supported via 
> the {{SlingHttpServletRequest}} for Sling Models.
> This would only matter though, where the same class would be adaptable from 
> both {{Resource}} and {{SlingHttpServletRequest}}. In that case though the 
> instantiation via the {{SlingHttpServletRequest}} would support more 
> injections (e.g. the SlingObjectInjector supports much more with the 
> {{SlingHttpServletRequest}}, compare with SLING-4083)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-5125) Make Sightly REPL JavaScript and CSS dependencies local to allow offline use

[Radu Cotescu (JIRA)]

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

Radu Cotescu closed SLING-5125.
---

> Make Sightly REPL JavaScript and CSS dependencies local to allow offline use
> 
>
> Key: SLING-5125
> URL: https://issues.apache.org/jira/browse/SLING-5125
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Affects Versions: Scripting Sightly REPL 1.0.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
> Fix For: Scripting Sightly REPL 1.0.2
>
>
> The Sightly REPL third-party resources should be local in order to allow the 
> REPL tool to be used offline.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-5126) Provide information on the Sightly REPL Java tab on how to enable source code generation

[Radu Cotescu (JIRA)]

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

Radu Cotescu closed SLING-5126.
---

> Provide information on the Sightly REPL Java tab on how to enable source code 
> generation
> 
>
> Key: SLING-5126
> URL: https://issues.apache.org/jira/browse/SLING-5126
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Affects Versions: Scripting Sightly REPL 1.0.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Minor
> Fix For: Scripting Sightly REPL 1.0.2
>
>
> The Sightly REPL tool should provide information on how to generate Java 
> source code in its Java tab.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-5127) Implement browser history support for the Sightly REPL tabs

[Radu Cotescu (JIRA)]

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

Radu Cotescu closed SLING-5127.
---

> Implement browser history support for the Sightly REPL tabs
> ---
>
> Key: SLING-5127
> URL: https://issues.apache.org/jira/browse/SLING-5127
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Affects Versions: Scripting Sightly REPL 1.0.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Minor
> Fix For: Scripting Sightly REPL 1.0.2
>
>
> The Sightly REPL tabs should provide support for browser history.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-5050) Disable AntiSamy's default formatOutput policy directive

[Radu Cotescu (JIRA)]

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

Radu Cotescu closed SLING-5050.
---

> Disable AntiSamy's default formatOutput policy directive
> 
>
> Key: SLING-5050
> URL: https://issues.apache.org/jira/browse/SLING-5050
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: XSS Protection API 1.0.4
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
> Fix For: XSS Protection API 1.0.6
>
>
> By default AntiSamy enables the {{formatOutput}} policy directive \[0\], 
> formatting markup sent to it. However this sometimes works against a 
> developer's intention of outputting markup with Sightly.
> \[0\] - https://owaspantisamy.googlecode.com/files/Developer%20Guide.pdf



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-5080) org.apache.sling.scripting.javascript fails baseline check with maven-bundle-plugin 3.0.0

[Radu Cotescu (JIRA)]

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

Radu Cotescu closed SLING-5080.
---

> org.apache.sling.scripting.javascript fails baseline check with 
> maven-bundle-plugin 3.0.0
> -
>
> Key: SLING-5080
> URL: https://issues.apache.org/jira/browse/SLING-5080
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting JavaScript 2.0.24
>Reporter: Robert Munteanu
>Assignee: Radu Cotescu
> Fix For: Scripting JavaScript 2.0.26
>
>
> After updating the maven-bundle-plugin to 3.0.0 the mentioned module fails to 
> build due to a baseline check. When compared to the 2.5.3 build output, I can 
> see that 
> 1. it complains about multiple {{org.mozilla.javascript}} split packages, 
> e..g.
> {noformat}[WARNING] Bundle 
> org.apache.sling:org.apache.sling.scripting.javascript:bundle:2.0.25-SNAPSHOT 
> : Split package, multiple jars provide the same 
> package:org/mozilla/javascript/serialize
> Use Import/Export Package directive 
> -split-package:=(merge-first|merge-last|error|first) to get rid of this 
> warning
> Package found in   [Jar:rhino, Jar:js]{noformat}
> 2. It thinks that org.mozilla.javascript should be exported with the 1.1.0 
> version instead of 1.0.0, due to multiple classes being added: 
> ScriptOrFnNode, PropertyException, NotAFunctionException, Node$Jump, 
> FunctionNode, ClassDefinitionException .
> The first note might hold the key to understanding why the second one happens 
> ; bnd might have changed the way it embeds/reexports classes and therefore 
> triggers this problem



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-5022) ImporterTopLevel is not set up correctly for the RhinoJavaScriptEngine

[Radu Cotescu (JIRA)]

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

Radu Cotescu closed SLING-5022.
---

> ImporterTopLevel is not set up correctly for the RhinoJavaScriptEngine
> --
>
> Key: SLING-5022
> URL: https://issues.apache.org/jira/browse/SLING-5022
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting JavaScript 2.0.24
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
> Fix For: Scripting JavaScript 2.0.26
>
>
> The {{ImporterTopLevel}} utility Rhino class is not set up correctly for the 
> RhinoJavaScriptEngine. As a consequence none of the utility {{import*}} 
> functions the {{ImporterTopLevel}} provides are available in the global scope.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [RESULT][VOTE] Release Apache Sling Scripting JavaScript 2.0.26

[Robert Munteanu]

On Mon, 2015-10-12 at 13:02 +, Radu Cotescu wrote:
> @PMC, please move the artifacts to dist.


r10789.

Robert

[jira] [Updated] (SLING-5134) Donation of sling pipes

[Nicolas Peltier (JIRA)]

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

Nicolas Peltier updated SLING-5134:
---
Attachment: sling-pipes.tar.gz

shasum gives {Code}7b199133ed12e915fd7c51410d8f15ae86e08da4{Code}

> Donation of sling pipes
> ---
>
> Key: SLING-5134
> URL: https://issues.apache.org/jira/browse/SLING-5134
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Nicolas Peltier
> Attachments: sling-pipes.tar.gz
>
>
> This issue tracks the donation of sling pipes as announced in [0]. Code & 
> documentation are there [1] https://github.com/npeltier/sling-pipes, two open 
> issues for now are tracked there a well [2]
> [0] http://sling.markmail.org/thread/n6yr6upogruem7qp
> [1] http://github.com/npeltier/sling-pipes
> [2] https://github.com/npeltier/sling-pipes/issues



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[RESULT][VOTE] Release Apache Sling Scripting Sightly Engine 1.0.6, Apache Sling Scripting Sightly Models Use Provider 1.0.0, Apache Sling Scripting Sightly REPL 1.0.2, Apache Sling Scripting Sightly

[Radu Cotescu]

Hi,

The vote passed with 3 +1 from Robert Munteanu, Carsten Ziegeler and Oliver
Lietz.

I'll start promoting the releases ASAP.

@PMC, please move the artifacts to dist.

Cheers,
Radu

[RESULT][VOTE] Release Apache Sling Scripting JavaScript 2.0.26

[Radu Cotescu]

Hi,

The vote passed with 3 +1 from Robert Munteanu, Carsten Ziegeler and Oliver
Lietz.

I'll start promoting the releases ASAP.

@PMC, please move the artifacts to dist.

Cheers,
Radu

[jira] [Assigned] (SLING-5096) Deploy API documentation for Sling 8

[Robert Munteanu (JIRA)]

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

Robert Munteanu reassigned SLING-5096:
--

Assignee: Robert Munteanu

> Deploy API documentation for Sling 8
> 
>
> Key: SLING-5096
> URL: https://issues.apache.org/jira/browse/SLING-5096
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4447) Improve JavaUseProvider to not fall back to a simple Pojo instantiation in case a Java class with @Model annotation cannot be instantiated

[Radu Cotescu (JIRA)]

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

Radu Cotescu closed SLING-4447.
---

> Improve JavaUseProvider to not fall back to a simple Pojo instantiation in 
> case a Java class with @Model annotation cannot be instantiated
> --
>
> Key: SLING-4447
> URL: https://issues.apache.org/jira/browse/SLING-4447
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Affects Versions: Scripting Sightly Engine 1.0.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Fix For: Scripting Sightly Models Use Provider 1.0.0
>
> Attachments: SLING-4447-v01.patch
>
>
> Currently in case a Java class is a Sling Model (i.e. has the Model 
> annotation) and cannot be instantiated (e.g. required injections not 
> possible) Sightly falls back to instantiate those as simple Pojos.
> This is never good, since a lot of NullPointerException might happen because 
> all injections have not been performed then.
> Therefore in the following code should be used instead 
> {code}
> if (modelFactory.isModelClass(resource, cls)) {
>   if (modelFactory.canCreateFromAdaptable(resource, cls)) {
> obj = modelFactory.createModel(resource, cls);
>   } else if (modelFactory.canCreateFromAdaptable(request, cls)) {
> obj = modelFactory.createModel(request, cls);
>   } else {
> throw new IllegalStateException("Could not adapt the given Sling Model 
> from neither resource nor request: " + cls);
>   }
> }
> {code}
> That way, exceptions would be propagated in case a Sling model cannot be 
> instantiated and developers more easily see why the Sling Model does not work 
> (instead of running into NullPointerExceptions in their model because it was 
> instantiated as simple Pojo)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-5036) Optimise the ModelsFactoryUseProvider to fail as early as possible if it cannot provide an object

[Radu Cotescu (JIRA)]

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

Radu Cotescu closed SLING-5036.
---

> Optimise the ModelsFactoryUseProvider to fail as early as possible if it 
> cannot provide an object
> -
>
> Key: SLING-5036
> URL: https://issues.apache.org/jira/browse/SLING-5036
> Project: Sling
>  Issue Type: Bug
>Affects Versions: Scripting Sightly Models Use Provider 1.0.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
> Fix For: Scripting Sightly Models Use Provider 1.0.0
>
>
> The 
> {{org.apache.sling.scripting.sightly.models.impl.ModelsFactoryUseProvider}} 
> should be further optimised to fail as early as possible if it cannot load a 
> Sling Model, which means that it should check if the provided identifier 
> pattern matches a Java class name pattern.
> Also some lazy bindings retrieval should be done in order to save time - the 
> {{Resource}} object should only be retrieved if the object is not adaptable 
> from {{SlingHttpServletRequest}}.
> At the same time a rename of the class should be done, to properly reflect 
> its purpose: {{ModelsFactoryUseProvider}} -> {{SlingModelsUseProvider}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4442) Invalid parametrisation of Sightly statements should lead to exceptions instead of errors

[Radu Cotescu (JIRA)]

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

Radu Cotescu closed SLING-4442.
---

> Invalid parametrisation of Sightly statements should lead to exceptions 
> instead of errors
> -
>
> Key: SLING-4442
> URL: https://issues.apache.org/jira/browse/SLING-4442
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Affects Versions: Scripting Sightly Engine 1.0.0
>Reporter: Konrad Windszus
>Assignee: Radu Cotescu
> Fix For: Scripting Sightly Engine 1.0.6
>
>
> Currently invalid parametrization of Sightly statements only leads to 
> errors/warnings in the log. Rather programmatic errors should lead to 
> exceptions so that errors are detected earlier during development and to 
> prevent invalid HTML output due to failures within a Sightly script (a HTML 
> page with a 500 status is the right thing to do IMHO).
> This affects:
> # data-sly-include with invalid/empty path
> # data-sly-call with invalid name (this does not even provide logging 
> currently)
> # data-sly-use when the identifier cannot be solved by any of the registered 
> {{UseProvider}} services



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4971) "static" node name not allowed as a script ancestor

[Radu Cotescu (JIRA)]

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

Radu Cotescu closed SLING-4971.
---

> "static" node name not allowed as a script ancestor
> ---
>
> Key: SLING-4971
> URL: https://issues.apache.org/jira/browse/SLING-4971
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting Sightly Engine 1.0.2
>Reporter: Nicolas Peltier
>Assignee: Radu Cotescu
>Priority: Minor
> Fix For: Scripting Sightly Engine 1.0.6
>
>
> Looks like having "static" as a script ancestor (e.g. 
> /apps/blah/static/foo/foo.html) will break badly the script rendering (and 
> all the rendering process), yelling:
> {noformat}
> Line 1, column 0 : The declared package "" does not match the expected 
> package "apps.blah.static.foo"
> Line 19, column 994 : Syntax error on token "static", Identifier expected
> at 
> org.apache.sling.scripting.sightly.impl.compiler.SightlyJavaCompilerService.compileSource(SightlyJavaCompilerService.java:143)
> at 
> org.apache.sling.scripting.sightly.impl.engine.UnitLoader.createUnit(UnitLoader.java:140)
> at 
> org.apache.sling.scripting.sightly.impl.engine.SightlyScriptEngine.evaluateScript(SightlyScriptEngine.java:94)
> at 
> org.apache.sling.scripting.sightly.impl.engine.SightlyScriptEngine.eval(SightlyScriptEngine.java:83)
> at 
> org.apache.sling.scripting.core.impl.DefaultSlingScript.call(DefaultSlingScript.java:361)
> at 
> org.apache.sling.scripting.core.impl.DefaultSlingScript.eval(DefaultSlingScript.java:171)
> at 
> org.apache.sling.scripting.core.impl.DefaultSlingScript.service(DefaultSlingScript.java:463)
> ... 258 common frames omitted
> Caused by: 
> org.apache.sling.scripting.sightly.impl.compiler.CompilerException: 
> org.apache.sling.scripting.sightly.impl.compiler.CompilerException: 
> Compilation errors in apps/blah/static/foo/SightlyJava_foo.java:
> Line 1, column 0 : The declared package "" does not match the expected 
> package "apps.blah.static.foo"
> Line 19, column 994 : Syntax error on token "static", Identifier expected
> at 
> org.apache.sling.scripting.sightly.impl.compiler.SightlyJavaCompilerService.compileJavaResource(SightlyJavaCompilerService.java:258)
> at 
> org.apache.sling.scripting.sightly.impl.compiler.SightlyJavaCompilerService.compileSource(SightlyJavaCompilerService.java:141)
> ... 264 common frames omitted
> Caused by: 
> org.apache.sling.scripting.sightly.impl.compiler.CompilerException: 
> Compilation errors in apps/blah/static/foo/SightlyJava_foo.java:
> Line 1, column 0 : The declared package "" does not match the expected 
> package "apps.blah.static.foo"
> Line 19, column 994 : Syntax error on token "static", Identifier expected
> at 
> org.apache.sling.scripting.sightly.impl.compiler.SightlyJavaCompilerService.compileJavaResource(SightlyJavaCompilerService.java:250)
> ... 265 common frames omitted
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: contribution proposal: sling pipes

[Robert Munteanu]

Hi,

On Sun, 2015-10-11 at 17:40 +, Nicolas Peltier wrote:
> Hi,
> 
> issue is finally here [0], tell me it needs more stuff, or is i
> should directly cast  a vote, thanks
> 
> Nicolas

Please attach an archive of the code that you wish to donate on the
Jira issue and add a comment with the checksums. Then we can start a
vote (IIRC).

Robert

> 
> [0] https://issues.apache.org/jira/browse/SLING-5134
> > On 13 Jul 2015, at 18:33, Nicolas Peltier 
> > wrote:
> > 
> > thanks !
> > 
> > will still need to add and fix things for the next couple of days,
> > will submit the contribution afterward
> > 
> > Nicolas
> > > On 11 Jul 2015, at 00:05, Oliver Lietz 
> > > wrote:
> > > 
> > > On Friday 10 July 2015 11:59:55 Nicolas Peltier wrote:
> > > > Hi,
> > > 
> > > hi Nicolas,
> > > 
> > > > what should be the next step?
> > > 
> > > open an issue and attach an archive with the code as Robert
> > > wrote.
> > > See https://issues.apache.org/jira/browse/SLING-4842 for example 
> > > - issue 
> > > should be New Feature instead of Bug though. Then cast a vote.
> > > 
> > > Regards,
> > > O.
> > > 
> > > > Nicolas
> > > > 
> > > > > On 06 Jul 2015, at 15:05, Nicolas Peltier  > > > > > wrote:
> > > > > 
> > > > > 
> > > > > 
> > > > > > 
> > > > > > Which version? 6.0 and 6.1 come with 3.x and a wrapped 2.5.
> > > > > 
> > > > > ha right, i tried 2.6, that’s why. I’ve just downgraded it to
> > > > > 2.5
> > > > > 
> > > > > Nicolas
> > > > 
> > > > 
> > > 
> > 
> 

[jira] [Closed] (SLING-5031) Switch the order in which a Use object is adapted in the JavaUseProvider

[Radu Cotescu (JIRA)]

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

Radu Cotescu closed SLING-5031.
---

> Switch the order in which a Use object is adapted in the JavaUseProvider
> 
>
> Key: SLING-5031
> URL: https://issues.apache.org/jira/browse/SLING-5031
> Project: Sling
>  Issue Type: Bug
>Affects Versions: Scripting Sightly Engine 1.0.4
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
> Fix For: Scripting Sightly Engine 1.0.6
>
>
> The 
> {{org.apache.sling.scripting.sightly.impl.engine.extension.use.JavaUseProvider}}
>  should first try to adapt the Use object to a request and then to a 
> resource, in order to provide consistency with the 
> {{org.apache.sling.scripting.sightly.models.impl.ModelFactoryUseProvider}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-5074) Provide a way to configure the priority of the Sling Models Use Provider

[Radu Cotescu (JIRA)]

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

Radu Cotescu closed SLING-5074.
---

> Provide a way to configure the priority of the Sling Models Use Provider
> 
>
> Key: SLING-5074
> URL: https://issues.apache.org/jira/browse/SLING-5074
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting Sightly Models Use Provider 1.0.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
> Fix For: Scripting Sightly Models Use Provider 1.0.0
>
>
> The {{SlingModelsUseProvider}} doesn't provide a way to configure its 
> priority ({{service.ranking}} value) like the other Use providers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[RESULT][VOTE] Release Apache Sling XSS Protection API 1.0.6

[Radu Cotescu]

Hi,

The vote passed with 3 +1 from Robert Munteanu, Carsten Ziegeler and Oliver
Lietz.

I'll start promoting the releases ASAP.

@PMC, please move the artifacts to dist.

Cheers,
Radu

Re: [RESULT][VOTE] Release Apache Sling XSS Protection API 1.0.6

[Robert Munteanu]

On Mon, 2015-10-12 at 13:02 +, Radu Cotescu wrote:
> @PMC, please move the artifacts to dist.

r10790

Robert

Re: [RESULT][VOTE] Release Apache Sling Scripting JavaScript 2.0.26

[Robert Munteanu]

On Mon, 2015-10-12 at 13:02 +, Radu Cotescu wrote:
> @PMC, please move the artifacts to dist.

r10789

Robert

[jira] [Commented] (SLING-5094) refactor discovery.impl to use discovery.commons (esp ViewStateManager)

[Stefan Egli (JIRA)]

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

Stefan Egli commented on SLING-5094:


Done in rev 1708119 - keeping open as we now have a SNAPSHOT dependency to 
discovery.commons (once that's released this one can also be closed)

> refactor discovery.impl to use discovery.commons (esp ViewStateManager)
> ---
>
> Key: SLING-5094
> URL: https://issues.apache.org/jira/browse/SLING-5094
> Project: Sling
>  Issue Type: Task
>  Components: Extensions
>Affects Versions: Discovery Impl 1.1.8
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Discovery Impl 1.1.10
>
>
> discovery.commons is introduced in an effort to bundle common code that will 
> be used by all three discovery.impl, discovery.oak and discovery.3rdparty 
> (zk/etcd). also see SLING-4685. discovery.impl's DiscoveryServiceImpl should 
> be refactored to use the ViewStateManager.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[VOTE] accept the donation of sling pipes tracked in SLING-5134

[Nicolas Peltier]

Hi,

this thread is about voting for the acceptation of sling pipes donation, 
tracked in SLING-5134.

An archive containing the contribution is attached to SLING-5134, shasum 
7b199133ed12e915fd7c51410d8f15ae86e08da4. HEAD is viewable on github at [0]

Please cast your votes.

Cheers,
Nicolas

[0] https://github.com/npeltier/sling-pipes

[jira] [Assigned] (SLING-5099) Create 'New and Noteworthy' page for Sling 8

[Robert Munteanu (JIRA)]

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

Robert Munteanu reassigned SLING-5099:
--

Assignee: Robert Munteanu

> Create 'New and Noteworthy' page for Sling 8
> 
>
> Key: SLING-5099
> URL: https://issues.apache.org/jira/browse/SLING-5099
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Handling credentials for non-apache services

[Radu Cotescu]

Hi Robert,

You could try to email the credentials to the PMC members encrypted with
their PGP public keys, since you already have access to them. This way the
information is passed securely to them.

Depending how many members of the PMC use keybase.io [0], that would also
be an option.

Cheers,
Radu

[0] - https://keybase.io

On Mon, 12 Oct 2015 at 16:20 Robert Munteanu  wrote:

> Hi,
>
> With Sling Launchpad 8 I intend to provide an 'official' Sling docker
> image, uploaded on https://hub.docker.com/ . I think this will make
> Sling much easier to try out and consume.
>
> However, this means creating an account on a non-ASF system which will
> be used to manage these contributions. I can obviously create this
> account on my own, but I'm not sure how to handle the credentials - I'd
> like them to be accessible to others so that I'm not the single point
> of access for that account.
>
> Thoughts?
>
> Robert
>

[jira] [Resolved] (SLING-4411) provide Oak features

[Oliver Lietz (JIRA)]

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

Oliver Lietz resolved SLING-4411.
-
Resolution: Done

r1708122 Sling JCR Oak Server 1.0.0

> provide Oak features
> 
>
> Key: SLING-4411
> URL: https://issues.apache.org/jira/browse/SLING-4411
> Project: Sling
>  Issue Type: New Feature
>  Components: Launchpad
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Launchpad Karaf Features 0.2.0
>
>
> provide features for Oak as we have now for Jackrabbit:
> * {{oak-sling}}
> * {{sling-jcr-oak}}
> * {{sling-launchpad-oak}}
> * {{sling-launchpad-oak-tar}}
> * {{sling-launchpad-oak-mongo}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SLING-5129) Update org.apache.sling.scripting.javascript to 2.0.26

[Radu Cotescu (JIRA)]

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

Radu Cotescu resolved SLING-5129.
-
Resolution: Fixed

Fixed in 
[r1708132|https://svn.apache.org/viewvc?view=revision=r1708132].

> Update org.apache.sling.scripting.javascript to 2.0.26
> --
>
> Key: SLING-5129
> URL: https://issues.apache.org/jira/browse/SLING-5129
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

New and noteworthy items for Sling 8

[Robert Munteanu]

Hi,

It would be nice to get a new and noteworthy page for the Sling 8
release. This would bring more attention to the release and the project
in general.

I have drafted a wiki page at [1] with a few items that I'm aware of.
Please add anything that you think is significant and I'll take care of
of transferring it on sling.apache.org once the release is out (
probably end of this week or start of next week ).

Robert

[1]: 
https://cwiki.apache.org/confluence/display/SLING/Sling+8+release+notes

[VOTE] Release Apache Sling Maven Plugin for Supporting Bundle Development 2.1.2

[Robert Munteanu]

Hi,

We solved 5 issues in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12319468

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1352

You can use this UNIX script to download the release and verify the
signatures:
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1352 /tmp/sling-staging

Please vote to approve this release:

  [ ] +1 Approve the release
  [ ]  0 Don't care
  [ ] -1 Don't release, because ...

This majority vote is open for at least 72 hours.

Thanks,

Robert

Handling credentials for non-apache services

[Robert Munteanu]

Hi,

With Sling Launchpad 8 I intend to provide an 'official' Sling docker
image, uploaded on https://hub.docker.com/ . I think this will make
Sling much easier to try out and consume.

However, this means creating an account on a non-ASF system which will
be used to manage these contributions. I can obviously create this
account on my own, but I'm not sure how to handle the credentials - I'd
like them to be accessible to others so that I'm not the single point
of access for that account.

Thoughts?

Robert

Re: Handling credentials for non-apache services

[Bertrand Delacretaz]

Hi Robert,

On Mon, Oct 12, 2015 at 4:20 PM, Robert Munteanu  wrote:
> ...I'm not sure how to handle the credentials - I'd
> like them to be accessible to others so that I'm not the single point
> of access for that account

We can create a PMC private svn folder under
https://svn.apache.org/repos/private/pmc/ - but IIRC all PMC members
have access to all content there.

You could also encrypt the info with the PGP keys of a few Sling PMC
members, so that all of them can read it but no one else.

-Bertrand

Re: [VOTE] Release Apache Sling Maven Plugin for Supporting Bundle Development 2.1.2

[Robert Munteanu]

On Mon, Oct 12, 2015 at 5:59 PM, Robert Munteanu  wrote:
> Please vote to approve this release:


+1

Robert

[jira] [Commented] (SLING-4603) discovery.oak: oak-based discovery implementation

[Stefan Egli (JIRA)]

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

Stefan Egli commented on SLING-4603:


As part of this I'm going to factor the topology-connector part of 
{{discovery.impl}} into its own bundle {{discovery.connectors}} - that one will 
then be used by both {{discovery.impl}} and {{discovery.oak}}.

> discovery.oak: oak-based discovery implementation
> -
>
> Key: SLING-4603
> URL: https://issues.apache.org/jira/browse/SLING-4603
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Stefan Egli
>Assignee: Stefan Egli
>
> When discovery is used in a stack based on jackrabbit oak as the repository, 
> the current way of discoving instances somewhat sounds like duplicating work: 
> oak, or more precisely documentnodestore, itself has a low-level [lease 
> mechanism|http://jackrabbit.apache.org/oak/docs/nodestore/documentmk.html] 
> where it stores information about the cluster nodes including a {{leaseEnd}} 
> indicating at what time others can consider a particular node as 
> dead/crashed. This corresponds pretty much to the discovery.impl heartbeat 
> mechanism. And in a stack which is built ontop of oak-documentMk, we could be 
> making use of this fact and delegate the decision about whether a node in a 
> cluster is alive or not to the oak layer. Also, with OAK-2597 the relevant 
> information: {{ActiveClusterNodes}} is nicely exposed via JMX - so that can 
> become the new source of truth defining the cluster view.
> When replacing discovery-owned heartbeats with oak-owned ones, there is one 
> important detail to be watched out for: it can no longer easily be determined 
> from another instance in the cluster, whether it has this new discovery 
> bundle activated or not. Hence it is not given that when a voting happens, 
> that all {{active}} nodes (as reported by oak-documentMk) are actually going 
> to respond. So the 'silent instance due to deactivated discovery bundle' case 
> needs special attention/handling.
> Other than that, given the normal case of all {{active}} nodes having the 
> bundle activated, the voting mechanism can stay the same as in 
> discovery.impl. The topology connectors can be treated the same too (by 
> storing announcements to their respective 
> {{/var/discovery/clusterInstances//announcements/}}
>  node. The properties can be handled the same too (by storing to 
> {{/properties}} node. Only thing that gets replaced is the {{heartbeats}}.
> Note that in order for such an oak-based discovery.impl this oak-lease 
> mechanism must be very robust (it should be so by its own interest already). 
> However, there are currently a few issues that should probably first be 
> resolved until discovery can be based on this: OAK-2739, OAK-2682 and 
> OAK-2681 are currently known in this area.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (SLING-5097) Deploy docker image to Docker Hub

[Robert Munteanu (JIRA)]

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

Robert Munteanu reassigned SLING-5097:
--

Assignee: Robert Munteanu

> Deploy docker image to Docker Hub
> -
>
> Key: SLING-5097
> URL: https://issues.apache.org/jira/browse/SLING-5097
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-5099) Create 'New and Noteworthy' page for Sling 8

[Robert Munteanu (JIRA)]

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

Robert Munteanu updated SLING-5099:
---
Description: WIP at 
https://cwiki.apache.org/confluence/display/SLING/Sling+8+release+notes

> Create 'New and Noteworthy' page for Sling 8
> 
>
> Key: SLING-5099
> URL: https://issues.apache.org/jira/browse/SLING-5099
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>
> WIP at https://cwiki.apache.org/confluence/display/SLING/Sling+8+release+notes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SLING-5130) Update org.apache.sling.xss to 1.0.6

[Radu Cotescu (JIRA)]

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

Radu Cotescu resolved SLING-5130.
-
Resolution: Fixed

Fixed in 
[r1708131|https://svn.apache.org/viewvc?view=revision=r1708131].

> Update org.apache.sling.xss to 1.0.6
> 
>
> Key: SLING-5130
> URL: https://issues.apache.org/jira/browse/SLING-5130
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SLING-5128) Update Sightly bundles

[Radu Cotescu (JIRA)]

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

Radu Cotescu resolved SLING-5128.
-
Resolution: Fixed

Fixed in 
[r1708133|https://svn.apache.org/viewvc?view=revision=r1708133].

> Update Sightly bundles
> --
>
> Key: SLING-5128
> URL: https://issues.apache.org/jira/browse/SLING-5128
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Minor
>
> The following Sightly bundles have to be included in Sling 8:
> # {{org.apache.sling.scripting.sightly}} - 1.0.6
> # {{org.apache.sling.scripting.sightly.js.provider}} - 1.0.10
> # {{org.apache.sling.scripting.sightly.models.provider}} - 1.0.0
> # {{org.apache.sling.scripting.sightly.repl}} - 1.0.2



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Handling credentials for non-apache services

[Robert Munteanu]

On Mon, Oct 12, 2015 at 6:03 PM, Bertrand Delacretaz
 wrote:
> Hi Robert,
>
> On Mon, Oct 12, 2015 at 4:20 PM, Robert Munteanu  wrote:
>> ...I'm not sure how to handle the credentials - I'd
>> like them to be accessible to others so that I'm not the single point
>> of access for that account
>
> We can create a PMC private svn folder under
> https://svn.apache.org/repos/private/pmc/ - but IIRC all PMC members
> have access to all content there.

The login says 'ASF members' and after adding my credentials I get a
403 status, so this won't work for everyone.

> You could also encrypt the info with the PGP keys of a few Sling PMC
> members, so that all of them can read it but no one else.

I like that idea, maybe there's another place where we can safely
store a gpg-signed credentials file.

Thanks,

Robert

-- 
Sent from my (old) computer

[jira] [Reopened] (SLING-4411) provide Oak features

[Oliver Lietz (JIRA)]

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

Oliver Lietz reopened SLING-4411:
-

remove {{editConfigurationFilePut("etc/org.apache.karaf.features.cfg", 
"serviceRequirements", "disable"), // TODO OAK-3083}} from 
{{KarafTestSupport}}, OAK-3503

> provide Oak features
> 
>
> Key: SLING-4411
> URL: https://issues.apache.org/jira/browse/SLING-4411
> Project: Sling
>  Issue Type: New Feature
>  Components: Launchpad
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Launchpad Karaf Features 0.2.0
>
>
> provide features for Oak as we have now for Jackrabbit:
> * {{oak-sling}}
> * {{sling-jcr-oak}}
> * {{sling-launchpad-oak}}
> * {{sling-launchpad-oak-tar}}
> * {{sling-launchpad-oak-mongo}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3227) FormLoginModulePlugin does not work with Oak

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler closed SLING-3227.
---

> FormLoginModulePlugin does not work with Oak
> 
>
> Key: SLING-3227
> URL: https://issues.apache.org/jira/browse/SLING-3227
> Project: Sling
>  Issue Type: Bug
>  Components: Authentication
>Reporter: Bertrand Delacretaz
>Assignee: Chetan Mehrotra
>  Labels: oak
> Fix For: Form Based Authentication 1.0.8
>
>
> Some integration tests (SLING-3221, SLING-3226) fail on Oak as our form 
> authentication handler doesn't work with Oak.
> We'll need to either deprecate this functionality on Oak, or supply an 
> alternative. Based on the oak dev list discussion [1], an OSGi-based JAAS 
> login module [2] should work.
> [1] http://oak.markmail.org/thread/bsmmpfx6igtcqb5u
> [2] http://felix.apache.org/documentation/subprojects/apache-felix-jaas.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache Sling Auth Forms 1.0.8

[Carsten Ziegeler]

Vote passes with four binding +1 votes

Carsten
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org