Hi,
I like the idea to have report generation on all modules.
But we should keep coherence across all james projects (server, mailbox,
mailets,...).
For example, server and mailbox don't have site for each modules.
On the other hand, mailet has site for each of its modules.
Repeating the skin and banners in each site.xml (as proposed in the
current patch) may be not the best reuse approach... but I don't know if
there's a better way to reuse the parent site.xml definitions from the
modules.
If there's no way to reuse the parent site.xml definitions, I'm still in
favor to commit the proposed patch, and open a jira to have the same
approach on server, mailbox,... projects.
Tks,
- Eric
On 23/02/2011 15:48, Felix Knecht wrote:
If this is an issue (and not on purpose) I can work over the over
projects as well. Please let me now which ones.
Regards
Felix
On 02/23/2011 03:38 PM, Felix Knecht (JIRA) wrote:
Missing site generation for modules
-----------------------------------
Key: IMAP-261
URL: https://issues.apache.org/jira/browse/IMAP-261
Project: JAMES Imap
Issue Type: Improvement
Components: Documentation
Affects Versions: 0.2
Environment: all
Reporter: Felix Knecht
"mvn site" only generates the site of the root module (imap/trunk)
but doesn't includes sites of the modules. This may be on purpose,
but all non aggregating reports like e.g. findbugs are likely to be
missed this way.
---------------------------------------------------------------------
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]
