maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Robinson <>
Subject Re: maven-site-plugin no longer multi-module?
Date Thu, 07 Oct 2010 19:40:08 GMT
Thanks, I'll take the ".", "maven." and ".version" into consideration
for our pom, but that is unrelated to the issue at hand. Either way it
is done, the site 2.1.1 plug-in does not execute the site for the
modules, only for the parent projects site directory. When I get a
chance, I will put together a test case and submit a bug.

It seems that there are several problems with the maven site, doxia
and related plugins in maven 2.2.1. I hope to site the site plugin
more mature in the next maven release.

On Wed, Oct 6, 2010 at 8:45 PM, Wayne Fay <> wrote:
>> My guess is that while dots are in general perhaps ill-advised,
>> 'maven.' is what really causes the problem here. In my experience,
>> dots in pom props are as common as dirt, and it's very much news to me
>> that they are a bad idea. There are a lot of poms at Apache that will
>> need to be edited if all dots are equally bad in prop names.
> At some point, there was a Maven bug that basically evaluated
> ${*.version} as equivalent to ${version} and so people were getting
> their current project version in all kinds of places they didn't
> expect. Ever since then, I've avoided dots in my properties names and
> told people to avoid them likewise.
> Wayne
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message