I also like the idea of externalizing the docs.
Have you thought about building maven archetypes? Not sure whether this
would be possible with gradle though.
Besides the archetype plugin sucks.
Regarding the versions. Wouldn't you you some sort of filtering during
build time?
--Hardy
On Th
On Fri, 2010-08-27 at 10:50 +0200, Hardy Ferentschik wrote:
> I also like the idea of externalizing the docs.
>
> Have you thought about building maven archetypes? Not sure whether this
> would be possible with gradle though.
> Besides the archetype plugin sucks.
Thought about it? Sure. My "i
I guess my concern here is mostly the lack of cohesion. So we'd be
discussing stuff in a web page opened in the users browser, referencing
source code that is open in their IDE.
I guess everything else is just technical details. Bottom line is
whether we think this is easier for users or less.
So I worked on this approach today.
http://anonsvn.jboss.org/repos/hibernate/core/trunk/documentation/quickstart/
This is the root source directory for the "Getting Started Guide" (its a
pom of type "jdocbook").
Under it is a "tutorials" directory which defines a (unrelated)
multi-module maven
