commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Schaible <joerg.schai...@scalaris.com>
Subject Re: [parent] maven 3 vs. 2 trick not inherited from commons-parent
Date Fri, 11 Mar 2011 07:31:39 GMT
Jörg Schaible wrote:

> Hi Gary,
> 
> Gary Gregory wrote:
> 
>> On Thu, Mar 10, 2011 at 10:27 PM, Jörg Schaible
>> <joerg.schaible@gmx.de>wrote:
>> 
>>> Hi Gary,
>>>
>>> Gary Gregory 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.
>>>
>>> What do you men with "this does not work"? It does.
>>>
>> 
>> If I take out the profiles element from the [codec] POM (from SVN) and
>> run "mvn clean site" with Maven 3, (almost) nothing happens. M3 says the
>> build was OK but it does not do anything.
> 
> The profile does add only the site-descriptor as an attached artifact
> anyway, simply because that's no longer done in M3. It has nothing to do
> with the site generation itself. However, your problem is that the pom of
> codec redefined the site-plugin in its pluginMgmt section again as version
> 2.2 - which will produce nothing for M3. This has to be removed (alongside
> with the redefinition with the profile). On top of it does the parent 18
> define version 2.0.1 in the reporting section - but that's relevant for M2
> only.

Fixed it.

- Jörg


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


Mime
View raw message