Why do you want to remove doxia-tools? I like the idea to have all the
independent apps collected in one folder.
Also, I think the original reason for maven-doxia-tools to go into
shared was to de-couple it from doxia, so it could be released
independently. I would prefer to leave it outside doxia/doxia-sitetools.
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)
Cheers,
-Lukas
Dennis Lundberg wrote:
Hi guys
Here's an attempt to summarize this discussion and also add some of my
personal preference. This is how I want the directory structure, which
matches the inheritance structure, to be
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-integration-tools (was shared/maven-doxia-tools)
+-- doxia-linkcheck (moved here from doxia-tools)
+-- doxia-site-renderer
+-- doxia-book-renderer (was doxia/doxia-book)
+-- doxia-book-maven-plugin (was doxia/doxia-maven-plugin)
+-- doxia-converter (moved here from doxia-tools)
+-- doxia-ide
a. Rebrand "Doxia" to "Doxia base" to differentiate it from Doxia - the
umbrella. We do not change the groupId.
b. doxia-test-docs stays where it is for now, until someone has the time
to look at it
c. shared/maven-doxia-tools moves to
doxia-sitetools/doxia-integration-tools. We should change the artifactId
and groupId now, because the current version of shared/maven-doxia-tools
is 1.4, but the new one will be 1.3.
d. In order to completely remove the psuedo-umbrella project doxia-tools
we move doxia-converter to the root and doxia-linkcheck to
doxia-sitetools. Another alternative is to move doxia-linkcheck to root.
e. doxia-book and doxia-maven-plugin work together, but should be
allowed to have independent release cycles, so they both move from doxia
to the root.
I also suggest changing their names to better reflect what they do.
doxia-book therefor becomes doxia-book-renderer and doxia-maven-plugin
becomes doxia-book-maven-plugin. This change should include changing the
artifactId for both of them.
Do we agree on this?
On 2012-03-31 08:55, Lukas Theussl wrote:
Hervé BOUTEMY wrote:
Le samedi 31 mars 2012 08:24:50 Lukas Theussl a écrit :
The other way round was it? doxia-book into Doxia Tools and
doxia-maven-plugin into Sitetools.
-Lukas
no, Tools can depend on Sitetools, but not the other way
Right, didn't think about the dependencies. I'd move both to Tools then,
that way they can have independent releases from doxia/sitetools.
-Lukas
the other ways would be do move both modules to Tools or Sitetools
but not doxia-book to Tools and doxia-maven-plugin to Sitetools
Regards,
Hervé
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
