Hi John, On 9/5/06, John E. Conlon <[EMAIL PROTECTED]> wrote:
Trustin, On Mon, 2006-09-04 at 11:38 +0900, Trustin Lee wrote: > Ah, but then shouldn't we rename all the artifact names? The Directory PMC > decided not to use the OSGi bundle naming convention for the JARs IIRC. Is > there any workaround? > Not clear on the latest decision regarding jar names. I know this debate has raged off and on at the felix mail list. http://www.mail-archive.com/[email protected]/msg01891.html Can you point me to a link regarding the directory discussions?
This is the only thread I was able to find: http://thread.gmane.org/gmane.comp.apache.incubator.directory.devel/6419/ 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. The important question would be 'can OSGi framework load an OSGi bundle with a JAR name which doesn't follow OSGi bundle naming convention?' If yes, there's no problem. Otherwise, we need a subproject for now. 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. 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. Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP key fingerprints: * E167 E6AF E73A CBCE EE41 4A29 544D DE48 FE95 4E7E * B693 628E 6047 4F8F CFA4 455E 1C62 A7DC 0255 ECA6
