perhaps my idea is best implemented as a gradle plugin.... not everyone is using gradle for java. and most probably wouldn't want the default dir structure...
but it would be useful for getting familiar with gradle and for new java projects where you don't mind having a default dir structure On Mon, Feb 22, 2010 at 12:11 PM, Paul Speed <[email protected]> wrote: > I missed this at first too, but in hindsight, gradle requires much less of > your environment than other similar build tools. > > For example, to start a new Java project, create a build.gradle file where > you want your module to be and put: > > usePlugin( 'java' ) > > ...or > apply id: 'java' > > ...in the latest version. > > Create a src/main/java/your/package directory. > Create your Java file. > run: gradle classes or gradle build > > Add the other stuff as you need them. This is in contrast to something like > maven where even the default pom is fairly verbose, etc.. > > For what it's worth, I do have environments where creating a new project is > more involved but in that case it's pretty easy just to have a > setup-model.gradle file that can be called with gradle -b just to build out > the initial project. > > I'm not saying gradle shouldn't have something like this (though I doubt I > would use it personally), just that there are pretty easy work-arounds. > > -Paul > > phil swenson wrote: >> >> I don't know if this is a good idea.... but I think it would be very >> cool to have a "gradle project" task... >> >> you run it and it creates an empty directory structure with the >> "optimal" layout for gradle. >> >> So something like >> >> "gradle project myproj" would create a directory structure like: >> >> myproj >> ---------modules >> ---------------------default >> -------------------------------lib >> -------------------------------src >> -------------------------------test >> -------------------------------conf >> -------------------------------build >> >> and a default gradle.build file would be generated with dummy sample >> tasks to build your dependencies. >> >> I don't know gradle well enough to know what an optimize directory >> structure is, but I was thinking of supporting different directory >> structures for each "module". Guess that would be an optional thing, >> as many project only have one module, so this could be overkill. >> >> Anyway, this is just an idea that popped into my head. Rails >> inspired.... it's really nice how in rails you can generate a skeleton >> very easily. I'm sure grails has something like this, but I'm >> thinking of the concept for any project, not just grails or a web >> project >> >> any thoughts? Am I retarded ? >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
