Hi Trustin, On Wed, 2006-09-06 at 11:27 +0900, Trustin Lee wrote:
> But we changed our mind to user a little bit longer name like > 'mina-filter-codec-netty'. IIRC, there was also some discussion about > artifactId relating to OSGi, but I don't remember it exactly. That discussion was in the Felix mail list and related to 'the convention' for naming jars in a consistent way for both Eclipse and Felix, one that would avoid name collisions. That was only a convention. There is no 'technical' reason to change the names of ApacheDS at this time. > > The important question would be 'can OSGi framework load an OSGi bundle with > a JAR name which doesn't follow OSGi bundle naming convention?' YES! (sorry to shout:-) > If yes, > there's no problem. No problem. > I think the cause of this problem is that Maven 2 doesn't provide a > systematic way to publish more than two artifacts with the same content and > different metadata which leads to multiple subprojects. It would be perfect > if we can generate and deploy two JARs from one project. So given a jar like mina-core, we can add OSGi metadata and keep the same name in order to create a jar that is also as an OSGi bundle. > > But we can still create integration-osgi directory and provide subprojects > to generate OSGi bundles although it's not really an ideal way if OSGi > specification forces us to follow its naming convention. Jar naming will not force us to create a separate project. cheers, John
