Yep, I worked around it, unfortunately the new JClouds is causing some issues... Hawt.io doesn't seem to be working correctly either (can't find jolokia after installing the hawt-karaf feature), not sure why... ugh.
On Wed, May 28, 2014 at 10:58 AM, Jean-Baptiste Onofré <[email protected]>wrote: > Thanks Ryan, > > I will tackle that. > > As a workaround, you can update the location of jclouds (new > groupId/artifactId/etc) in etc/org.apache.karaf.features.repos.cfg. > > Regards > JB > > > On 05/28/2014 04:54 PM, Ryan Moquin wrote: > >> Sure, no prob! >> >> KARAF-3008 >> >> Ryan >> >> >> On Wed, May 28, 2014 at 12:43 AM, Achim Nierbeck >> <[email protected] <mailto:[email protected]>> wrote: >> >> Hi Ryan, >> >> Could you please open an issue for this. We can add it to the repo >> list. >> >> Regards, Achim >> >> sent from mobile device >> >> Am 27.05.2014 22 <tel:27.05.2014%2022>:57 schrieb "Ryan Moquin" >> <[email protected] <mailto:[email protected]>>: >> >> >> I just noticed that the JClouds features url has changed due to >> the promotion to a top level apache project. I had been >> wondering why when I installed JClouds in Karaf, I would only >> get 1.6.0, if I typed feature:repo-add jclouds. 1.7.2 wouldn't >> resolve. Looking in the main maven repo for jclouds, it looks >> like the latest releases are using the org.apache.jclouds groupId: >> >> *http://search.maven.org/#search%7Cga%7C1%7Cjclouds-karaf* >> * >> * >> *Ryan* >> >> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com >
