Changes that are made to the site.xml file will *not* be picked up by the site plugin in all cases. You need to do:
  mvn clean
  mvn site
to get those changes into the generated site.

fuvo wrote:
Hello Wayne and Dennis,

of course, we have our own parent pom which is the parent for all our
projects. And of Course, I have found the documentation of the site plugin.
But I cant see there, how and where I have to configure the use of our own
site.
Ok, I can change the site.xml to format the date and so on. But where do I
have to announce it, so that all 'child' projects can inherit it just like
the parent pom? If i put a changed site.xml (only the date changed as mentioned on the
examples page of the site plugin) in a src/site dir of our parent pom, then
it will be deployed in the repository parallel to our company.pom. But if i
generate the reports, it has no effect to the generated site.

Can anybody tell me how I can get this to work?

regards, Volker



Wayne Fay wrote:
Put the configuration in a parent and make all your projects derive
from it. Your skin has to be declared *somewhere* otherwise the
default is used.

Wayne

On 8/15/07, fuvo <[EMAIL PROTECTED]> wrote:
Hi,

I searching for a way to make my own template/skin and use this in
different
projects as default skin. As I understand, I have to put my created
template/skin in every project. But thats really not what I want.

What I want is:
my own skin jar (like
http://svn.apache.org/viewvc/maven/skins/trunk/maven-classic-skin/) which
will automatically used whenever I calll 'mvn site' on any project
without
configuring this in every project. Generating the skin jar is no problem,
but I have no idea what I have to do that maven uses my skin instead of
the
maven default skin.

Can anybody help me with this?

regards,

Volker
--
View this message in context:
http://www.nabble.com/customized-Site-Skin-Template-for-use-in-different-projects-tf4273529s177.html#a12163346
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






--
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to