[jira] [Closed] (SLING-8646) Remove LogService implementation

2019-08-29 Thread Carsten Ziegeler (Jira)


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

Carsten Ziegeler closed SLING-8646.
---

> Remove LogService implementation
> 
>
> Key: SLING-8646
> URL: https://issues.apache.org/jira/browse/SLING-8646
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
>Priority: Major
> Fix For: Commons Log Service 1.1.0
>
>
> As discussed on the mailing list, we should avoid implementing our own 
> LogService, especially with the updates of R7 to the LogService specification 
> this would mean to add a lot of new functionality.
> Therefore we should remove the LogService implementation from this bundle but 
> keep logging to SLF4J through a LogListener service



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Closed] (SLING-5263) Request to implement junit test cases for LogSupport.java

2019-08-29 Thread Carsten Ziegeler (Jira)


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

Carsten Ziegeler closed SLING-5263.
---

> Request to implement junit test cases for LogSupport.java
> -
>
> Key: SLING-5263
> URL: https://issues.apache.org/jira/browse/SLING-5263
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Reporter: Tien Nguyen Viet
>Assignee: Robert Munteanu
>Priority: Trivial
> Fix For: Commons Log Service 1.1.0
>
>
> org.apache.sling.commons.logservice.internal.LogSupport.java is not 100% 
> covered by junit test cases, can i request to let me implement the test cases 
> ?
> CC: [~cziegeler]



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[VOTE RESULT] Release Apache Sling Commons LogService 1.1.0

2019-08-29 Thread Carsten Ziegeler

The vote passed with three binding +1 votes and one non binding +1 vote

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


[jira] [Commented] (SLING-8655) Add an Annotation to Sling Model to mark a property to be Externalized

2019-08-29 Thread Andreas Schaefer (Jira)


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

Andreas Schaefer commented on SLING-8655:
-

I updated the PRs with an updated version that provides a Json Serializer. This 
was not to do as the serializer does not have a reference to OSGi system nor 
does it has access to the underlying resource of the Model.

My expertise is limited when it comes to Sling Models and Jackson and so I 
might have gone awry here. That said I have the most trouble with finding a 
solution for the Annotation Parameters to create an elegant way to tell the 
Externalized Path Provider to get the services it needs but I though with the 
Resource one can get the most out of Sling with adaption and so this is what I 
did.

> Add an Annotation to Sling Model to mark a property to be Externalized
> --
>
> Key: SLING-8655
> URL: https://issues.apache.org/jira/browse/SLING-8655
> Project: Sling
>  Issue Type: New Feature
>  Components: Sling Models
>Affects Versions: Sling Models API 1.3.8
>Reporter: Andreas Schaefer
>Assignee: Andreas Schaefer
>Priority: Major
> Fix For: Sling Models API 1.3.10
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> For Peregrine CMS we use Sling Models to obtain data in JSon format to be 
> rendered on the client side. This means that the returned content is not 
> externalized aka paths are not mapped to the external view.
> Sling Model should have an Annotation (@ExternalizedPath) that marks a 
> property to be externalized when loaded.
> In order to be flexible the Externalized Path Injector should be pluggable so 
> that customers can add their custom Externalized Path Providers if they 
> choose to do so. By default there is a provider that uses the Resource 
> Resolver's map() function.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[RESULT] [VOTE] Release Apache Sling Starter Content 1.0.6, Apache Sling Dynamic Include 3.1.6, Apache Sling Form Based Authentication 1.0.16

2019-08-29 Thread Robert Munteanu
Hi,

The vote has passed with the following result:

+1 (binding): Georg Henzler, Carsten Ziegeler, Dan Klco, Radu Cotescu, Robert 
Munteanu
+1 (non-binding): Andreas Schaefer

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

Regards,
Robert Munteanu


[jira] [Resolved] (SLING-8584) Donation proposal of nodejs slingpackager

2019-08-29 Thread Robert Munteanu (Jira)


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

Robert Munteanu resolved SLING-8584.

Resolution: Fixed

Added in [sling-whiteboard commit 
58399dc|https://github.com/apache/sling-whiteboard/commit/58399dc], thanks 
[~hsagi...@gmail.com]!

> Donation proposal of nodejs slingpackager
> -
>
> Key: SLING-8584
> URL: https://issues.apache.org/jira/browse/SLING-8584
> Project: Sling
>  Issue Type: New Feature
>Reporter: Henry Saginor
>Assignee: Robert Munteanu
>Priority: Minor
> Attachments: slingpackager.tar.gz
>
>
> h1. Modules
> This donation proposal covers one module.
> ||Module||Source||Description||
> |slingpackager|on 
> [GitHub|https://github.com/peregrine-cms/slingpackager/tree/apacheContrib]
>  or [^slingpackager.tar.gz] 
> (shasum ee91c707070f81d9516c8fedbab0aec30605c225)|A nodejs based command line 
> tool alternative to the maven plugin.
>  This tool covers the following use cases.
>  * build a content package form a local folder
>  * upload a content package onto a server
>  * install a content package on a server
>  * list all installed packages on the server
>  * uninstall a content package from the server
>  * delete a content package on the server|



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


Re: [VOTE] Accept the donation of the Sling Packager tool, SLING-8584

2019-08-29 Thread Robert Munteanu
On Mon, 2019-08-26 at 16:42 +0200, Robert Munteanu wrote:
> Please vote to accept the donation of the Sling Packager module
> described in SLING-8584 [1].

Hi,

The vote has passed with the following result:

+1 (binding): Carsten Ziegeler, Daniel Klco, Radu Cotescu, Robert
Munteanu, Stefan Seifert, Bertrand Delacretaz, Karl Pauls, Nicolas
Peltier
+1 (non-binding): Andreas Schaefer

Thanks all for voting. I will add the contribution to the Sling
whiteboard.

Robert


signature.asc
Description: This is a digitally signed message part


[Jenkins] Sling » sling-org-apache-sling-launchpad-testing » master #291 is FIXED

2019-08-29 Thread Apache Jenkins Server
Please see 
https://builds.apache.org/job/Sling/job/sling-org-apache-sling-launchpad-testing/job/master/291/
 for details.

No further emails will be sent until the status of the build is changed.

Re: Github wiki page

2019-08-29 Thread Bertrand Delacretaz
Hi,

On Thu, Aug 29, 2019 at 2:52 PM Jason E Bailey  wrote:
>
> I believe prior conversations around documentation was to centralize it on 
> the sling website
> versus each bundle having different locations where the documentation could 
> be found...

My recollection is more than each module should be *discoverable* from
https://sling.apache.org/ but we already have modules which have their
own docs in their Git repositories, see
https://sling.apache.org/documentation/bundles/caching-services.html
for example.

For docs in a GitHub repository, a common pattern is to put them in a
"docs" folder and link from the README.

-Bertrand


Re: Github wiki page

2019-08-29 Thread Simone Tripodi
Thanks both Robert and Jason,
I'll switch then my focus on providing the documentation in the right place
~Simo

http://people.apache.org/~simonetripodi/
http://www.99soft.org/

On Thu, Aug 29, 2019 at 2:52 PM Jason E Bailey  wrote:
>
> I believe prior conversations around documentation was to centralize it on 
> the sling website versus each bundle having different locations where the 
> documentation could be found.
>
> --
> Jason
>
> On Thu, Aug 29, 2019, at 8:46 AM, Simone Tripodi wrote:
> > Hi all,
> > I need to massively update the Content-Packages to Feature Model
> > converter documentation and one-page does not fit anymore, the tool
> > has grown and there are a lot of parts that need to be deeply
> > explained, so I wanted to add a wiki section, but... looks like the
> > Wiki is not enabled in the project[1].
> >
> > Is there any way you PMCs can enable it, please?
> >
> > TIA!
> > ~Simo
> >
> > [1] https://github.com/apache/sling-org-apache-sling-feature-cpconverter
> >
> > http://people.apache.org/~simonetripodi/
> > http://www.99soft.org/
> >


Re: Github wiki page

2019-08-29 Thread Jason E Bailey
I believe prior conversations around documentation was to centralize it on the 
sling website versus each bundle having different locations where the 
documentation could be found. 

--
Jason

On Thu, Aug 29, 2019, at 8:46 AM, Simone Tripodi wrote:
> Hi all,
> I need to massively update the Content-Packages to Feature Model
> converter documentation and one-page does not fit anymore, the tool
> has grown and there are a lot of parts that need to be deeply
> explained, so I wanted to add a wiki section, but... looks like the
> Wiki is not enabled in the project[1].
> 
> Is there any way you PMCs can enable it, please?
> 
> TIA!
> ~Simo
> 
> [1] https://github.com/apache/sling-org-apache-sling-feature-cpconverter
> 
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>


Re: Github wiki page

2019-08-29 Thread Robert Munteanu
Hi Simo,

On Thu, 2019-08-29 at 14:46 +0200, Simone Tripodi wrote:
> Hi all,
> I need to massively update the Content-Packages to Feature Model
> converter documentation and one-page does not fit anymore, the tool
> has grown and there are a lot of parts that need to be deeply
> explained, so I wanted to add a wiki section, but... looks like the
> Wiki is not enabled in the project[1].
> 
> Is there any way you PMCs can enable it, please?
> 

We can't enable it, it's controlled by ASF Infra. May I ask why you
prefer to use GH wikis instead of the Sling website for documentation?

Thanks,

Robert

> TIA!
> ~Simo
> 
> [1] 
> https://github.com/apache/sling-org-apache-sling-feature-cpconverter
> 
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/



Github wiki page

2019-08-29 Thread Simone Tripodi
Hi all,
I need to massively update the Content-Packages to Feature Model
converter documentation and one-page does not fit anymore, the tool
has grown and there are a lot of parts that need to be deeply
explained, so I wanted to add a wiki section, but... looks like the
Wiki is not enabled in the project[1].

Is there any way you PMCs can enable it, please?

TIA!
~Simo

[1] https://github.com/apache/sling-org-apache-sling-feature-cpconverter

http://people.apache.org/~simonetripodi/
http://www.99soft.org/