maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benson Margulies <bimargul...@gmail.com>
Subject Re: maven-site-plugin no longer multi-module?
Date Thu, 07 Oct 2010 01:56:10 GMT
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.

On Wed, Oct 6, 2010 at 6:49 PM, Dennis Lundberg <dennisl@apache.org> wrote:
> On 2010-10-06 00:13, Andrew Robinson wrote:
>> I am trying to get our build system moved over from maven 2.0.8 to
>> 2.2.1, but we have been having problems with the site plugin. While
>> converting over, I am supporting a profile that changes the plugin
>> version. Here is the setup:
>>
>>
>>   <properties>
>>   ...
>>     <maven.site.plugin.version>2.0.1</maven.site.plugin.version> <!--
>> Use the one that 2.0.8 uses by default -->
>
> You should avoid using properties that contains dots in a Maven POM. The
> newer versions of Maven are more picky in this respect. I suggest that
> you rename maven.site.plugin.version to mavenSitePluginVersion
>
>>   </properties>
>>   ...
>>   <build>
>>     <pluginManagement>
>>       <plugins>
>>         ...
>>         <plugin>
>>           <groupId>org.apache.maven.plugins</groupId>
>>           <artifactId>maven-site-plugin</artifactId>
>>           <version>${maven.site.plugin.version}</version>
>>           <dependencies>
>>             <dependency>
>>              <groupId>commons-httpclient</groupId>
>>              <artifactId>commons-httpclient</artifactId>
>>              <version>3.1</version>
>>              <exclusions>
>>                <exclusion>
>>                  <groupId>commons-logging</groupId>
>>                  <artifactId>commons-logging</artifactId>
>>                </exclusion>
>>              </exclusions>
>>            </dependency>
>>           </dependencies>
>>         </plugin>
>>       </plugins>
>>     </pluginManagement>
>>   </build>
>>   ...
>>   <profiles>
>>     ...
>>     <profile>
>>       <id>siteFix</id>
>>       <activation>
>>         <activeByDefault>false</activeByDefault>
>>       </activation>
>>       <properties>
>>         <maven.site.plugin.version>2.1.1</maven.site.plugin.version>
>>       </properties>
>>     </profile>
>>   </profiles>
>> ...
>>
>>
>> When I execute "mvn site" from the top level pom directory in maven
>> 2.0.8, it builds the site for the top directory and all of the
>> modules. If I execute "mvn -PsiteFix site" from maven 2.2.1, it does
>> not build the modules and only builds the site for the current
>> directory.
>>
>> Is there a way to get this to function as it did before?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Mime
View raw message