On Fri, 2003-05-30 at 16:35, Sonnek, Ryan wrote:
>
> Placing the root files in a subproject seems to be a pretty good idea. Will
> the Reactor still perform as it should? This is the project layout that
> you're suggesting right?
>
> +MyProject
> |--+common subproject
> |--project.xml (extend
main project.xml defining dependencies, etc)
|--maven.xml
so, no files exist outside of a subproject? Does this seem like a good
solution or more of a hack?
Ryan
-Original Message-
From: Gilles Dodinet [mailto:[EMAIL PROTECTED]
Sent: Friday, May 30, 2003 10:14 AM
To: Maven Users List
Subject
y 30, 2003 10:14 AM
To: Maven Users List
Subject: Re: eclipse subprojects
your layout makes me think you need to have one and only one eclipse
project (say root), with several source directories (common/src/java,
ejb/src/java, etc..). maven-new module illustrates that. The drawback of
such an a
your layout makes me think you need to have one and only one eclipse
project (say root), with several source directories (common/src/java,
ejb/src/java, etc..). maven-new module illustrates that. The drawback of
such an approach is that .classpath isnot easily generated since
maven-eclipse-plu
This is a problem, because while Eclipse can handle nested sources via
exclusion filters, it can't actually handle nested projects where you
need to have the eclipse project metadata somewhere at a root level, and
below that have eclipse project metadata for other projects.
Now what will work i
Ack!
I've just switched my project over to maven and have broken it up into
several subprojects (ejb, common, war, etc). now, I know this is not a
"maven" problem, but as this is a common layout for a maven project I hope
someone will be able to help. i've been able to create my subprojects
withi
