RE: Pending deletion of maven plugin docs?

[Stefan Seifert]

this worked!

i've changed the distribution URL to 
https://svn.apache.org/repos/asf/sling/site/trunk/content/components
and updated the sling release documentation steps [1]

stefan

[1] http://sling.apache.org/documentation/development/release-management.html


>-Original Message-
>From: Konrad Windszus [mailto:konra...@gmx.de]
>Sent: Sunday, June 4, 2017 7:30 PM
>To: dev@sling.apache.org
>Subject: Re: Pending deletion of maven plugin docs?
>
>Most probably we just need to adjust the URL from
>https://svn.apache.org/repos/infra/websites/production/sling/content/compon
>ents/
>to
>https://svn.apache.org/repos/infra/websites/staging/sling/trunk/content/com
>ponents/
>
>> Am 04.06.2017 um 19:10 schrieb Konrad Windszus :
>>
>> The issue https://issues.apache.org/jira/browse/INFRA-13644 was just
>updated recently and obviously extpath is behaving differently than
>expected. The suggested workaround to instead publish to the staging area
>and still do a final manual publishing. This sounds reasonable to me but I
>am unsure on how to achieve that.
>> @Stefan: Would you be willing to look into that? In the best case only
>the URL needs to be adjusted and the documentation in
>http://sling.apache.org/documentation/development/release-
>management.html#appendix-d-deploy-maven-plugin-documentation-if-applicable.
>>
>>> Am 13.03.2017 um 12:49 schrieb Stefan Seifert :
>>>
>>> and the issue is only a "display issue" - the plugin docs are not
>deleted, you can safely publish changes on the site.
>>> but the publish diff view is unfortunately quite unusable currently.
>>>
>>> stefan
>>>
 -Original Message-
 From: Konrad Windszus [mailto:konra...@gmx.de]
 Sent: Monday, March 13, 2017 12:37 PM
 To: dev@sling.apache.org
 Subject: Re: Pending deletion of maven plugin docs?

 This was already raised in http://www.mail-
 archive.com/dev@sling.apache.org/msg65399.html.

 Subsequently Bertrand opened
>https://issues.apache.org/jira/browse/INFRA-
 13644.

> On 13 Mar 2017, at 12:35, Robert Munteanu  wrote:
>
> Hi,
>
> When trying to publish the latest version of the site from [1] I get a
> large number of deleted files from under content/components/htl-maven-
> plugin .
>
> Is that intended? I am going to hold on the publishing for now.
>
> Robert
>
> [1]: https://cms.apache.org/sling/publish?diff=1

>>>
>>>
>>
>

RE: [VOTE] Release JSPC Maven Plugin 2.1.0

[Stefan Seifert]

+1

i've also published the auto-generated plugin documentation as maven site [1]

stefan

[1] http://sling.apache.org/components/jspc-maven-plugin/

RE: [VOTE] Release Apache Sling Slingstart Archetype version 1.0.2

[Stefan Seifert]

+1

[jira] [Commented] (SLING-6422) Allow for specifying oak restrictions with repoinit

[Nitin Nizhawan (JIRA)]

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

Nitin Nizhawan commented on SLING-6422:
---

Hi [~bdelacretaz] That is an interesting point. IIUC, you mean that match 
should unordered like that for privileges. I could not find "unorderedness" of 
values in documentation and assumed them to be ordered since everywhere API is 
using an array to store these values.
So, current method implementation assumes that values are "ordered" but not 
sorted i.e. order of values is meaningful and preserved by underlying layer. 
You are correct that for OOTB restrictions like rep:ntNames and rep:itemNames 
the order of values does not matter. But we have written some custom 
restriction providers (based on same assumption) for which order of values does 
matter, so, if I make the match unordered (by either sorting or using a set) 
the those restriction providers would break. TBH, now even I am not too sure if 
orderedness assumption is valid.

CC: [~anchela]

> Allow for specifying oak restrictions with repoinit
> ---
>
> Key: SLING-6422
> URL: https://issues.apache.org/jira/browse/SLING-6422
> Project: Sling
>  Issue Type: New Feature
>  Components: Repoinit
>Reporter: Nitin Nizhawan
> Attachments: SLING6422ApplyRestrictionsV2.patch, 
> SLING6422ApplyRestrictionsV3.patch, 
> SLING6422_interpretparsedrestrictionclause.patch, SLING-6422.patch
>
>
> Allow for specifying oak restrictions with repoinit. Currently repoinit 
> allows one to ADD remove ACLs but there is no way to specify oak restrictions.
> http://jackrabbit.apache.org/oak/docs/security/authorization/restriction.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: composum upload does not update jcr:lastModified for files and images

[Robert Munteanu]

On Mon, 2017-06-12 at 18:44 +0300, Ioan Eugen Stan wrote:
> Hello Robert,
> 
> 
> Thanks for the suggestions. I got a reply on Composum github
> issues[1]
> 
> It seems Composum does not update related properties by default. If I
> change jcr:data via upload, only jcr:data is updated.
> 
> In the reply, it says it is fixed in Composum 1.8, just released. I
> did
> not check it.

Good to know, thanks for getting back on this.

Robert

> 
> 
> Regards,
> 
> [1] https://github.com/ist-dresden/composum/issues/84
> 
> 
> On 08.06.2017 11:48, Robert Munteanu wrote:
> > Hi Eugen,
> > 
> > On Thu, 2017-06-01 at 16:41 +0300, Ioan Eugen Stan wrote:
> > > Hello,
> > > 
> > > I have posted this issue on the composum issue tracker [0], but
> > > not
> > > sure
> > > where is the right place so I'm posting it here as well.
> > > 
> > > I'm using the latest sling-launchpad
> > > org.apache.sling.launchpad-9-20170531.170627-12089.jar with
> > > composum
> > > browser.
> > > 
> > > I use the browser to create a |nt:file| image
> > > |content/hello.png|. I
> > > can
> > > preview the image.
> > > After that I upload a new image by double clicking on the
> > > jcr:data
> > > and
> > > using the upload dialog there.
> > > 
> > > Using the preview button on |jcr:content| node, I can see the new
> > > image.
> > > Using preview on the |hello.png| file shows the old version.
> > > 
> > > Also, viewing the image on the public link displayes the old
> > > image as
> > > well [1]
> > > 
> > > One workaround is to manually change the |jcr:lastModified|
> > > property
> > > of
> > > the 'jcr:content' node.
> > > That way, the image is updated.
> > > 
> > > 
> > > The same thing happens with file updates as well. Editing a file
> > > via
> > > the
> > > composum web interface does not change the contents in the public
> > > link,
> > > unless you update the jcr:lastModified proeprty.
> > 
> > From your description this sounds like a composum issue. Out of
> > curiosity, do file uploads performed without composum exhibit the
> > same
> > issue?
> > 
> > Thanks,
> > 
> > Robert
> > 
> > > 
> > > [0] https://github.com/ist-dresden/composum/issues/84
> > > 
> > > [1] http://localhost:8080/content/hello.png
> > > 
> 
> 

[jira] [Commented] (SLING-6201) Deploy Sling 9 docker image to Docker Hub

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-6201:


Thanks for the tip, will use that.

> Deploy Sling 9 docker image to Docker Hub
> -
>
> Key: SLING-6201
> URL: https://issues.apache.org/jira/browse/SLING-6201
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>
> Note - we should switch to the apache account instead of the apachesling one.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-6201) Deploy Sling 9 docker image to Docker Hub

[Ioan Eugen Stan (JIRA)]

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

Ioan Eugen Stan commented on SLING-6201:


The Java image has been deprecated on docker hub. I imagine because Oracle JRE 
cannot be distributed without Oracle approval. 

Please use openjdk image instead: https://hub.docker.com/_/openjdk/
I recommend using "openjdk:jre-alpine" as it is much smaller (based on alpine 
linux) than the full one (based on ubuntu). 

Alpine Linux contains the kernel, busy-box, openjdk jre and sling app. 


> Deploy Sling 9 docker image to Docker Hub
> -
>
> Key: SLING-6201
> URL: https://issues.apache.org/jira/browse/SLING-6201
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>
> Note - we should switch to the apache account instead of the apachesling one.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: composum upload does not update jcr:lastModified for files and images

[Ioan Eugen Stan]

Hello Robert,


Thanks for the suggestions. I got a reply on Composum github issues[1]

It seems Composum does not update related properties by default. If I
change jcr:data via upload, only jcr:data is updated.

In the reply, it says it is fixed in Composum 1.8, just released. I did
not check it.


Regards,

[1] https://github.com/ist-dresden/composum/issues/84


On 08.06.2017 11:48, Robert Munteanu wrote:
> Hi Eugen,
>
> On Thu, 2017-06-01 at 16:41 +0300, Ioan Eugen Stan wrote:
>> Hello,
>>
>> I have posted this issue on the composum issue tracker [0], but not
>> sure
>> where is the right place so I'm posting it here as well.
>>
>> I'm using the latest sling-launchpad
>> org.apache.sling.launchpad-9-20170531.170627-12089.jar with composum
>> browser.
>>
>> I use the browser to create a |nt:file| image |content/hello.png|. I
>> can
>> preview the image.
>> After that I upload a new image by double clicking on the jcr:data
>> and
>> using the upload dialog there.
>>
>> Using the preview button on |jcr:content| node, I can see the new
>> image.
>> Using preview on the |hello.png| file shows the old version.
>>
>> Also, viewing the image on the public link displayes the old image as
>> well [1]
>>
>> One workaround is to manually change the |jcr:lastModified| property
>> of
>> the 'jcr:content' node.
>> That way, the image is updated.
>>
>>
>> The same thing happens with file updates as well. Editing a file via
>> the
>> composum web interface does not change the contents in the public
>> link,
>> unless you update the jcr:lastModified proeprty.
> From your description this sounds like a composum issue. Out of
> curiosity, do file uploads performed without composum exhibit the same
> issue?
>
> Thanks,
>
> Robert
>
>>
>> [0] https://github.com/ist-dresden/composum/issues/84
>>
>> [1] http://localhost:8080/content/hello.png
>>




signature.asc
Description: OpenPGP digital signature

[jira] [Commented] (SLING-6203) Create a Maven archetype for content packages

[Andreas Schaefer (JIRA)]

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

Andreas Schaefer commented on SLING-6203:
-

I create two archetypes (project / project-all) that create a project with 
content-package modules.

See ticket: https://issues.apache.org/jira/browse/SLING-6922

If you just want an archetype for a single content package then you can these 
as blueprints.

- Andy

> Create a Maven archetype for content packages
> -
>
> Key: SLING-6203
> URL: https://issues.apache.org/jira/browse/SLING-6203
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-6422) Allow for specifying oak restrictions with repoinit

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-6422:


[~nitin.nizhawan] the {{sameRestrictions}} method assumes the 
{{getRestrictions}} and {{getMVRestrictions}} methods return a sorted list of 
values - in the for loop that compares old and new values.

Is that ordering guaranteed? The javadocs [1] do not mention ordering.

If the Value array is not sorted I think you need a more robust comparison.

[1] 
https://jackrabbit.apache.org/api/2.8/org/apache/jackrabbit/api/security/JackrabbitAccessControlEntry.html#getRestrictions(java.lang.String)

> Allow for specifying oak restrictions with repoinit
> ---
>
> Key: SLING-6422
> URL: https://issues.apache.org/jira/browse/SLING-6422
> Project: Sling
>  Issue Type: New Feature
>  Components: Repoinit
>Reporter: Nitin Nizhawan
> Attachments: SLING6422ApplyRestrictionsV2.patch, 
> SLING6422ApplyRestrictionsV3.patch, 
> SLING6422_interpretparsedrestrictionclause.patch, SLING-6422.patch
>
>
> Allow for specifying oak restrictions with repoinit. Currently repoinit 
> allows one to ADD remove ACLs but there is no way to specify oak restrictions.
> http://jackrabbit.apache.org/oak/docs/security/authorization/restriction.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [VOTE] Release JSPC Maven Plugin 2.1.0

[Robert Munteanu]

On Mon, 2017-06-12 at 15:45 +0300, Carsten Ziegeler wrote:
> Please vote to approve this release:

+1

Robert


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

[jira] [Commented] (SLING-6422) Allow for specifying oak restrictions with repoinit

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-6422:


bq. ...i would have expected you to be able to review changes made to it and to 
care about it...

Yes. I'm giving you the opportunity to have a look before I commit this as you 
apparently reviewed previous versions of this code as per your 19/May/17 
comment above. 
Thanks for your review!

> Allow for specifying oak restrictions with repoinit
> ---
>
> Key: SLING-6422
> URL: https://issues.apache.org/jira/browse/SLING-6422
> Project: Sling
>  Issue Type: New Feature
>  Components: Repoinit
>Reporter: Nitin Nizhawan
> Attachments: SLING6422ApplyRestrictionsV2.patch, 
> SLING6422ApplyRestrictionsV3.patch, 
> SLING6422_interpretparsedrestrictionclause.patch, SLING-6422.patch
>
>
> Allow for specifying oak restrictions with repoinit. Currently repoinit 
> allows one to ADD remove ACLs but there is no way to specify oak restrictions.
> http://jackrabbit.apache.org/oak/docs/security/authorization/restriction.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-6422) Allow for specifying oak restrictions with repoinit

[angela (JIRA)]

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

angela commented on SLING-6422:
---

[~nitin.nizhawan], had a quick look and it didn't spot any major issues.
[~bdelacretaz]... the repo-init is your code not mine... i would have expected 
you to be able to review changes made to it and to care about it. 

> Allow for specifying oak restrictions with repoinit
> ---
>
> Key: SLING-6422
> URL: https://issues.apache.org/jira/browse/SLING-6422
> Project: Sling
>  Issue Type: New Feature
>  Components: Repoinit
>Reporter: Nitin Nizhawan
> Attachments: SLING6422ApplyRestrictionsV2.patch, 
> SLING6422ApplyRestrictionsV3.patch, 
> SLING6422_interpretparsedrestrictionclause.patch, SLING-6422.patch
>
>
> Allow for specifying oak restrictions with repoinit. Currently repoinit 
> allows one to ADD remove ACLs but there is no way to specify oak restrictions.
> http://jackrabbit.apache.org/oak/docs/security/authorization/restriction.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [VOTE] Release JSPC Maven Plugin 2.1.0

[Carsten Ziegeler]

+1

 

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

[jira] [Commented] (SLING-6422) Allow for specifying oak restrictions with repoinit

[Nitin Nizhawan (JIRA)]

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

Nitin Nizhawan commented on SLING-6422:
---

 [~anchela] Not an issue. I have raised a fresh PR 
https://github.com/apache/sling/pull/241  also link to original PR which you 
had reviewed
https://github.com/apache/sling/pull/232
CC: [~bdelacretaz]

Thanks
Nitin

> Allow for specifying oak restrictions with repoinit
> ---
>
> Key: SLING-6422
> URL: https://issues.apache.org/jira/browse/SLING-6422
> Project: Sling
>  Issue Type: New Feature
>  Components: Repoinit
>Reporter: Nitin Nizhawan
> Attachments: SLING6422ApplyRestrictionsV2.patch, 
> SLING6422ApplyRestrictionsV3.patch, 
> SLING6422_interpretparsedrestrictionclause.patch, SLING-6422.patch
>
>
> Allow for specifying oak restrictions with repoinit. Currently repoinit 
> allows one to ADD remove ACLs but there is no way to specify oak restrictions.
> http://jackrabbit.apache.org/oak/docs/security/authorization/restriction.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[VOTE] Release JSPC Maven Plugin 2.1.0

[Carsten Ziegeler]

Hi,

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

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

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 1741 /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.

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

[GitHub] sling pull request #241: SLING-6422, Allow for specifying oak restrictions w...

[nitin-nizhawan]

GitHub user nitin-nizhawan opened a pull request:

https://github.com/apache/sling/pull/241

SLING-6422, Allow for specifying oak restrictions with repoinit

   - Interpret parsed restriction clauses from repoinit

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nitin-nizhawan/sling 
nnizhawa/SLING_6422ApplyRestrictionsV3

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/sling/pull/241.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #241


commit 4aa930056d48655995629b9253edd1bd394f7ecb
Author: Nitin Nizhawan 
Date:   2017-05-16T11:01:56Z

SLING-6422, Allow for specifying oak restrictions with repoinit

   - Interpret parsed restriction clauses from repoinit




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (SLING-6422) Allow for specifying oak restrictions with repoinit

[ASF GitHub Bot (JIRA)]

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

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

GitHub user nitin-nizhawan opened a pull request:

https://github.com/apache/sling/pull/241

SLING-6422, Allow for specifying oak restrictions with repoinit

   - Interpret parsed restriction clauses from repoinit

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nitin-nizhawan/sling 
nnizhawa/SLING_6422ApplyRestrictionsV3

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/sling/pull/241.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #241


commit 4aa930056d48655995629b9253edd1bd394f7ecb
Author: Nitin Nizhawan 
Date:   2017-05-16T11:01:56Z

SLING-6422, Allow for specifying oak restrictions with repoinit

   - Interpret parsed restriction clauses from repoinit




> Allow for specifying oak restrictions with repoinit
> ---
>
> Key: SLING-6422
> URL: https://issues.apache.org/jira/browse/SLING-6422
> Project: Sling
>  Issue Type: New Feature
>  Components: Repoinit
>Reporter: Nitin Nizhawan
> Attachments: SLING6422ApplyRestrictionsV2.patch, 
> SLING6422ApplyRestrictionsV3.patch, 
> SLING6422_interpretparsedrestrictionclause.patch, SLING-6422.patch
>
>
> Allow for specifying oak restrictions with repoinit. Currently repoinit 
> allows one to ADD remove ACLs but there is no way to specify oak restrictions.
> http://jackrabbit.apache.org/oak/docs/security/authorization/restriction.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (SLING-6940) JSPC plugin violates Maven naming convention

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler resolved SLING-6940.
-
Resolution: Fixed
  Assignee: Carsten Ziegeler

Renamed to jspc-maven-plugin in rev 1798449 (Sling is already part of the group 
id)

> JSPC plugin violates Maven naming convention
> 
>
> Key: SLING-6940
> URL: https://issues.apache.org/jira/browse/SLING-6940
> Project: Sling
>  Issue Type: Bug
>  Components: Maven Plugins and Archetypes
>Affects Versions: Maven JSPC Plugin 2.0.8
>Reporter: Tobias Bocanegra
>Assignee: Carsten Ziegeler
> Fix For: Maven JSPC Plugin 2.1.0
>
>
> the current plugin name {{maven-jspc-plugin}} violates the maven plugin 
> convention, as it starts with "maven-":
> {noformat}
> [INFO] --- maven-plugin-plugin:3.4:helpmojo (help-goal) @ maven-jspc-plugin 
> ---
> [ERROR]
> Artifact Ids of the format maven-___-plugin are reserved for
> plugins in the Group Id org.apache.maven.plugins
> Please change your artifactId to the format ___-maven-plugin
> In the future this error will break the build.
> {noformat}
> Suggest to rename it to: {{sling-jspc-maven-plugin}}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-6422) Allow for specifying oak restrictions with repoinit

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-6422:


I can merge the patch but would prefer [~anchela] to have a look first as IIUC 
you reviewed it before.

> Allow for specifying oak restrictions with repoinit
> ---
>
> Key: SLING-6422
> URL: https://issues.apache.org/jira/browse/SLING-6422
> Project: Sling
>  Issue Type: New Feature
>  Components: Repoinit
>Reporter: Nitin Nizhawan
> Attachments: SLING6422ApplyRestrictionsV2.patch, 
> SLING6422ApplyRestrictionsV3.patch, 
> SLING6422_interpretparsedrestrictionclause.patch, SLING-6422.patch
>
>
> Allow for specifying oak restrictions with repoinit. Currently repoinit 
> allows one to ADD remove ACLs but there is no way to specify oak restrictions.
> http://jackrabbit.apache.org/oak/docs/security/authorization/restriction.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SLING-6940) JSPC plugin violates Maven naming convention

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler updated SLING-6940:

Fix Version/s: Maven JSPC Plugin 2.0.10

> JSPC plugin violates Maven naming convention
> 
>
> Key: SLING-6940
> URL: https://issues.apache.org/jira/browse/SLING-6940
> Project: Sling
>  Issue Type: Bug
>  Components: Maven Plugins and Archetypes
>Affects Versions: Maven JSPC Plugin 2.0.8
>Reporter: Tobias Bocanegra
> Fix For: Maven JSPC Plugin 2.0.10
>
>
> the current plugin name {{maven-jspc-plugin}} violates the maven plugin 
> convention, as it starts with "maven-":
> {noformat}
> [INFO] --- maven-plugin-plugin:3.4:helpmojo (help-goal) @ maven-jspc-plugin 
> ---
> [ERROR]
> Artifact Ids of the format maven-___-plugin are reserved for
> plugins in the Group Id org.apache.maven.plugins
> Please change your artifactId to the format ___-maven-plugin
> In the future this error will break the build.
> {noformat}
> Suggest to rename it to: {{sling-jspc-maven-plugin}}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-6422) Allow for specifying oak restrictions with repoinit

[angela (JIRA)]

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

angela commented on SLING-6422:
---

[~nitin.nizhawan], sorry... it lost the context in order to be able to properly 
review the v3 patch, can you send me a link to a github-commit, where it is 
easier to review for someone like me that is not the author of the original 
source? thanks. also i can't merge... you have to find someone else.

> Allow for specifying oak restrictions with repoinit
> ---
>
> Key: SLING-6422
> URL: https://issues.apache.org/jira/browse/SLING-6422
> Project: Sling
>  Issue Type: New Feature
>  Components: Repoinit
>Reporter: Nitin Nizhawan
> Attachments: SLING6422ApplyRestrictionsV2.patch, 
> SLING6422ApplyRestrictionsV3.patch, 
> SLING6422_interpretparsedrestrictionclause.patch, SLING-6422.patch
>
>
> Allow for specifying oak restrictions with repoinit. Currently repoinit 
> allows one to ADD remove ACLs but there is no way to specify oak restrictions.
> http://jackrabbit.apache.org/oak/docs/security/authorization/restriction.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SLING-6195) Initial release of the Content-Package Maven Plugin

[Robert Munteanu (JIRA)]

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

Robert Munteanu updated SLING-6195:
---
Parent Issue: SLING-6950  (was: SLING-6194)

> Initial release of the Content-Package Maven Plugin
> ---
>
> Key: SLING-6195
> URL: https://issues.apache.org/jira/browse/SLING-6195
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SLING-6203) Create a Maven archetype for content packages

[Robert Munteanu (JIRA)]

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

Robert Munteanu updated SLING-6203:
---
Parent Issue: SLING-6950  (was: SLING-6194)

> Create a Maven archetype for content packages
> -
>
> Key: SLING-6203
> URL: https://issues.apache.org/jira/browse/SLING-6203
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SLING-6196) Initial release of the content package support for the Installer

[Robert Munteanu (JIRA)]

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

Robert Munteanu updated SLING-6196:
---
Parent Issue: SLING-6950  (was: SLING-6194)

> Initial release of the content package support for the Installer
> 
>
> Key: SLING-6196
> URL: https://issues.apache.org/jira/browse/SLING-6196
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (SLING-6950) Support Content-Package based development

[Robert Munteanu (JIRA)]

Robert Munteanu created SLING-6950:
--

 Summary: Support Content-Package based development
 Key: SLING-6950
 URL: https://issues.apache.org/jira/browse/SLING-6950
 Project: Sling
  Issue Type: Bug
  Components: General
Reporter: Robert Munteanu
 Fix For: Launchpad Builder 10


Tracking task for supporting development based on Content Packages with Sling.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Sling 9 release notes - cross-check

[Robert Munteanu]

Good point, included.

Robert

On Mon, 2017-06-12 at 14:42 +0300, Carsten Ziegeler wrote:
> Lgtm, thanks Robert
> 
> We could mention the new slingshot sample
> 
> Regards
> Carsten
> 
> Robert Munteanu wrote
> > Hi,
> > 
> > Please cross-check the Sling 9 release notes at
> > 
> >   http://sling.apache.org/news/sling-launchpad-9-released.html
> > 
> > (these are public, but not yet linked to the front page or
> > announced )
> > 
> > If there's anything that I missed or that I wrote incorrectly
> > please
> > fix.
> > 
> > Thanks,
> > 
> > Robert
> > 
> 
> 
>  
> 

Re: Sling 9 release notes - cross-check

[Carsten Ziegeler]

Lgtm, thanks Robert

We could mention the new slingshot sample

Regards
Carsten

Robert Munteanu wrote
> Hi,
> 
> Please cross-check the Sling 9 release notes at
> 
>   http://sling.apache.org/news/sling-launchpad-9-released.html
> 
> (these are public, but not yet linked to the front page or announced )
> 
> If there's anything that I missed or that I wrote incorrectly please
> fix.
> 
> Thanks,
> 
> Robert
> 


 

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

Re: [VOTE] Release Apache Sling Slingstart Archetype version 1.0.2

[Carsten Ziegeler]

+1

 

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

Re: [VOTE] Release Apache Sling Slingstart Archetype version 1.0.2

[Robert Munteanu]

On Mon, 2017-06-12 at 14:13 +0300, Robert Munteanu wrote:
> Please vote to approve this release:

+1

Robert

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

Re: Sling 9 release notes - cross-check

[Robert Munteanu]

On Mon, 2017-06-12 at 13:13 +0200, Konrad Windszus wrote:
> There is a linebreak missing on the left-hand side navigation below
> API Docs between Sling 9 and Sling 8.
> Otherwise it looks good.

Fixed, thanks! I wondered the other lines had trailing whitespace. Now
I know :-)

Robert

> Konrad
> > On 12. Jun 2017, at 12:04, Robert Munteanu 
> > wrote:
> > 
> > Hi,
> > 
> > Please cross-check the Sling 9 release notes at
> > 
> >  http://sling.apache.org/news/sling-launchpad-9-released.html
> > 
> > (these are public, but not yet linked to the front page or
> > announced )
> > 
> > If there's anything that I missed or that I wrote incorrectly
> > please
> > fix.
> > 
> > Thanks,
> > 
> > Robert
> 
> 

[VOTE] Release Apache Sling Slingstart Archetype version 1.0.2

[Robert Munteanu]

Hi,

We solved 1 issue in this release:
https://issues.apache.org/jira/projects/SLING/versions/12333899

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

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 1740 /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.

Re: Sling 9 release notes - cross-check

[Konrad Windszus]

There is a linebreak missing on the left-hand side navigation below API Docs 
between Sling 9 and Sling 8.
Otherwise it looks good.
Konrad
> On 12. Jun 2017, at 12:04, Robert Munteanu  wrote:
> 
> Hi,
> 
> Please cross-check the Sling 9 release notes at
> 
>  http://sling.apache.org/news/sling-launchpad-9-released.html
> 
> (these are public, but not yet linked to the front page or announced )
> 
> If there's anything that I missed or that I wrote incorrectly please
> fix.
> 
> Thanks,
> 
> Robert

[jira] [Resolved] (SLING-6204) Use launchpad version 9 in the Maven archetypes

[Robert Munteanu (JIRA)]

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

Robert Munteanu resolved SLING-6204.

Resolution: Fixed

Fixed in [r1798436|https://svn.apache.org/r1798436]

> Use launchpad version 9 in the Maven archetypes
> ---
>
> Key: SLING-6204
> URL: https://issues.apache.org/jira/browse/SLING-6204
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SLING-6204) Use launchpad version 9 in the Maven archetypes

[Robert Munteanu (JIRA)]

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

Robert Munteanu updated SLING-6204:
---
Fix Version/s: Slingstart Archetype 1.0.2

> Use launchpad version 9 in the Maven archetypes
> ---
>
> Key: SLING-6204
> URL: https://issues.apache.org/jira/browse/SLING-6204
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Slingstart Archetype 1.0.2
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (SLING-6204) Use launchpad version 9 in the Maven archetypes

[Robert Munteanu (JIRA)]

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

Robert Munteanu reassigned SLING-6204:
--

Assignee: Robert Munteanu

> Use launchpad version 9 in the Maven archetypes
> ---
>
> Key: SLING-6204
> URL: https://issues.apache.org/jira/browse/SLING-6204
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Slingstart Archetype 1.0.2
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Sling 9 release notes - cross-check

[Robert Munteanu]

Hi,

Please cross-check the Sling 9 release notes at

  http://sling.apache.org/news/sling-launchpad-9-released.html

(these are public, but not yet linked to the front page or announced )

If there's anything that I missed or that I wrote incorrectly please
fix.

Thanks,

Robert

[jira] [Resolved] (SLING-6202) Create 'New and Noteworthy' page for Sling 9

[Robert Munteanu (JIRA)]

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

Robert Munteanu resolved SLING-6202.

Resolution: Fixed

Fixed in [r1798432|https://svn.apache.org/r1798432], 
[r1798433|https://svn.apache.org/r1798433].

> Create 'New and Noteworthy' page for Sling 9
> 
>
> Key: SLING-6202
> URL: https://issues.apache.org/jira/browse/SLING-6202
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>
> This should be similar to 
> http://sling.apache.org/news/sling-launchpad-8-released.html . Staging page 
> is at https://cwiki.apache.org/confluence/display/SLING/Sling+9+Release+Notes



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-6422) Allow for specifying oak restrictions with repoinit

[Nitin Nizhawan (JIRA)]

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

Nitin Nizhawan commented on SLING-6422:
---

[~bdelacretaz] [~anchela] Updated patch after resolving conflicts with latest 
code [^SLING6422ApplyRestrictionsV3.patch] . Could you please review and merge.

> Allow for specifying oak restrictions with repoinit
> ---
>
> Key: SLING-6422
> URL: https://issues.apache.org/jira/browse/SLING-6422
> Project: Sling
>  Issue Type: New Feature
>  Components: Repoinit
>Reporter: Nitin Nizhawan
> Attachments: SLING6422ApplyRestrictionsV2.patch, 
> SLING6422ApplyRestrictionsV3.patch, 
> SLING6422_interpretparsedrestrictionclause.patch, SLING-6422.patch
>
>
> Allow for specifying oak restrictions with repoinit. Currently repoinit 
> allows one to ADD remove ACLs but there is no way to specify oak restrictions.
> http://jackrabbit.apache.org/oak/docs/security/authorization/restriction.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SLING-6422) Allow for specifying oak restrictions with repoinit

[Nitin Nizhawan (JIRA)]

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

Nitin Nizhawan updated SLING-6422:
--
Attachment: SLING6422ApplyRestrictionsV3.patch

> Allow for specifying oak restrictions with repoinit
> ---
>
> Key: SLING-6422
> URL: https://issues.apache.org/jira/browse/SLING-6422
> Project: Sling
>  Issue Type: New Feature
>  Components: Repoinit
>Reporter: Nitin Nizhawan
> Attachments: SLING6422ApplyRestrictionsV2.patch, 
> SLING6422ApplyRestrictionsV3.patch, 
> SLING6422_interpretparsedrestrictionclause.patch, SLING-6422.patch
>
>
> Allow for specifying oak restrictions with repoinit. Currently repoinit 
> allows one to ADD remove ACLs but there is no way to specify oak restrictions.
> http://jackrabbit.apache.org/oak/docs/security/authorization/restriction.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SLING-5787) Modularise the Sightly script engine

[Radu Cotescu (JIRA)]

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

Radu Cotescu updated SLING-5787:

Labels: Sling-9-ReleaseNotes  (was: )

> Modularise the Sightly script engine
> 
>
> Key: SLING-5787
> URL: https://issues.apache.org/jira/browse/SLING-5787
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Affects Versions: Scripting Sightly Engine 1.0.18
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>  Labels: Sling-9-ReleaseNotes
> Fix For: Scripting HTL Engine 1.0.20, Scripting HTL Compiler 
> 1.0.0, Scripting HTL Java Compiler 1.0.0
>
>
> The Sightly script engine should be broken into three modules:
> # a Sightly frontend compiler that interprets Sightly scripts and produces an 
> Abstract Syntax Tree (AST)
> # a Sightly Java backend compiler that interprets the AST and produces Java 
> class files
> # a Compilable Script Engine that reuses the previous two modules



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Robert Munteanu (JIRA)]

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

Robert Munteanu reassigned SLING-6202:
--

Assignee: Robert Munteanu

> Create 'New and Noteworthy' page for Sling 9
> 
>
> Key: SLING-6202
> URL: https://issues.apache.org/jira/browse/SLING-6202
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>
> This should be similar to 
> http://sling.apache.org/news/sling-launchpad-8-released.html . Staging page 
> is at https://cwiki.apache.org/confluence/display/SLING/Sling+9+Release+Notes



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (SLING-6200) Deploy API documentation for Sling 9

[Robert Munteanu (JIRA)]

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

Robert Munteanu resolved SLING-6200.

Resolution: Fixed
  Assignee: Robert Munteanu

Deployed in [r1798428|https://svn.apache.org/r1798428]

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




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (SLING-6201) Deploy Sling 9 docker image to Docker Hub

[Robert Munteanu (JIRA)]

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

Robert Munteanu reassigned SLING-6201:
--

Assignee: Robert Munteanu

> Deploy Sling 9 docker image to Docker Hub
> -
>
> Key: SLING-6201
> URL: https://issues.apache.org/jira/browse/SLING-6201
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>
> Note - we should switch to the apache account instead of the apachesling one.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (SLING-6199) Update local launchpad references to 9 or 10-SNAPSHOT

[Robert Munteanu (JIRA)]

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

Robert Munteanu resolved SLING-6199.

Resolution: Fixed

No local references found to 9-SNAPSHOT

> Update local launchpad references to 9 or 10-SNAPSHOT
> -
>
> Key: SLING-6199
> URL: https://issues.apache.org/jira/browse/SLING-6199
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (SLING-6199) Update local launchpad references to 9 or 10-SNAPSHOT

[Robert Munteanu (JIRA)]

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

Robert Munteanu reassigned SLING-6199:
--

Assignee: Robert Munteanu

> Update local launchpad references to 9 or 10-SNAPSHOT
> -
>
> Key: SLING-6199
> URL: https://issues.apache.org/jira/browse/SLING-6199
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (SLING-6198) Deploy the Launchpad 9 artifact to the dist site and Maven central

[Robert Munteanu (JIRA)]

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

Robert Munteanu resolved SLING-6198.

Resolution: Fixed

> Deploy the Launchpad 9 artifact to the dist site and Maven central
> --
>
> Key: SLING-6198
> URL: https://issues.apache.org/jira/browse/SLING-6198
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (SLING-6198) Deploy the Launchpad 9 artifact to the dist site and Maven central

[Robert Munteanu (JIRA)]

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

Robert Munteanu reassigned SLING-6198:
--

Assignee: Robert Munteanu

> Deploy the Launchpad 9 artifact to the dist site and Maven central
> --
>
> Key: SLING-6198
> URL: https://issues.apache.org/jira/browse/SLING-6198
> Project: Sling
>  Issue Type: Sub-task
>  Components: General
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[RESULT][VOTE] Release Apache Sling Launchpad Application Builder 9, Apache Sling Launchpad Testing 9, Apache Sling Launchpad Testing WAR version 9, Apache Sling Launchpad Testing Fragment Bundle 2.0.

[Robert Munteanu]

Hi,

The vote has passed with the following result :

+1 (binding): Carsten Ziegeler, Karl Pauls, Daniel Klco, Robert
Munteanu

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