Hi Scott,
> -----Original Message-----
> From: Scott Stirling [mailto:[EMAIL PROTECTED]
> Sent: 02 June 2003 10:18
> To: [EMAIL PROTECTED]
> Subject: multiple sourceDirectory elements in a build
>
> Hi,
>
> Just joined the mailing list after a quick search on the archives
turned
> up
> nothing on this.
Humm.. strange as this is a hot FAQ! :-)
(BTW, I've just noticed we don't a FAQ entry for this... hum...)
>
> I would like to be able to have either multiple <sourceDirectory>
elements
> per <build>, or multiple <build> elements per project (ideally, both),
> which
> should generate multiple <javac> targets in the output build file if I
do
> "maven ant"
The Maven philosophy is to have a single source tree per project. If you
need several then simply split into several projects. Creating a project
in Maven simply consists in creating a project.xml file.
Myoverallproject
|_ project1
|_ src/java
|_ project.xml (can inherit from ../project.xml)
|_ project2
|_ src/java
|_ project.xml (can inherit from ../project.xml)
|_ project.xml
|_ maven.xml
The maven.xml file can use the <reactor> tag to automatically build
project1 and project2.
> and should output multiple <classpathentry kind="src"
> path="src/codebaseN"> if I do "maven eclipse."
>
> More to the point, what's the Maven way to do a compile of two
codebases
> in
> the same project, where all the dependencies are the same (for the
sake of
> argument), but classes and testcases are separated by codebase? We
rely on
> codebases for JAAS testing purposes and IDE test running, where we
want to
> compile two source codebases in one ClearCase component (a
mini-project)
> to
> two different classfile codebases, such as system and user (which also
> become separately named jar files). I'm getting the intuition that
Maven
> would like this to be two separate projects because they are separate
> codebases.
Yep. See above.
-Vincent
>
> Any thoughts?
>
> Thank you,
>
> Scott Stirling
> Framingham, MA
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
