> On 29 Mar 2017, at 15:12, Oliver Lietz wrote:
>
> On Wednesday 29 March 2017 14:48:06 Oliver Lietz wrote:
>> On Wednesday 29 March 2017 14:37:58 Konrad Windszus wrote:
>>> This is still not 100% fixed.
>>> The Jenkins Workspace still contains the folder
>>>
On Wednesday 29 March 2017 14:48:06 Oliver Lietz wrote:
> On Wednesday 29 March 2017 14:37:58 Konrad Windszus wrote:
> > This is still not 100% fixed.
> > The Jenkins Workspace still contains the folder
> > https://builds.apache.org/job/sling-bundles-extensions-validation-core-1.8
> > /
> >
On Wednesday 29 March 2017 14:37:58 Konrad Windszus wrote:
> This is still not 100% fixed.
> The Jenkins Workspace still contains the folder
> https://builds.apache.org/job/sling-bundles-extensions-validation-core-1.8/
> ws/sling/repository/index/indexWriterDir/ outside of target. That folder
>
This is still not 100% fixed.
The Jenkins Workspace still contains the folder
https://builds.apache.org/job/sling-bundles-extensions-validation-core-1.8/ws/sling/repository/index/indexWriterDir/
outside of target.
That folder must have been created by PaxExam after I wiped out the workspace
in
On Thursday 16 March 2017 15:21:32 Konrad Windszus wrote:
> Some javadocs in
> https://github.com/apache/sling/blob/trunk/testing/org.apache.sling.testing
> .paxexam/src/main/java/org/apache/sling/testing/paxexam/SlingOptions.java#L8
> 62 would be really helpful, which explain under which
Some javadocs in
https://github.com/apache/sling/blob/trunk/testing/org.apache.sling.testing.paxexam/src/main/java/org/apache/sling/testing/paxexam/SlingOptions.java#L862
would be really helpful, which explain under which circumstances you have to
use the methods with the workingDirectory and
On Thursday 16 March 2017 13:45:44 Konrad Windszus wrote:
> Maybe this is related to
> https://issues.apache.org/jira/browse/SLING-4649?focusedCommentId=14508857;
> page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#commen
> t-14508857. It seems that the Lucene index relies on a
On Thursday 16 March 2017 13:54:23 Konrad Windszus wrote:
> Probably this commit
> https://github.com/apache/sling/blame/trunk/testing/org.apache.sling.testin
> g.paxexam/src/main/java/org/apache/sling/testing/paxexam/SlingOptions.java#L
> 645 is not correct. The localIndexDir should be IMHO set
On Thursday 16 March 2017 13:31:15 Konrad Windszus wrote:
> Hi,
Hi Konrad,
> it seems that PaxExam based ITs may create folders outside the target folder
> (see
> https://builds.apache.org/job/sling-bundles-extensions-validation-core-1.8/
> ws/) For Validation the folder
>
Probably this commit
https://github.com/apache/sling/blame/trunk/testing/org.apache.sling.testing.paxexam/src/main/java/org/apache/sling/testing/paxexam/SlingOptions.java#L645
is not correct. The localIndexDir should be IMHO set as absolute path (not
relative!) This is done correctly in
Maybe this is related to
https://issues.apache.org/jira/browse/SLING-4649?focusedCommentId=14508857=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14508857.
It seems that the Lucene index relies on a framework property (named
repository.home) if this is not explicitly
Hi,
it seems that PaxExam based ITs may create folders outside the target folder
(see
https://builds.apache.org/job/sling-bundles-extensions-validation-core-1.8/ws/)
For Validation the folder sling/repository/index/lucene-1488547426482/data was
obviously created by PaxExam.
Usually the
12 matches
Mail list logo