Hi Phil,
Comparing PDE and Gradle is a but like comparing apples and oranges.
It would be good to know what kind of projects you are developing. As
PDE is an acronym for "Plug-in Development Environment", the purpose of
Eclipse's "PDE" is building eclipse based applications (Eclipse plugins,
Eclipse RCP apps). In addition pde can be used to build osgi based
projects (non eclipse specific).
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)
In my opinion, even though you're developing eclipse based projects,
using the gradle pde plugin has some nice advantages. Instead of losing
oneself in xml hell (thats what pde in my opinion is) you can write your
custom build logic in groovy. Furthermore gradle offers a nice api for
dependency and repository managemt.
Leveraging PDE to build plain java projects (or groovy, scala etc.) is
definitely nonsense! But if you want to leverage your eclipse based /
osgi projects you should take a look at buckminster
(http://www.eclipse.org/buckminster/)
regards,
René
Am 18.05.10 22:17, schrieb phil swenson:
A few of people in my company are pushing for gradle as our
build/automation system. We hear others advocating leveraging
Eclipse's "PDE". I don't know anything about PDE. Could someone
expand on pros/cons of leveraging PDE?
Thanks
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
------------------------------------
Rene Groeschke
[email protected]
http://www.breskeby.com
http://twitter.com/breskeby
------------------------------------
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
