Hi all,
I'm in the process of adding the eclipse plugins to the cvs. (would hate to loose this stuff to a airport thief or something ;)
Until now I have been having the complete hibernateext as one big project in my eclipse,
and that has worked fine.
But the plugin development I have "bumped" into a issue with the problem that
eclipse projects cannot be nested, e.g. you cannot have a project x inside project y.
(btw. can Idea handle this ?)
One strategy for me would be to just create a eclipse project for each submodule
(tools, console, metadata, org.hibernate.eclipse.core, org.hibernate.console etc.)
And this works fine, *except* that I then cannot access within eclipse the files
located directly below hibernateext directory - including common-build.xml and others ;(
My suggestion is thus to move the common build stuff to a "shared" or "common" module in hibernateext
which will allow for a better structure (at least in eclipse).
It will require a one line change in all the build.xml's (trivial) where they do the import of common-build.xml.
Does anyone have objections or see problems with this ? Otherwise i'll do it over the weekend.
TIA ;)
-- -- Max Rydahl Andersen callto://max.rydahl.andersen
Hibernate [EMAIL PROTECTED] http://hibernate.org
JBoss Inc [EMAIL PROTECTED] http://jboss.com
------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
