On Aug 21, 2009, at 1:52 AM, Adam Murdoch wrote:
Hans Dockter wrote:
I have just submitted a new build structure for the Gradle build.
The Gradle build is now a multi-project build with a root project
and two subprojects.
root
- gradle-core (which contains everything except wrapper)
- gradle-wrapper
ATM root is doing user's guide, distribution, release and
integtest. The integtest are still part of gradle-core but executed
from root. Although this shows the enormous flexibility of Gradle
it probably should not remain like this.
How do we want to go from here? Some idea:
root (integtest (including dealing with the integ test sources),
distribution, release
- user's guide
- gradle-ui
- gradle-wrapper
- gradle-core
- plugins
-- osgi
-- jetty
-- eclipse
-- maven
-- ...
What should we do with the website? I'd much rather it were under
gradle-core/trunk, along with everything else.
That would make sense. We have to do the merging then, which is quite
painful as long as we use svn. But therefore we don't need to specify
the referring gradle working copy and manually build the website docs.
And the release could be truly 1-click (and not 2-click as it is now).
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
