On 5/27/10 5:50 PM, Felix Knecht wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/27/10 17:41, Emmanuel Lecharny wrote:
On 5/27/10 5:31 PM, Felix Knecht wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
To have our custom checkstyle configuration there seems the need of
having a module containing the configuration
(http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html).
Do we put this into a new project on its own (e.g.
directory/build-tools) and be able to use the same checkstyle
configuration for all directory projects or do we add the build-tools
module to every project wanted and have (jsut in case) different
checkstyle configurations for different directory projects?
Can't we use the 'project' module for that ?
IMO no. It's pom packaged not jar (<packaging>pom</packaging>) and we
need a jar file as dependency.
"The packaging type required to be pom for parent and aggregation
(multi-module) projects." (http://maven.apache.org/pom.html#Inheritance)
So one per module ?
apacheds/build-tools
shared/build-tools
installer/build-tools
...
Would this be ok?
What about having one single external project, as you initially
suggested, in which we also push the doco, assuming that we may want to
use docbook to generate the documentation, instead of confluence ?
Is it a possibility ?
If we do so, is there a way from a docbook documentation to update the
web site ? (I guess it is, as we have the template).
wdyt ?
--
Regards,
Cordialement,
Emmanuel Lécharny
www.nextury.com
