Thank you Thomas, I'm not 100% sure the fact that JDT embed other the Jar due to OSGi, it could be but I've never used that feature. And it sound weird to me as then JDT should be used in an OSGi environment (yes Eclipse is based on OSGi, but I don't think GWT Ant build starts any OSGi environment)
I mean, I remember it is possible to do embed jars, but OSGi does not mandate to do that, and in fact I use OSGi exactly for the opposite reason: to not have 20 MB .war files with all the libs embedded in it. In OSGi the manifest is used to declare dependencies, it works at the level of packages (instead of artifacts like Maven), you declare dependencies on packages and packages exported by it. It is a bit complex sometime but allow to have a good modularity for applications. What I would like to do, is to OSGI-fy GWT-Servlet (at first, and if it works the same could be applied to requestfactory) so it can be used inside an OSGi container. In that case, the GWT-Servlet could be deployed as a bundle providing the GWT classe, it will be available as a "platform library", and web application will not need to embed it (I remember time ago I was putting libraries in Tomcat endorsed folder, consider it something like that but standardized). I will try to add the BND Ant Task on the GWT Build and if it work I will report it and we can evaluate if it is ok to use it also for the official release. Regards, Cristiano 2013/11/3 Thomas Broyer <t.bro...@gmail.com> > > > On Thursday, October 31, 2013 9:16:57 AM UTC+1, Cristiano wrote: >> >> Hi All, >> >> I would like to know if the plan for 2.6.0 is to still use Ant or release >> it already from Gradle. >> > > Ant. > > >> I ask this because I would to check the feasibility of OSGIfy the >> GWT-Servlet jar. >> Having an OSGi compliant GWT-Servlet should make it easier to use GWT on >> OSGi containers (I suppose it is enough to OSGIfy GWT-Servlet as it is the >> only Jar I expect to to on the server side). >> > > There's requestfactory-client and requestfactory-server too. > > >> Some background information: >> OSGI-fization takes place by modify the META-INF/MANIFEST.MF file of the >> Jar and adding new headers that allow the jar to be used more "friendly" in >> an OSGi environment. >> >> This modification is mostly transparent, many much jar lbraries you are >> using are already OSGIfied or exist in an OSGIfied version (one example >> among all: the org.eclipse.jdt.core_3.8.3.v20130121-145325.jar that is >> in GWT-Tools is OSGIfied). >> > > Not the best example, as JDT's OSGi nature is an issue for us (need to > extract a JAR that's embedded in the JAR; I think it's because of OSGi, but > don't know OSGi that much) > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > --- > You received this message because you are subscribed to the Google Groups > "GWT Contributors" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
