One alternative is to use the pattern of having a separate
site-pom.xml to document such a 'disconnected' parent.
See, for example:
https://svn.apache.org/repos/asf/maven/pom/trunk/asf
On Sat, Aug 20, 2011 at 4:24 PM, Lukas Theussl wrote:
>
> This is probably related to http://jira.codehaus.org
This is probably related to http://jira.codehaus.org/browse/MSITE-600.
Can you provide a simple test project? I am currently looking into it.
-Lukas
Randy Sr wrote:
I moved from 3.0-beta3 to 3.0 of the maven site plugin and now my site
deployment is broken. I have a root project with a site
I moved from 3.0-beta3 to 3.0 of the maven site plugin and now my site
deployment is broken. I have a root project with a site and a multi-module
project that has the root project as a parent but with a
completely separate site. With the 3.0 maven site plugin, it makes the
multi-module project sit
On 20 August 2011 10:45, Ansgar Konermann
wrote:
>
> Am 20.08.2011 11:37 schrieb "Tim Pizey" :
>>
>> Hi,
>>
>> I see from
>> https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-PluginMetaversionResolution
>>
>> Plugin Metaversion Resolution
>> Internally, Ma
Am 20.08.2011 11:37 schrieb "Tim Pizey" :
>
> Hi,
>
> I see from
https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-PluginMetaversionResolution
>
> Plugin Metaversion Resolution
> Internally, Maven 2.x used the special version markers RELEASE and
> LATEST to
Hi,
I see from
https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-PluginMetaversionResolution
Plugin Metaversion Resolution
Internally, Maven 2.x used the special version markers RELEASE and
LATEST to support automatic plugin version resolution. These
met
