It's actually possible to use nested projects in Eclipse if you:
1. Check out the parent project into your workspace.
2. Type "mvn eclipse:eclipse" in the parent dir - eclipse project files
are now generated for all submodules.
3. Delete or rename the .project file in the parent dir.
4. Choose "Import" --> "Existing projects into workspace" and browse to
the parent dir
You can now import the subprojects into your workspace
(won't work unless you removed the parent's .project file)
5. Restore the parent's .project file
Martin
On Tue, 24 Apr 2007 18:55:45 +0200, Andrea Chiumenti <[EMAIL PROTECTED]>
wrote:
I know that a lot of ppl use eclipse, but refactoring a project based on
an
ide limitation, remind me that evil of MSIE.
Do we really want a weak project structure because of an ide limitation ?
On 4/24/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
Eclipse doesn't do nested projects, otherwise I would structure it that
way. And it is important to me to allow everything to be built
seperately
and in layers (I expect tapestry-ioc to be used outside of Tapestry, for
example).
On 4/24/07, Massimo Lusetti <[EMAIL PROTECTED]> wrote:
>
> On 4/24/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
>
> > I think things are back the way they should be.
>
> Great news!
> I've only one question, why you have kept the
> tapestry-(project|core|ioc...) distinction ? Personally i would have
> preferred that trunk would have become -project which contained all
> other submodules (core, ioc etc). Any reason why to keep that besides
> keeping unchanched poms?
>
> --
> Massimo
> http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
