Generally when building bundles as plain Java you will miss out on the manifest validation. When PDE Build builds bundles it will validate the manifest configuration of your bundles i.e. trying to use non exported packages will render build errors...
PDE Build honors the multiple classpaths that is the signature of OSGi and plain Java builds are based on the one "mega" classpath... Still, PDE Build may not have the best of approaches to building... ;) /Patrik Pfau, Matthias wrote: > > >> Gradle can be used to build a wide range of projects. There are plugins >> available to build groovy, java, scala, clojure projects. Furthermore >> Gregory Boissinot wrote a pde plugin, which can be used to wrap a pde >> build in a gradle build. (see http://github.com/gboissinot/gradleplugins >> for details) >> > > I like the plugin but I do not like the general pde building approaches. > I think that the basic problem is, that Eclipse-Developers refuse on > using a dependency management solution. I haven't found a single up to > date repository with all eclipse artifacts. That is why I wrote an OSGI > to Maven converter: > http://github.com/mpfau/osgi2maven > > Based on this, building eclipse RCP-applications is very easy. You just > have to do a "plain" Java compile and copy dependencies to a defined > folder structure for creating your product. > > Do you see any flaws of this approach? > > Kind Regards > Matthias > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > -- View this message in context: http://old.nabble.com/PDE-tp28600882p28693676.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
