[jira] [Assigned] (SLING-5369) Update to JUnit 4.12

[Oliver Lietz (JIRA)]

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

Oliver Lietz reassigned SLING-5369:
---

Assignee: Oliver Lietz

> Update to JUnit 4.12
> 
>
> Key: SLING-5369
> URL: https://issues.apache.org/jira/browse/SLING-5369
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Affects Versions: Parent 25, JUnit Core 1.0.14
>Reporter: Thierry Ygé
>Assignee: Oliver Lietz
> Fix For: Parent 26, JUnit Core 1.0.16
>
>
> Currently JUnit Core is based on JUnit 4.11, in SLING-5352, some improvement 
> could benefit from the enhancement implemented  in JUnit 4.12 related to 
> possibility to combine both ClassRule and Rule annotation for a static field.
> That would be a great help to simplify the use case discussed in SLING-5352.
> simply update the version on the pom.xml would be sufficient.
> from  4.11
> {noformat}
> ...
> 
> 4.11
> 1.3
> 0.6.2.201302030002
> 
> ...
> {noformat}
> to 4.12
> {noformat}
> ...
> 
> 4.12
> 1.3
> 0.6.2.201302030002
> 
> ...
> {noformat}



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

Re: CI build for contrib

[Oliver Lietz]

On Thursday 10 December 2015 10:32:18 Oliver Lietz wrote:
[...]
> 
> Currently only Groovy-related integration tests fail.

fixed by moving groovy and gsp scripts to test in r1720154, 
https://svn.apache.org/r1720154

O.

[...]

[jira] [Commented] (SLING-5026) Allow to set multiple validation error messages in one Validator

[ASF GitHub Bot (JIRA)]

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

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

GitHub user kwin opened a pull request:

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

SLING-5026 improve validator error message



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

$ git pull https://github.com/kwin/sling 
SLING-5026-improve-validator-return-value

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

https://github.com/apache/sling/pull/117.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 #117


commit b5f37d029ab54c165929d89f5faa055e284c4d7e
Author: Konrad Windszus 
Date:   2015-12-15T16:48:43Z

SLING-5026 improve validator error message




> Allow to set multiple validation error messages in one Validator
> 
>
> Key: SLING-5026
> URL: https://issues.apache.org/jira/browse/SLING-5026
> Project: Sling
>  Issue Type: Improvement
>  Components: Validation
>Affects Versions: Validation 1.0.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Fix For: Validation 1.0.0
>
>
> Currently each {{Validator}} can only set one error message through the 
> String return value (SLING-4010). It should be possible for one 
> {{Validator.validate}} call to set multiple validation messages at once.
> Maybe the solution [~radu.cotescu] proposed in 
> https://issues.apache.org/jira/browse/SLING-4027?focusedCommentId=14219170=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14219170
>  can be used here to just pass the ValidationResult around.



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

[GitHub] sling pull request: SLING-5026 improve validator error message

[kwin]

GitHub user kwin opened a pull request:

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

SLING-5026 improve validator error message



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

$ git pull https://github.com/kwin/sling 
SLING-5026-improve-validator-return-value

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

https://github.com/apache/sling/pull/117.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 #117


commit b5f37d029ab54c165929d89f5faa055e284c4d7e
Author: Konrad Windszus 
Date:   2015-12-15T16:48:43Z

SLING-5026 improve validator error message




---
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] [Resolved] (SLING-5369) Update to JUnit 4.12

[Oliver Lietz (JIRA)]

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

Oliver Lietz resolved SLING-5369.
-
Resolution: Done

[r1720119|https://svn.apache.org/r1720119]
[r1720127|https://svn.apache.org/r1720127]


> Update to JUnit 4.12
> 
>
> Key: SLING-5369
> URL: https://issues.apache.org/jira/browse/SLING-5369
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Affects Versions: Parent 25, JUnit Core 1.0.14
>Reporter: Thierry Ygé
>Assignee: Oliver Lietz
> Fix For: Parent 26, JUnit Core 1.0.16
>
>
> Currently JUnit Core is based on JUnit 4.11, in SLING-5352, some improvement 
> could benefit from the enhancement implemented  in JUnit 4.12 related to 
> possibility to combine both ClassRule and Rule annotation for a static field.
> That would be a great help to simplify the use case discussed in SLING-5352.
> simply update the version on the pom.xml would be sufficient.
> from  4.11
> {noformat}
> ...
> 
> 4.11
> 1.3
> 0.6.2.201302030002
> 
> ...
> {noformat}
> to 4.12
> {noformat}
> ...
> 
> 4.12
> 1.3
> 0.6.2.201302030002
> 
> ...
> {noformat}



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

Re: snapshot deployment/build failure

[Oliver Lietz]

On Monday 14 December 2015 17:11:00 Robert Munteanu wrote:
> Hi Olli,

Hi Robert,
 
> On Mon, 2015-12-14 at 13:35 +0100, Oliver Lietz wrote:
> > hi,
> > 
> > another build failure caused by a SNAPSHOT dependency:
> > 
> > ERROR: Failed to parse POMs
> > java.io.IOException: remote file operation failed:
> >  at
> > hudson.remoting.Channel@55c16db1:jenkins-ubuntu-1404-4gb-437:
> > hudson.remoting.ProxyException:
> > hudson.maven.MavenModuleSetBuild$MavenExecutionException:
> > org.apache.maven.project.ProjectBuildingException: Some problems were
> > encountered while processing the POMs:
> > [FATAL] Non-resolvable parent POM: Could not find artifact
> > org.apache.sling:sling:pom:26-SNAPSHOT and 'parent.relativePath'
> > points at no
> > local POM @ line 24, column 11
> > 
> > I was under the impression that our snapshots are deployed to Nexus
> > automatically by a build job. This seems to be not the case right
> > now.
> 
> Deploying takes a long time on Jenkins so it's only done for the
> 'sling-trunk-1.7' job. IIRC the parent is not part of that.

would it help speeding up if we break the contrib build into smaller ones?
Nevertheless we should have a job with deployment to Nexus for parent, no?

Thanks,
O.

> Robert

Re: [VOTE] Release Apache Sling Scripting Java 2.0.14

[Carsten Ziegeler]

+1


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

[jira] [Commented] (SLING-5375) RMI doesn't work in Sling-8

[Christoph Thodte (JIRA)]

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

Christoph Thodte commented on SLING-5375:
-

Saving means i open system/console then i choose configuration. There i open 
the rmi config and push the button save.

In sling 7 was this step nescessary to Start rmi access to repo  initial

> RMI doesn't work in Sling-8
> ---
>
> Key: SLING-5375
> URL: https://issues.apache.org/jira/browse/SLING-5375
> Project: Sling
>  Issue Type: Bug
>Reporter: Christoph Thodte
>
> when I save the RMI configuration in sling 8 the rmi port 1099 starts 
> listening. now in sling 8 it doesn't work. I see the following error in 
> console 
> "registerRepositroy: Repository not to bew registrated - Service 464 has no 
> name property, nothing to unregister"
> When I look for 464 in my instance I find the following service:
> [org.apache.sling.jcr.api.SlingRepository, javax.jcr.Repository]
> What's wrong? Is there a configuration missing? Is it a bug? Do you can fix 
> it? 



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

[jira] [Commented] (SLING-5375) RMI doesn't work in Sling-8

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-5375:


Please indicate exactly what "save the RMI configuration" means so that we can 
reproduce your issue.

> RMI doesn't work in Sling-8
> ---
>
> Key: SLING-5375
> URL: https://issues.apache.org/jira/browse/SLING-5375
> Project: Sling
>  Issue Type: Bug
>Reporter: Christoph Thodte
>
> when I save the RMI configuration in sling 8 the rmi port 1099 starts 
> listening. now in sling 8 it doesn't work. I see the following error in 
> console 
> "registerRepositroy: Repository not to bew registrated - Service 464 has no 
> name property, nothing to unregister"
> When I look for 464 in my instance I find the following service:
> [org.apache.sling.jcr.api.SlingRepository, javax.jcr.Repository]
> What's wrong? Is there a configuration missing? Is it a bug? Do you can fix 
> it? 



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

[jira] [Commented] (SLING-5375) RMI doesn't work in Sling-8

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-5375:


Thanks - which is " the rmi config"?  The OSGi console will use an URL like 
http://localhost:4502/system/console/configMgr/PATH , we need to know what PATH 
is, just to make sure there's no confusion.

> RMI doesn't work in Sling-8
> ---
>
> Key: SLING-5375
> URL: https://issues.apache.org/jira/browse/SLING-5375
> Project: Sling
>  Issue Type: Bug
>Reporter: Christoph Thodte
>
> when I save the RMI configuration in sling 8 the rmi port 1099 starts 
> listening. now in sling 8 it doesn't work. I see the following error in 
> console 
> "registerRepositroy: Repository not to bew registrated - Service 464 has no 
> name property, nothing to unregister"
> When I look for 464 in my instance I find the following service:
> [org.apache.sling.jcr.api.SlingRepository, javax.jcr.Repository]
> What's wrong? Is there a configuration missing? Is it a bug? Do you can fix 
> it? 



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

Re: [RESULT] [VOTE] Release Apache Sling Commons Scheduler version 2.4.12

[Julian Sedding]

Thanks Carsten!

On Tue, Dec 15, 2015 at 8:48 AM, Carsten Ziegeler  wrote:
> Julian Sedding wrote
>> Hi,
>>
>> The vote has passed with the following result :
>>
>> +1 (binding): Daniel Klco, Carsten Ziegeler, Stefan Seifert
>> +1 (non binding): Julian Sedding
>>
>> Thanks for voting.
>>
>> I will promote the artifacts to the central Maven repository and
>> update the news page.
>>
>> @any PMC member: please copy this release to the Sling dist directory.
>>
> Done
>
> Carsten
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org

[jira] [Commented] (SLING-5375) RMI doesn't work in Sling-8

[Christoph Thodte (JIRA)]

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

Christoph Thodte commented on SLING-5375:
-

Sorry I can't build. I'n no developer of sling :-)

I want to use it in my application :-)

But what you write sounds like the problem.

> RMI doesn't work in Sling-8
> ---
>
> Key: SLING-5375
> URL: https://issues.apache.org/jira/browse/SLING-5375
> Project: Sling
>  Issue Type: Bug
>Reporter: Christoph Thodte
>
> when I save the RMI configuration in sling 8 the rmi port 1099 starts 
> listening. now in sling 8 it doesn't work. I see the following error in 
> console 
> "registerRepositroy: Repository not to bew registrated - Service 464 has no 
> name property, nothing to unregister"
> When I look for 464 in my instance I find the following service:
> [org.apache.sling.jcr.api.SlingRepository, javax.jcr.Repository]
> What's wrong? Is there a configuration missing? Is it a bug? Do you can fix 
> it? 



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

[jira] [Commented] (SLING-5375) RMI doesn't work in Sling-8

[Christoph Thodte (JIRA)]

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

Christoph Thodte commented on SLING-5375:
-

Sorry I can't build. I'n no developer of sling :-)

I want to use it in my application :-)

But what you write sounds like the problem.

> RMI doesn't work in Sling-8
> ---
>
> Key: SLING-5375
> URL: https://issues.apache.org/jira/browse/SLING-5375
> Project: Sling
>  Issue Type: Bug
>Reporter: Christoph Thodte
>
> when I save the RMI configuration in sling 8 the rmi port 1099 starts 
> listening. now in sling 8 it doesn't work. I see the following error in 
> console 
> "registerRepositroy: Repository not to bew registrated - Service 464 has no 
> name property, nothing to unregister"
> When I look for 464 in my instance I find the following service:
> [org.apache.sling.jcr.api.SlingRepository, javax.jcr.Repository]
> What's wrong? Is there a configuration missing? Is it a bug? Do you can fix 
> it? 



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

RE: [VOTE] Release Apache Sling Scripting Java 2.0.14

[Stefan Seifert]

+1

>-Original Message-
>From: Oliver Lietz [mailto:apa...@oliverlietz.de]
>Sent: Tuesday, December 15, 2015 12:02 AM
>To: dev@sling.apache.org
>Subject: [VOTE] Release Apache Sling Scripting Java 2.0.14
>
>Hi,
>
>we solved 2 issues in this release:
>https://issues.apache.org/jira/browse/SLING/fixforversion/12328674
>
>Staging repository:
>https://repository.apache.org/content/repositories/orgapachesling-1384/
>
>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 1384 /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,
>O.

[jira] [Commented] (SLING-5375) RMI doesn't work in Sling-8

[Oliver Lietz (JIRA)]

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

Oliver Lietz commented on SLING-5375:
-

[~bdelacretaz], I looked at the sources and I think the {{name}} property is 
missing from {{OakSlingRepositoryManager}}. {{SlingServerRepositoryManager}} 
has:

{noformat}
@Property(value = "")
public static final String REPOSITORY_REGISTRATION_NAME = "name";
{noformat}

[~thodte], can you add this property to {{OakSlingRepositoryManager}}, rebuild 
{{oak-server}} and check if it works for you?

> RMI doesn't work in Sling-8
> ---
>
> Key: SLING-5375
> URL: https://issues.apache.org/jira/browse/SLING-5375
> Project: Sling
>  Issue Type: Bug
>Reporter: Christoph Thodte
>
> when I save the RMI configuration in sling 8 the rmi port 1099 starts 
> listening. now in sling 8 it doesn't work. I see the following error in 
> console 
> "registerRepositroy: Repository not to bew registrated - Service 464 has no 
> name property, nothing to unregister"
> When I look for 464 in my instance I find the following service:
> [org.apache.sling.jcr.api.SlingRepository, javax.jcr.Repository]
> What's wrong? Is there a configuration missing? Is it a bug? Do you can fix 
> it? 



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

Re: [VOTE] Release Apache Sling Scripting Java 2.0.14

[Julian Sedding]

+1 (non binding)

Regards
Julian


On Tue, Dec 15, 2015 at 9:40 AM, Stefan Seifert  wrote:
> +1
>
>>-Original Message-
>>From: Oliver Lietz [mailto:apa...@oliverlietz.de]
>>Sent: Tuesday, December 15, 2015 12:02 AM
>>To: dev@sling.apache.org
>>Subject: [VOTE] Release Apache Sling Scripting Java 2.0.14
>>
>>Hi,
>>
>>we solved 2 issues in this release:
>>https://issues.apache.org/jira/browse/SLING/fixforversion/12328674
>>
>>Staging repository:
>>https://repository.apache.org/content/repositories/orgapachesling-1384/
>>
>>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 1384 /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,
>>O.
>

[VOTE] Release Apache Sling Content Distribution Core version 0.1.12 and Distribution API 0.3.0

[Marius Petria]

Hi,


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



There are still some outstanding issues:
https://issues.apache.org/jira/browse/SLING/component/12323405

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

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 1385 /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,
Marius

[jira] [Commented] (SLING-5369) Update to JUnit 4.12

[Oliver Lietz (JIRA)]

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

Oliver Lietz commented on SLING-5369:
-

[~bdelacretaz], [~joelrich] asked for releasing Commons Testing (SLING-5341). I 
think we should keep the version of JUnit across Sling in sync, which means 
updating {{parent}} to {{4.12}} also before doing a release of Commons Testing. 
Is updating to {{4.12}} ok? Btw, the embedded JUnit causes havoc when running 
Lauchpad ITs against Karaf (SLING-3821), see 
[PAXEXAM-723|https://ops4j1.jira.com/browse/PAXEXAM-723].

> Update to JUnit 4.12
> 
>
> Key: SLING-5369
> URL: https://issues.apache.org/jira/browse/SLING-5369
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Affects Versions: JUnit Core 1.0.14
>Reporter: Thierry Ygé
>
> Currently JUnit Core is based on JUnit 4.11, in SLING-5352, some improvement 
> could benefit from the enhancement implemented  in JUnit 4.12 related to 
> possibility to combine both ClassRule and Rule annotation for a static field.
> That would be a great help to simplify the use case discussed in SLING-5352.
> simply update the version on the pom.xml would be sufficient.
> from  4.11
> {noformat}
> ...
> 
> 4.11
> 1.3
> 0.6.2.201302030002
> 
> ...
> {noformat}
> to 4.12
> {noformat}
> ...
> 
> 4.12
> 1.3
> 0.6.2.201302030002
> 
> ...
> {noformat}



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

Re: [VOTE] Release Apache Sling Scripting Java 2.0.14

[David Bosschaert]

+1 (non-binding)

David

On 14 December 2015 at 23:02, Oliver Lietz  wrote:
> Hi,
>
> we solved 2 issues in this release:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12328674
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1384/
>
> 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 1384 /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,
> O.
>

[jira] [Commented] (SLING-5369) Update to JUnit 4.12

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-5369:


JUnit 4.12 should be ok, if the full build including integration tests passes 
we're good.

I haven't found time to look at SLING-3821 yet.

> Update to JUnit 4.12
> 
>
> Key: SLING-5369
> URL: https://issues.apache.org/jira/browse/SLING-5369
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Affects Versions: JUnit Core 1.0.14
>Reporter: Thierry Ygé
>
> Currently JUnit Core is based on JUnit 4.11, in SLING-5352, some improvement 
> could benefit from the enhancement implemented  in JUnit 4.12 related to 
> possibility to combine both ClassRule and Rule annotation for a static field.
> That would be a great help to simplify the use case discussed in SLING-5352.
> simply update the version on the pom.xml would be sufficient.
> from  4.11
> {noformat}
> ...
> 
> 4.11
> 1.3
> 0.6.2.201302030002
> 
> ...
> {noformat}
> to 4.12
> {noformat}
> ...
> 
> 4.12
> 1.3
> 0.6.2.201302030002
> 
> ...
> {noformat}



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

[jira] [Updated] (SLING-5369) Update to JUnit 4.12

[Oliver Lietz (JIRA)]

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

Oliver Lietz updated SLING-5369:

Fix Version/s: JUnit Core 1.0.16
   Parent 26

> Update to JUnit 4.12
> 
>
> Key: SLING-5369
> URL: https://issues.apache.org/jira/browse/SLING-5369
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Affects Versions: Parent 25, JUnit Core 1.0.14
>Reporter: Thierry Ygé
> Fix For: Parent 26, JUnit Core 1.0.16
>
>
> Currently JUnit Core is based on JUnit 4.11, in SLING-5352, some improvement 
> could benefit from the enhancement implemented  in JUnit 4.12 related to 
> possibility to combine both ClassRule and Rule annotation for a static field.
> That would be a great help to simplify the use case discussed in SLING-5352.
> simply update the version on the pom.xml would be sufficient.
> from  4.11
> {noformat}
> ...
> 
> 4.11
> 1.3
> 0.6.2.201302030002
> 
> ...
> {noformat}
> to 4.12
> {noformat}
> ...
> 
> 4.12
> 1.3
> 0.6.2.201302030002
> 
> ...
> {noformat}



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

[jira] [Resolved] (SLING-5300) Set defaults for distribution components target references

[Marius Petria (JIRA)]

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

Marius Petria resolved SLING-5300.
--
   Resolution: Fixed
Fix Version/s: Content Distribution Core 0.1.12

Fixed in 
https://github.com/apache/sling/commit/24d08d99db232e2d76431083fdd3feecf6ea2cc2

> Set defaults for distribution components target references
> --
>
> Key: SLING-5300
> URL: https://issues.apache.org/jira/browse/SLING-5300
> Project: Sling
>  Issue Type: Improvement
>  Components: Distribution
>Reporter: Marius Petria
>Assignee: Marius Petria
> Fix For: Content Distribution Core 0.1.12
>
>




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

[jira] [Updated] (SLING-4979) org.apache.sling.commons.testing.jcr.RepositoryUtil should allow to instantiate a SlingRepository where loginService is supported

[Oliver Lietz (JIRA)]

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

Oliver Lietz updated SLING-4979:

Fix Version/s: (was: Commons Testing 2.0.24)

> org.apache.sling.commons.testing.jcr.RepositoryUtil should allow to 
> instantiate a SlingRepository where loginService is supported
> -
>
> Key: SLING-4979
> URL: https://issues.apache.org/jira/browse/SLING-4979
> Project: Sling
>  Issue Type: Wish
>  Components: Commons
>Affects Versions: Commons Testing 2.0.18
>Reporter: Tommaso Teofili
>
> When using _org.apache.sling.commons.testing_ (2.0.18) and trying to call 
> loginService on the returned {{SlingRepository}} results in an exception as 
> the API has not been updated to support such kind of calls, while it'd be 
> nice to be able also to test a class (e.g. a service) using _loginService_ to 
> authenticate.
> However I understand that it might be complicated to inject which services 
> can do what, or at least it may be not too useful as the candidate test 
> classes wanting to use such a repository would use services according to how 
> mappings have been defined... Maybe we could offer 1 or 2 services that are 
> enabled (admin / anonymous like).



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

[jira] [Updated] (SLING-4979) org.apache.sling.commons.testing.jcr.RepositoryUtil should allow to instantiate a SlingRepository where loginService is supported

[Oliver Lietz (JIRA)]

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

Oliver Lietz updated SLING-4979:

Summary: org.apache.sling.commons.testing.jcr.RepositoryUtil should allow 
to instantiate a SlingRepository where loginService is supported  (was: 
commons.testing.util.RepositoryUtil should allow to instantiate a 
SlingRepository where loginService is supported)

> org.apache.sling.commons.testing.jcr.RepositoryUtil should allow to 
> instantiate a SlingRepository where loginService is supported
> -
>
> Key: SLING-4979
> URL: https://issues.apache.org/jira/browse/SLING-4979
> Project: Sling
>  Issue Type: Wish
>  Components: Commons
>Affects Versions: Commons Testing 2.0.18
>Reporter: Tommaso Teofili
> Fix For: Commons Testing 2.0.24
>
>
> When using _org.apache.sling.commons.testing_ (2.0.18) and trying to call 
> loginService on the returned {{SlingRepository}} results in an exception as 
> the API has not been updated to support such kind of calls, while it'd be 
> nice to be able also to test a class (e.g. a service) using _loginService_ to 
> authenticate.
> However I understand that it might be complicated to inject which services 
> can do what, or at least it may be not too useful as the candidate test 
> classes wanting to use such a repository would use services according to how 
> mappings have been defined... Maybe we could offer 1 or 2 services that are 
> enabled (admin / anonymous like).



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

[jira] [Resolved] (SLING-4979) org.apache.sling.commons.testing.jcr.RepositoryUtil should allow to instantiate a SlingRepository where loginService is supported

[Oliver Lietz (JIRA)]

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

Oliver Lietz resolved SLING-4979.
-
Resolution: Won't Fix

{{RepositoryUtil}} is Jackrabbit only (which is no longer supported in Sling) 
and we have now JCR mocks

> org.apache.sling.commons.testing.jcr.RepositoryUtil should allow to 
> instantiate a SlingRepository where loginService is supported
> -
>
> Key: SLING-4979
> URL: https://issues.apache.org/jira/browse/SLING-4979
> Project: Sling
>  Issue Type: Wish
>  Components: Commons
>Affects Versions: Commons Testing 2.0.18
>Reporter: Tommaso Teofili
>
> When using _org.apache.sling.commons.testing_ (2.0.18) and trying to call 
> loginService on the returned {{SlingRepository}} results in an exception as 
> the API has not been updated to support such kind of calls, while it'd be 
> nice to be able also to test a class (e.g. a service) using _loginService_ to 
> authenticate.
> However I understand that it might be complicated to inject which services 
> can do what, or at least it may be not too useful as the candidate test 
> classes wanting to use such a repository would use services according to how 
> mappings have been defined... Maybe we could offer 1 or 2 services that are 
> enabled (admin / anonymous like).



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

Re: Need a solution to install content with the teleported test

[Julian Sedding]

Hi Bertrand

Thinking about this a little more, I wondered whether lambda
expressions would be a good fit? The usage could look something like
this:

builderService
.forResource("/")
.resource("foo/c/d", d -> {
d.resource("a", a -> a.resource("b/c"));
d.resource("b");
d.resource("c");
})
.resource("bar/a/b") // bar is a sibling of foo

The signature ".resource(path, lambda)" would not change the parent
context of the underlying builder. Thus chaining calls would result in
sibling resources.

WDYT?

Regards
Julian



On Mon, Dec 14, 2015 at 7:13 PM, Peter Hunsberger
 wrote:
> I'm new enough to this that I'm not sure my expectations count, but that
> seems pretty good.
>
> In theory there would be a version that mixes concerns a little but makes
> the syntax a little simpler.  Something like:
>
> resourceHandler  rh = resourceResolver,getHandler("/apps");
> rh2 = rh.resource("1/2").resource("3/4");// yields 1/2/3/4
> rh2.resource("5/6"); // yields 1/2/3/4/5/6
> rh2.resource("7/8"); // builds 1/2/3/4/7/8
>
> I suspect this pattern would require multiple inheritance to avoid massive
> refactoring so it's likely best left for the day you rewrite Sling in Scala
> (you're going to do that right ? )
>
> I'm running away now.
>
>
>
> Peter Hunsberger
>
> On Mon, Dec 14, 2015 at 7:31 AM, Bertrand Delacretaz > wrote:
>
>> Hi,
>>
>> On Sat, Dec 12, 2015 at 5:47 PM, Peter Hunsberger
>>  wrote:
>> > ...I see. I had assumed a more functional style with the state travelling
>> > with the return value, that then get's chained to the next call
>>
>> I have modified the ResourceBuilder interface to work in this way, so
>> you can now do
>>
>>   final Resource r = resourceResolver.getResource("/apps");
>>   builderService.forParent(r).resource("1/2);
>>   builderService.forParent(r).resource("3/4");
>>
>> To create both /apps/1/2 and /apps/3/4.
>>
>> Basically you need to use either forResolver(ResourceResolver r) or
>> forParent(Resource r) on the ResourceBuilder service to get a stateful
>> ResourceBuilder, where you can then chain calls but not call the for*
>> methods again.
>>
>> Is that closer to what you expected, or do you have a better idea?
>>
>> -Bertrand
>>

[jira] [Resolved] (SLING-5346) Clarify distribution queue statuses

[Marius Petria (JIRA)]

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

Marius Petria resolved SLING-5346.
--
   Resolution: Fixed
Fix Version/s: Content Distribution Core 0.1.12

https://github.com/apache/sling/commit/3a8e93e3a4e2526c2a111e31faa4adfa19b0d756

> Clarify distribution queue statuses
> ---
>
> Key: SLING-5346
> URL: https://issues.apache.org/jira/browse/SLING-5346
> Project: Sling
>  Issue Type: Bug
>  Components: Distribution
>Reporter: Marius Petria
>Assignee: Marius Petria
> Fix For: Content Distribution Core 0.1.12
>
>
> A distribution queue can be passive or active. Passive is when it does not 
> have an associated processing action, and active when it does (for eg. 
> delivery to an endpoint).
> An active queue can be in three states: Idle, Running, Blocked or Paused.



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

[jira] [Resolved] (SLING-5295) Use slingRepository.impersonateFromService to impersonate distribution user

[Marius Petria (JIRA)]

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

Marius Petria resolved SLING-5295.
--
   Resolution: Fixed
 Assignee: Marius Petria
Fix Version/s: Content Distribution Core 0.1.12

https://github.com/apache/sling/commit/283ee95c4221f37ae1b6460d91a2fecbb1dd29da#diff-f1ccda7fd026b49181e4c246e7dd6047

> Use slingRepository.impersonateFromService to impersonate distribution user
> ---
>
> Key: SLING-5295
> URL: https://issues.apache.org/jira/browse/SLING-5295
> Project: Sling
>  Issue Type: Bug
>  Components: Distribution
>Reporter: Marius Petria
>Assignee: Marius Petria
> Fix For: Content Distribution Core 0.1.12
>
>




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

[jira] [Updated] (SLING-5369) Update to JUnit 4.12

[Oliver Lietz (JIRA)]

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

Oliver Lietz updated SLING-5369:

Affects Version/s: Parent 25

> Update to JUnit 4.12
> 
>
> Key: SLING-5369
> URL: https://issues.apache.org/jira/browse/SLING-5369
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Affects Versions: Parent 25, JUnit Core 1.0.14
>Reporter: Thierry Ygé
>
> Currently JUnit Core is based on JUnit 4.11, in SLING-5352, some improvement 
> could benefit from the enhancement implemented  in JUnit 4.12 related to 
> possibility to combine both ClassRule and Rule annotation for a static field.
> That would be a great help to simplify the use case discussed in SLING-5352.
> simply update the version on the pom.xml would be sufficient.
> from  4.11
> {noformat}
> ...
> 
> 4.11
> 1.3
> 0.6.2.201302030002
> 
> ...
> {noformat}
> to 4.12
> {noformat}
> ...
> 
> 4.12
> 1.3
> 0.6.2.201302030002
> 
> ...
> {noformat}



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

[jira] [Created] (SLING-5378) Use version of Groovy in GSPScriptEngineFactory for language version

[Oliver Lietz (JIRA)]

Oliver Lietz created SLING-5378:
---

 Summary: Use version of Groovy in GSPScriptEngineFactory for 
language version
 Key: SLING-5378
 URL: https://issues.apache.org/jira/browse/SLING-5378
 Project: Sling
  Issue Type: Improvement
  Components: Scripting
Affects Versions: Scripting Groovy 1.0.0
Reporter: Oliver Lietz
Assignee: Oliver Lietz
 Fix For: Scripting Groovy 1.0.2


return {{ReleaseInfo.getVersion()}} instead of {{1.0}}



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

[jira] [Resolved] (SLING-5378) Use version of Groovy in GSPScriptEngineFactory for language version

[Oliver Lietz (JIRA)]

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

Oliver Lietz resolved SLING-5378.
-
Resolution: Done

[r1720287|https://svn.apache.org/r1720287]

> Use version of Groovy in GSPScriptEngineFactory for language version
> 
>
> Key: SLING-5378
> URL: https://issues.apache.org/jira/browse/SLING-5378
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Affects Versions: Scripting Groovy 1.0.0
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Scripting Groovy 1.0.2
>
>
> return {{ReleaseInfo.getVersion()}} instead of {{1.0}}



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

Re: [VOTE] Release Apache Sling Content Distribution Core version 0.1.12 and Distribution API 0.3.0

[Carsten Ziegeler]

+1


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

[jira] [Created] (SLING-5377) Update Groovy to 2.4.5

[Oliver Lietz (JIRA)]

Oliver Lietz created SLING-5377:
---

 Summary: Update Groovy to 2.4.5
 Key: SLING-5377
 URL: https://issues.apache.org/jira/browse/SLING-5377
 Project: Sling
  Issue Type: Task
  Components: Scripting
Affects Versions: Scripting Groovy 1.0.0
Reporter: Oliver Lietz
Assignee: Oliver Lietz
 Fix For: Scripting Groovy 1.0.2


use {{groovy}}, {{groovy-json}}, {{groovy-templates}} and {{groovy-xml}} 
instead of {{groovy-all}}



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

[jira] [Resolved] (SLING-5377) Update Groovy to 2.4.5

[Oliver Lietz (JIRA)]

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

Oliver Lietz resolved SLING-5377.
-
Resolution: Done

[r1720149|https://svn.apache.org/r1720149]

> Update Groovy to 2.4.5
> --
>
> Key: SLING-5377
> URL: https://issues.apache.org/jira/browse/SLING-5377
> Project: Sling
>  Issue Type: Task
>  Components: Scripting
>Affects Versions: Scripting Groovy 1.0.0
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Scripting Groovy 1.0.2
>
>
> use {{groovy}}, {{groovy-json}}, {{groovy-templates}} and {{groovy-xml}} 
> instead of {{groovy-all}}



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

[jira] [Updated] (SLING-5362) [ext][sling pipes] default output should be truncated

[Nicolas Peltier (JIRA)]

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

Nicolas Peltier updated SLING-5362:
---
Priority: Major  (was: Minor)

> [ext][sling pipes] default output should be truncated
> -
>
> Key: SLING-5362
> URL: https://issues.apache.org/jira/browse/SLING-5362
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Nicolas Peltier
> Attachments: SLING-5362.patch
>
>
> default output is the paths of modified resources, which tends to be far too 
> big as soon as you do lot of changes, should be truncated / paginated by 
> default.
> This issue had been fixed already between initial donation and final commit. 
> Will attach the patch to this ticket



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

[jira] [Commented] (SLING-5362) [ext][sling pipes] default output should be truncated

[Nicolas Peltier (JIRA)]

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

Nicolas Peltier commented on SLING-5362:


setting to major as in the context of the tool it's important

> [ext][sling pipes] default output should be truncated
> -
>
> Key: SLING-5362
> URL: https://issues.apache.org/jira/browse/SLING-5362
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Nicolas Peltier
> Attachments: SLING-5362.patch
>
>
> default output is the paths of modified resources, which tends to be far too 
> big as soon as you do lot of changes, should be truncated / paginated by 
> default.
> This issue had been fixed already between initial donation and final commit. 
> Will attach the patch to this ticket



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

[jira] [Updated] (SLING-5361) [ext][sling pipes] plain string expressions shouldn't be evaluated

[Nicolas Peltier (JIRA)]

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

Nicolas Peltier updated SLING-5361:
---
Priority: Major  (was: Minor)

> [ext][sling pipes] plain string expressions shouldn't be evaluated
> --
>
> Key: SLING-5361
> URL: https://issues.apache.org/jira/browse/SLING-5361
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Nicolas Peltier
> Attachments: issue10.patch
>
>
> when adding simple string expressions to a sling pipe, there are ERROR 
> messages at execution mentionning the generated expression is not evaluated 
> correctly. JS Engine shouldn't be called in the first place. This has been 
> fixed between initial donation and effective commit (see [0]). 
> will attach a patch with failing test & fix.
> [0] https://github.com/npeltier/sling-pipes/issues/10



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

[jira] [Commented] (SLING-5361) [ext][sling pipes] plain string expressions shouldn't be evaluated

[Nicolas Peltier (JIRA)]

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

Nicolas Peltier commented on SLING-5361:


setting to major so the issue is not filtered out :-), guess it's important in 
the context of the tool

> [ext][sling pipes] plain string expressions shouldn't be evaluated
> --
>
> Key: SLING-5361
> URL: https://issues.apache.org/jira/browse/SLING-5361
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Nicolas Peltier
> Attachments: issue10.patch
>
>
> when adding simple string expressions to a sling pipe, there are ERROR 
> messages at execution mentionning the generated expression is not evaluated 
> correctly. JS Engine shouldn't be called in the first place. This has been 
> fixed between initial donation and effective commit (see [0]). 
> will attach a patch with failing test & fix.
> [0] https://github.com/npeltier/sling-pipes/issues/10



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

Re: [VOTE] Release Apache Sling Content Distribution Core version 0.1.12 and Distribution API 0.3.0

[Daniel Klco]

+1

On Tue, Dec 15, 2015 at 7:43 AM, Carsten Ziegeler 
wrote:

> +1
>
>
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>