Intelli-J has the notion of modules. A project in Intelli-J is made up of one or more modules. A module "base" can be inside the overall project directory structure. Is that what you mean?
How do your directories look? And how do you want them partitioned?
currently:
hibernateext <--- here common-build.xml is located (and when using eclipse a .project)
hibernateext/console <-- each module has their own src etc. and their build.xml point to ..\common-build.xml
hibernateext/tools
hibernateext/metadata
...
wanted:
hibernateext/ <--- now basically empty (build moved to common and .project cannot be here if i want to load the plugin projects)
hibernateext/common <--- here common-build.xml is located
hibernateext/console <-- each module has their own src etc. and their build.xml point to ..\common\common-build.xml
hibernateext/tools
hibernateext/metadata
hibernateext/org.hibernate.eclipse.core <-- eclipse plugins need their own .project
hibernateext/org.hibernate.console.eclipse
Makes sense ? ;)
/max
[mailto:hibernate-devel------Original Message----- From: [EMAIL PROTECTED]project[EMAIL PROTECTED] On Behalf Of Max Rydahl Andersen Sent: Friday, November 12, 2004 4:03 AM To: Hibernate development Subject: [Hibernate] hibernateext build structure and eclipse plugins
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 bigproblemin my eclipse, and that has worked fine.
But the plugin development I have "bumped" into a issue with theinsidethat eclipse projects cannot be nested, e.g. you cannot have a project xtheproject 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 eclipsecommon-build.xmlfiles located directly below hibernateext directory - includingwhereand 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)i'll dothey do the import of common-build.xml.
Does anyone have objections or see problems with this ? Otherwiseit 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
------------------------------------------------------- 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_idU88&alloc_id065&op=click _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
-- -- 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