On 9/4/06, Trustin Lee <[EMAIL PROTECTED]> wrote:
Hi John, On 9/2/06, John E. Conlon <[EMAIL PROTECTED]> wrote: > > Hi Trustin, > > On Fri, 2006-09-01 at 12:17 +0900, Trustin Lee wrote: > > > Cool. I really appreciate your will! One question: where would these > maven > > projects should be located? > > I think the MINA OSGi bundles should be > > splitted into multiple bundles as we did for MINA JARs (mina-core, > > mina-filter-ssl, ...). If so, placing these directories directly > under > > trunks/mina will not look really good. Here's my suggestion for the > > directory structure: > > > > trunks/mina > > - core > > - filter-ssl > > - filter-codec-asn1 > > - filter-codec-netty2 > > - integration-spring > > - integration-osgi > > ---- core (OSGi bundle for core) > > ---- filter-codec-asn1 (OSGi bundle for filter-codec-asn1) > > ... > > > > Of course, we wouldn't need this hierarchy if maven-osgi-plugin can > generate > > multiple buldles with one project. > > > > WDYT? > Initially we can just add the osgi plugin specifications to the existing > projects' pom.xml files and not create any new projects. Adding the > plugin specifications will create the necessary metadata in the jar when > > it is built allowing the jar to also act as an OSGi bundle. In other > words the jar still acts like it did before - for any non-osgi > application, but it also works as an OSGi bundle. (Sort of like Clark > Kent and Superman. Clark still goes to work at the Daily Planet:) > > For the first Mina OSGi effort I suggest offering Mina packages and > classes to other bundles in the OSGi framework - in other words Mina at > first will be a set of OSGi library bundles. This is relatively easy. > > Have already done this for the Mina core project by adding the OSGi > plugin specs to the core project ( will soon post a patch to Jira) > pom.xml. Will begin filter-ssl, filter-codec-asn1, and filter-codec- > netty2 today. Once done Mina becomes a first class OSGi citizen. (Good > bye wrapper projects.) Very cool enough! ...and the superman analogy makes me smile. :D
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? 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
