Yes I see, worth pointing out. Exchanging a dependency on the JDK for one on ECJ is no big deal at all.
On 14/08/07, Jeff McAffer <[EMAIL PROTECTED]> wrote: > > > ok. I was curious because using ECJ does not mean you have to "run > eclipse" etc. That compiler is a completely stand-alone 1.5MB JAR. It > happens to have OSGi markup in the manifest and so can be run as a bundle > but does not need to be nor does it include/require any other parts of > Eclipse. Javac is fine except that you have to have a JDK. ECJ runs > embedded on Foundation 1.0. > > Anyway, I am not trying to "sell" you on this, just looking to remove any > misconceptions. > > Jeff > > > > *"Mike Gould" <[EMAIL PROTECTED]>* > Sent by: [EMAIL PROTECTED] > > 08/14/2007 05:05 AM Please respond to > [EMAIL PROTECTED]; Please respond to > OSGi Developer Mail List <[email protected]> > > To > [email protected] cc > > Subject > Re: Re[2]: [osgi-dev] calling javac/JavaCompilerTool within OSGi > > > > > > > Only that the library that uses the compiler comes from a third party and > has many existing non-eclipse deployments. I'm sure most of their customers > wouldn't welcome an additional dependency on eclipse when from their point > of view the javac complier is perfectly adequate. > > I think we have a more generic solution which I should be able to describe > for you later. > > Thanks > MG > > On 13/08/07, *Jeff McAffer* <* [EMAIL PROTECTED]<[EMAIL PROTECTED]>> > wrote: > > Mike, just as a point of curiosity, what is the problem with depending on > Eclipse code? > > Jeff > > *"Mike Gould" <[EMAIL PROTECTED] <[EMAIL PROTECTED]>*>* > Sent by: [EMAIL PROTECTED] <[EMAIL PROTECTED]> > > 08/02/2007 06:44 AM > Please respond to* > [EMAIL PROTECTED] <[EMAIL PROTECTED]>; Please respond to > OSGi Developer Mail List <[EMAIL PROTECTED]<[email protected]> > > > > > To > "OSGi Developer Mail List" <[EMAIL PROTECTED]<[email protected]> > > cc > > Subject > Re: Re[2]: [osgi-dev] calling javac/JavaCompilerTool within OSGi > > > > > > > > > Little more research... > Looking at > *http://www-128.ibm.com/developerworks/opensource/library/os-ast/?ca=dgr-lnxw97ASTParser > *<http://www-128.ibm.com/developerworks/opensource/library/os-ast/?ca=dgr-lnxw97ASTParser>it > shouldn't be too hard to write a wrapper that takes a string/file/whatever > and returns a class object. Looks like the compiler will simply use the > existing classloaders' classpath which makes most of the pain go away. > Unfortunately this software is not in any way related to OSGi so adding a > dependency on eclipse to support one particular deployment won't make it to > the main stream. Any way of portably using javac would be preferable. > > Mike > > On 02/08/07, *Peter Kriens* <[EMAIL PROTECTED] *<[EMAIL PROTECTED]>> > wrote: > I would be interested in the results ... > > Kind regards, > > Peter Kriens > > MG> Thanks Jeff, that's a good idea. I'll have a good look at the eclipse > compiler. > > MG> I'm investigating the possibility of porting an existing > MG> application which uses javac into the OSGi world. It does some on > MG> the fly code generation and compilation of individual classes for > MG> optimisation purposes. As it's a third party product I'm keen to > MG> know if it can be done without a lot of change. > > MG> Cheers > MG> MikeG > > > _______________________________________________ > OSGi Developer Mail List* > [EMAIL PROTECTED] <[email protected]>* > **http://www2.osgi.org/mailman/listinfo/osgi-dev*<http://www2.osgi.org/mailman/listinfo/osgi-dev> > > > > -- > - MikeG _______________________________________________ > OSGi Developer Mail List > [email protected] > http://www2.osgi.org/mailman/listinfo/osgi-dev > -- - MikeG
_______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev
