How t configure Karaf to not look for newest SNAPSHOTs

Hi I have several bundles and features that are -SNAPSHOT versioned, residing in $HOME/.m2/repository (together with all the other bundles) Karaf (v3.0.8) should _not_ attempt to look for a newer version, but simply use what is there. Is this possible? I have

Re: How t configure Karaf to not look for newest SNAPSHOTs

Hi Martin, you can configure local repository as remote and remove the @snapshot flag. Then it will only consider release. Regards JB On 09/16/2016 08:16 AM, Martin Lichtin wrote: Hi I have several bundles and features that are -SNAPSHOT versioned, residing in $HOME/.m2/repository

Re: How t configure Karaf to not look for newest SNAPSHOTs

Hi, I assume he wants to configure the local repository as the only one that provides snapshots. So snapshots from .m2 are used, but no lookup for newer remote provided versions is done.

Re: How t configure Karaf to not look for newest SNAPSHOTs

Well, disabling snapshot repositories as indicated by JB should work. The default list looks like (in etc/org.ops4j.pax.url.mvn.cfg): http://repo1.maven.org/maven2@id=central, http://repository.springsource.com/maven/bundles/release@id=spring.ebr.release,

Re: How t configure Karaf to not look for newest SNAPSHOTs

Thank you all for the tips. Indeed in my case I can simply remove all repositories org.ops4j.pax.url.mvn.repositories= and this works very well to avoid any remote lookups. - Martin PS: Still baffling that "org.ops4j.pax.url.mvn.globalUpdatePolicy" has had no effect. Guillaume Nodet-2 wrote

Re: Karaf Cellar - updating a bundle in cluster

Thank you very much JB! Will it be available after push here: https://github.com/apache/karaf-cellar ? Or it will be other location? Kind regards Sergiy On Thu, 15 Sep 2016 15:24:44 +0200, Jean-Baptiste Onofré wrote: I will rebase & push. Regards JB On 09/15/2016

Re: Unable to use http://karaf.apache.org/xmlns/shell/v1.0.0

Hi, maybe it should be up to kotoole to attache something to the Jira. In my case, the error with http://karaf.apache.org/xmlns/shell/v1.0.0 says: org.xml.sax.SAXParseException; systemId: bundle://80.0:2/org/apache/karaf/shell/console/commands/karaf-shell-1.1.0.xsd; lineNumber: 28;

Re: configuration admin files with property references in the values: how's it done?

Never mind, I worked out for myself that fileinstall does the job. On Fri, Sep 16, 2016 at 11:17 AM, Benson Margulies wrote: > I've been asked to try an experiment in moving some of the code we run > in Karaf into a minimal Felix container deployment. I've run into one >

configuration admin files with property references in the values: how's it done?

I've been asked to try an experiment in moving some of the code we run in Karaf into a minimal Felix container deployment. I've run into one snag: Some of my .cfg files in Karaf take advantage of writing values that contain system property references, like ${karaf.etc}/something/something. I had