-
From: ewryan [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 28, 2008 1:53 PM
To: users@maven.apache.org
Subject: Maven2 site plugin inheritence
I have a multi-module project with the following directory structure:
my-app
|
|---my-client-ui
| |
| |---pom.xml
|
|---my-core
ewryan wrote:
I define properties such as ${myVersion}, ${myArtifactId}, ${myGroupId} in
the parent pom. These properties are inherited by the children (as
expected) when running goals such as clean, package, or install.
I start to see problems when I try to use the site plugin.
Hi
is, is it possible for me to use the site plugin with property
inheritance?
--
View this message in context:
http://www.nabble.com/Maven2-site-plugin-inheritence-tp15743257s177p15743257.html
Sent from the Maven - Users mailing list archive at Nabble.com
Hi John,
On 1/10/06, John Fallows [EMAIL PROTECTED] wrote:
Yeah, I considered that, but don't think it is quite right. This issue of
headings is specific to /index.html in the generated site, and does not
affect any other page. If Java.Net was not prepending anything special for
the
Hi Brett,
On 1/29/06, Brett Porter [EMAIL PROTECTED] wrote:
Hi John,
On 1/10/06, John Fallows [EMAIL PROTECTED] wrote:
Yeah, I considered that, but don't think it is quite right. This issue
of
headings is specific to /index.html in the generated site, and does not
affect any other
Summary:
I'm using the maven-site-plugin for Maven2 to generate the site
documentation for a Java.Net project and the APT parser is choking on the
syntax needed to get the desired look for the index page.
org.codehaus.doxia.module.apt.AptParseException: expected SECTION1, found
SECTION2 at line
Hi John,
I think the answer is not to change the APT parsing, but allow mapping
level 1 to h3, level 2 to h4, etc (I think that's what you wanted?) It
still may be worth looking into.
Either way, these are core changes that would need to be investigated
(please JIRA). In the interim, can you
Hi Brett,
On 1/9/06, Brett Porter [EMAIL PROTECTED] wrote:
Hi John,
I think the answer is not to change the APT parsing, but allow mapping
level 1 to h3, level 2 to h4, etc (I think that's what you wanted?) It
still may be worth looking into.
Yeah, I considered that, but don't think it is
I've seen the site plugin still not available from
http://maven.apache.org/maven2/plugin-list.html
so i would like to know:
Which technology will site plugin use ?
Do you plan to make the plugin pluggable with different site
generation technology ?
Regards
--
Massimo
http://meridio.blogspot.com
On 5/3/05, Massimo Lusetti [EMAIL PROTECTED] wrote:
I've seen the site plugin still not available from
http://maven.apache.org/maven2/plugin-list.html
so i would like to know:
Which technology will site plugin use ?
Our own implementation that is quite small and fast. It still reads
xdoc, but
10 matches
Mail list logo
