Hi all,
Maybe its just me, but currently the Sling (main) integration tests run
extremely unstable. Most of the time I only have one failure. But 1 out
of 4 runs, I have a random (but rather high) number of test failures.
I run "mvn -o clean install" in the launchpad/testing folder af
All,
For doing some end-to-end testing of the new Resource Access Tags, I added some
integration tests into the project. These tests take approximately 16 seconds
to run and require starting up an instance of Sling on a random port. Should
these tests be included as part of the default
d now...
Justin
On 9/9/10 8:53 AM, Felix Meschberger wrote:
> Hi all,
>
> Maybe its just me, but currently the Sling (main) integration tests run
> extremely unstable. Most of the time I only have one failure. But 1 out
> of 4 runs, I have a random (but rather high) number of test failures
revision), both have
> passed pretty consistently.
>
> Running a build now...
>
> Justin
>
> On 9/9/10 8:53 AM, Felix Meschberger wrote:
>> Hi all,
>>
>> Maybe its just me, but currently the Sling (main) integration tests run
>> extremely unstable. Most of t
On Thu, Sep 9, 2010 at 12:53 PM, Felix Meschberger wrote:
> ...Maybe its just me, but currently the Sling (main) integration tests run
> extremely unstable. Most of the time I only have one failure. But 1 out
> of 4 runs, I have a random (but rather high) number of test failures
ad/testing would always pass.
>>
>> Since about a week ago (sorry, don't know the revision), both have
>> passed pretty consistently.
>>
>> Running a build now...
>>
>> Justin
>>
>> On 9/9/10 8:53 AM, Felix Meschberger wrote:
>>> H
On Thu, Sep 9, 2010 at 5:56 PM, Justin Edelson wrote:
> ...$ mvn clean install
> $ mvn clean install
>
> consistently fails. This should be reasonably simple to resolve by
> adding an execution of the clean plugin to the root pom...
IIRC mvn clean -> delete sling folder is configured (didn't che
On 9/9/10 2:04 PM, Bertrand Delacretaz wrote:
> On Thu, Sep 9, 2010 at 5:56 PM, Justin Edelson
> wrote:
>> ...$ mvn clean install
>> $ mvn clean install
>>
>> consistently fails. This should be reasonably simple to resolve by
>> adding an execution of the clean plugin to the root pom...
>
> IIRC
On Thu, Sep 9, 2010 at 6:06 PM, Justin Edelson wrote:
> On 9/9/10 2:04 PM, Bertrand Delacretaz wrote:
>>... IIRC mvn clean -> delete sling folder is configured (didn't check
>> right now) but maybe doesn't work for full reactor build?
>>
> mvn clean will delete [root]/launchpad/testing/sling. It
ng this until about a week ago, but it was slightly
>>> different... a full reactor build would fail, but mvn clean install in
>>> launchpad/testing would always pass.
>>>
>>> Since about a week ago (sorry, don't know the revision), both have
>>> pass
On 9/9/10 2:18 PM, Bertrand Delacretaz wrote:
> On Thu, Sep 9, 2010 at 6:06 PM, Justin Edelson
> wrote:
>> On 9/9/10 2:04 PM, Bertrand Delacretaz wrote:
>>> ... IIRC mvn clean -> delete sling folder is configured (didn't check
>>> right now) but maybe doesn't work for full reactor build?
>>>
>>
t; On 09.09.2010 15:55, Justin Edelson wrote:
>>>> I _was_ seeing this until about a week ago, but it was slightly
>>>> different... a full reactor build would fail, but mvn clean install in
>>>> launchpad/testing would always pass.
>>>>
>>>>
eschberger wrote:
Hi all,
Maybe its just me, but currently the Sling (main) integration tests run
extremely unstable. Most of the time I only have one failure. But 1 out
of 4 runs, I have a random (but rather high) number of test failures.
I run "mvn -o clean install" in the laun
FWIW, which probably isn't much...
On a clean Ubuntu 10.04 VM with all updates and OpenJDK 6b18 and Maven
2.2.1, I've had 5 clean integration test suite runs in a row.
On 9/9/10 8:53 AM, Felix Meschberger wrote:
> Hi all,
>
> Maybe its just me, but currently the Sling (main
10 8:53 AM, Felix Meschberger wrote:
Hi all,
Maybe its just me, but currently the Sling (main) integration tests run
extremely unstable. Most of the time I only have one failure. But 1 out
of 4 runs, I have a random (but rather high) number of test failures.
I run "mvn -o clean install&quo
gt; Maybe its just me, but currently the Sling (main) integration tests run
>> extremely unstable. Most of the time I only have one failure. But 1 out
>> of 4 runs, I have a random (but rather high) number of test failures.
>>
>> I run "mvn -o clean install" in the la
Hi all,
the integration tests fail for me. In the trunk I do
> cd launchpad/integration-tests
> mvn test -Dtest=PostServlet*
I get tons of "connection refused" exceptions:
--
Hi Dan,
On Mon, May 20, 2013 at 7:39 PM, Dan Klco wrote:
> For doing some end-to-end testing of the new Resource Access Tags, I added
> some integration tests into the project.
> These tests take approximately 16 seconds to run and require starting up an
> instance of Sling on a
Hi,
On Thu, Nov 5, 2009 at 10:12 AM, Ian Boston wrote:
> Is it possible to run just one of the tests in the launchpad/testing project
> ?
> I have tried mvn -Dtest=**/PrefixTest.java but I get a whole bunch of errors
> when the testing webapp doesnt start up.
Yes it's possible, but you need to s
On 5 Nov 2009, at 11:10, Bertrand Delacretaz wrote:
Hi,
On Thu, Nov 5, 2009 at 10:12 AM, Ian Boston wrote:
Is it possible to run just one of the tests in the launchpad/
testing project
?
I have tried mvn -Dtest=**/PrefixTest.java but I get a whole bunch
of errors
when the testing webapp
On 15.02.11 21:02, "Alexander Klimetschek" wrote:
>the integration tests fail for me. In the trunk I do
>
>> cd launchpad/integration-tests
>> mvn test -Dtest=PostServlet*
I got it running in the meantime (thanks to Bertrand). The above is not
enough, you need to do:
On Wed, Feb 16, 2011 at 5:58 PM, Alexander Klimetschek
wrote:
> ...you need to do:
>
> (1) start the sling testing instance
>
> cd launchpad/testing
> mvn clean
> mvn launchpad:run
>
> (2) in a separate shell, run the integration tests
>
> cd launchpad/integration
It seems our jenkins jobs fail because of tests in the validation fail
Could someone please look into it?
Thanks
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
[
https://issues.apache.org/jira/browse/SLING-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-837.
--
> Integrate JCRInstall integration tests with the main integration te
moved (SLING-1141), marking
won't fix.
> Integrate JCRInstall integration tests with the main integration tests
> --
>
> Key: SLING-837
> URL: https://issues.apache.
Hi
With the newest trunk the osgi.installer integration tests are hanging,
without displaying an error.
best regards
mike
output from maven
Hi,
it seems that the integration tests in the installer fail for some
time now. I'm actually not sure if this is a problem of the installer,
the test or a general problem. The interesting thing is, if you build
the integration tests standalone, they run fine without problems. Only
in the re
Hi,
encoding the redirect url breaks our integration tests (therefore I
reopened SLING-2543).
It seems that our tests do not except an encoded redirect url and I'm
wondering about existing clients.
Regards
Carsten
--
Carsten Ziegeler
cziege...@apache.org
module is released it may be required to release the integration test project
as well.
a goal would be to move most of module-specific integration tests "near to the
module" or just in the module project itself, using one oft the numerous
available integration test tool support av
Hi,
Dunno if someone is already looking at this?
When building bundles/extensions/models/integration-tests
RemoteIT.testInterfaceInjection
testInterfaceInjection(org.apache.sling.models.it.SimpleTest): Model
is null
RemoteIT.testConstructorInjection
testConstructorInjection
Sorry for that. Should be fixed now.
Konrad
> Am 14.04.2015 um 18:12 schrieb Carsten Ziegeler :
>
> It seems our jenkins jobs fail because of tests in the validation fail
>
> Could someone please look into it?
>
> Thanks
> Carsten
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege..
Hi,
I noticed that our sling-contrib build is quite slow on Jenkins,
taking around 90 minutes. Out of those, about 60 minutes are spent in
the 'Apache Sling Launchpad Karaf - Integration Tests' module.
I am not familiar with that module, but perhaps there's a low-hanging
fruit wh
HI,
The ITs at
https://github.com/apache/sling-org-apache-sling-models-integration-tests built
through
https://ci-builds.apache.org/blue/organizations/jenkins/Sling%2Fmodules%2Fsling-org-apache-sling-models-integration-tests/activity
are failing since quite some time and also reference pretty
Sample Integration tests should run in the integration-tests phase
--
Key: SLING-2023
URL: https://issues.apache.org/jira/browse/SLING-2023
Project: Sling
Issue Type
[
https://issues.apache.org/jira/browse/SLING-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-2023.
-
Resolution: Won't Fix
> Sample Integration tests should run in the integrati
Mike Müller wrote
> Hi
>
> With the newest trunk the osgi.installer integration tests are hanging,
> without displaying an error.
>
Strange - it works for me without any problems.
Are you doing a full reactor build?
Carsten
> best regards
> mike
&
I did the whole sling build with
mvn clean install in the sling directory.
best regards
mike
> -Original Message-
> From: Carsten Ziegeler [mailto:cziege...@apache.org]
> Sent: Wednesday, August 25, 2010 3:04 PM
> To: dev@sling.apache.org
> Subject: Re: osgi.installer in
On 8/25/10 9:04 AM, Carsten Ziegeler wrote:
> Mike Müller wrote
>> Hi
>>
>> With the newest trunk the osgi.installer integration tests are hanging,
>> without displaying an error.
>>
> Strange - it works for me without any problems.
ditto
>
> Are yo
Maybe it's a problem only on windows xp, but the felix framework
seems to hung...
> -Original Message-
> From: Justin Edelson [mailto:justinedel...@gmail.com]
> Sent: Wednesday, August 25, 2010 3:27 PM
> To: dev@sling.apache.org
> Subject: Re: osgi.installer integrati
> With the newest trunk the osgi.installer integration tests are hanging,
> without displaying an error.
>
> best regards
> m
ight be windows related ???
One thing that would be worth checking is what version of Felix Pax Exam
is using.
Justin
>
> Regards
> Felix
>
> On 25.08.2010 14:29, Mike Müller wrote:
>> Hi
>>
>> With the newest trunk the osgi.installer integration tests are han
I am aware from another project that PermGen space problems can be
really nasty...
As a wild guess this might help:
How to deal with “java.lang.OutOfMemoryError: PermGen space” error
http://stackoverflow.com/questions/88235/how-to-deal-with-java-lang-outofmemoryerror-permgen-space-error
Cheers,
; it seems that the integration tests in the installer fail for some
> time now. I'm actually not sure if this is a problem of the installer,
> the test or a general problem. The interesting thing is, if you build
> the integration tests standalone, they run fine without problems. Only
>
ne works but reactor build fails.
>
> As I'm always using Java 5 I've no idea when this changed :(
>
> Regards
> Carsten
>
> 2011/9/19 Carsten Ziegeler :
>> Hi,
>>
>> it seems that the integration tests in the installer fail for some
>> time now.
On 2012-09-26 07:38, Carsten Ziegeler wrote:
Hi,
encoding the redirect url breaks our integration tests (therefore I
reopened SLING-2543).
It seems that our tests do not except an encoded redirect url and I'm
wondering about existing clients.
What clients in particular? Browsers shou
Hi,
FYI, just tried to run the launchpad/testing integration tests and
most or all JSP-related tests are failing.
Haven't investigated further yet.
-Bertrand
Failing tests:
testInfiniteLoopDetection(org.apache.sling.launchpad.webapp.integrationtest.JspIncludeTest)
testForcedResourc
i've used the teleporter rules in the integration tests for the context-aware
configs:
https://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/contextaware-config/integration-tests
on my machines they run smooth on a fast machine, but flaky on a not-so-fast
machine.
source o
Hi,
I moved the i18n integration tests to use Oak (instead of jackrabbit 2)
and now one integration test fails. Right now, I don't see a good reason
why.
Any help or hint appreciated.
Thanks
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
ease the integration
> test project as well.
>
> a goal would be to move most of module-specific integration tests "near to
> the module" or just in the module project itself, using one oft the
> numerous available integration test tool support available in sling today.
ist hat different aspects are mixed in one project, and
> > if a new module is released it may be required to release the integration
> > test project as well.
> >
> > a goal would be to move most of module-specific integration tests "near to
> > the module" or
On Wed, 2016-09-28 at 22:06 +, Stefan Seifert wrote:
> a goal would be to move most of module-specific integration tests
> "near to the module" or just in the module project itself, using one
> oft the numerous available integration test tool support available in
> sling
On Mon, Oct 3, 2016 at 12:48 PM Robert Munteanu wrote:
> On Wed, 2016-09-28 at 22:06 +, Stefan Seifert wrote:
> > a goal would be to move most of module-specific integration tests
> > "near to the module" or just in the module project itself, using one
>
Hi,
On Thu, Sep 29, 2016 at 12:06 AM, Stefan Seifert wrote:
> ...a goal would be to move most of module-specific integration tests "near to
> the module" or just in the
> module project itself, using one oft the numerous available integration test
> tool support avai
>-Original Message-
>From: Bertrand Delacretaz [mailto:bdelacre...@apache.org]
>Sent: Tuesday, October 4, 2016 9:48 AM
>To: dev
>Subject: Re: Integration tests near to modules
...
>I did attend (most of) the committers roundtable at adaptTo, I don't
>think we ma
Hi,
On Tue, Oct 4, 2016 at 10:48 AM, Stefan Seifert wrote:
>>-Original Message-
>>From: Bertrand Delacretaz [mailto:bdelacre...@apache.org]
>>I...I don't
>>think we made any decisions there and those would not be valid anyway
>>as they didn't happen on this list.
>
> yes, see [1]..
ah ok
Hi,
I would like to add an integration test that covers SCD binary less feature
(Use Binary References) in a specific setup:
Two instances with shared caching blob store (AFAIK any blob
store that implements [0] such as [1]).
I wonder two things
1. Is it fine to run integration tests
Hi,
On Fri, Aug 29, 2014 at 10:57 AM, Bertrand Delacretaz
wrote:
> Hi,
>
> Dunno if someone is already looking at this?
>
> When building bundles/extensions/models/integration-tests
>
> RemoteIT.testInterfaceInjection
> testInterfaceInjection(org.apache.sling.models.it
>I filed https://issues.apache.org/jira/browse/SLING-3884 for this a
>couple of day ago.
patch attached in the ticket.
stefan
On Fri, Aug 29, 2014 at 10:54 AM, Stefan Seifert wrote:
>>I filed https://issues.apache.org/jira/browse/SLING-3884 for this a
>>couple of day ago.
> patch attached in the ticket...
Ah great, thanks! I'll have a look at your patch now.
-Bertrand
On Thursday 23 April 2015 13:46:52 Robert Munteanu wrote:
> Hi,
Hi Robert,
> I noticed that our sling-contrib build is quite slow on Jenkins,
> taking around 90 minutes. Out of those, about 60 minutes are spent in
> the 'Apache Sling Launchpad Karaf - Integration Tests' mod
On Thu, Apr 23, 2015 at 1:51 PM, Oliver Lietz wrote:
> ...Apart from that we can create a dedicated build job for Karaf
> Launchpad
That would be great as it looks like that would speed up the contrib
build job a lot.
-Bertrand
While we're at it, my build takes forever at
"Building Apache Sling Launchpad Debian Package Builder 8-SNAPSHOT"
it seems its executing scripts and whatnot. Does anyone know what it
actually does?
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
rib
> build job a lot.
Yes, the 53 integration tests currently take 40 minutes when not failing and
this is worth a dedicated build job.
While we're at it... is there a build job for running Launchpad's integration
tests?
I still have failing tests when running Launchpad's integ
On Thu, Apr 23, 2015 at 4:19 PM, Carsten Ziegeler wrote:
> While we're at it, my build takes forever at
>
> "Building Apache Sling Launchpad Debian Package Builder 8-SNAPSHOT"
>
> it seems its executing scripts and whatnot. Does anyone know what it
> actually does?
https://issues.apache.org/jira
>
>> That would be great as it looks like that would speed up the contrib
>> build job a lot.
>
> Yes, the 53 integration tests currently take 40 minutes when not failing and
> this is worth a dedicated build job.
>
> While we're at it... is there a build job for runn
Am 24.04.15 um 11:44 schrieb Robert Munteanu:
> On Thu, Apr 23, 2015 at 4:19 PM, Carsten Ziegeler
> wrote:
>> While we're at it, my build takes forever at
>>
>> "Building Apache Sling Launchpad Debian Package Builder 8-SNAPSHOT"
>>
>> it seems its executing scripts and whatnot. Does anyone know w
hello konrad.
yes, that's an important open issue. the ideal solution would be a) switch to
sling 12 + integrate the integration tests in the models impl repository, and
have them automatically executed in jenkins when models impl change.
this probably involves splitting the integration
Hi,
On Fri, 2023-07-07 at 15:04 +, Stefan Seifert wrote:
> hello konrad.
>
> yes, that's an important open issue. the ideal solution would be a)
> switch to sling 12 + integrate the integration tests in the models
> impl repository, and have them automatically exec
lo konrad.
>>
>> yes, that's an important open issue. the ideal solution would be a)
>> switch to sling 12 + integrate the integration tests in the models
>> impl repository, and have them automatically executed in jenkins when
>> models impl change.
>
>
Hi Konrad,
On Mon, 2023-07-10 at 19:22 +0200, Konrad Windszus wrote:
> Hi,
> Thanks for the input. I started with a draft which uses the Starter
> during the IT of the Models Impl in
> https://github.com/apache/sling-org-apache-sling-models-impl/pull/46.
> Unfortunately the “repository” goal of th
On 14 September 2010 18:56, Andreas Kuckartz wrote:
> I am aware from another project that PermGen space problems can be
> really nasty...
>
> As a wild guess this might help:
>
> How to deal with “java.lang.OutOfMemoryError: PermGen space” error
> http://stackoverflow.com/questions/88235/how-to-d
Hi all,
I did a `maven clean install` in testing/samples/integration-tests. But I
get following error in tests.
I get the same error when I write my own test cases.
What could be the problem?
---
T E S T S
Hi
The integration tests now fail, because the SortingServiceTracker could not be
found in the released version of commons/osgi.
Am I correct, that the only way to correct this is to release Commons OSGi
bundle in 2.1.2.
Or are there any alternative ways to make the tests run again?
best
I guess the new commons classloader bundle is missing.
Carsten
Bertrand Delacretaz wrote:
> Hi,
>
> FYI, just tried to run the launchpad/testing integration tests and
> most or all JSP-related tests are failing.
>
> Haven't investigated further yet.
>
>
On Fri, Jul 17, 2009 at 10:28 AM, Carsten Ziegeler wrote:
> I guess the new commons classloader bundle is missing.
It was missing, tried to add it manually but JSP scripts still don't run.
steps to reproduce:
cd launchpad/testing
mvn clean package jetty:run
add commons classloader bundle
start b
[
https://issues.apache.org/jira/browse/SLING-7923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Klco closed SLING-7923.
---
> Simplify integration tests
> --
>
> Key
Hi Stefan,
On Fri, Sep 2, 2016 at 12:32 PM, Stefan Seifert wrote:
>
> ...in the old HttpTestBase there was a concept with launchpad.ready.1 URLs
> defined which were checked to see if the
> instances was really ready - is there an equivalent concept in the teleporter
> rule, how to configure it
>To: dev
>Subject: Re: flaky integration tests with teleporte rule
>
>Hi Stefan,
>
>On Fri, Sep 2, 2016 at 12:32 PM, Stefan Seifert
>wrote:
>>
>> ...in the old HttpTestBase there was a concept with launchpad.ready.1
>URLs defined which were checked to see if th
On Friday 02 September 2016 10:32:38 Stefan Seifert wrote:
> i've used the teleporter rules in the integration tests for the
> context-aware configs:
> https://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/contextawar
> e-config/integration-tests
>
> on my machin
> Hi,
>
> I moved the i18n integration tests to use Oak (instead of jackrabbit 2)
> and now one integration test fails. Right now, I don't see a good reason
> why.
> Any help or hint appreciated.
>
I found the problem: the it test was buggy. It created duplicate messag
that implements [0] such as [1]).
>
> I wonder two things
>
> 1. Is it fine to run integration tests using FileDataStores (rather than
> the potentially much faster memory based data stores) ?
Oak Server, Scripting Thymeleaf and FreeMarker use "real" Sling instances with
; >
> > Two instances with shared caching blob store (AFAIK any blob
> > store that implements [0] such as [1]).
> >
> > I wonder two things
> >
> > 1. Is it fine to run integration tests using FileDataStores (rather than
> > the potentially much fast
n test that covers SCD binary less
> >
> > feature
> >
> > > (Use Binary References) in a specific setup:
> > > Two instances with shared caching blob store (AFAIK any blob
> > >
> > > store that implements [0] such as [1]).
> > >
red caching blob store (AFAIK any
> blob
> > > >
> > > > store that implements [0] such as [1]).
> > > >
> > > > I wonder two things
> > > >
> > > > 1. Is it fine to run integration tests using FileDataStores (rather
> than
Eric Norman created SLING-10436:
---
Summary: Move integration tests
Key: SLING-10436
URL: https://issues.apache.org/jira/browse/SLING-10436
Project: Sling
Issue Type: Improvement
Eric Norman created SLING-10437:
---
Summary: Move integration tests
Key: SLING-10437
URL: https://issues.apache.org/jira/browse/SLING-10437
Project: Sling
Issue Type: Improvement
-jcr-jackrabbit-accessmanager/commit/fc200f8fa18d1751cfdb4b1013ce0fee055e06fe]
> Move integration tests
> --
>
> Key: SLING-10436
> URL: https://issues.apache.org/jira/browse/SLING-10436
> Project: Sling
>
-jcr-jackrabbit-usermanager/commit/9e8abdef9a29c51f45b5d69339907f8127e91b46]
> Move integration tests
> --
>
> Key: SLING-10437
> URL: https://issues.apache.org/jira/browse/SLING-10437
> Project: Sling
>
are setting up the HTTP client in
{{UserManagerClientTestSupport}} and I think we could move that logic to the
testing-paxexam module. Created SLING-10445 for that.
> Move integration tests
> --
>
> Key: SLING-10437
> URL: https://iss
Oliver Lietz created SLING-7923:
---
Summary: Simplify integration tests
Key: SLING-7923
URL: https://issues.apache.org/jira/browse/SLING-7923
Project: Sling
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/SLING-7337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz closed SLING-7337.
---
> Add integration tests
> -
>
> Key
> Simplify integration tests
> --
>
> Key: SLING-7923
> URL: https://issues.apache.org/jira/browse/SLING-7923
> Project: Sling
> Issue Type: Improvement
> Components: JCR
>
bnd Maven plugins
* make initial content bundle an option
* use resource presence to wait for installed content
was:
* remove boilerplate code and use Testing PaxExam instead
* use Sling Parent 34 and bnd Maven plugins
> Simplify integration te
[
https://issues.apache.org/jira/browse/SLING-7923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-7923.
-
Resolution: Done
> Simplify integration te
Oliver Lietz created SLING-7337:
---
Summary: Add integration tests
Key: SLING-7337
URL: https://issues.apache.org/jira/browse/SLING-7337
Project: Sling
Issue Type: Task
Components
[
https://issues.apache.org/jira/browse/SLING-7337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-7337.
-
Resolution: Done
> Add integration tests
> -
>
>
> [INFO] Apache Sling RepoInit Integration Tests ... FAILURE [4.379s]
> [ERROR] Failed to execute goal on project org.apache.sling.repoinit.it: Could
> not resolve dependencies for project
> org.apache.sling:org.apache.sling.repoinit.it:slingstart:0.0.1-SNAPSHOT:
>
The SlingRepository Integration Tests (in
/bundles/jcr/it-jackrabbit-ok/) fails on a new system. I'm not sure
but I think the reason might be that JackrabbitRepositoryIT &
OakRepositoryIT contains the line
mavenBundle("org.apache.sling", "org.apache.sling.jcr.base"
Integration tests for authentication
Key: SLING-1786
URL: https://issues.apache.org/jira/browse/SLING-1786
Project: Sling
Issue Type: Test
Components: Authentication
Reporter
Hi,
On Fri, Nov 2, 2012 at 10:06 AM, Mike Müller wrote:
> ...The integration tests now fail, because the SortingServiceTracker could
> not be
> found in the released version of commons/osgi.
> Am I correct, that the only way to correct this is to release Commons OSGi
> bundle
1 - 100 of 2494 matches
Mail list logo
