Can't make features-maven-plugin:generate-features-xml to work

2011-04-19 Thread tm...@yahoo.com
Hi, I have not been able to get generate-features-xml to work a very simple example, and I didn't find any luck on Google/Bing/this forum for a solution (exception this one,

Re: Can't make features-maven-plugin:generate-features-xml to work

2011-04-19 Thread Andreas Pieber
The problem sounds like one already reported. Is it possible that you're running with mvn3? Can you please try the same using the latest m2 version? 2.2.x is compatible with jdk5 and m2; all major releases (very probably all future minor releases of the 2.x branch too) will drop m2 and jdk5

Re: Karaf shell. Start bundle by SymbolicName and Version

2011-04-19 Thread Sergey_Zhemzhitsky
Hi JB, Thanks a lot. I've got the idea. Best Regards, Sergey Zhemzhitsky Information Technology Division Troika Dialog, 4, Romanov lane, Moscow 125009, Russia Phone. +7 495 2580500 ext. 1246 Jean-Baptiste Onofré j...@nanthrax.net 18.04.2011 20:45 Please respond to user@karaf.apache.org

Re: Karaf shell. Start bundle by SymbolicName and Version

2011-04-19 Thread Sergey_Zhemzhitsky
Hi Adrian, Thanks for the suggestion. A separate feature for a bundle doesn't fit my needs, so I will use karaf trunk for now. Best Regards, Sergey Zhemzhitsky Information Technology Division Troika Dialog, 4, Romanov lane, Moscow 125009, Russia Phone. +7 495 2580500 ext. 1246 Adrian

Re: Can't make features-maven-plugin:generate-features-xml to work

2011-04-19 Thread tm...@yahoo.com
Shoot! You are right. I didn't realize that i was on maven 3. My Mac automatically updated maven from 2.2.1 to maven 3. Thanks. - Triet -- View this message in context: http://karaf.922171.n3.nabble.com/Can-t-make-features-maven-plugin-generate-features-xml-to-work-tp2837746p2839666.html

Re: Multiple instances of Karaf on same host

2011-04-19 Thread tm...@yahoo.com
I observed that by default both 8080 and 8181 will be in used if starting karaf with http feature installed. This is because jetty default port is set to 8080 in jetty.xml and http org.osgi.service.http.port is set to 8181. I would expect only one of these 2 configurations to be used, but look