[jira] [Commented] (SLING-6935) Context-Aware web console default experience difficult

2017-09-22 Thread Alexander Klimetschek (JIRA) 

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

Alexander Klimetschek commented on SLING-6935:
--

Thanks!

> Context-Aware web console default experience difficult
> --
>
> Key: SLING-6935
> URL: https://issues.apache.org/jira/browse/SLING-6935
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Context-Aware Configuration Impl 1.4.2
>Reporter: Alexander Klimetschek
>Assignee: Stefan Seifert
> Fix For: Context-Aware Configuration Impl 1.4.4
>
>
> A resolve with the default values doesn't give anything. Default values 
> should be:
> * Content Path "/content"
> * other config name "."
> Which should on a typical system give you something, such as 
> "/conf/global/settings" for example. This makes exploring the UI much simpler.
> If no config name is set, one gets a 500 error "Invalid configuration name: 
> null".



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

[jira] [Closed] (SLING-6935) Context-Aware web console default experience difficult

2017-09-22 Thread Stefan Seifert (JIRA) 

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

Stefan Seifert closed SLING-6935.
-

> Context-Aware web console default experience difficult
> --
>
> Key: SLING-6935
> URL: https://issues.apache.org/jira/browse/SLING-6935
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Context-Aware Configuration Impl 1.4.2
>Reporter: Alexander Klimetschek
>Assignee: Stefan Seifert
> Fix For: Context-Aware Configuration Impl 1.4.4
>
>
> A resolve with the default values doesn't give anything. Default values 
> should be:
> * Content Path "/content"
> * other config name "."
> Which should on a typical system give you something, such as 
> "/conf/global/settings" for example. This makes exploring the UI much simpler.
> If no config name is set, one gets a 500 error "Invalid configuration name: 
> null".



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

[jira] [Closed] (SLING-7016) caconfig: Override is not applied for a configuration name if no config resource exist

2017-09-22 Thread Stefan Seifert (JIRA) 

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

Stefan Seifert closed SLING-7016.
-

> caconfig: Override is not applied for a configuration name if no config 
> resource exist
> --
>
> Key: SLING-7016
> URL: https://issues.apache.org/jira/browse/SLING-7016
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Context-Aware Configuration Impl 1.4.2
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Minor
>  Labels: contextaware-config
> Fix For: Context-Aware Configuration Impl 1.4.4
>
>
> if for a given configuration name no config resource exist (not even on 
> higher levels or on one of the fallback paths), then configured override 
> values are not applied.
> overrides should always be applied regardless of existing configuration.



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

[RESULT] [VOTE] Release Apache Sling Context-Aware Configuration Impl 1.4.4

2017-09-22 Thread Stefan Seifert 
Hi,

The vote has passed with the following result :

+1 (binding): Stefan Seifert, Robert Munteanu, Bertrand Delacretaz, Karl Pauls, 
Daniel Klco
+1 (non binding): Timothee Maret 

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

stefan

Re: [VOTE] Release Apache Sling Context-Aware Configuration Impl 1.4.4

2017-09-22 Thread Daniel Klco 
+1

On Fri, Sep 22, 2017 at 12:39 PM, Karl Pauls  wrote:

> +1
>
> regards,
>
> Karl
>
> On Fri, Sep 22, 2017 at 6:37 PM, Bertrand Delacretaz
>  wrote:
> > Please vote to approve this release:
> >
> >
> > +1
> > Bertrand
>
>
>
> --
> Karl Pauls
> karlpa...@gmail.com
>

Re: [VOTE] Release Apache Sling Context-Aware Configuration Impl 1.4.4

2017-09-22 Thread Karl Pauls 
+1

regards,

Karl

On Fri, Sep 22, 2017 at 6:37 PM, Bertrand Delacretaz
 wrote:
> Please vote to approve this release:
>
>
> +1
> Bertrand



-- 
Karl Pauls
karlpa...@gmail.com

Re: [VOTE] Release Apache Sling Context-Aware Configuration Impl 1.4.4

2017-09-22 Thread Bertrand Delacretaz 
Please vote to approve this release:


+1
Bertrand

RE: [VOTE] Release Apache Sling Context-Aware Configuration Impl 1.4.4

2017-09-22 Thread Stefan Seifert 
one (binding) vote is missing

(there are some hours left for the 72h period - but i need it for my adaptto 
talk on monday... so last call before weekend)

stefan

[jira] [Updated] (SLING-6423) Allow for specifying ACL merge mode (ACHandling) in repoinit

2017-09-22 Thread Timothee Maret (JIRA) 

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

Timothee Maret updated SLING-6423:
--
Fix Version/s: (was: Repoinit Parser 1.2.0)
   Repoinit JCR 1.1.8

> Allow for specifying ACL merge mode (ACHandling) in repoinit
> 
>
> Key: SLING-6423
> URL: https://issues.apache.org/jira/browse/SLING-6423
> Project: Sling
>  Issue Type: New Feature
>  Components: Repoinit
>Reporter: Nitin Nizhawan
>Assignee: Timothee Maret
> Fix For: Repoinit JCR 1.1.8
>
> Attachments: SLING-6423_parser_changes.patch, 
> SLING-6423_testcases.patch, SLING_6423_testcasesV2.patch
>
>
> Repoinit by default just add new ACLs if they are not already present.
> By contract package manager provides various strategies for ACL merging
> Extend repoinit to allow specifying these strategies 
> https://jackrabbit.apache.org/filevault/apidocs/org/apache/jackrabbit/vault/fs/io/AccessControlHandling.html#MERGE



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

[RESULT] [VOTE] Release Apache Sling Repoinit JCR version 1.1.6 and Repoinit Parser version 1.2.0

2017-09-22 Thread Timothee Maret 
Hi,

The vote has passed with the following result :

+1 (binding): Stefan Seifert, Robert Munteanu, Bertrand Delacretaz

Could a member of the PMC please push the release to
https://dist.apache.org/repos/dist/release/sling ?

I'll take care of the remaining steps once this is done.

Regards,

Timothee

[jira] [Commented] (SLING-7144) JcrSystemUserValidator should identify disabled users as invalid

2017-09-22 Thread angela (JIRA) 

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

angela commented on SLING-7144:
---

[~marett], [~bdelacretaz], since you have been working on reflecting 
{{User.disable}} in the repo-init code base, you may also want to take care of 
this bug report? Thanks a lot.

> JcrSystemUserValidator should identify disabled users as invalid
> 
>
> Key: SLING-7144
> URL: https://issues.apache.org/jira/browse/SLING-7144
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Reporter: angela
> Attachments: JcrSystemUserValidatorTest.patch, SLING-7144.patch
>
>
> The {{JcrSystemUserValidator}} verifies that a given service mapping points 
> to an existing, valid system user. However, it doesn't take 
> {{User.isDisabled()}} into account.



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

[jira] [Updated] (SLING-7144) JcrSystemUserValidator should identify disabled users as invalid

2017-09-22 Thread angela (JIRA) 

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

angela updated SLING-7144:
--
Attachment: SLING-7144.patch
JcrSystemUserValidatorTest.patch

Proposed patch for {{JcrSystemUserValidator}}.
I wanted to write tests for the change and additionally extend the somewhat 
poor test coverage with {{JcrSystemUserValidatorTest}}... unfortunately that 
test is based on {{RepositoryTestBase}}, which afaik cannot run against an Oak 
repository and thus cannot be used for the tests I wanted to contribute. 
{{JcrSystemUserValidatorTest.patch}} illustrates how the tests should look like 
IMHO but they currently fail due to the dependency to the Jackrabbit 2.x... 
maybe it would be time to adjust {{RepositoryBaseTest}}?

> JcrSystemUserValidator should identify disabled users as invalid
> 
>
> Key: SLING-7144
> URL: https://issues.apache.org/jira/browse/SLING-7144
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Reporter: angela
> Attachments: JcrSystemUserValidatorTest.patch, SLING-7144.patch
>
>
> The {{JcrSystemUserValidator}} verifies that a given service mapping points 
> to an existing, valid system user. However, it doesn't take 
> {{User.isDisabled()}} into account.



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

[jira] [Created] (SLING-7144) JcrSystemUserValidator should identify disabled users as invalid

2017-09-22 Thread angela (JIRA) 
angela created SLING-7144:
-

 Summary: JcrSystemUserValidator should identify disabled users as 
invalid
 Key: SLING-7144
 URL: https://issues.apache.org/jira/browse/SLING-7144
 Project: Sling
  Issue Type: Bug
  Components: JCR
Reporter: angela


The {{JcrSystemUserValidator}} verifies that a given service mapping points to 
an existing, valid system user. However, it doesn't take {{User.isDisabled()}} 
into account.



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

Re: [git] Please test sample migrated git projects and repo setup

2017-09-22 Thread Robert Munteanu 
On Thu, 2017-09-21 at 11:18 +0300, Robert Munteanu wrote:
> > According to Eric Raymond (http://esr.ibiblio.org/?p=6778), who
> > claims
> > to have some experience with svn to git migrations, git-svn is not
> > up
> > to the task. Maybe that's where the history is lost.
> > 
> > In any case, I think we need to start the migration from the SVN
> > repository, given that https://github.com/apache/sling already
> > lacks
> > the history.
> > 
> > Maybe reposurgeon, the tool E. Raymond wrote, can help overcome the
> > issue with lost history when copying branches?
> 
> I'll try reposurgeon, thanks for the pointer. The thing is that the
> git
> remote seems to have the right rename handling, but it's lost when I
> create the module. But let's see after I try reposurgeon.
> 
> Thanks,
> 
> Robert

I'm delayed a bit with this. The reason is that this tool requires a
full SVN repository dump to operate. I've started doing it the default
way - svnsync, which would take weeks.

I've tried importing the dumps from http://svn-dump.apache.org/ , but
after some long hours of downloading and extracting I found out that
the warning on the page regarding the repository size is out of date.
Unexpanded it takes ~230 GB ( + ~75 for temporary extraction ) rather
than 65 as advertised. I don't have that kind of disk space around
unfortunately. I'll try and find an alternative somehow, but it's going
to take a bit more.

Robert

[jira] [Commented] (SLING-6081) Sling Content Package Maven Plugin

2017-09-22 Thread Robert Munteanu (JIRA) 

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

Robert Munteanu commented on SLING-6081:


Yes, agreed.

> Sling Content Package Maven Plugin
> --
>
> Key: SLING-6081
> URL: https://issues.apache.org/jira/browse/SLING-6081
> Project: Sling
>  Issue Type: New Feature
>  Components: Maven Plugins and Archetypes
>Reporter: Stefan Seifert
>
> in this mail thread better support for resource/content packaging was 
> discussed: http://sling.markmail.org/message/m2xfrnljzhqnfbpc
> part of this is having a open source alternative for the [adobe content 
> package maven 
> plugin|https://repo.adobe.com/nexus/content/groups/public/com/day/jcr/vault/content-package-maven-plugin/]
>  in sling.
> a good starting point for this may be the wcm.io content package maven plugin:
> * http://wcm.io/tooling/maven/plugins/wcmio-content-package-maven-plugin/
> * 
> https://github.com/wcm-io/wcm-io-tooling/tree/develop/maven/plugins/wcmio-content-package-maven-plugin
> which i would be happy to contribute to sling. it also supports good and 
> production-proven support for uploading and downloading packages (and tries 
> to use plugin configuration as near to the adobe plugin as possible).
> the only thing to add is support for creating the file vault package zip from 
> the project files.



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

[jira] [Commented] (SLING-6081) Sling Content Package Maven Plugin

2017-09-22 Thread Stefan Seifert (JIRA) 

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

Stefan Seifert commented on SLING-6081:
---

from [this 
comment|https://issues.apache.org/jira/browse/JCRVLT-202?focusedCommentId=16168087#comment-16168087]
 is assume there will be a separate plugin for package upload/download in some 
time - and maybe the jackrabbit project is the better place for such a plugin 
than sling. until then 
http://wcm.io/tooling/maven/plugins/wcmio-content-package-maven-plugin/ can be 
used.

> Sling Content Package Maven Plugin
> --
>
> Key: SLING-6081
> URL: https://issues.apache.org/jira/browse/SLING-6081
> Project: Sling
>  Issue Type: New Feature
>  Components: Maven Plugins and Archetypes
>Reporter: Stefan Seifert
>
> in this mail thread better support for resource/content packaging was 
> discussed: http://sling.markmail.org/message/m2xfrnljzhqnfbpc
> part of this is having a open source alternative for the [adobe content 
> package maven 
> plugin|https://repo.adobe.com/nexus/content/groups/public/com/day/jcr/vault/content-package-maven-plugin/]
>  in sling.
> a good starting point for this may be the wcm.io content package maven plugin:
> * http://wcm.io/tooling/maven/plugins/wcmio-content-package-maven-plugin/
> * 
> https://github.com/wcm-io/wcm-io-tooling/tree/develop/maven/plugins/wcmio-content-package-maven-plugin
> which i would be happy to contribute to sling. it also supports good and 
> production-proven support for uploading and downloading packages (and tries 
> to use plugin configuration as near to the adobe plugin as possible).
> the only thing to add is support for creating the file vault package zip from 
> the project files.



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

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

2017-09-22 Thread Stefan Seifert (JIRA) 

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

Stefan Seifert closed SLING-6195.
-

> 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] [Closed] (SLING-6081) Sling Content Package Maven Plugin

2017-09-22 Thread Stefan Seifert (JIRA) 

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

Stefan Seifert closed SLING-6081.
-

> Sling Content Package Maven Plugin
> --
>
> Key: SLING-6081
> URL: https://issues.apache.org/jira/browse/SLING-6081
> Project: Sling
>  Issue Type: New Feature
>  Components: Maven Plugins and Archetypes
>Reporter: Stefan Seifert
>
> in this mail thread better support for resource/content packaging was 
> discussed: http://sling.markmail.org/message/m2xfrnljzhqnfbpc
> part of this is having a open source alternative for the [adobe content 
> package maven 
> plugin|https://repo.adobe.com/nexus/content/groups/public/com/day/jcr/vault/content-package-maven-plugin/]
>  in sling.
> a good starting point for this may be the wcm.io content package maven plugin:
> * http://wcm.io/tooling/maven/plugins/wcmio-content-package-maven-plugin/
> * 
> https://github.com/wcm-io/wcm-io-tooling/tree/develop/maven/plugins/wcmio-content-package-maven-plugin
> which i would be happy to contribute to sling. it also supports good and 
> production-proven support for uploading and downloading packages (and tries 
> to use plugin configuration as near to the adobe plugin as possible).
> the only thing to add is support for creating the file vault package zip from 
> the project files.



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

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

2017-09-22 Thread Stefan Seifert (JIRA) 

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

Stefan Seifert resolved SLING-6195.
---
Resolution: Won't Fix

obsolete together with SLING-6081

> 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] [Commented] (SLING-6081) Sling Content Package Maven Plugin

2017-09-22 Thread Robert Munteanu (JIRA) 

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

Robert Munteanu commented on SLING-6081:


The vault plugin will not have support for interacting with a server-side 
package manager - either CRX or Composum. So there is no 100% equivalence with 
a potential sling plugin, but I'm not sure if we should pursue it though.

> Sling Content Package Maven Plugin
> --
>
> Key: SLING-6081
> URL: https://issues.apache.org/jira/browse/SLING-6081
> Project: Sling
>  Issue Type: New Feature
>  Components: Maven Plugins and Archetypes
>Reporter: Stefan Seifert
>
> in this mail thread better support for resource/content packaging was 
> discussed: http://sling.markmail.org/message/m2xfrnljzhqnfbpc
> part of this is having a open source alternative for the [adobe content 
> package maven 
> plugin|https://repo.adobe.com/nexus/content/groups/public/com/day/jcr/vault/content-package-maven-plugin/]
>  in sling.
> a good starting point for this may be the wcm.io content package maven plugin:
> * http://wcm.io/tooling/maven/plugins/wcmio-content-package-maven-plugin/
> * 
> https://github.com/wcm-io/wcm-io-tooling/tree/develop/maven/plugins/wcmio-content-package-maven-plugin
> which i would be happy to contribute to sling. it also supports good and 
> production-proven support for uploading and downloading packages (and tries 
> to use plugin configuration as near to the adobe plugin as possible).
> the only thing to add is support for creating the file vault package zip from 
> the project files.



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

[jira] [Resolved] (SLING-6081) Sling Content Package Maven Plugin

2017-09-22 Thread Stefan Seifert (JIRA) 

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

Stefan Seifert resolved SLING-6081.
---
Resolution: Won't Fix

> Sling Content Package Maven Plugin
> --
>
> Key: SLING-6081
> URL: https://issues.apache.org/jira/browse/SLING-6081
> Project: Sling
>  Issue Type: New Feature
>  Components: Maven Plugins and Archetypes
>Reporter: Stefan Seifert
>
> in this mail thread better support for resource/content packaging was 
> discussed: http://sling.markmail.org/message/m2xfrnljzhqnfbpc
> part of this is having a open source alternative for the [adobe content 
> package maven 
> plugin|https://repo.adobe.com/nexus/content/groups/public/com/day/jcr/vault/content-package-maven-plugin/]
>  in sling.
> a good starting point for this may be the wcm.io content package maven plugin:
> * http://wcm.io/tooling/maven/plugins/wcmio-content-package-maven-plugin/
> * 
> https://github.com/wcm-io/wcm-io-tooling/tree/develop/maven/plugins/wcmio-content-package-maven-plugin
> which i would be happy to contribute to sling. it also supports good and 
> production-proven support for uploading and downloading packages (and tries 
> to use plugin configuration as near to the adobe plugin as possible).
> the only thing to add is support for creating the file vault package zip from 
> the project files.



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

[jira] [Commented] (SLING-6081) Sling Content Package Maven Plugin

2017-09-22 Thread Stefan Seifert (JIRA) 

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

Stefan Seifert commented on SLING-6081:
---

i think this ticket is obsolete as there now is a 
"filevault-package-maven-plugin" in jackrabbit: JCRVLT-202

> Sling Content Package Maven Plugin
> --
>
> Key: SLING-6081
> URL: https://issues.apache.org/jira/browse/SLING-6081
> Project: Sling
>  Issue Type: New Feature
>  Components: Maven Plugins and Archetypes
>Reporter: Stefan Seifert
>
> in this mail thread better support for resource/content packaging was 
> discussed: http://sling.markmail.org/message/m2xfrnljzhqnfbpc
> part of this is having a open source alternative for the [adobe content 
> package maven 
> plugin|https://repo.adobe.com/nexus/content/groups/public/com/day/jcr/vault/content-package-maven-plugin/]
>  in sling.
> a good starting point for this may be the wcm.io content package maven plugin:
> * http://wcm.io/tooling/maven/plugins/wcmio-content-package-maven-plugin/
> * 
> https://github.com/wcm-io/wcm-io-tooling/tree/develop/maven/plugins/wcmio-content-package-maven-plugin
> which i would be happy to contribute to sling. it also supports good and 
> production-proven support for uploading and downloading packages (and tries 
> to use plugin configuration as near to the adobe plugin as possible).
> the only thing to add is support for creating the file vault package zip from 
> the project files.



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

[jira] [Commented] (SLING-7108) FullTextIndexingTest times out on Java 9

2017-09-22 Thread Robert Munteanu (JIRA) 

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

Robert Munteanu commented on SLING-7108:


The Tika issue is fixed and according to 
https://issues.apache.org/jira/browse/TIKA-2466?focusedCommentId=16175449=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16175449
 

{quote}We'll probably roll 1.17 shortly after the next version of PDFBox is 
available...next few weeks.{quote}

> FullTextIndexingTest times out on Java 9
> 
>
> Key: SLING-7108
> URL: https://issues.apache.org/jira/browse/SLING-7108
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Reporter: Robert Munteanu
> Fix For: Launchpad Testing 9
>
>
> {noformat}Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 
> 45.657 sec <<< FAILURE! - in 
> org.apache.sling.launchpad.webapp.integrationtest.indexing.FullTextIndexingTest
> testUploadedPdfIsIndexed[0 - 
> lorem-ipsum.pdf](org.apache.sling.launchpad.webapp.integrationtest.indexing.FullTextIndexingTest)
>   Time elapsed: 15.232 sec  <<< FAILURE!
> java.lang.AssertionError: RetryLoop failed, condition is false after 15 
> seconds: A document containing 'Excepteur' is found under 
> /tmp/test-FullTextIndexingTest
>   at org.junit.Assert.fail(Assert.java:88)
>   at 
> org.apache.sling.testing.tools.retry.RetryLoop.(RetryLoop.java:65)
>   at 
> org.apache.sling.launchpad.webapp.integrationtest.indexing.FullTextIndexingTest.testUploadedPdfIsIndexed(FullTextIndexingTest.java:97)
> testUploadedPdfIsIndexed[1 - 
> another.pdf](org.apache.sling.launchpad.webapp.integrationtest.indexing.FullTextIndexingTest)
>   Time elapsed: 15.212 sec  <<< FAILURE!
> java.lang.AssertionError: RetryLoop failed, condition is false after 15 
> seconds: A document containing 'some text that we will search for' is found 
> under /var/test-FullTextIndexingTest
>   at org.junit.Assert.fail(Assert.java:88)
>   at 
> org.apache.sling.testing.tools.retry.RetryLoop.(RetryLoop.java:65)
>   at 
> org.apache.sling.launchpad.webapp.integrationtest.indexing.FullTextIndexingTest.testUploadedPdfIsIndexed(FullTextIndexingTest.java:97)
> testUploadedPdfIsIndexed[2 - 
> french.pdf](org.apache.sling.launchpad.webapp.integrationtest.indexing.FullTextIndexingTest)
>   Time elapsed: 15.211 sec  <<< FAILURE!
> java.lang.AssertionError: RetryLoop failed, condition is false after 15 
> seconds: A document containing 'un autre PDF pour le test fulltext' is found 
> under /libs/test-FullTextIndexingTest
>   at org.junit.Assert.fail(Assert.java:88)
>   at 
> org.apache.sling.testing.tools.retry.RetryLoop.(RetryLoop.java:65)
>   at 
> org.apache.sling.launchpad.webapp.integrationtest.indexing.FullTextIndexingTest.testUploadedPdfIsIndexed(FullTextIndexingTest.java:97){noformat}



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