Brilliant, thanks a lot!
On Wed, Nov 16, 2016 at 3:28 PM, Robert Munteanu wrote:
> On Wed, 2016-11-09 at 21:37 +0100, Julian Sedding wrote:
>> Hi Robert
>>
>> Yes absolutely, that sounds great!
>>
>> Thanks for your prompt replies.
>
>
> Done, see https://issues.apache.org/jira/browse/SLING-6290
On Wed, 2016-11-09 at 21:37 +0100, Julian Sedding wrote:
> Hi Robert
>
> Yes absolutely, that sounds great!
>
> Thanks for your prompt replies.
Done, see https://issues.apache.org/jira/browse/SLING-6290 .
I've added the 'rebuildDaily' property for the oak-server module, feel
free to add it to
Hi Robert
Yes absolutely, that sounds great!
Thanks for your prompt replies.
Regards
Julian
On Wed, Nov 9, 2016 at 9:16 PM, Robert Munteanu wrote:
> On Wed, 2016-11-09 at 20:49 +0100, Julian Sedding wrote:
>> Hi Robert
>>
>> Thanks for the hints.
>>
>> I was wondering if it is possible to tri
On Wed, 2016-11-09 at 20:49 +0100, Julian Sedding wrote:
> Hi Robert
>
> Thanks for the hints.
>
> I was wondering if it is possible to trigger a build of each module
> at
> least once every 24h? Even if there are no changes in the module.
>
> Writing a Jenkins trigger, extracting dependencies f
Hi Robert
Thanks for the hints.
I was wondering if it is possible to trigger a build of each module at
least once every 24h? Even if there are no changes in the module.
Writing a Jenkins trigger, extracting dependencies from PaxExam tests
does not sound trivial. And that may be only one case of
Hi Julian,
On Tue, 2016-11-08 at 22:29 +0100, Julian Sedding wrote:
> Hi Robert
>
> I think the test failures in oak-server did not come up because of
> the
> modularised jenkins jobs we have now.
>
> The bundle's build seems to have run last after changes were applied
> to it. However, a refere
Brilliant. Thanks Carsten.
On Wed, Nov 9, 2016 at 7:49 AM, Carsten Ziegeler wrote:
> I just started the vote for the repoinit modules, so hopefully we'll be
> out of this snapshot mess soon
>
> Regards
> Carsten
>
> Julian Sedding wrote
>> Hi Robert
>>
>> I think the test failures in oak-server d
I just started the vote for the repoinit modules, so hopefully we'll be
out of this snapshot mess soon
Regards
Carsten
Julian Sedding wrote
> Hi Robert
>
> I think the test failures in oak-server did not come up because of the
> modularised jenkins jobs we have now.
>
> The bundle's build seems
Hi Robert
I think the test failures in oak-server did not come up because of the
modularised jenkins jobs we have now.
The bundle's build seems to have run last after changes were applied
to it. However, a referenced SNAPSHOT dependency has evolved since and
made the tests fail.
Any ideas how to
Hi Alex.
On Tue, 2016-11-08 at 20:01 +, Alexander Klimetschek wrote:
> I have some trouble building Sling (all of it, it's been a while
> since I tried that :)
>
> 1. It seems the Sling build requires Java 1.8 ("Apache Sling Testing
> PaxExam" project failed with not all bundles loaded when I
Hi Alex
I was looking at the same tests and just found out that the failures
are due to an incompatibility between
org.apache.sling.repoinit.parser:1.0.4 and (the current)
org.apache.sling.jcr.repoinit:1.0.3-SNAPSHOT. Updating to
org.apache.sling.repoinit.parser:1.0.5-SNAPSHOT in the Pax-Definitio
I have some trouble building Sling (all of it, it's been a while since I tried
that :)
1. It seems the Sling build requires Java 1.8 ("Apache Sling Testing PaxExam"
project failed with not all bundles loaded when I ran it with a 1.7 JDK). A
check/hint at the start of the build would be great.
12 matches
Mail list logo
