The second option would still include the classes inside the jar. The only difference is that these classes would be hidden when inside an OSGi environment, while the javax.* classes would be visible. In a non-OSGi env, everything would be visible. I've just committed a fix and the classes are now back in the jar. I'd have to test it in an OSGi env...
On 10/19/07, Rick McGuire <[EMAIL PROTECTED]> wrote: > They are used by the provider jar also, so it would need to be the first > option, I believe. This is how I ran into the problem originally. > > Rick > > Guillaume Nodet wrote: > > So the question is wether these classes are meant to be seen by other > > jars or if they are only used by the javax.mail package. If they are > > to be exported, then it should be > > > > > > <geronimo.osgi.export.pkg>javax.mail*,org.apache.geronimo.mail*</geronimo.osgi.export.pkg> > > > > but if they should be of private use, we need to add the following property > > > > > > <geronimo.osgi.private.pkg>org.apache.geronimo.mail*</geronimo.osgi.private.pkg> > > > > I'm leaning toward the second option > > > > On 10/19/07, Rick McGuire <[EMAIL PROTECTED]> wrote: > > > >> Guillaume, > >> > >> I'm working on a project that requires the latest javamail specs, and > >> I've discovered that the OSGI changes have caused the org.apache.* > >> classes to be ommitted from the jar file, which essentially renders this > >> package inoperable. I was able to get those classes included by > >> changing the <geronimo.osgi.export.pkg> definition to "*". Is that the > >> correct fix, or is something else more appropriate? > >> > >> Rick > >> > >> > > > > > > > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
