Hi Joachim,
Joachim Schreiber wrote on Saturday, April 16, 2005 6:28 PM:
[snip]
> When I now check out the complete trunk in the new Maven 2
> layout I have all ejbs (sub projects/modules) in one
> directory and when I start the multi-project build all ejbs
> are generated with e.g. xdoclet. This takes a long time and
> no advantage of the binary dependency build is available any longer.
> The solution is now to delete all ejbs I do not need to
> develop only for example a few modules. But this is not a
> fine solution to tell your developers please check out the
> trunk and after this you're allowed to delete this and this
> and..... It's nicer to say check out this core projects and
> then the module you want to work with.
>
> After a checkout from a project I use in Maven 1 the
> maven-eclipse-plugin to generate .classpath and .project. Is
> this working with the new directory structure too?
>
> I hope my bad English can explain my prob clear enough?!
You may tell your developers to work with a local build.properties file in the
multiproject root, that contains the maven.multiproject.include (or
maven.multiproject.include) property, e.g.
maven.multiproject.include=\
ejb1/project.xml, \
ejb2/project.xml, \
webapp1\project.xml
... you get the idea. The value just overrides the one found in
project.properties. If they check out individual subprojects only, you might
even generate that entry for all locally available subprojects with a script.
This way everyone can have an individual multiproject builds. Just ensure, that
build.properties is excluded in the .cvsignore (this file should never be
checked in anyway).
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
