Sounds great. I will try it.
Thanks a lot,
Dário
Alexandre Poitras wrote:
Oh great, didn't know that ;) Sometimes the answer is just too simple...
On 3/29/06, Konstantin Polyzois <[EMAIL PROTECTED]> wrote:
Would not this work?
Project pom
<module>components/Comp1</module>
...
<module>components/CompN</module>
I have tried it, and it worked.
/Konstantin
On 3/29/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
Realize that if you go this route, you won't be able to go to the top
parent directory and issue a single "mvn install" type of command to
build and package each module in turn and install into your local
repo.
But if you simply want to share the parent pom for
dependencyManagement and other general project reasons, then this
should be fine.
Wayne
On 3/29/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
Depends of what you want.
If you want a multi-modules project then I think the answer is no.
If you want to have a common parent pom, there is no problem, you can
put it wherever you want. Just don't declare any modules in your pom.
On 3/29/06, Dario Luis Coneglian Oliveros <[EMAIL PROTECTED]> wrote:
Hi there,
Does anybody know if there's a way to create a multiproject by having
its modules in a different directory depth level ?
AFAIK, when setting up a multiproject, its respective modules must be
placed under it as subdirectories.
I would like to have something as follows:
+ Project
- pom.xml
+ components
+ Comp1
- pom.xml
...
+ CompN
- pom.xml
Thanks,
Dário
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Alexandre Poitras
Québec, Canada
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Alexandre Poitras
Québec, Canada
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
