maven repo settings when using profiles

[mroslyak]

Hi.

I am having a strange problem deploying our code as features as part of profiles.

If I try to deploy features without fabric, everything works great, if I update

org.ops4j.pax.url.mvn.cfg to include our maven repository.

When I create a profile, add features to it,  and try to apply it to a container, I get an error "error - java.io.IOException: Error downloading mvn..."

in the log I see that features are trying to be installed form my local ~/.m2/repository

which are not there.

Do I need to specify additional settings in a profile?

Also, Fuse management Console finds the features while configuring a profile,

and fails trying to apply it to a container.

Thanks

[iocanel]

The fabric-agent which is responsible to "apply" the profile to your container, will use the maven repositories defined in: org.fusesource.fabric.agent pid using the org.ops4j.pax.url.mvn.repositories key.

So you should just edit the profile using the profile-edit command (or via fmc) to add the target repository:

fabric:profile-edit --append --pid org.fusesource.fabric.agent/org.ops4j.pax.url.mvn.repositories=http://my.repo.url default

In the example above I added that to the default profile so all profiles can inherit from it.

If you provide some details on the failure (when using fmc), I could possibly help you get through it.

[mroslyak]

Thanks

That was it.