Provisioning vs. Felix Fileinstaller

2013-05-13 Thread Michael Prieß
Hi, actually I use features to deploy all my OSGi bundles. But to initialize some infrastructure for example an embedded broker I use 2-3 Spring XML files which are located in the deploy directory. Now I have the following behavior: The Spring XML files are deployed before the provisioning happen

Re: Deploy into deployment directory

2013-02-04 Thread Michael Prieß
those artifacts are already deployed. > > regards, Achim > > > 2013/2/4 Michael Prieß >> >> Hi, >> >> is it possible to choose a deployment directory with the install command? >> >> What I miss is something like: >> >> install mvn:com

Deploy into deployment directory

2013-02-04 Thread Michael Prieß
Hi, is it possible to choose a deployment directory with the install command? What I miss is something like: install mvn:com.foo/my-route/1.8.3/xml $KARAF_DEPLOY I like it to have all routes in the deployment directory. Regards, Michael

Re: Web application development using unpacked WAR

2012-07-30 Thread Michael Prieß
x27;t find the Web-ContextPath inside the manifest header. (Karaf 2.2.8) Regards, Michael 2012/7/30 helander : > Michael, > > there is no OSGI manifest (it's a "standard" WAR ). > What do you mean by the "command headers ID"? > Which Felix plugin? > >

Re: Web application development using unpacked WAR

2012-07-30 Thread Michael Prieß
Seems like there is a problem with the symbolic name. Could you please attach the exploded OSGi manifest, the output of the command headers ID and the configuration of the felix plugin? Cheers, Michael 2012/7/30 helander : > I have created a Jira: > > https://issues.apache.org/jira/browse/KARAF

Re: Fetching feature from a nexus repository

2011-11-15 Thread Michael Prieß
Hi, a slash before my repository definition was the mistake. Thanks for your help. Cheers, Michael

Re: Fetching feature from a nexus repository

2011-11-15 Thread Michael Prieß
entral when it's present locally, correct ? > > Could you check in your Nexus log if the repository is able to get the > artifacts from central (maybe a firewall configuration missing between your > Nexus and the Central) ? > > Regards > JB > > On 11/15/2011 0

Re: Fetching feature from a nexus repository

2011-11-15 Thread Michael Prieß
is 60 seconds: > >        private static final int MAVEN_TIMEOUT = 6; > > Do you think it was longer ? > > Regards > JB > > On 11/15/2011 02:09 PM, Michael Prieß wrote: >> >> Hi, >> >> requesting the jar with wget works, but the response need a l

Re: Fetching feature from a nexus repository

2011-11-15 Thread Michael Prieß
t the wrapper jar file. > > Could you try a simple wget or curl from where Karaf is installed and check > that you can get the file ? > I had something similar, but due to a HTTP proxy. > > Regards > JB > > On 11/15/2011 01:55 PM, Michael Prieß wrote: >> >

Re: Fetching feature from a nexus repository

2011-11-15 Thread Michael Prieß
epo > basically) > - second, check in your .m2/repository > - finally, check in the repositories defined in the PAX URL property > > Could you check in your local repo ? > Do you use a proxy to access your local maven repo ? > > Regards > JB > > On 11/15/2011 01:23

Re: Fetching feature from a nexus repository

2011-11-15 Thread Michael Prieß
raf.shell.wrapper jar file in your > m2 local folder ? I bet it's not a jar file (a HTML one for instance). > > Regards > JB > > On 11/15/2011 01:02 PM, Michael Prieß wrote: >> >> Hello, >> >> my Karaf Installation is behind a Firewall, so I have to us

Fetching feature from a nexus repository

2011-11-15 Thread Michael Prieß
Hello, my Karaf Installation is behind a Firewall, so I have to use my own Maven Repository in the same subnet (Nexus) to fetch the wrapper feature from my nexus. So I changed the file org.ops4j.pax.url.mvn.cfg, uncommented the other repository and added my repository: org.ops4j.pax.url.mvn.repo

Race between Features and Spring/Blueprint XML

2011-03-09 Thread Michael Prieß
Hi all, i like to deploy camel-routes and features inside the deploy directory. A deployment look like the following: - a feature.xml which contain bundles like Apache Camel, Spring with a start level definition. - and many xml camel-routes which contain configurations for my components. Now i