On 2012-03-31 16:46, Hervé BOUTEMY wrote: > Le samedi 31 mars 2012 16:09:44 Dennis Lundberg a écrit : >>> Here's my bid: >>> >>> doxia >>> +-- doxia-base (was doxia) >>> >>> +-- doxia-core >>> +-- doxia-logging-api >>> +-- doxia-modules >>> +-- doxia-sink-api >>> +-- doxia-test-docs (stays here for now) >>> >>> +-- doxia-sitetools >>> >>> +-- doxia-decoration-model >>> +-- doxia-doc-renderer >>> +-- doxia-site-renderer >>> >>> +-- doxia-tools >>> >>> +-- doxia-book-renderer (was doxia/doxia-book) >>> +-- doxia-book-maven-plugin (was doxia/doxia-maven-plugin) >>> +-- doxia-converter >>> +-- doxia-ide (moved here from root) >>> +-- doxia-linkcheck >>> +-- doxia-integration-tools (was shared/maven-doxia-tools) >> >> The only thing we seem to not agree on, is whether to keep the >> doxia-tools directory or not. Apart from that I'm fine with your bid. > in this version, doxia-tools can be not the parent module for one single > release cycle, but a simple directory from the site (like /plugins/ for maven) > > doxia-ide, for example, with its main compoentn doxia-eclipse, won't be > released as part as a unique doxia-tools release > > So with Lukas directory structure, and the doxia-tools nature change to a > simple directory, each sub-diretory having its own release cycle, I think wa > can have the best of everyone ideas
So, we keep the doxia-tools directory, but remove the parent pom.xml that is in that directory? Works for me. That means that there won't be an artifact named doxia-tools any more, which was my main driver, and we can gradually remove it from the site. -- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
