Re: commons-logging needed for commons-configuration feature
Hello Ioannis, Thanks. I am suspecting a problem with different plugin configurations/versions in pluginsManagement in parent pom and plugins in pom. There was also an issue with builds.apache.org not building OSGi bundles (a bug, which seems fixed now). This made debugging harder. I'll check it over the weekend again. Cheers, -- Ioan Eugen Stan / CTO / http://axemblr.com
Re: Karaf Cellar 3.0.0 SNAPSHOT
Hi Ryan, yes, I started to work on both Cellar 2.3.x and trunk yesterday. It should be better by the end of this week. Regards JB On 01/16/2013 05:12 AM, Ryan Moquin wrote: I know I was told that this version isn't stable yet, but I still wanted to see if the build should be able to complete successfully or not. I want to determine if some issues I'm having are something on my end or not. Currently the itests always seem to fail with cellar trunk, is that the current known state of it? Or is it failing on my side only? Thanks, Ryan -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Karat wont start bundle with start-level 99 ??
I just happen to change some of my bundle to start at level 100 and the bundle get 'installed' state and would not go to 'active'. No error found in log. Can some one confirm? May karaf is 2.3.0 Thanks -Dan
Re: Karat wont start bundle with start-level 99 ??
Hi Dan, We have an issue about Aries Blueprint in Karaf 2.3.0. Your bundles are blueprint bundles ? I saw the issue randomly with Karaf sshd and management blueprint bundles for instance. A fix has been performed in Aries, I submitted another patch to be able to work with Blueprint CM and the new Blueprint Core version. Regards JB On 01/16/2013 08:14 PM, Dan Tran wrote: I just happen to change some of my bundle to start at level 100 and the bundle get 'installed' state and would not go to 'active'. No error found in log. Can some one confirm? May karaf is 2.3.0 Thanks -Dan -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Karat wont start bundle with start-level 99 ??
That's expecte because the start level of the framework is set to 100. You can change that in etc/config.properties iirc. On Wed, Jan 16, 2013 at 8:14 PM, Dan Tran dant...@gmail.com wrote: I just happen to change some of my bundle to start at level 100 and the bundle get 'installed' state and would not go to 'active'. No error found in log. Can some one confirm? May karaf is 2.3.0 Thanks -Dan -- Guillaume Nodet Blog: http://gnodet.blogspot.com/ FuseSource, Integration everywhere http://fusesource.com
Re: Karat wont start bundle with start-level 99 ??
Yes, I am seeing 2 properties under config.properties org.osgi.framework.startlevel.beginning=100 karaf.startlevel.bundle=80 It would be nice if those 2 are documented in the config file so that other user may able to figure out the issue when the same problem encounter. May be org.osgi.framework.startlevel.beginning should start with higher number so that karaf user would have a longer range to work with? Thanks -D On Wed, Jan 16, 2013 at 11:31 AM, Guillaume Nodet gno...@gmail.com wrote: That's expecte because the start level of the framework is set to 100. You can change that in etc/config.properties iirc. On Wed, Jan 16, 2013 at 8:14 PM, Dan Tran dant...@gmail.com wrote: I just happen to change some of my bundle to start at level 100 and the bundle get 'installed' state and would not go to 'active'. No error found in log. Can some one confirm? May karaf is 2.3.0 Thanks -Dan -- Guillaume Nodet Blog: http://gnodet.blogspot.com/ FuseSource, Integration everywhere http://fusesource.com
Re: Karat wont start bundle with start-level 99 ??
yes i am using blueprint for all of our bundle -D On Wed, Jan 16, 2013 at 11:18 AM, Jean-Baptiste Onofré j...@nanthrax.net wrote: Hi Dan, We have an issue about Aries Blueprint in Karaf 2.3.0. Your bundles are blueprint bundles ? I saw the issue randomly with Karaf sshd and management blueprint bundles for instance. A fix has been performed in Aries, I submitted another patch to be able to work with Blueprint CM and the new Blueprint Core version. Regards JB On 01/16/2013 08:14 PM, Dan Tran wrote: I just happen to change some of my bundle to start at level 100 and the bundle get 'installed' state and would not go to 'active'. No error found in log. Can some one confirm? May karaf is 2.3.0 Thanks -Dan -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Can not login into karaf-webconsole on Karaf 2.3.0 and 2.2.10
Hey Krzysztof, Yeah, 2.3.0 and 2.2.10 contains change which is not backward compatible: KARAF-1305. I belive it should not happen in 2.2.x branch. Anyway, I'll review your patches and start necessary branches for webconsole to support current Karaf releases. Best regards, Lukasz Wiadomość napisana przez Krzysztof Sobkowiak w dniu 16 sty 2013, o godz. 01:46: Hi To solve the problem with itest with karaf.version 2.3.0 I have attached a patch upgrading the itests to PAX Exam 2.6.0 and PAX Exam Karaf Best regards Krzysztof -- Apache Karaf http://karaf.apache.org/ Committer PMC OPS4J Pax Web http://wiki.ops4j.org/display/paxweb/Pax+Web/ Committer Project Lead OPS4J Pax for Vaadin http://team.ops4j.org/wiki/display/PAXVAADIN/Home Commiter Project Lead blog http://notizblog.nierbeck.de/
Re: Orderly shutting down services
Hi Dan, did you try both with Karaf 2.2.x and 2.3.x ? did you see differences in the behavior ? Regards JB On 01/16/2013 09:17 PM, Dan Tran wrote: Hi I have a service's PreDestroy method which requires a service from other bundle during shutdown. However at shutdown time, blueprint make the required service 'unavailable'. Using start level ordering does not seem to help. What are your experiences dealing with this issue? Big thanks ahead. -Dan -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Can not login into karaf-webconsole on Karaf 2.3.0 and 2.2.10
Hi, We discussed about this with Achim (he's the author of the changes). He proposed to rollback his change in Karaf 2.2.x. Regards JB On 01/16/2013 09:18 PM, Łukasz Dywicki wrote: Hey Krzysztof, Yeah, 2.3.0 and 2.2.10 contains change which is not backward compatible: KARAF-1305. I belive it should not happen in 2.2.x branch. Anyway, I'll review your patches and start necessary branches for webconsole to support current Karaf releases. Best regards, Lukasz Wiadomość napisana przez Krzysztof Sobkowiak w dniu 16 sty 2013, o godz. 01:46: Hi To solve the problem with itest with karaf.version 2.3.0 I have attached a patch upgrading the itests to PAX Exam 2.6.0 and PAX Exam Karaf Best regards Krzysztof -- Apache Karaf http://karaf.apache.org/ Committer PMC OPS4J Pax Web http://wiki.ops4j.org/display/paxweb/Pax+Web/ Committer Project Lead OPS4J Pax for Vaadin http://team.ops4j.org/wiki/display/PAXVAADIN/Home Commiter Project Lead blog http://notizblog.nierbeck.de/ -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Orderly shutting down services
Hi JB, I only try 2.3, my new work does not work with 2.2 what is osgi/karaf shutdown sequencing flow? like it would shutdown all bundles with the same start- level in the order from high to low ? Thanks -D On Wed, Jan 16, 2013 at 12:18 PM, Jean-Baptiste Onofré j...@nanthrax.net wrote: Hi Dan, did you try both with Karaf 2.2.x and 2.3.x ? did you see differences in the behavior ? Regards JB On 01/16/2013 09:17 PM, Dan Tran wrote: Hi I have a service's PreDestroy method which requires a service from other bundle during shutdown. However at shutdown time, blueprint make the required service 'unavailable'. Using start level ordering does not seem to help. What are your experiences dealing with this issue? Big thanks ahead. -Dan -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Can not login into karaf-webconsole on Karaf 2.3.0 and 2.2.10
Yeah my bad, sorry for this. I'm going to open a new issue for this and will fix it for 2.2.x sent from tablet Am 16.01.2013 21:20 schrieb Jean-Baptiste Onofré j...@nanthrax.net: Hi, We discussed about this with Achim (he's the author of the changes). He proposed to rollback his change in Karaf 2.2.x. Regards JB On 01/16/2013 09:18 PM, Łukasz Dywicki wrote: Hey Krzysztof, Yeah, 2.3.0 and 2.2.10 contains change which is not backward compatible: KARAF-1305. I belive it should not happen in 2.2.x branch. Anyway, I'll review your patches and start necessary branches for webconsole to support current Karaf releases. Best regards, Lukasz Wiadomość napisana przez Krzysztof Sobkowiak w dniu 16 sty 2013, o godz. 01:46: Hi To solve the problem with itest with karaf.version 2.3.0 I have attached a patch upgrading the itests to PAX Exam 2.6.0 and PAX Exam Karaf Best regards Krzysztof -- Apache Karaf http://karaf.apache.org/ Committer PMC OPS4J Pax Web http://wiki.ops4j.org/**display/paxweb/Pax+Web/http://wiki.ops4j.org/display/paxweb/Pax+Web/ Committer Project Lead OPS4J Pax for Vaadin http://team.ops4j.org/wiki/**display/PAXVAADIN/Homehttp://team.ops4j.org/wiki/display/PAXVAADIN/Home Commiter Project Lead blog http://notizblog.nierbeck.de/** -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Can not login into karaf-webconsole on Karaf 2.3.0 and 2.2.10
Many thanks for quick response. This rollback will make versioning of dependant projects easier! Cheers, Lukasz -- l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-house.org Wiadomość napisana przez Achim Nierbeck w dniu 16 sty 2013, o godz. 22:01: Yeah my bad, sorry for this. I'm going to open a new issue for this and will fix it for 2.2.x sent from tablet Am 16.01.2013 21:20 schrieb Jean-Baptiste Onofré j...@nanthrax.net: Hi, We discussed about this with Achim (he's the author of the changes). He proposed to rollback his change in Karaf 2.2.x. Regards JB On 01/16/2013 09:18 PM, Łukasz Dywicki wrote: Hey Krzysztof, Yeah, 2.3.0 and 2.2.10 contains change which is not backward compatible: KARAF-1305. I belive it should not happen in 2.2.x branch. Anyway, I'll review your patches and start necessary branches for webconsole to support current Karaf releases. Best regards, Lukasz Wiadomość napisana przez Krzysztof Sobkowiak w dniu 16 sty 2013, o godz. 01:46: Hi To solve the problem with itest with karaf.version 2.3.0 I have attached a patch upgrading the itests to PAX Exam 2.6.0 and PAX Exam Karaf Best regards Krzysztof -- Apache Karaf http://karaf.apache.org/ Committer PMC OPS4J Pax Web http://wiki.ops4j.org/display/paxweb/Pax+Web/ Committer Project Lead OPS4J Pax for Vaadin http://team.ops4j.org/wiki/display/PAXVAADIN/Home Commiter Project Lead blog http://notizblog.nierbeck.de/ -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Karat wont start bundle with start-level 99 ??
Well, originally, it karaf.startlevel.bundle was at 50, and for some reasons, it kept increasing over time. I think 100 start levels is good enough, but we should lower from 80 back to 50, which would give more room for users. On Wed, Jan 16, 2013 at 9:01 PM, Dan Tran dant...@gmail.com wrote: Yes, I am seeing 2 properties under config.properties org.osgi.framework.startlevel.beginning=100 karaf.startlevel.bundle=80 It would be nice if those 2 are documented in the config file so that other user may able to figure out the issue when the same problem encounter. May be org.osgi.framework.startlevel.beginning should start with higher number so that karaf user would have a longer range to work with? Thanks -D On Wed, Jan 16, 2013 at 11:31 AM, Guillaume Nodet gno...@gmail.com wrote: That's expecte because the start level of the framework is set to 100. You can change that in etc/config.properties iirc. On Wed, Jan 16, 2013 at 8:14 PM, Dan Tran dant...@gmail.com wrote: I just happen to change some of my bundle to start at level 100 and the bundle get 'installed' state and would not go to 'active'. No error found in log. Can some one confirm? May karaf is 2.3.0 Thanks -Dan -- Guillaume Nodet Blog: http://gnodet.blogspot.com/ FuseSource, Integration everywhere http://fusesource.com -- Guillaume Nodet Blog: http://gnodet.blogspot.com/ FuseSource, Integration everywhere http://fusesource.com
Re: Karat wont start bundle with start-level 99 ??
The way the start level service is that when the framework boots, it goes from 0 to the value specified by org.osgi.framework.startlevel.beginning. At each level, the start level service will start bundles on that level. I think the default value is 1 if not otherwise specified. On Wed, Jan 16, 2013 at 10:57 PM, Dan Tran dant...@gmail.com wrote: I understand that when user does not specify the start-level of a bundle in the feature file, it is default to the value of karaf.startlevel.bundle ( which is 80) However, what is the purpose of org.osgi.framework.startlevel.beginning ?? ( max start-level allowed? ) Thanks -Dan On Wed, Jan 16, 2013 at 1:49 PM, Jean-Baptiste Onofré j...@nanthrax.net wrote: To be honest, I don't remember why we increased the Karaf start level. Let me dig in the Jira/e-mails ;) Regards JB On 01/16/2013 10:47 PM, Guillaume Nodet wrote: Well, originally, it karaf.startlevel.bundle was at 50, and for some reasons, it kept increasing over time. I think 100 start levels is good enough, but we should lower from 80 back to 50, which would give more room for users. On Wed, Jan 16, 2013 at 9:01 PM, Dan Tran dant...@gmail.com mailto:dant...@gmail.com wrote: Yes, I am seeing 2 properties under config.properties org.osgi.framework.startlevel.beginning=100 karaf.startlevel.bundle=80 It would be nice if those 2 are documented in the config file so that other user may able to figure out the issue when the same problem encounter. May be org.osgi.framework.startlevel.beginning should start with higher number so that karaf user would have a longer range to work with? Thanks -D On Wed, Jan 16, 2013 at 11:31 AM, Guillaume Nodet gno...@gmail.com mailto:gno...@gmail.com wrote: That's expecte because the start level of the framework is set to 100. You can change that in etc/config.properties iirc. On Wed, Jan 16, 2013 at 8:14 PM, Dan Tran dant...@gmail.com mailto:dant...@gmail.com wrote: I just happen to change some of my bundle to start at level 100 and the bundle get 'installed' state and would not go to 'active'. No error found in log. Can some one confirm? May karaf is 2.3.0 Thanks -Dan -- Guillaume Nodet Blog: http://gnodet.blogspot.com/ FuseSource, Integration everywhere http://fusesource.com -- Guillaume Nodet Blog: http://gnodet.blogspot.com/ FuseSource, Integration everywhere http://fusesource.com -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Guillaume Nodet Blog: http://gnodet.blogspot.com/ FuseSource, Integration everywhere http://fusesource.com
Re: Can not login into karaf-webconsole on Karaf 2.3.0 and 2.2.10
Thanks Achim ! Regards JB On 01/16/2013 11:21 PM, Achim Nierbeck wrote: it's https://issues.apache.org/jira/browse/KARAF-2120 and I'm taking care of it 2013/1/16 Łukasz Dywicki l...@code-house.org mailto:l...@code-house.org Many thanks for quick response. This rollback will make versioning of dependant projects easier! Cheers, Lukasz -- l...@code-house.org mailto:l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-house.org Wiadomość napisana przez Achim Nierbeck w dniu 16 sty 2013, o godz. 22:01: Yeah my bad, sorry for this. I'm going to open a new issue for this and will fix it for 2.2.x sent from tablet Am 16.01.2013 21:20 schrieb Jean-Baptiste Onofré j...@nanthrax.net mailto:j...@nanthrax.net: Hi, We discussed about this with Achim (he's the author of the changes). He proposed to rollback his change in Karaf 2.2.x. Regards JB On 01/16/2013 09:18 PM, Łukasz Dywicki wrote: Hey Krzysztof, Yeah, 2.3.0 and 2.2.10 contains change which is not backward compatible: KARAF-1305. I belive it should not happen in 2.2.x branch. Anyway, I'll review your patches and start necessary branches for webconsole to support current Karaf releases. Best regards, Lukasz Wiadomość napisana przez Krzysztof Sobkowiak w dniu 16 sty 2013, o godz. 01:46: Hi To solve the problem with itest with karaf.version 2.3.0 I have attached a patch upgrading the itests to PAX Exam 2.6.0 and PAX Exam Karaf Best regards Krzysztof -- Apache Karaf http://karaf.apache.org/ Committer PMC OPS4J Pax Web http://wiki.ops4j.org/__display/paxweb/Pax+Web/ http://wiki.ops4j.org/display/paxweb/Pax+Web/ Committer Project Lead OPS4J Pax for Vaadin http://team.ops4j.org/wiki/__display/PAXVAADIN/Home http://team.ops4j.org/wiki/display/PAXVAADIN/Home Commiter Project Lead blog http://notizblog.nierbeck.de/__ -- Jean-Baptiste Onofré jbono...@apache.org mailto:jbono...@apache.org http://blog.nanthrax.net http://blog.nanthrax.net/ Talend - http://www.talend.com http://www.talend.com/ -- Apache Karaf http://karaf.apache.org/ Committer PMC OPS4J Pax Web http://wiki.ops4j.org/display/paxweb/Pax+Web/ Committer Project Lead OPS4J Pax for Vaadin http://team.ops4j.org/wiki/display/PAXVAADIN/Home Commiter Project Lead blog http://notizblog.nierbeck.de/ -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Karaf RPMs - what options are out there?
Jamie,
Once you're clear on the methodology, I will volunteer test it for the
project in CentOS 6.3 (building it, then deploying it as an RPM package).
On 1/16/2013 12:39 AM, jgoodyear [via Karaf] wrote:
The concept of providing an RPM/Deb release option is perfectly fine
from my POV, this would require opening issues in Jira to add these
release targets. A quick search turns up a Maven rpm plugin
(http://mojo.codehaus.org/rpm-maven-plugin/) that may be used to keep
our release process streamlined. There may be other methodologies
available that we should consider as well
(http://www.rpm.org/max-rpm-snapshot/rpmbuild.8.html).
A couple of things we'd also have to check is how we can sign these
artifacts in accordance with ASF procedures, update release process to
reflect any new steps, and test our new RPMs.
One thing I would like to do before hand however is see how other
Apache projects provide RPMs. Far as I can tell RPMs are being
provided by other groups (i.e., HTTPD and Tomcat can be found as RPMs
but the project pages do not have links for obtaining them, OpenOffice
seems to be one of the few to list these other packages
http://www.openoffice.org/download/other.html). We need to check if
there are any guidance from the ASF regarding their standards for
RPM/Deb/DMG/etc package releases.
Cheers,
Jamie
On Tue, Jan 15, 2013 at 10:54 PM, Andreas Pieber [hidden email]
/user/SendEmail.jtp?type=nodenode=4027307i=0 wrote:
TBH I'm still not against the idea of having deb/rpm for Karaf. So the
release manager would
a) run mvn release:prepare ...
b) scripts/rpmPackaging.sh
c) deploy the final artifact to a rpm repo? Or simply provide it for
download with the rest of the distribution in hope someone will pick
up the package and distribute it to their favorite repos?
Feel free to correct me, but it sounds reasonable to me. BUT the
decision need to be made by our release managers:
@Jamie: WDYT?
Kind regards,
Andreas
p.s.: yes, please create an issue with this script anyway. Would make
it ways easier to find later on.
On Tue, Jan 15, 2013 at 6:37 PM, [hidden email]
/user/SendEmail.jtp?type=nodenode=4027307i=1 [hidden email]
/user/SendEmail.jtp?type=nodenode=4027307i=2 wrote:
That's simpler than distributing an RPM to the repos, by a long
ways. With that approach, all we'd need would be the spec (build)
script. I append the example at the end of this email. As you can see,
it's not very much. I'm sure it could be better written (I'm no RPM
maven {grin}) but it's a place to start. I used the Tanuki Java
wrapper as part of the dependency, because that software is commonly
available for almost any Linux distro. I also included a separate
body of source for the package (shown below as wrapper-gear) which
is just the files that Karaf creates from its wrapper: commands.
These two inclusions allow the RPM to install Karaf as a Linux system
service using the Tanuki wrapper.
Graham-- I'll send you a tarball of wrapper-gear off-list, just
so you can see what I did.
It's this worthy of opening an issue?
---
A. Soroka
Software Systems Engineering :: Online Library Environment
the University of Virginia Library
On Jan 15, 2013, at 12:26 PM, Graham Leggett wrote:
On 15 Jan 2013, at 7:09 PM, [hidden email]
/user/SendEmail.jtp?type=nodenode=4027307i=3 wrote:
I have, for local consumption. I based the build on an ActiveMQ
RPM script. It wasn't too difficult and I can send you the example, if
you like.
If you can, I would hugely appreciate it.
There has been discussion before on this list about maintaining a
semi-blessed RPM of Karaf directly from the project. I'd be happy to
work on that, if I could get guidance and help integrating it into the
release process.
I maintain the spec file that is shipped with Apache httpd, the
idea is that you can download a httpd tarball and run rpmbuild -tb
tarball and it just works. All that is required is that a file
called package.spec exists in the root of the tarball. (It might
also work if the spec file is elsewhere in the tree, but I've not tried).
I am busy looking at the jpackage version of karaf, and it seems
to have a significantly different structure to that shipped by Apache.
Still need to get my head around it.
Regards,
Graham
--
[ajs6f@esbdev2 SPECS]$ cat apache-karaf.spec
# turn off Red Hat's jar repacking macro
%define __jar_repack %{nil}
#
# Spec file for packaging Apach Karaf
#
Summary: Apache Karaf
Name: apache-karaf
Version: 2.2.7
Release: 1
License: Apache
Group: Networking/Daemons
Source0:
http://www.apache.org/dyn/closer.cgi/karaf/2.2.7/apache-karaf-2.2.7.tar.gz
Source1: wrapper-gear
URL: http://karaf.apache.org/
Vendor: Apache Foundation
Packager: A. Soroka [hidden email]
/user/SendEmail.jtp?type=nodenode=4027307i=4
BuildArch: noarch
Requires:
Re: Karat wont start bundle with start-level 99 ??
According to my experience the start-level is set to 'karaf.startlevel.bundle' if not specify in the feature xml file. Also, what is the shutdown sequence, just like start up, but going backward from org.osgi.framework.startlevel.beginning to 0? does the shutdown ensure each start-level completely shutdown before moving on to the next downward level? I am asking this question, is because i am having a unordering shutdown behavior Thanks -Dan On Wed, Jan 16, 2013 at 2:03 PM, Guillaume Nodet gno...@gmail.com wrote: The way the start level service is that when the framework boots, it goes from 0 to the value specified by org.osgi.framework.startlevel.beginning. At each level, the start level service will start bundles on that level. I think the default value is 1 if not otherwise specified. On Wed, Jan 16, 2013 at 10:57 PM, Dan Tran dant...@gmail.com wrote: I understand that when user does not specify the start-level of a bundle in the feature file, it is default to the value of karaf.startlevel.bundle ( which is 80) However, what is the purpose of org.osgi.framework.startlevel.beginning ?? ( max start-level allowed? ) Thanks -Dan On Wed, Jan 16, 2013 at 1:49 PM, Jean-Baptiste Onofré j...@nanthrax.net wrote: To be honest, I don't remember why we increased the Karaf start level. Let me dig in the Jira/e-mails ;) Regards JB On 01/16/2013 10:47 PM, Guillaume Nodet wrote: Well, originally, it karaf.startlevel.bundle was at 50, and for some reasons, it kept increasing over time. I think 100 start levels is good enough, but we should lower from 80 back to 50, which would give more room for users. On Wed, Jan 16, 2013 at 9:01 PM, Dan Tran dant...@gmail.com mailto:dant...@gmail.com wrote: Yes, I am seeing 2 properties under config.properties org.osgi.framework.startlevel.beginning=100 karaf.startlevel.bundle=80 It would be nice if those 2 are documented in the config file so that other user may able to figure out the issue when the same problem encounter. May be org.osgi.framework.startlevel.beginning should start with higher number so that karaf user would have a longer range to work with? Thanks -D On Wed, Jan 16, 2013 at 11:31 AM, Guillaume Nodet gno...@gmail.com mailto:gno...@gmail.com wrote: That's expecte because the start level of the framework is set to 100. You can change that in etc/config.properties iirc. On Wed, Jan 16, 2013 at 8:14 PM, Dan Tran dant...@gmail.com mailto:dant...@gmail.com wrote: I just happen to change some of my bundle to start at level 100 and the bundle get 'installed' state and would not go to 'active'. No error found in log. Can some one confirm? May karaf is 2.3.0 Thanks -Dan -- Guillaume Nodet Blog: http://gnodet.blogspot.com/ FuseSource, Integration everywhere http://fusesource.com -- Guillaume Nodet Blog: http://gnodet.blogspot.com/ FuseSource, Integration everywhere http://fusesource.com -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Guillaume Nodet Blog: http://gnodet.blogspot.com/ FuseSource, Integration everywhere http://fusesource.com
Re: Karaf Cellar 3.0.0 SNAPSHOT
No problem, I just want to figure out what the state of things are so I know if it's just me or if it's possible it doesn't build. If it's possible it doesn't I can file a couple jiras with suggested fixes for you. The is also an enhancement request to file along with the suggested fixes. Anyhow, I don't want to file jiras that are false and take up your time, but if I can help you to resolve some issues quicker, then I wantbto do that. If you want me to file what I think are problems then I'll just go ahead. :) Ryan On Jan 16, 2013 10:54 AM, Jean-Baptiste Onofré j...@nanthrax.net wrote: Hi Ryan, yes, I started to work on both Cellar 2.3.x and trunk yesterday. It should be better by the end of this week. Regards JB On 01/16/2013 05:12 AM, Ryan Moquin wrote: I know I was told that this version isn't stable yet, but I still wanted to see if the build should be able to complete successfully or not. I want to determine if some issues I'm having are something on my end or not. Currently the itests always seem to fail with cellar trunk, is that the current known state of it? Or is it failing on my side only? Thanks, Ryan -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Gogo vs. Karaf Commands
Hi Gareth, Michael As I expressed I have a quick fix which is dirty ATM. I'll clean it up and upload a patch in JIRA. To give you further details of what I have: It can list gogo commands along with other karaf commands in help with their descriptions those provided with @Descriptor annotation. Prints No description if not provided. It also prints some limited information in help command - command description + command's argument types with their description if provided with @Descriptor. On Thu, Jan 17, 2013 at 6:38 AM, Gareth gareth.o.coll...@gmail.com wrote: Hi Mike, I wasn't suggesting actually forking and maintaining Karaf. I was just suggesting using GitHub as a collaboration platform to complete the implementation. It is much easier to work with than svn diffs :). Anyway, I have added the JIRA: https://issues.apache.org/jira/browse/KARAF-2121 thanks, Gareth -- View this message in context: http://karaf.922171.n3.nabble.com/Gogo-vs-Karaf-Commands-tp4027219p4027358.html Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Karaf 3.0.0 Console Extender
Hi As stated in https://issues.apache.org/jira/browse/KARAF-1001 the attribute name has been removed from the command/ in 3.x and the command name can be only configured using the @Command annotation. Please remove the attribute from your blueprint file. Best regards Krzysztof -- View this message in context: http://karaf.922171.n3.nabble.com/Karaf-3-0-0-Console-Extender-tp4027276p4027360.html Sent from the Karaf - User mailing list archive at Nabble.com.
