The css works for me perfect. Generated under resource/css and it will
be copied in the correct target location.
I use xdocs, because I want to have full control over html and the content.
What I also have done ... created in the vm file an additional tag,
because I need an additional container in the body (important for me),
but it shows that there should be more control over the xdocs. E.g. you
have a $bodyContent and why not have a $section and $subsection, where
you have seperate control with macros over the content. Currently I
don't have access to the plugins ... (in maven 1 this was a feature I
loved ... check the plugins, change it, try it. Currently I have to work
in a jar file ....)
Another thing after I checked the DoxiaMojo.class ... the project report
will only and only than generated when you add the ${project} tag into
the site.xml. If you don't have a report, the site for project info
isn't generated. For me .. a must. This are the things, that made maven
strong. Got the properties from the project directly in an info page for
your project docu.
Thank for your help. I will check tomorrow how I can help.
Heiko
ahgt sur laposte.net wrote:
=> What do you think about m2 site generation?
It's fast.
The both xdoc and apt format are a good thing
Globaly, it looks better structured.
But...
It appears, for the time being, that there is even less flexibility and
"basic and important features" available than in M1.
Ex : being able to write some Xdoc with css class in the tags... And
have them in the xhtml produce. This is flexible, and let the user go
further in style and nice presentation...
I hope it is "for the time being"... And the site feature will (soon)
allow most of the features needed to publish a site...
=> We don't have properties in m2. You can create a css directory under
the
site directory ant put in it your rewritten css file.
I tried this, but it seems that the last .css file that are copied in
the destination folder, are the maven original ones.
I may try again this test if you confirm it should be the rewritten ones
that comes to the destination folder last... (real overriding the
original one).
No properties ? How to configure what was in properties ? Date ?
Copiryght ?, etc....
=> many thanks for the maven site plugin... And the help...
Antoine
-----Message d'origine-----
De : Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 30 juin 2005 16:27
À : Maven Users List
Objet : Re: RE : m2 site
ahgt sur laposte.net wrote:
Sorry, I use M2 for site and have no answer.
What do you think about m2 site generation?
But... How do you change the css files used in the page ?
The properties "maven.xdoc.theme.url" in M1.1 does not seem to work.
For the time being, I change the maven-theme.css in the jar of
maven... But this is no proper solution.... If you have an answer
about the properties that where used in M1...
We don't have properties in m2. You can create a css directory under the
site directory ant put in it your rewritten css file.
Emmanuel
Antoine
-----Message d'origine-----
De : puschteblume [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 30 juin 2005 13:34
À : [email protected]
Objet : m2 site
Hi, where have the externalLink classes and newWindow gone? If I
create
a <a href> with an externalLink the classes attribute isn't appended.
Also if I manual assign a css class, the resulting html code doesn't
include it. Do you filter the $bodyContent in Doxia?
Heiko
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
