Hi Tim,
thanks for your reply.
I tried to use the command you suggested, but unfortunately,
the links are also incorrect in this setting. In particular
the modules links.
--
Julien
On Mon, Jun 18, 2007 at 04:42:40PM -0400, Tim Foster wrote:
Hi Julien,
Regarding the site links not working, I found that the relative paths
were not correct until I ran the site:stage goal as follows:
mvn site:stage -DstagingDirectory=path_to_your_staging_area
Then open the index.html at the top level of the staging area. I think
the same thing can be accomplished with site:deploy, but I haven't
gotten that far yet.
Tim
-Original Message-
From: Julien Stern [mailto:[EMAIL PROTECTED]
Sent: Monday, June 18, 2007 8:10 AM
Hi list,
Using Maven 2.0.6 and Continuum 1.1-alpha-2.
I have the following problem with multi-modules setup:
I tried the two following approaches (both with modules and aggregation)
A) parent pom in the top-level dir
- pom.xml (parent)
- module 1
- pom.xml
- module 2
- pom.xml
B) parent pom at the same level as modules
- parent
- pom.xml
- module 1
- pom.xml
- module 2
- pom.xml
Approach A causes problem with continuum: each change in ANY module
is detected by the parent project which is rebuilt, leading to the
recompilation of every module.
Approach B causes problem with site generation:
the modules links in the parent site are incorrect (they point
one level higher than they should).
Multi-module setup seems to be a fairly common setting, so I'm sure
that I have missed something. Is there any way to have a multimodule
setup that works both for site generation and for Continuum ?
Regards,
--
Julien
-
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]
