On Tue, 12 Apr 2005 20:43:43 +0200, John Franey <[EMAIL PROTECTED]> wrote:

Just to let you know, I'm making some progress on this, I'm almost obsessed.

Good to hear ;)

I'm cc'ing this to devel list so others can see it.
I'm also cc'ing this to our jboss ide mailing list since its also something
they are working on and the info here is relevant for them too (but you just
keep the focus on the hibernate related plugins ;)


I have read that some plugin developers prefer not to use PDE Build
because it doesn't build plugins targetted for Eclipse 2.x.

Doesn't matter for us. Eclipse 2.x and 3.0 is old news in this context.

argument that their build scripts are better than PDE Build if only
because their scripts fit into existing build procedures.

I don't like PDE Build because its so tightly connected to eclipse, but I think there is also too many "cringes" with a manual built ant script for a eclipse build - so at the moment PDE build looks like the better solution and already tried by eclipse team them selve.

A document under work at bug page
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=87151> says that PDE
Build 3.0 can build plugins that are dependent on Eclipse 3.1.   This

Thanks for the link !

Setting up PDE Build will be less effort than constructing a full ant
based build framework for Hibernate.   I support use of PDE Build
because of the level of effort, and because Eclipse organization uses it
to build the plugins they produce.  PDE Build supports the list of goals
I outlined in the first mail on this topic.  In additon, PDE Build also
supports automatic testing and source distributions.

It still sounds like the correct plan to me ,)

/max






In the hibernate developer's mail archive there is discussion on the structure of the cvs tree for plugins. The PDE Build can accomodate an arbitrary structure easily by changing the contents of one file. So, it is immune to future changes to the cvs tree, useful to know in case you are unsatisfied with current structure.

PDE Build can accomodate different cvs tags for each plugin, but its
easier to manage if they all share the same tag.  Currently,
org.hibernate.eclipse and org.hibernate.eclipse.feature spell the ALPHA
2 tags differently.

A place in the cvs tree for the PDE Build artifacts will be needed when
I get close to finishing.  There are four files so far: a shell script,
a map file (maps plugins to cvs location), a build.properties files, and
a custom ant build script.  No action required yet, just a heads up.


Regards, John





-- -- Max Rydahl Andersen callto://max.rydahl.andersen

Hibernate
[EMAIL PROTECTED]
http://hibernate.org

JBoss Inc
[EMAIL PROTECTED]
http://jboss.com


------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel

Reply via email to