Hi, it's "as karaf", so basically, it uses your .m2/repository by default and then goes into the repository in etc/org.ops4j.pax.url.mvn.cfg.
So, you have to use PaxExam Configuration to add the staging repo there. I don't have such issue locally because I'm building Karaf based on the tag. Regards JB On 08/06/2019 18:46, Eric Lilja wrote: > Ah, when doing some more testing I noticed my Pax Exam tests using Karaf do > not work, because some artifacts cannot be resolved (I believe > org.apache.karaf.scr.management was among them). I updated my maven > settings to use the staging repository (both for repository and > pluginRepository) and at build-time I can resolve artifacts without issue), > but I believe I need to tweak my Pax Exam test to also use the staging > repository. So it's a little more involved to evaluate Karaf since I also > have to tweak my Pax Exam tests, it's not just simply adding staging > repository to Maven's setting.xml. Maybe someone has some tips about that? > Basically I want Pax Exam to use repository setup from my settings.xml, I > don't want to duplicate that information in Pax Exam itself. I'm sure > others are using Pax Exam too, how do you manage repository information? > > - Eric L > > On Sat, Jun 8, 2019 at 1:06 AM Eric Lilja <mindcoo...@gmail.com> wrote: > >> +1 (non-binding) >> >> - Eric Lilja >> >> On Fri, Jun 7, 2019 at 10:54 PM Robert Varga <n...@hq.sk> wrote: >> >>> On 07/06/2019 13:13, Jean-Baptiste Onofré wrote: >>>> Hi all, >>>> >>>> I submit Apache Karaf (runtime) 4.2.6 to your vote. This is a >>>> maintenance release on the 4.2.x series, bringing some improvements and >>>> bug fixes (scr with equinox, dependencies updates, and much more !). >>>> >>>> Release Notes: >>>> >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140&version=12345365 >>>> >>>> Staging Repository: >>>> https://repository.apache.org/content/repositories/orgapachekaraf-1132/ >>>> >>>> Git Tag: >>>> karaf-4.2.6 >>>> >>>> Please vote to approve this release: >>>> >>>> [ ] +1 Approve the release >>>> [ ] -1 Don't approve the release (please provide specific comments) >>> >>> +1, non-binding, based on very basic validation with OpenDaylight. >>> >>> One question: pax-web-features-7.2.10 still references >>> commons-beanutils/1.8.3, which trips up vuln scanners, is this >>> intentional? >>> >>> Thanks, >>> Robert >>> >> > -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
