I checked they subsystem spec before I made my entry.  In the spec, their
example uses a period-delimited name.  However, the spec does not mandate
that usage.



David Jencks wrote:
> 
> On Oct 13, 2011, at 8:55 AM, Ioannis Canellos wrote:
> 
>> Hi David,
>> 
>> The fact that the features you mentioned are provided by the Karaf
>> doesn't
>> mean that we need to prefix them with karaf.
>> For example we can only use the project that implements those features
>> and
>> end up with something like this:
>> 
>> aries-jndi
>> aries-tx
>> spring-tx
>> camel-jpa
>> karaf-webconsole
>> 
>> wdyt?
> 
> Absolutely not.  If geronimo wants to use a different selection of bundles
> for an aries-jndi feature it should be able to without any difference in
> naming convention.
> 
> I'd check the subsystem spec to see what they plan to use.  The sample
> subsystems I've seen all use a bsn-like name. 
> 
> thanks
> david jencks
> 
>> 
>> -- 
>> *Ioannis Canellos*
>> *
>> FuseSource <http://fusesource.com>
>> 
>> **
>> Blog: http://iocanel.blogspot.com
>> **
>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>> Apache ServiceMix <http://servicemix.apache.org/>  Committer
>> Apache Gora <http://incubator.apache.org/gora/> Committer
>> *
> 


-----
Mike Van
Mike Van's Open Source Technologies Blog 
NCI, Inc. 
Atraxia Technologes 
--
View this message in context: 
http://karaf.922171.n3.nabble.com/feature-names-are-potentially-ambiguous-tp3263950p3420297.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.

Reply via email to