Mailing-List: contact user-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@karaf.apache.org
Mail-Followup-To: user@karaf.apache.org
To: user@karaf.apache.org
From: Steinar Bang <sb@dod.no>
Subject: Re: Karaf Feature vs. OBR
Date: Sun, 03 Sep 2017 11:35:36 +0200
Organization: Probably a good idea
Lines: 68
Message-ID: <86r2vof7kn.fsf@dod.no>
References: <03A43093-4908-433F-BEE9-945D36074F92@leangen.net>
	<CAA66Tpq3fvcrOar0eY=fHTMepW-J8vp1mhTJk6B3F4QwrrLM4Q@mail.gmail.com>
	<ED5B5E5E-BA56-4030-B039-84D1B368C38E@leangen.net>
	<upzc60fxqdzx.fsf@dod.no>
	<dfc2f06f-edf3-f708-0bbf-a01d27a6a781@nanthrax.net>
	<upzc1sqlqams.fsf@dod.no> <upzcshizq1ns.fsf@dod.no>
	<868thzh91q.fsf@dod.no>
	<CAA66Tposmm-3AOmG84+U98Ym4BtRVqmwXERoJqj0iuZqFER-1g@mail.gmail.com>
	<864lsnh0vu.fsf@dod.no>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (windows-nt)
Mail-Copies-To: never
Cancel-Lock: sha1:+djTe3DtXBToNgOrMwHCTfw3aGE=
archived-at: Sun, 03 Sep 2017 09:36:53 -0000

>>>>> Steinar Bang <sb@dod.no>:
>>>>> Guillaume Nodet <gnodet@apache.org>:

>> Fwiw, bundle:watch is very specific and only check the local repository,=
 so
>> it won't work if you upload a new snapshot on a remote repository.

> I was sort of hoping it would work for a different maven repo in the
> local file system, which is what I currently have.

I tried one (actually two experiments):
 1. Made the repository deployed to by travis-ci karaf's local
    repository.=20
    Using the same local repository as maven builds worked when I tried
    it out on my development machine (after I had made the repository
    writable by karaf).
    But it failed when using the repository deployed to by travis-ci on
    my production machine, because karaf was unable to recognize the
    deployed snapshots as snapshots in the local repository (actual
    repositories have a different snapshot structure to the local
    repository)

 2. Since I was in experimentation mode I tried making the repository
    are both the local repository and added it as a repository, like so:
     config:edit org.ops4j.pax.url.mvn
     config:property-set org.ops4j.pax.url.mvn.localRepository /var/www-mav=
en/repository
     config:property-append org.ops4j.pax.url.mvn.repositories ", file:///v=
ar/www-maven/repository, http://maven.vaadin.com/vaadin-addons"
     config:update

    But this made karaf terribly confused:
     karaf@root()> feature:repo-add mvn:no.priv.bang.ukelonn/ukelonn.karaf/=
LATEST/xml/featuresAdding feature url mvn:no.priv.bang.ukelonn/ukelonn.kara=
f/LATEST/xml/features
     Error executing command: Error resolving artifact no.priv.bang.ukelonn=
:ukelonn.karaf:xml:features:1.0.0-SNAPSHOT: [Could not transfer artifact no=
.priv.bang.ukelonn:ukelonn.karaf:xml:features:1.0.0-SNAPSHOT from/to repo_1=
276108016 (http://artifactory.lampiris.be/remote-repos/): artifactory.lampi=
ris.be, Could not find artifact no.priv.bang.ukelonn:ukelonn.karaf:xml:feat=
ures:1.0.0-SNAPSHOT in apache (http://repository.apache.org/content/groups/=
snapshots-group/), Could not find artifact no.priv.bang.ukelonn:ukelonn.kar=
af:xml:features:1.0.0-SNAPSHOT in sonatype.snapshots.deploy (https://oss.so=
natype.org/content/repositories/snapshots/), Could not find artifact no.pri=
v.bang.ukelonn:ukelonn.karaf:xml:features:1.0.0-SNAPSHOT in ops4j.sonatype.=
snapshots.deploy (https://oss.sonatype.org/content/repositories/ops4j-snaps=
hots/), Could not find artifact no.priv.bang.ukelonn:ukelonn.karaf:xml:feat=
ures:1.0.0-SNAPSHOT in spring-ebr-repository (http://repository.springsourc=
e.com/maven/bundles/external/)] : mvn:no.priv.bang.ukelonn/ukelonn.karaf/LA=
TEST/xml/features
     karaf@root()>

(I didn't expect the second experiement to work. I just tried it out to
see what would happen...:-) )

So now I'm back to running with the https-URL pointing to the travis-ci
deployment repository added to the mvn.repositories setting:
 config:edit org.ops4j.pax.url.mvn
 config:property-append org.ops4j.pax.url.mvn.repositories ", https://maven=
.bang.priv.no/repository/@snapshots, http://maven.vaadin.com/vaadin-addons"
 config:property-set org.ops4j.pax.url.mvn.globalUpdatePolicy always
 config:update

So, no success yet at totally automating the deployment from a
travis-ci build.=20=20

I still need to to "bundle:update" from the karaf console on each bundle
I want updated after a new snapshot has been added.