[jira] [Created] (SLING-7449) sling-mock: Allow to set SlingScript in SlingScriptHelper

[Stefan Seifert (JIRA)]

Stefan Seifert created SLING-7449:
-

 Summary: sling-mock: Allow to set SlingScript in SlingScriptHelper
 Key: SLING-7449
 URL: https://issues.apache.org/jira/browse/SLING-7449
 Project: Sling
  Issue Type: Improvement
  Components: Testing
Reporter: Stefan Seifert
Assignee: Stefan Seifert
 Fix For: Testing Sling Mock 1.9.12, Testing Sling Mock 2.2.16


we should add a possibility to set and get SlingScript instances in 
MockSlingScriptHelper to be able to test script engine implementations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (SLING-7449) sling-mock: Allow to set SlingScript in SlingScriptHelper

[Stefan Seifert (JIRA)]

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

Stefan Seifert resolved SLING-7449.
---
Resolution: Fixed

1.x: 
https://github.com/apache/sling-org-apache-sling-testing-sling-mock/commit/7409682fb3f243fe11a2e20ae1d5ae1942d5a8d0
2.x: 
https://github.com/apache/sling-org-apache-sling-testing-sling-mock/commit/1aa0b5bf04a2f84693dda2388f9d15e0ad3428f5

> sling-mock: Allow to set SlingScript in SlingScriptHelper
> -
>
> Key: SLING-7449
> URL: https://issues.apache.org/jira/browse/SLING-7449
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Major
>  Labels: mocks
> Fix For: Testing Sling Mock 1.9.12, Testing Sling Mock 2.2.16
>
>
> we should add a possibility to set and get SlingScript instances in 
> MockSlingScriptHelper to be able to test script engine implementations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (SLING-7438) Migrate pax exam test module to Oak 1.8

[Oliver Lietz (JIRA)]

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

Oliver Lietz reassigned SLING-7438:
---

Assignee: Oliver Lietz

> Migrate pax exam test module to Oak 1.8
> ---
>
> Key: SLING-7438
> URL: https://issues.apache.org/jira/browse/SLING-7438
> Project: Sling
>  Issue Type: Sub-task
>  Components: Testing
>Reporter: Christian Schneider
>Assignee: Oliver Lietz
>Priority: Major
>
> We need to adapt the pax exam testing module to Oak 1.8. This is more than 
> just updating the version as Oak 1.8 needs a few more bundles.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-7438) Update options and versions to Oak 1.8

[Oliver Lietz (JIRA)]

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

Oliver Lietz updated SLING-7438:

Summary: Update options and versions to Oak 1.8  (was: Migrate pax exam 
test module to Oak 1.8)

> Update options and versions to Oak 1.8
> --
>
> Key: SLING-7438
> URL: https://issues.apache.org/jira/browse/SLING-7438
> Project: Sling
>  Issue Type: Sub-task
>  Components: Testing
>Reporter: Christian Schneider
>Assignee: Oliver Lietz
>Priority: Major
>
> We need to adapt the pax exam testing module to Oak 1.8. This is more than 
> just updating the version as Oak 1.8 needs a few more bundles.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-7423) Upgrade Oak to 1.8

[Oliver Lietz (JIRA)]

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

Oliver Lietz updated SLING-7423:

Summary: Upgrade Oak to 1.8  (was: Support Oak 1.8 in JCR Oak Server)

> Upgrade Oak to 1.8
> --
>
> Key: SLING-7423
> URL: https://issues.apache.org/jira/browse/SLING-7423
> Project: Sling
>  Issue Type: Sub-task
>Affects Versions: JCR Oak Server 1.1.4
>Reporter: Christian Schneider
>Assignee: Oliver Lietz
>Priority: Major
>
> The oak server bundle currently does not work with Oak 1.7 and 1.8 as the API 
> was changed in an incompatible way. We should adapt to these changes. See 
> below for the changed classes.
> 1.6
> import org.apache.jackrabbit.oak.plugins.index.aggregate.NodeAggregator; 
> import org.apache.jackrabbit.oak.plugins.nodetype.write.InitialContent;
> import org.apache.jackrabbit.oak.spi.whiteboard.WhiteboardIndexEditorProvider;
> import org.apache.jackrabbit.oak.spi.whiteboard.WhiteboardIndexProvider;
> 1.7
> import org.apache.jackrabbit.oak.spi.query.QueryIndex.NodeAggregator; -> 
> oak-query-spi
> import org.apache.jackrabbit.oak.InitialContent; -> oak-core
> import org.apache.jackrabbit.oak.spi.query.WhiteboardIndexProvider; -> 
> oak-query-spi
> import org.apache.jackrabbit.oak.plugins.index.WhiteboardIndexEditorProvider; 
> -> oak-core
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-7438) Update options and versions to Oak 1.8

[Oliver Lietz (JIRA)]

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

Oliver Lietz updated SLING-7438:

Description: 
We need to adapt the pax exam testing module to Oak 1.8. This is more than just 
updating the version as Oak 1.8 needs a few more bundles.



Preparing for Oak 1.8 in branch 
[feature/oak-1.8|https://github.com/apache/sling-org-apache-sling-testing-paxexam/tree/feature/oak-1.8].

  was:We need to adapt the pax exam testing module to Oak 1.8. This is more 
than just updating the version as Oak 1.8 needs a few more bundles.


> Update options and versions to Oak 1.8
> --
>
> Key: SLING-7438
> URL: https://issues.apache.org/jira/browse/SLING-7438
> Project: Sling
>  Issue Type: Sub-task
>  Components: Testing
>Reporter: Christian Schneider
>Assignee: Oliver Lietz
>Priority: Major
>
> We need to adapt the pax exam testing module to Oak 1.8. This is more than 
> just updating the version as Oak 1.8 needs a few more bundles.
> 
> Preparing for Oak 1.8 in branch 
> [feature/oak-1.8|https://github.com/apache/sling-org-apache-sling-testing-paxexam/tree/feature/oak-1.8].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-7423) Upgrade Oak to 1.8

[Oliver Lietz (JIRA)]

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

Oliver Lietz updated SLING-7423:

Description: 
The oak server bundle currently does not work with Oak 1.7 and 1.8 as the API 
was changed in an incompatible way. We should adapt to these changes. See below 
for the changed classes.

1.6
import org.apache.jackrabbit.oak.plugins.index.aggregate.NodeAggregator; 
import org.apache.jackrabbit.oak.plugins.nodetype.write.InitialContent;
import org.apache.jackrabbit.oak.spi.whiteboard.WhiteboardIndexEditorProvider;
import org.apache.jackrabbit.oak.spi.whiteboard.WhiteboardIndexProvider;

1.7
import org.apache.jackrabbit.oak.spi.query.QueryIndex.NodeAggregator; -> 
oak-query-spi
import org.apache.jackrabbit.oak.InitialContent; -> oak-core
import org.apache.jackrabbit.oak.spi.query.WhiteboardIndexProvider; -> 
oak-query-spi
import org.apache.jackrabbit.oak.plugins.index.WhiteboardIndexEditorProvider; 
-> oak-core



Preparing for Oak 1.8 in branch 
[feature/oak-1.8|https://github.com/apache/sling-org-apache-sling-jcr-oak-server/tree/feature/oak-1.8].
 

  was:
The oak server bundle currently does not work with Oak 1.7 and 1.8 as the API 
was changed in an incompatible way. We should adapt to these changes. See below 
for the changed classes.

1.6
import org.apache.jackrabbit.oak.plugins.index.aggregate.NodeAggregator; 
import org.apache.jackrabbit.oak.plugins.nodetype.write.InitialContent;
import org.apache.jackrabbit.oak.spi.whiteboard.WhiteboardIndexEditorProvider;
import org.apache.jackrabbit.oak.spi.whiteboard.WhiteboardIndexProvider;

1.7
import org.apache.jackrabbit.oak.spi.query.QueryIndex.NodeAggregator; -> 
oak-query-spi
import org.apache.jackrabbit.oak.InitialContent; -> oak-core
import org.apache.jackrabbit.oak.spi.query.WhiteboardIndexProvider; -> 
oak-query-spi
import org.apache.jackrabbit.oak.plugins.index.WhiteboardIndexEditorProvider; 
-> oak-core

 


> Upgrade Oak to 1.8
> --
>
> Key: SLING-7423
> URL: https://issues.apache.org/jira/browse/SLING-7423
> Project: Sling
>  Issue Type: Sub-task
>Affects Versions: JCR Oak Server 1.1.4
>Reporter: Christian Schneider
>Assignee: Oliver Lietz
>Priority: Major
>
> The oak server bundle currently does not work with Oak 1.7 and 1.8 as the API 
> was changed in an incompatible way. We should adapt to these changes. See 
> below for the changed classes.
> 1.6
> import org.apache.jackrabbit.oak.plugins.index.aggregate.NodeAggregator; 
> import org.apache.jackrabbit.oak.plugins.nodetype.write.InitialContent;
> import org.apache.jackrabbit.oak.spi.whiteboard.WhiteboardIndexEditorProvider;
> import org.apache.jackrabbit.oak.spi.whiteboard.WhiteboardIndexProvider;
> 1.7
> import org.apache.jackrabbit.oak.spi.query.QueryIndex.NodeAggregator; -> 
> oak-query-spi
> import org.apache.jackrabbit.oak.InitialContent; -> oak-core
> import org.apache.jackrabbit.oak.spi.query.WhiteboardIndexProvider; -> 
> oak-query-spi
> import org.apache.jackrabbit.oak.plugins.index.WhiteboardIndexEditorProvider; 
> -> oak-core
> 
> Preparing for Oak 1.8 in branch 
> [feature/oak-1.8|https://github.com/apache/sling-org-apache-sling-jcr-oak-server/tree/feature/oak-1.8].
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-7442) Upgrade Karaf Features to Oak 1.8

[Oliver Lietz (JIRA)]

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

Oliver Lietz updated SLING-7442:

Description: Preparing for Oak 1.8 in branch 
[feature/oak-1.8|https://github.com/apache/sling-org-apache-sling-karaf-features/tree/feature/oak-1.8]
 (ITs: 
[feature/oak-1.8|https://github.com/apache/sling-org-apache-sling-karaf-integration-tests/tree/feature/oak-1.8]).

> Upgrade Karaf Features to Oak 1.8
> -
>
> Key: SLING-7442
> URL: https://issues.apache.org/jira/browse/SLING-7442
> Project: Sling
>  Issue Type: Sub-task
>  Components: Karaf
>Reporter: Christian Schneider
>Assignee: Oliver Lietz
>Priority: Major
> Fix For: Karaf Features 0.2.0, Karaf Integration Tests 0.2.0
>
>
> Preparing for Oak 1.8 in branch 
> [feature/oak-1.8|https://github.com/apache/sling-org-apache-sling-karaf-features/tree/feature/oak-1.8]
>  (ITs: 
> [feature/oak-1.8|https://github.com/apache/sling-org-apache-sling-karaf-integration-tests/tree/feature/oak-1.8]).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7446) Support Oak 1.8

[Oliver Lietz (JIRA)]

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

Oliver Lietz commented on SLING-7446:
-

[~ch...@die-schneider.net], can you build Testing PaxExam and JCR Oak Server 
from branch {{feature/oak-1.8}} each and check if it works for you?

> Support Oak 1.8
> ---
>
> Key: SLING-7446
> URL: https://issues.apache.org/jira/browse/SLING-7446
> Project: Sling
>  Issue Type: Task
>  Components: JCR, Karaf, Launchpad, Testing
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>Priority: Major
>  Labels: Sling-11-ReleaseNotes
>
> Oak 1.8 introduced several new modules and reorganized some public packages.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

RE: apache/sling as github landing repository

[Stefan Seifert]

+1

stefan

>-Original Message-
>From: Alexander Klimetschek [mailto:aklim...@adobe.com.INVALID]
>Sent: Friday, January 26, 2018 12:54 AM
>To: dev@sling.apache.org
>Subject: apache/sling as github landing repository
>
>Hi everyone,
>
>after the move to github and source code modularization (cool), the
>previous sling repository apache/sling [0] is now empty. Except for a
>readme that currently mostly addresses active committers (few, experts that
>know the context) rather than users of sling (many, newbies that see Sling
>code for the first time). It was renamed to apache/sling-old-svn-mirror.
>Old links – if they include a branch or revision will still work, including
>trunk – which is good.
>
>However, sling now doesn't have a good github "landing" repository anymore.
>You know, a central place that tells you where to find the code, which is
>now scattered across many repos, or that allows you to browse it without
>knowing exactly what to search for.
>
>Currently the very well hidden answers are [1] and [2], which aren't
>obvious. When hitting apache/sling, you find a readme that links to the
>project info page [3] that among many other links and lots of texts has a
>link to [1], which is hard to find IMO and has too many steps.
>
>Furthermore, [1] is not curated and depends on whatever result order sling
>gives you. But it might be very useful to categorize the repos, say all
>"resource resolver" related stuff, or extensions. Oliver Lietz built [5]
>based on automatic processing of [2], but it's also not curated and hard to
>find things if you don't know exactly how things are split up and named.
>
>My humble suggestion would be:
>
>1. restore the apache/sling named repo, since that should help with SEO and
>"keeping" the existing brand
>
>2. have a readme in there as the github landing page, just like any github
>project nowadays, which should include an about project and most
>information how to use sling/download it, find source repos and how to
>build it. Similar to the project information page [3], but more easily
>digestible with less text.
>
>3. move the aggregator [2] to apache/sling, as that feels like a natural
>place (since this all happens on the new "master" branch, there is no
>conflict with the old sling code base in there)
>
>4. have a curated list of repos in there (could be a separated markdown
>prominently linked from the main readme given its size), which would
>provide some categorization and e.g. start with the important stuff at the
>top. Guidelines for creating new repos/changing repos should hint at
>updating this readme. But even if it's not 100% up to date all the time,
>the vast majority of repos that don't change over time will be explorable.
>
>WDYT?
>
>FYI, this was initially discussed on [4]. I was always looking at Sling
>source code on github before, searching, reading, looking at the version
>history, even when it was "just" a mirror of the svn. When you were only
>reading, this didn't matter, and github's web view is so much better than
>the svn web view. I believe many folks did the same. The switch now is a
>bit of a break in that approach, if you can't easily find the source code
>anymore.
>
>[0] https://github.com/apache/sling
>[1] https://github.com/apache/?q=sling
>[2] https://github.com/apache/sling-aggregator
>[3] https://sling.apache.org/project-information.html#source-repository
>[4] https://github.com/apache/sling-old-svn-
>mirror/commit/9c14db46650bd9b6017511e8a61d021e17b4e1d2#commitcomment-
>26941906
>[5] https://oliverlietz.github.io/apache-sling-aggregator/
>
>Cheers,
>Alex

[jira] [Commented] (SLING-7227) Repo Init: Add ability to register custom privileges

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-7227:


Thanks [~karlpauls], looks good!

For the syntax I think "register abstract privilege" would be more consistent 
with the existing syntax, compared to "create service user" for example. 
Instead of the "as abstract" suffix and with "abstract" being optional of 
course. 

FWIW there's a full syntax example at 
https://sling.apache.org/documentation/bundles/repository-initialization.html , 
for comparison with other statements.

If you agree, that's just a small parser change. Apart from that I think you're 
good to go, thanks!

In general we should add tests to {{ParsingErrorsTest}} [1] when introducing 
new syntax. If you think of interesting error cases please add them, but given 
that this new syntax is simple and flexible there might not be any. Just 
mentioning this in case someone looks at this ticket as an example later.

[1] 
https://github.com/apache/sling-org-apache-sling-repoinit-parser/blob/master/src/test/java/org/apache/sling/repoinit/parser/test/ParsingErrorsTest.java



> Repo Init: Add ability to register custom privileges
> 
>
> Key: SLING-7227
> URL: https://issues.apache.org/jira/browse/SLING-7227
> Project: Sling
>  Issue Type: Improvement
>  Components: Repoinit
>Reporter: angela
>Assignee: Karl Pauls
>Priority: Major
> Fix For: Repoinit Parser 1.2.2, Repoinit JCR 1.1.8
>
>
> [~marett], [~bdelacretaz], looking at the repo-init source I couldn't find a 
> way to register a custom privilege during repo init. I am sure this is an 
> oversight and hasn't been omitted intentionally.
> The corresponding API calls are:
> {code}
> JackrabbitWorkspace.getPrivilegeManager()
> PrivilegeManager.registerPrivilege(String privilegeName, boolean isAbstract, 
> String[] declaredAggregateNames)
> {code}
> See also
> http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/JackrabbitWorkspace.java?view=markup
> http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/security/authorization/PrivilegeManager.java?view=markup
> I would be appreciate if the repo init could have this gap filled. Thanks.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[VOTE] Release Apache Sling Testing Sling Mock 1.9.12, Sling Mock 2.2.16

[Stefan Seifert]

Hi,

Apache Sling Testing Sling Mock 1.9.12  (1 issue)
https://issues.apache.org/jira/browse/SLING/fixforversion/12341771

Apache Sling Testing Sling Mock 2.2.16  (1 issue)
https://issues.apache.org/jira/browse/SLING/fixforversion/12341772

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

You can use this UNIX script to download the release and verify the signatures:
https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD

Usage:
sh check_staged_release.sh 1864 /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.

stefan

RE: [VOTE] Release Apache Sling Testing Sling Mock 1.9.12, Sling Mock 2.2.16

[Stefan Seifert]

+1

[jira] [Commented] (SLING-7227) Repo Init: Add ability to register custom privileges

[Karl Pauls (JIRA)]

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

Karl Pauls commented on SLING-7227:
---

[~bdelacretaz], I changed the syntax to what you recommended - please review 
the PR's again and let me know if you want me to merge. Thanks!

> Repo Init: Add ability to register custom privileges
> 
>
> Key: SLING-7227
> URL: https://issues.apache.org/jira/browse/SLING-7227
> Project: Sling
>  Issue Type: Improvement
>  Components: Repoinit
>Reporter: angela
>Assignee: Karl Pauls
>Priority: Major
> Fix For: Repoinit Parser 1.2.2, Repoinit JCR 1.1.8
>
>
> [~marett], [~bdelacretaz], looking at the repo-init source I couldn't find a 
> way to register a custom privilege during repo init. I am sure this is an 
> oversight and hasn't been omitted intentionally.
> The corresponding API calls are:
> {code}
> JackrabbitWorkspace.getPrivilegeManager()
> PrivilegeManager.registerPrivilege(String privilegeName, boolean isAbstract, 
> String[] declaredAggregateNames)
> {code}
> See also
> http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/JackrabbitWorkspace.java?view=markup
> http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/security/authorization/PrivilegeManager.java?view=markup
> I would be appreciate if the repo init could have this gap filled. Thanks.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Release Apache Sling Testing Sling Mock 1.9.12, Sling Mock 2.2.16

[Daniel Klco]

+1

On Fri, Jan 26, 2018 at 5:13 AM, Stefan Seifert 
wrote:

> +1
>
>
>

[jira] [Commented] (SLING-7227) Repo Init: Add ability to register custom privileges

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-7227:


...I forgot another nitpick, please add a few examples of the new syntax in 
test-99.txt which is supposed to have short examples of everything. That's the 
file that we copy to the website docs, slightly adapted to indicate required 
bundle versions.

Apart from that I'm fine with you merging those changes in, thanks!

> Repo Init: Add ability to register custom privileges
> 
>
> Key: SLING-7227
> URL: https://issues.apache.org/jira/browse/SLING-7227
> Project: Sling
>  Issue Type: Improvement
>  Components: Repoinit
>Reporter: angela
>Assignee: Karl Pauls
>Priority: Major
> Fix For: Repoinit Parser 1.2.2, Repoinit JCR 1.1.8
>
>
> [~marett], [~bdelacretaz], looking at the repo-init source I couldn't find a 
> way to register a custom privilege during repo init. I am sure this is an 
> oversight and hasn't been omitted intentionally.
> The corresponding API calls are:
> {code}
> JackrabbitWorkspace.getPrivilegeManager()
> PrivilegeManager.registerPrivilege(String privilegeName, boolean isAbstract, 
> String[] declaredAggregateNames)
> {code}
> See also
> http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/JackrabbitWorkspace.java?view=markup
> http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/security/authorization/PrivilegeManager.java?view=markup
> I would be appreciate if the repo init could have this gap filled. Thanks.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7227) Repo Init: Add ability to register custom privileges

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SLING-7227:
---

karlpauls closed pull request #1: SLING-7227:  Add ability to register custom 
privileges.
URL: https://github.com/apache/sling-org-apache-sling-repoinit-parser/pull/1
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Repo Init: Add ability to register custom privileges
> 
>
> Key: SLING-7227
> URL: https://issues.apache.org/jira/browse/SLING-7227
> Project: Sling
>  Issue Type: Improvement
>  Components: Repoinit
>Reporter: angela
>Assignee: Karl Pauls
>Priority: Major
> Fix For: Repoinit Parser 1.2.2, Repoinit JCR 1.1.8
>
>
> [~marett], [~bdelacretaz], looking at the repo-init source I couldn't find a 
> way to register a custom privilege during repo init. I am sure this is an 
> oversight and hasn't been omitted intentionally.
> The corresponding API calls are:
> {code}
> JackrabbitWorkspace.getPrivilegeManager()
> PrivilegeManager.registerPrivilege(String privilegeName, boolean isAbstract, 
> String[] declaredAggregateNames)
> {code}
> See also
> http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/JackrabbitWorkspace.java?view=markup
> http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/security/authorization/PrivilegeManager.java?view=markup
> I would be appreciate if the repo init could have this gap filled. Thanks.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7227) Repo Init: Add ability to register custom privileges

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SLING-7227:
---

karlpauls closed pull request #1: SLING-7227:  Add ability to register custom 
privileges.
URL: https://github.com/apache/sling-org-apache-sling-jcr-repoinit/pull/1
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Repo Init: Add ability to register custom privileges
> 
>
> Key: SLING-7227
> URL: https://issues.apache.org/jira/browse/SLING-7227
> Project: Sling
>  Issue Type: Improvement
>  Components: Repoinit
>Reporter: angela
>Assignee: Karl Pauls
>Priority: Major
> Fix For: Repoinit Parser 1.2.2, Repoinit JCR 1.1.8
>
>
> [~marett], [~bdelacretaz], looking at the repo-init source I couldn't find a 
> way to register a custom privilege during repo init. I am sure this is an 
> oversight and hasn't been omitted intentionally.
> The corresponding API calls are:
> {code}
> JackrabbitWorkspace.getPrivilegeManager()
> PrivilegeManager.registerPrivilege(String privilegeName, boolean isAbstract, 
> String[] declaredAggregateNames)
> {code}
> See also
> http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/JackrabbitWorkspace.java?view=markup
> http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/security/authorization/PrivilegeManager.java?view=markup
> I would be appreciate if the repo init could have this gap filled. Thanks.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (SLING-7227) Repo Init: Add ability to register custom privileges

[Karl Pauls (JIRA)]

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

Karl Pauls resolved SLING-7227.
---
Resolution: Fixed

[~bdelacretaz], I added the examples and merged the PR's. 

> Repo Init: Add ability to register custom privileges
> 
>
> Key: SLING-7227
> URL: https://issues.apache.org/jira/browse/SLING-7227
> Project: Sling
>  Issue Type: Improvement
>  Components: Repoinit
>Reporter: angela
>Assignee: Karl Pauls
>Priority: Major
> Fix For: Repoinit Parser 1.2.2, Repoinit JCR 1.1.8
>
>
> [~marett], [~bdelacretaz], looking at the repo-init source I couldn't find a 
> way to register a custom privilege during repo init. I am sure this is an 
> oversight and hasn't been omitted intentionally.
> The corresponding API calls are:
> {code}
> JackrabbitWorkspace.getPrivilegeManager()
> PrivilegeManager.registerPrivilege(String privilegeName, boolean isAbstract, 
> String[] declaredAggregateNames)
> {code}
> See also
> http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/JackrabbitWorkspace.java?view=markup
> http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/security/authorization/PrivilegeManager.java?view=markup
> I would be appreciate if the repo init could have this gap filled. Thanks.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (SLING-7447) Race condition in ThreadLocalCleaner initialization code

[Konrad Windszus (JIRA)]

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

Konrad Windszus edited comment on SLING-7447 at 1/26/18 3:34 PM:
-

Fixed in 
https://github.com/apache/sling-org-apache-sling-commons-threads/commit/c472954b67524042618b59bb0e45f180bcea146f


was (Author: rombert):
Fixed in [sling-org-apache-sling-commons-threads commit 
5a85b22|https://github.com/apache/sling-org-apache-sling-commons-threads/commit/5a85b22]
 

> Race condition in ThreadLocalCleaner initialization code
> 
>
> Key: SLING-7447
> URL: https://issues.apache.org/jira/browse/SLING-7447
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Affects Versions: Commons Threads 3.2.14
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Blocker
> Fix For: Commons Threads 3.2.16
>
>
> There is a race condition in the {{ThreadLocalCleaner}} initialization code 
> that can lead to the fields not being fully initialized when read.
> The stack trace is similar to
> {noformat}Exception in thread "sling-oak-observation-2" 
> java.lang.NullPointerException
> at 
> org.apache.sling.commons.threads.impl.ThreadLocalCleaner.copy(ThreadLocalCleaner.java:110)
> at 
> org.apache.sling.commons.threads.impl.ThreadLocalCleaner.saveOldThreadLocals(ThreadLocalCleaner.java:230)
> at 
> org.apache.sling.commons.threads.impl.ThreadLocalCleaner.(ThreadLocalCleaner.java:155)
> at 
> org.apache.sling.commons.threads.impl.ThreadPoolExecutorCleaningThreadLocals.beforeExecute(ThreadPoolExecutorCleaningThreadLocals.java:58)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1139)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748){noformat}
> Assume that two threads, _T1_ and _T2_ enter the constructor at more or less 
> the same time. The following events can then occur, leading to the above 
> invalid access
> ||T1||T2||
> |check threadLocalsField (is null)|  |
> |invoke initReflectionFields, load threadLocalsField|  |
> |  | check threadLocalsField (is not null) |
> |  | invoke saveOldTreadLocals |
> |  | invoke copy |
> At this point, the {{tableField}} field is null since 
> {{initReflectionFields}} has not yet completed, which leads to the above NPE.
> _edit_: formatting



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7320) NPE in sling commons threads

[Konrad Windszus (JIRA)]

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

Konrad Windszus commented on SLING-7320:


Actually my fix was not sufficient. The correct fix for the first NPE is now in 
SLING-7447.

> NPE in sling commons threads
> 
>
> Key: SLING-7320
> URL: https://issues.apache.org/jira/browse/SLING-7320
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Affects Versions: Commons Threads 3.2.10
> Environment: Linux, jdk18
>Reporter: Ivo Leitão
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: Commons Threads 3.2.16
>
>
> I'm currently running a number of integration tests via pax exam and 
> sometimes I see the following stacktrace. I've already seen this in a running 
> sling also. This happens only in some runs but on that cases is breaking my 
> CI workflow
> Exception in thread "sling-default-5" java.lang.NullPointerException
>   at 
> org.apache.sling.commons.threads.impl.ThreadLocalCleaner.copy(ThreadLocalCleaner.java:186)
>   at 
> org.apache.sling.commons.threads.impl.ThreadLocalCleaner.saveOldThreadLocals(ThreadLocalCleaner.java:176)
>   at 
> org.apache.sling.commons.threads.impl.ThreadLocalCleaner.(ThreadLocalCleaner.java:51)
>   at 
> org.apache.sling.commons.threads.impl.ThreadPoolExecutorCleaningThreadLocals.beforeExecute(ThreadPoolExecutorCleaningThreadLocals.java:55)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at java.lang.Thread.run(Thread.java:748)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: apache/sling as github landing repository

[Bertrand Delacretaz]

Hi,

On Fri, Jan 26, 2018 at 12:54 AM, Alexander Klimetschek
 wrote:
>...
> 1. restore the apache/sling named repo...
> 2. have a readme in there as the github landing page, just like any github 
> project nowadays,
> which should include an about project and most information how to use 
> sling/download it...

I like the idea in general, thanks!

We already have download/build information on our website, I think we
shouldn't duplicate - so either remove the webiste info or point to it
from that README, but create something consistent and that does not
easily get stale.

For now, I have created a list of all our repositories at
http://sling.apache.org/repolist.html based on the XML list of
projects generated at https://github.com/apache/sling-aggregator. It
would be nice to expand it with a few words about each repository but
I haven't checked how to generate that so far - and whether that would
interfere with the repo tool.

-Bertrand

[jira] [Commented] (SLING-7331) Set up Maven aggregator project for all regular modules

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-7331:


I haven't checked how you generate the list of modules - note that we have an 
autogenerated one at https://github.com/apache/sling-aggregator, which I'm now 
using the generate the new http://sling.apache.org/repolist.html page

> Set up Maven aggregator project for all regular modules
> ---
>
> Key: SLING-7331
> URL: https://issues.apache.org/jira/browse/SLING-7331
> Project: Sling
>  Issue Type: Task
>  Components: General, Tooling
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>Priority: Major
>
> Goals:
> * open all regular modules with a single POM in IDEs
>   ** groups: core, scripting, models, karaf, commons, distribution, 
> discovery, ...
> * _full_ build
> 
> https://github.com/oliverlietz/apache-sling-aggregator
> {noformat}
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Apache Sling Adapter Annotations ... SUCCESS [ 12.689 
> s]
> [INFO] Apache Sling JAR Resource Bundle ... SUCCESS [  0.535 
> s]
> [INFO] Apache Sling HTL Maven Plugin .. SUCCESS [ 15.121 
> s]
> [INFO] Apache Sling Maven JSP Compiler Plugin . SUCCESS [  5.573 
> s]
> [INFO] Apache Sling Launchpad Comparator .. SUCCESS [ 10.489 
> s]
> [INFO] Apache Sling Maven JCROCM Plugin ... SUCCESS [  1.183 
> s]
> [INFO] Apache Sling Maven Launchpad Plugin  SUCCESS [ 14.740 
> s]
> [INFO] Apache Sling Maven Sling Plugin  SUCCESS [  7.567 
> s]
> [INFO] Apache Sling Adapter Manager Implementation  SUCCESS [  5.527 
> s]
> [INFO] Apache Sling API ... SUCCESS [ 11.931 
> s]
> [INFO] Apache Sling Authentication Service  SUCCESS [  4.236 
> s]
> [INFO] Apache Sling Form Based Authentication Handler . SUCCESS [ 18.973 
> s]
> [INFO] Apache Sling Authentication XING API ... SUCCESS [  2.086 
> s]
> [INFO] Apache Sling Authentication XING Login . SUCCESS [  6.348 
> s]
> [INFO] Apache Sling Authentication XING OAuth . SUCCESS [  2.301 
> s]
> [INFO] Apache Sling Models bnd Plugin . SUCCESS [  2.557 
> s]
> [INFO] Apache Sling Bundle Resource Provider .. SUCCESS [  2.935 
> s]
> [INFO] Apache Sling Context-Aware Configuration API ... SUCCESS [  1.440 
> s]
> [INFO] Apache Sling Context-Aware Configuration bnd Plugin  SUCCESS [  1.131 
> s]
> [INFO] Apache Sling Context-Aware Configuration Implementation SUCCESS [ 
> 14.570 s]
> [INFO] Apache Sling Context-Aware Configuration SPI ... SUCCESS [  2.591 
> s]
> [INFO] Apache Sling Validation Framework Core Implementation SUCCESS [01:54 
> min]
> [INFO] Apache Sling Sample Slingshot .. SUCCESS [ 10.975 
> s]
> [INFO] Apache Sling Context-Aware Configuration Integration Tests SUCCESS [ 
> 48.131 s]
> [INFO] Apache Sling Cassandra Resource Provider ... FAILURE [01:20 
> min]
> [INFO] Apache Sling Commons Cache API . SUCCESS [  8.379 
> s]
> [INFO] Apache Sling OSGi PAX Exam support library . SUCCESS [ 10.545 
> s]
> [INFO] Apache Sling Cache API Implementation support library SUCCESS [  0.336 
> s]
> [INFO] Apache Sling Cache API EhCache implementation .. FAILURE [ 52.695 
> s]
> [INFO] Apache Sling Cache Portal Cache  FAILURE [  1.036 
> s]
> [INFO] Apache Sling Dynamic Class Loader Support .. SUCCESS [ 10.888 
> s]
> [INFO] Apache Sling Commons Java Compiler . SUCCESS [  4.175 
> s]
> [INFO] Apache Sling Content Detection Support . SUCCESS [ 20.521 
> s]
> [INFO] Apache Sling Commons FileSystem ClassLoader  SUCCESS [  2.955 
> s]
> [INFO] Apache Sling Commons HTML Utilities  SUCCESS [  1.610 
> s]
> [INFO] Apache Sling Commons Johnzon Wrapper Library ... SUCCESS [  2.192 
> s]
> [INFO] Apache Sling Commons Log ... SUCCESS [ 40.843 
> s]
> [INFO] Apache Sling Log WebConsole  SUCCESS [ 16.236 
> s]
> [INFO] Apache Sling OSGi LogService Implementation  SUCCESS [  1.673 
> s]
> [INFO] Apache Sling Commons Messaging . SUCCESS [  1.422 
> s]
> [INFO] Apache Sling Commons Messaging Mail  SUCCESS [ 21.980 
> s]
> [INFO] Apache Sling Metrics ... SUCCESS [ 18.032 
> s]
> [INFO] Apache Sling RRD4J metrics reporter  SUCCESS [  6.611 
> s]
> [INFO] Apache Sling Commons MIME type mappin

[jira] [Commented] (SLING-7331) Set up Maven aggregator project for all regular modules

[Konrad Windszus (JIRA)]

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

Konrad Windszus commented on SLING-7331:


This is rather related to SLING-7262.

> Set up Maven aggregator project for all regular modules
> ---
>
> Key: SLING-7331
> URL: https://issues.apache.org/jira/browse/SLING-7331
> Project: Sling
>  Issue Type: Task
>  Components: General, Tooling
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>Priority: Major
>
> Goals:
> * open all regular modules with a single POM in IDEs
>   ** groups: core, scripting, models, karaf, commons, distribution, 
> discovery, ...
> * _full_ build
> 
> https://github.com/oliverlietz/apache-sling-aggregator
> {noformat}
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Apache Sling Adapter Annotations ... SUCCESS [ 12.689 
> s]
> [INFO] Apache Sling JAR Resource Bundle ... SUCCESS [  0.535 
> s]
> [INFO] Apache Sling HTL Maven Plugin .. SUCCESS [ 15.121 
> s]
> [INFO] Apache Sling Maven JSP Compiler Plugin . SUCCESS [  5.573 
> s]
> [INFO] Apache Sling Launchpad Comparator .. SUCCESS [ 10.489 
> s]
> [INFO] Apache Sling Maven JCROCM Plugin ... SUCCESS [  1.183 
> s]
> [INFO] Apache Sling Maven Launchpad Plugin  SUCCESS [ 14.740 
> s]
> [INFO] Apache Sling Maven Sling Plugin  SUCCESS [  7.567 
> s]
> [INFO] Apache Sling Adapter Manager Implementation  SUCCESS [  5.527 
> s]
> [INFO] Apache Sling API ... SUCCESS [ 11.931 
> s]
> [INFO] Apache Sling Authentication Service  SUCCESS [  4.236 
> s]
> [INFO] Apache Sling Form Based Authentication Handler . SUCCESS [ 18.973 
> s]
> [INFO] Apache Sling Authentication XING API ... SUCCESS [  2.086 
> s]
> [INFO] Apache Sling Authentication XING Login . SUCCESS [  6.348 
> s]
> [INFO] Apache Sling Authentication XING OAuth . SUCCESS [  2.301 
> s]
> [INFO] Apache Sling Models bnd Plugin . SUCCESS [  2.557 
> s]
> [INFO] Apache Sling Bundle Resource Provider .. SUCCESS [  2.935 
> s]
> [INFO] Apache Sling Context-Aware Configuration API ... SUCCESS [  1.440 
> s]
> [INFO] Apache Sling Context-Aware Configuration bnd Plugin  SUCCESS [  1.131 
> s]
> [INFO] Apache Sling Context-Aware Configuration Implementation SUCCESS [ 
> 14.570 s]
> [INFO] Apache Sling Context-Aware Configuration SPI ... SUCCESS [  2.591 
> s]
> [INFO] Apache Sling Validation Framework Core Implementation SUCCESS [01:54 
> min]
> [INFO] Apache Sling Sample Slingshot .. SUCCESS [ 10.975 
> s]
> [INFO] Apache Sling Context-Aware Configuration Integration Tests SUCCESS [ 
> 48.131 s]
> [INFO] Apache Sling Cassandra Resource Provider ... FAILURE [01:20 
> min]
> [INFO] Apache Sling Commons Cache API . SUCCESS [  8.379 
> s]
> [INFO] Apache Sling OSGi PAX Exam support library . SUCCESS [ 10.545 
> s]
> [INFO] Apache Sling Cache API Implementation support library SUCCESS [  0.336 
> s]
> [INFO] Apache Sling Cache API EhCache implementation .. FAILURE [ 52.695 
> s]
> [INFO] Apache Sling Cache Portal Cache  FAILURE [  1.036 
> s]
> [INFO] Apache Sling Dynamic Class Loader Support .. SUCCESS [ 10.888 
> s]
> [INFO] Apache Sling Commons Java Compiler . SUCCESS [  4.175 
> s]
> [INFO] Apache Sling Content Detection Support . SUCCESS [ 20.521 
> s]
> [INFO] Apache Sling Commons FileSystem ClassLoader  SUCCESS [  2.955 
> s]
> [INFO] Apache Sling Commons HTML Utilities  SUCCESS [  1.610 
> s]
> [INFO] Apache Sling Commons Johnzon Wrapper Library ... SUCCESS [  2.192 
> s]
> [INFO] Apache Sling Commons Log ... SUCCESS [ 40.843 
> s]
> [INFO] Apache Sling Log WebConsole  SUCCESS [ 16.236 
> s]
> [INFO] Apache Sling OSGi LogService Implementation  SUCCESS [  1.673 
> s]
> [INFO] Apache Sling Commons Messaging . SUCCESS [  1.422 
> s]
> [INFO] Apache Sling Commons Messaging Mail  SUCCESS [ 21.980 
> s]
> [INFO] Apache Sling Metrics ... SUCCESS [ 18.032 
> s]
> [INFO] Apache Sling RRD4J metrics reporter  SUCCESS [  6.611 
> s]
> [INFO] Apache Sling Commons MIME type mapping support . SUCCESS [  1.908 
> s]
> [INFO] Apache Sling Commons OSGi support .. SUCCESS [  4.255 
> s]
> [INFO] Apache Sling Commons Scheduler Support . SUCCESS [  3.

[jira] [Commented] (SLING-7262) Generate reusable list of repositories for machine consumption

[Konrad Windszus (JIRA)]

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

Konrad Windszus commented on SLING-7262:


There is already the file {{.sling-module.xml}} within 
https://github.com/apache/sling-aggregator which could be used instead as 
starting point.

> Generate reusable list of repositories for machine consumption
> --
>
> Key: SLING-7262
> URL: https://issues.apache.org/jira/browse/SLING-7262
> Project: Sling
>  Issue Type: Task
>  Components: Build and Source Control
>Reporter: Robert Munteanu
>Priority: Major
>
> We currently have two 'clients' that query the github repos and the 
> .sling-module.xml descriptors:
> * the jenkins job creation DSL script
> * the repo manifest creation script
> We've also discussed in SLING-7161 the possibility of listing all 
> repositories on the website.
> To minimize the effort of talking to github in each location and reduce the 
> number of calls to Github ( for rate limiting purposes ) we should generate a 
> JSON/XML file that contains all information about the git repos. This file is 
> in turns read by various "clients" that need the information.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: apache/sling as github landing repository

[Konrad Windszus]

Thanks, maybe we can use the branch from 
https://github.com/apache/sling-site/tree/scm-project-url-list 
 (mentioned in 
https://issues.apache.org/jira/browse/SLING-7161 
) as a basis instead. That 
provides already much more information and leveraging the already existing xml 
file from sling-aggregator is a good idea as long as 
https://issues.apache.org/jira/browse/SLING-7262 
 is not resolved.
Konrad

> On 26. Jan 2018, at 18:05, Bertrand Delacretaz  wrote:
> 
> Hi,
> 
> On Fri, Jan 26, 2018 at 12:54 AM, Alexander Klimetschek
>  wrote:
>> ...
>> 1. restore the apache/sling named repo...
>> 2. have a readme in there as the github landing page, just like any github 
>> project nowadays,
>> which should include an about project and most information how to use 
>> sling/download it...
> 
> I like the idea in general, thanks!
> 
> We already have download/build information on our website, I think we
> shouldn't duplicate - so either remove the webiste info or point to it
> from that README, but create something consistent and that does not
> easily get stale.
> 
> For now, I have created a list of all our repositories at
> http://sling.apache.org/repolist.html based on the XML list of
> projects generated at https://github.com/apache/sling-aggregator. It
> would be nice to expand it with a few words about each repository but
> I haven't checked how to generate that so far - and whether that would
> interfere with the repo tool.
> 
> -Bertrand

[jira] [Comment Edited] (SLING-7262) Generate reusable list of repositories for machine consumption

[Konrad Windszus (JIRA)]

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

Konrad Windszus edited comment on SLING-7262 at 1/26/18 5:33 PM:
-

There is already the file {{default.xml}} within 
https://github.com/apache/sling-aggregator which could be used instead as 
starting point.


was (Author: kwin):
There is already the file {{.sling-module.xml}} within 
https://github.com/apache/sling-aggregator which could be used instead as 
starting point.

> Generate reusable list of repositories for machine consumption
> --
>
> Key: SLING-7262
> URL: https://issues.apache.org/jira/browse/SLING-7262
> Project: Sling
>  Issue Type: Task
>  Components: Build and Source Control
>Reporter: Robert Munteanu
>Priority: Major
>
> We currently have two 'clients' that query the github repos and the 
> .sling-module.xml descriptors:
> * the jenkins job creation DSL script
> * the repo manifest creation script
> We've also discussed in SLING-7161 the possibility of listing all 
> repositories on the website.
> To minimize the effort of talking to github in each location and reduce the 
> number of calls to Github ( for rate limiting purposes ) we should generate a 
> JSON/XML file that contains all information about the git repos. This file is 
> in turns read by various "clients" that need the information.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7331) Set up Maven aggregator project for all regular modules

[Oliver Lietz (JIRA)]

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

Oliver Lietz commented on SLING-7331:
-

[~bdelacretaz], I'm using a [Python 
script|https://github.com/oliverlietz/apache-sling-aggregator/blob/tooling/sling-aggregator.py]
 and parse [ASF's GitBox OPML|https://gitbox.apache.org/repos/asf?a=opml] (no 
need to install Groovy, don't have to think about GitHub's limitations). It 
builds a 
[manifest|https://github.com/oliverlietz/apache-sling-aggregator/blob/repo/default.xml]
 for Repo, an [aggregator 
project|https://github.com/oliverlietz/apache-sling-aggregator/blob/master/pom.xml]
 for Maven and a [page|https://oliverlietz.github.io/apache-sling-aggregator/] 
for GitHub in one go.

> Set up Maven aggregator project for all regular modules
> ---
>
> Key: SLING-7331
> URL: https://issues.apache.org/jira/browse/SLING-7331
> Project: Sling
>  Issue Type: Task
>  Components: General, Tooling
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>Priority: Major
>
> Goals:
> * open all regular modules with a single POM in IDEs
>   ** groups: core, scripting, models, karaf, commons, distribution, 
> discovery, ...
> * _full_ build
> 
> https://github.com/oliverlietz/apache-sling-aggregator
> {noformat}
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Apache Sling Adapter Annotations ... SUCCESS [ 12.689 
> s]
> [INFO] Apache Sling JAR Resource Bundle ... SUCCESS [  0.535 
> s]
> [INFO] Apache Sling HTL Maven Plugin .. SUCCESS [ 15.121 
> s]
> [INFO] Apache Sling Maven JSP Compiler Plugin . SUCCESS [  5.573 
> s]
> [INFO] Apache Sling Launchpad Comparator .. SUCCESS [ 10.489 
> s]
> [INFO] Apache Sling Maven JCROCM Plugin ... SUCCESS [  1.183 
> s]
> [INFO] Apache Sling Maven Launchpad Plugin  SUCCESS [ 14.740 
> s]
> [INFO] Apache Sling Maven Sling Plugin  SUCCESS [  7.567 
> s]
> [INFO] Apache Sling Adapter Manager Implementation  SUCCESS [  5.527 
> s]
> [INFO] Apache Sling API ... SUCCESS [ 11.931 
> s]
> [INFO] Apache Sling Authentication Service  SUCCESS [  4.236 
> s]
> [INFO] Apache Sling Form Based Authentication Handler . SUCCESS [ 18.973 
> s]
> [INFO] Apache Sling Authentication XING API ... SUCCESS [  2.086 
> s]
> [INFO] Apache Sling Authentication XING Login . SUCCESS [  6.348 
> s]
> [INFO] Apache Sling Authentication XING OAuth . SUCCESS [  2.301 
> s]
> [INFO] Apache Sling Models bnd Plugin . SUCCESS [  2.557 
> s]
> [INFO] Apache Sling Bundle Resource Provider .. SUCCESS [  2.935 
> s]
> [INFO] Apache Sling Context-Aware Configuration API ... SUCCESS [  1.440 
> s]
> [INFO] Apache Sling Context-Aware Configuration bnd Plugin  SUCCESS [  1.131 
> s]
> [INFO] Apache Sling Context-Aware Configuration Implementation SUCCESS [ 
> 14.570 s]
> [INFO] Apache Sling Context-Aware Configuration SPI ... SUCCESS [  2.591 
> s]
> [INFO] Apache Sling Validation Framework Core Implementation SUCCESS [01:54 
> min]
> [INFO] Apache Sling Sample Slingshot .. SUCCESS [ 10.975 
> s]
> [INFO] Apache Sling Context-Aware Configuration Integration Tests SUCCESS [ 
> 48.131 s]
> [INFO] Apache Sling Cassandra Resource Provider ... FAILURE [01:20 
> min]
> [INFO] Apache Sling Commons Cache API . SUCCESS [  8.379 
> s]
> [INFO] Apache Sling OSGi PAX Exam support library . SUCCESS [ 10.545 
> s]
> [INFO] Apache Sling Cache API Implementation support library SUCCESS [  0.336 
> s]
> [INFO] Apache Sling Cache API EhCache implementation .. FAILURE [ 52.695 
> s]
> [INFO] Apache Sling Cache Portal Cache  FAILURE [  1.036 
> s]
> [INFO] Apache Sling Dynamic Class Loader Support .. SUCCESS [ 10.888 
> s]
> [INFO] Apache Sling Commons Java Compiler . SUCCESS [  4.175 
> s]
> [INFO] Apache Sling Content Detection Support . SUCCESS [ 20.521 
> s]
> [INFO] Apache Sling Commons FileSystem ClassLoader  SUCCESS [  2.955 
> s]
> [INFO] Apache Sling Commons HTML Utilities  SUCCESS [  1.610 
> s]
> [INFO] Apache Sling Commons Johnzon Wrapper Library ... SUCCESS [  2.192 
> s]
> [INFO] Apache Sling Commons Log ... SUCCESS [ 40.843 
> s]
> [INFO] Apache Sling Log WebConsole  SUCCESS [ 16.236 
> s]
> [INFO] Apache Sling OSGi LogService Implementation  SUCCESS [  1.673 
> s]
> [INFO] Apache Sling Commons

[jira] [Commented] (SLING-7331) Set up Maven aggregator project for all regular modules

[Oliver Lietz (JIRA)]

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

Oliver Lietz commented on SLING-7331:
-

btw, I will extend that Python script so one can build a POM and manifest for a 
"group", e.g. {{org.apache.sling.scripting.*}}

> Set up Maven aggregator project for all regular modules
> ---
>
> Key: SLING-7331
> URL: https://issues.apache.org/jira/browse/SLING-7331
> Project: Sling
>  Issue Type: Task
>  Components: General, Tooling
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>Priority: Major
>
> Goals:
> * open all regular modules with a single POM in IDEs
>   ** groups: core, scripting, models, karaf, commons, distribution, 
> discovery, ...
> * _full_ build
> 
> https://github.com/oliverlietz/apache-sling-aggregator
> {noformat}
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Apache Sling Adapter Annotations ... SUCCESS [ 12.689 
> s]
> [INFO] Apache Sling JAR Resource Bundle ... SUCCESS [  0.535 
> s]
> [INFO] Apache Sling HTL Maven Plugin .. SUCCESS [ 15.121 
> s]
> [INFO] Apache Sling Maven JSP Compiler Plugin . SUCCESS [  5.573 
> s]
> [INFO] Apache Sling Launchpad Comparator .. SUCCESS [ 10.489 
> s]
> [INFO] Apache Sling Maven JCROCM Plugin ... SUCCESS [  1.183 
> s]
> [INFO] Apache Sling Maven Launchpad Plugin  SUCCESS [ 14.740 
> s]
> [INFO] Apache Sling Maven Sling Plugin  SUCCESS [  7.567 
> s]
> [INFO] Apache Sling Adapter Manager Implementation  SUCCESS [  5.527 
> s]
> [INFO] Apache Sling API ... SUCCESS [ 11.931 
> s]
> [INFO] Apache Sling Authentication Service  SUCCESS [  4.236 
> s]
> [INFO] Apache Sling Form Based Authentication Handler . SUCCESS [ 18.973 
> s]
> [INFO] Apache Sling Authentication XING API ... SUCCESS [  2.086 
> s]
> [INFO] Apache Sling Authentication XING Login . SUCCESS [  6.348 
> s]
> [INFO] Apache Sling Authentication XING OAuth . SUCCESS [  2.301 
> s]
> [INFO] Apache Sling Models bnd Plugin . SUCCESS [  2.557 
> s]
> [INFO] Apache Sling Bundle Resource Provider .. SUCCESS [  2.935 
> s]
> [INFO] Apache Sling Context-Aware Configuration API ... SUCCESS [  1.440 
> s]
> [INFO] Apache Sling Context-Aware Configuration bnd Plugin  SUCCESS [  1.131 
> s]
> [INFO] Apache Sling Context-Aware Configuration Implementation SUCCESS [ 
> 14.570 s]
> [INFO] Apache Sling Context-Aware Configuration SPI ... SUCCESS [  2.591 
> s]
> [INFO] Apache Sling Validation Framework Core Implementation SUCCESS [01:54 
> min]
> [INFO] Apache Sling Sample Slingshot .. SUCCESS [ 10.975 
> s]
> [INFO] Apache Sling Context-Aware Configuration Integration Tests SUCCESS [ 
> 48.131 s]
> [INFO] Apache Sling Cassandra Resource Provider ... FAILURE [01:20 
> min]
> [INFO] Apache Sling Commons Cache API . SUCCESS [  8.379 
> s]
> [INFO] Apache Sling OSGi PAX Exam support library . SUCCESS [ 10.545 
> s]
> [INFO] Apache Sling Cache API Implementation support library SUCCESS [  0.336 
> s]
> [INFO] Apache Sling Cache API EhCache implementation .. FAILURE [ 52.695 
> s]
> [INFO] Apache Sling Cache Portal Cache  FAILURE [  1.036 
> s]
> [INFO] Apache Sling Dynamic Class Loader Support .. SUCCESS [ 10.888 
> s]
> [INFO] Apache Sling Commons Java Compiler . SUCCESS [  4.175 
> s]
> [INFO] Apache Sling Content Detection Support . SUCCESS [ 20.521 
> s]
> [INFO] Apache Sling Commons FileSystem ClassLoader  SUCCESS [  2.955 
> s]
> [INFO] Apache Sling Commons HTML Utilities  SUCCESS [  1.610 
> s]
> [INFO] Apache Sling Commons Johnzon Wrapper Library ... SUCCESS [  2.192 
> s]
> [INFO] Apache Sling Commons Log ... SUCCESS [ 40.843 
> s]
> [INFO] Apache Sling Log WebConsole  SUCCESS [ 16.236 
> s]
> [INFO] Apache Sling OSGi LogService Implementation  SUCCESS [  1.673 
> s]
> [INFO] Apache Sling Commons Messaging . SUCCESS [  1.422 
> s]
> [INFO] Apache Sling Commons Messaging Mail  SUCCESS [ 21.980 
> s]
> [INFO] Apache Sling Metrics ... SUCCESS [ 18.032 
> s]
> [INFO] Apache Sling RRD4J metrics reporter  SUCCESS [  6.611 
> s]
> [INFO] Apache Sling Commons MIME type mapping support . SUCCESS [  1.908 
> s]
> [INFO] Apache Sling Commons OSGi support .. SUCCESS [  4.2