On Jan 18, 2010, at 1:10 PM, Kay Röpke wrote: >> I just scanned the pages for OSGi. uh, what the hell is it? ;) What would >> you need? > > http://en.wikipedia.org/wiki/OSGi has a pretty good overview :) > > osgi is basically a framework for handling code modularity, allowing for a > very dynamic environment for code bundles (basically jars). > it's pretty strict on classloading, because it versions the packages and > generally you cannot expect context classloaders do to what you would > normally think they'd do. > in general it would be easy to create the necessary manifest headers to the > antlr jars, and ST would only need minimal changes, i assume (basically > injecting the correct classloader) > for what i would like to do pretty soon, it would be awesome to let antlr > find its codegen templates dynamically, even if contributed by different > bundles.
ok, i'll rely on you to tell me what we need later ;) Ter _______________________________________________ antlr-dev mailing list [email protected] http://www.antlr.org/mailman/listinfo/antlr-dev
