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 page. If Java.Net was not prepending anything special > for > > the /index.html content (in addition to the regular Java.Net chrome), > then > > my src/site/apt/index.apt file would be of the form: > > For all this, I guess the best solution is going to be to allow out of > order sections (perhaps with a warning). This shouldn't be harmful, I > don't think. > > Can you file that in JIRA?
http://jira.codehaus.org/browse/MNG-2024 I would like to be able to have a clean build with no warnings, despite having some APT fragment files in the project, and it would be important to still get warnings for other non-fragment APT files in case of user error. > Btw, is there any support in site skinning to supply an additional > Velocity > > Macro template for special files that have fixed names and should only > be > > generated once for the whole project, rather than running the macro on > every > > file in the site? > > No this is generally done by reports, but I'm not sure that's what you > are looking for here since it is really just a fragment. > > You can include it in the resources in the skin to have it hopy as > direct HTML - we might need to add some filtering though to be able to > modify it. That would be a new feature request if just static HTML is > not sufficient. I currently have a static HTML file in site/resources that successfully integrates with the Java.Net chrome. However, since this static file contains references to dynamically generated reports, I would like to generate this HTML fragment during site generation to keep the list of reports and their links synchronized. Having a custom report to generate this chrome fragment seems like a workaround, since we'll also need to customize the Velocity template used during site generation (which I understand can be customized by a site "skin"). I would like to have a single Java.Net "skin" that both gets the Velocity template correct and also generates the chrome fragment to dyamically link in the generated site reports. > Many of the standard Maven reports are duplicates of the Java.Net ones > added > > in the chrome at runtime, so we'd need to be able to exclude the > well-known > > duplicates and capture the rest automatically. > > > > It would be really great if all of this could actually be captured in a > > single site skin. > > The skin isn't really related to the selected reports at this point. > It might just need to be a FAQ on how to enable the right reports. Yep, fair enough. Even if these are generated anyway, it doesn't matter too much. Kind Regards, John Fallows. --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://apress.com/book/bookDisplay.html?bID=10044 Author: Pro JSF and Ajax: Building Rich Internet Components, Apress
