Sorry for reposting, but I thought it got lost somewhere on the way as I
haven't seen it after hours ...
On 02/24/2011 06:53 AM, Felix Knecht wrote:
Hi all
Trying to get the module sites generated I'm getting a little bit
confused about the usage of pom files.
I can't see the need of the module 'parent' containing only a pom.xml
with type <packaging>pom</packaging>. This parent/pom.xml does various
definitions for reporting, building, dependencies.
Then we have the ./pom.xml, also as <packaging>pom</packaging>. This
pom.xml has a strange cycling dependency to it's parent pom - once as
<parent> and once as <module>. In fact you only get the up to date
parent because of the <relativePath> which can be indicated (and BTW not
liked by maven 3.x). Without using the relativePath the parent will be
always one step behind actual changes - actual parent pom will be as
module. Furthermore definitions in ./pom.xml mostly exists already in
the parent/pom.xml.
Last but not least the site generation seems to work (for me) only when
deploying the site, otherwise I get strange results. I guess this is
because when deploying the generated site of the parent gets overridden
with the site generated from ./pom.xml.
IMO it would make sense to merge these to poms (both of
<packaging>pom</packaging>) and have just one ./pom.xml and skip the
./parent completely.
Can please somebody throw some light on my confusion?
Thanks and kind regards
Felix
---------------------------------------------------------------------
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]
