2012/3/3 Jeremy Boynes :
> Thanks Olivier. Based on this, this is my suggestion for taglibs:
>
> Remove the site entries from the parent project so we don't impact taglib
> modules when the site content changes.
> Make the site module responsible for the top-level site (o.a.t/taglibs) and
> each
Thanks Olivier. Based on this, this is my suggestion for taglibs:
Remove the site entries from the parent project so we don't impact taglib
modules when the site content changes.
Make the site module responsible for the top-level site (o.a.t/taglibs) and
each taglib (currently standard and rdc)
euh as there isn't any distributionManagement-> site
this will go no where
Maybe do as I have done for the maven plugin see
http://tomcat.apache.org/maven-plugin.html
so versionned documentation is published.
http://tomcat.apache.org/maven-plugin-${project.version}
Pom content:
apach
Is there any information lying around on how to update the taglibs site?
Is taglibs-parent/site.xml actually used or is everything in the site module?
What's the process for publishing? Where does it deploy to? Is a vote needed
before push? Do we want to preview changes online or is a review bas
