commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dennis Lundberg <denn...@apache.org>
Subject Re: [parent] maven 3 vs. 2 trick not inherited from commons-parent
Date Fri, 11 Mar 2011 20:37:24 GMT
On 2011-03-11 08:32, Jochen Wiedmann wrote:
> Stupid question: Is there any reason for not using the 3.x site plugin
> with Maven 2?

There were quite a lot of internal changes made in Maven 3, that
requires a different approach to site generation compared to Maven 2.
Some work has begun where we're trying to see if it's possible to make
the 3.x Site Plugin compatible with Maven 2, but it's in its still infancy.

> 
> On Thu, Mar 10, 2011 at 10:08 PM, Gary Gregory <garydgregory@gmail.com> wrote:
> 
>> In [paren] v18, we have a nice trick to use maven-site-plugin 2.x with Maven
>> 2.x and maven-site-plugin 3.x with Maven 3.x .
>>
>> See
>> http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html
>>
>> If you want to look at the parent POM, look for:
>>
>>    <profile>
>>      <id>maven-3</id>
>>
>> But, this does not work.
>>
>> When I have the same bit of XML in [codec]'s POM for example, it works.
>>
>> Any ideas what needs to be done for this to work without adding the XML to
>> every project?
>>
>> For [codec], it just works, you invoke m2 or m3 without additional
>> arguments.
>>
>> --
>> Thank you,
>> Gary
>>
>> http://garygregory.wordpress.com/
>> http://garygregory.com/
>> http://people.apache.org/~ggregory/
>> http://twitter.com/GaryGregory
>>
> 
> 
> 


-- 
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message