On Tue, Jul 8, 2008 at 4:44 PM, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 8, 2008 at 5:15 PM, Hendy Irawan <[EMAIL PROTECTED]> > wrote: > > > Besides it won't hurt at all for the rest of the "Qi4j sans OSGi" users > > right? > > Yes, it doesn't hurt, but I want to ensure that we are doing the > "right thing" from the start to avoid problems down the line. To > Export-Packge "org.qi4j.core.runtime" for instance is definitely > wrong. > > I'll take a look at the "soon", and see what we can come up with. But > I am sure we will need a "watch dog" to ensure that new packages are > handled, since none of us have an OSGi-centric view in Qi4j at the > moment. > I agree, which is the reason why I request guidance... if at least Qi4j core developers don't have the resources for OSGi focus at this time, I may be able to contribute something. POM changes is all I ask. WRT the specific case you mentioned, it is a potential mishap indeed however in my example it only exports bootstrap, not org.qi4j.core.runtime : Export-Package: org.qi4j.bootstrap;uses:="org.qi4j.composite,org.qi4j. runtime.composite,org.qi4j.runtime.structure,org.qi4j.structure,org.q i4j.runtime.object,org.qi4j.runtime.entity.association,org.qi4j.util, org.qi4j.runtime.entity,org.qi4j.spi.service.provider,org.qi4j.entity ,org.qi4j.property,org.qi4j,org.qi4j.runtime.service.qi,org.qi4j.serv ice,org.qi4j.object,org.qi4j.runtime,org.qi4j.runtime.property";versi on="0.3.0.SNAPSHOT" I'd presume even in case that the manifests are 'wrong', this can be categorized as "osgi.bnd tweaks" which is should be more trivial to fix than "actual bugs". What I request is a compromise in order to make it convenient for both of our intentions... Ok we'll wait for full OSGi support, but at least can we get OSGi manifests in the short term since (1) we need/want to try it , (2) we can tweak the POMs in the mean time if you don't have the resources , (3) you still hold full commit authority and can review our "code" (not technically code, just declarative/manifests), (4) make us learn the WAY to do things right (technically) in Qi4j community... -- Best regards, Hendy Irawan
_______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
