camel features:install bundle resolution problem

[heatlamp]

Just downloaded the binary distro of apache-servicemix-4.4.0-fuse-00-27 on windows, started it up (servicemix.bat), trying to install camel features, as noted here:  http://fusesource.com/docs/ide/camel/1.0/comp_guide/Intro-ComponentsList.htm. 

I'm seeing errors that bundles can't be found, for example

karaf@root> features:install camel-jetty

Error executing command: URL mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.commons-httpclient/3.1_4 could not be resolved.

karaf@root> features:install camel-http4

Error executing command: URL mvn:org.apache.httpcomponents/httpcore-osgi/4.1 could not be resolved.

Running jdk 1.6.

Anyone tell me what I might be doing wrong?

Thx, Jim

[heatlamp]

As this looks related to servicemix access to our local maven/nexus repository and to the net, I tried hardcoding settings.xml and  M2 repo locations in etc/org.ops4j.pax.url.mvn.cfg.

However this made no difference.

Still looking for any other input.

Thx,

Jim

[ffang]

Hi,

Yes, it's related to download artifacts remotely.

I guess the machine running ESB is behind the firewall and can only access your internal nexus, right, basically you need edit etc/org.ops4j.pax.url.mvn.cfg to add your nexus server. Could you elaborate how you configure the etc/org.ops4j.pax.url.mvn.cfg? And could you check if your nexus server is configured correctly which means it can download from external maven repo on demand?

Freeman

[heatlamp]

Thanks Freeman,

Confirming your suspicion, I've found that features install properly when I connect my laptop via VPN to the company's network, but not when connected directly to the intranet.    (Good excuse to work from home.)

However I do have internet connectivity from work, and I can paste the URL of the resource that couldn't be resolved into a browser and access that resource.   I can also access the nexus repo normally from in my Eclipse mvn camel project.

I tried

1) modifying org.ops4j.pax.url.mvn.localRepository to point directly to my local repo

2) modifying org.ops4j.pax.url.mvn.settings to point directly to my settings.xml

3) commenting out all of the addresses in org.ops4j.pax.url.mvn.repositories.

However I did not try adding the address of our nexus repo to the list in org.ops4j.pax.url.mvn.repositories, is this what you are suggesting?

Thanks again,

Jim

[ffang]

Hi,

Yes,  you just need add the address of your nexus repo to the list in org.ops4j.pax.url.mvn.repositories.

Freeman

[blackard]

So the /local-repo seems to be a hard coded local repository.  I have a local repository that I use for more than one project, and more than one version of ServiceMix that I'm testing.

Is this just something that's broken in 00-27 and will be fixed in a later release?

Thanks

Edited by: blackard on Jun 27, 2011 4:22 PM

[blackard]

I did a little more experimentation.  Could it be that variable substitution in 4.4 patch 00-27 has problems?  I replaced the $ environment variable (which on windows was defined as C:\Development\ProvingGround) with C:/Development/ProvingGround in the org.ops4j.pax.url.mvn.localRepository and everything seems to have started working.

Again, is this just a 00-27 issue that will be fixed in a later release?

[davsclaus]

Hi

Thanks for reporting. I have logged a ticket for the engineering team to look into this

http://fusesource.com/issues/browse/ESB-1499