Using our artifactory instead of the Fuse maven repo

[djbza1]

Hi,

I'm in Fuse 6.2.1.  I use Jenkins/Artifactory currently.

I have a conceptual block in the intended workflow for deploying bundles into a fabric container.

So currently I have all my bundles in the /deploy folder.  Now I want to add some load balancing for hot deployment of newer versions of bundles.

To get gateway-http profile though, I need to be running in a fabric ensemble, instead of a standalone, it seems, since none of the fabric:commands are available until you create a fabric.

I've managed to create the fabric, create a child container, edit a profile in the hawtio UI, and change the child container to use that profile.

But it doesn't show any of the /deploy apps in the osgi:list.  My goal is now to deploy my bunde jars to this child container.

I see there's a drag and drop place in the hawtio UI.  So I try that.  But I get:

ArtifactNotFoundException: Could not find artifact my.company:App:jar:4.0.2 in karaf-default (file:/opt/fuse/system/)

As far as I can tell, Fuse is looking in its own maven repo.  My poms build the jars into Artifactory.  Totally different repo.

So how do I get Fuse to look in my Artifactory?

Is this possible?  Is this correct?  Is this really how it's meant to be done?  Is there not a way to just configure a profile to use the contents of a directory like /deploy or something? 

Seems like a lot of configuration on a running system. Ideally, since this is in a docker container, I would be able to set up the whole Fuse, and just map the deploy directory and be done with it. 

Regards

Daniel

[grgrzybek]

Hello

In standalone mode, all maven access is performed using pax-url-aether library. In fabric mode, the same happens via fabric-maven.

There's much new information about Maven in official Fuse docs, but also you can check:

- http://ggrzybek.blogspot.com/2016/07/using-maven-with-osgi-part-1.html (Aether information)

- http://ggrzybek.blogspot.com/2016/07/using-maven-with-osgi-part-2.html (Configuration of pax-url-aether)

- http://ggrzybek.blogspot.com/2016/10/using-maven-with-osgi-part-3.html (SNAPSHOT handling)

To give you a quick summary, if you want to add your external Artifactory server (actually it's recommended approach if you have several fabric containers), please add its URL to io.fabric8.agent PID, org.ops4j.pax.url.mvn.repositories property. You can add it via hawtio or using OSGi command:

profile-edit --pid io.fabric8.agent/org.ops4j.pax.url.mvn.repositories=http://my.artifactory.com:PORT/xyz default

you can also use --append option for the above command, but actually it's better to use hawtio - you can adjust the default settings to your needs.

regards

Grzegorz Grzybek

[djbza1]

Thanks Grzegorz,

but I'm still getting an error.

I've added my artifactory repos

org.ops4j.pax.url.mvn.repositories= \

    http://repo1.maven.org/maven2@id=maven.central.repo, \

    http://repository.jboss.org/nexus/content/repositories/public@id=jboss.public.repo, \

    https://repo.fusesource.com/nexus/content/repositories/releases@id=fusesource.release.repo, \

    https://repo.fusesource.com/nexus/content/groups/ea@id=fusesource.ea.repo, \

    http://svn.apache.org/repos/asf/servicemix/m2-repo@id=servicemix.repo, \

    http://repository.springsource.com/maven/bundles/release@id=springsource.release.repo, \

    http://repository.springsource.com/maven/bundles/external@id=springsource.external.repo, \

http://10.20.2.21:8081/artifactory/libs-release, \

http://10.20.2.21:8081/artifactory/libs-snapshot, \

http://10.20.2.21:8081/artifactory/all-local, \

http://10.20.2.21:8081/artifactory/plugins-release, \

http://10.20.2.21:8081/artifactory/plugins-snapshot, \

http://10.20.2.21:8081/artifactory/plugins-release

But it still just searches the local repos.  Doesn't bother with mine.

The log:display says:

java.io.IOException: Error resolving artifact my.company:authorizationService:jar:4.0.2: Could not find artifact my.company:authorizationService:jar:4.0.2 in karaf-default (file:/opt/fuse/system/)

and hawtio has a similar, but URL style error:

Caused by: java.io.IOException: Error resolving artifact my.company:authorizationService:jar:4.0.2: Could not find artifact my.company:authorizationService:jar:4.0.2 in repo_1511216736 (http://10.20.30.46:8181/maven/download/)

It's just ignoring my remote repo settings?

Any idea?

Thanks

Daniel

[grgrzybek]

Hello Daniel

io.fabric8.agent PID and org.ops4j.pax.url.mvn.repositories property is used by fabric-agent to provision the container.

The list of remote repositories from this property is prepended with a list of fabric-mavaen-proxy repositories that registered itself in ZooKeeper registry. So agent actually first asks fabric-maven-proxy (you can see its url in the error message: "Could not find artifact my.company:authorizationService:jar:4.0.2 in repo_1511216736 (http://10.20.30.46:8181/maven/download/)").

That means that the fabric-maven-proxy can't find the artifact. You can always try invoking:

curl -v http://10.20.30.46:8181/maven/download/my/company/authorizationService/4.0.2/authorizationService-4.0.2.jar

fabric-maven-proxy uses relevant configuration from io.fabric8.maven PID and io.fabric8.maven.repositories property, which by default points to io.fabric8.agent PID and org.ops4j.pax.url.mvn.repositories property - but please check it.

I suggest increasing Maven-related logging as well:

profile-edit --pid org.ops4j.pax.logging/log4j.logger.org.eclipse.aether=TRACE karaf profile-edit --pid org.ops4j.pax.logging/log4j.logger.org.apache.http.headers=DEBUG karaf profile-edit --pid org.ops4j.pax.logging/log4j.logger.io.fabric8.maven.util=TRACE karaf profile-edit --pid org.ops4j.pax.logging/log4j.logger.io.fabric8.maven.url=TRACE karaf profile-edit --pid org.ops4j.pax.logging/log4j.logger.io.fabric8.agent.download=DEBUG karaf

this way you'll see in logs which repositories are actually being contacted.

regards

Grzegorz Grzybek