Dean Schulze wrote:
I'd like to start adopting gradle by making a gradle build to parallel
the Ant build*.xml files that I use for my J2EE projects.
I've looked at the user guide and the java examples that come with
gradle, but they're not much help. The 2 examples aren't remotely
like a typical J2EE project, and the user guide isn't much better.
The Java multi-project sample is intended to be a typical J2EE project -
it produces a WAR file and a bunch of JAR files. I'm surprised that you
think it isn't remotely like one. How can we improve things to make this
more clear, do you think? What's different to your J2EE project?
There's a walk-through of this sample at
http://www.gradle.org/0.6/docs/userguide/tutorial_java_projects.html
If you don't want to split your build up into multiple projects, you
could use the web application quick start sample. There's an
(incomplete) walk-through at
http://www.gradle.org/0.6/docs/userguide/web_project_tutorial.html
One thing these samples don't do is produce an EAR task. You can either
use the Zip task, or Ant's Ear task in your build. You might want to
have a look at
http://www.gradle.org/0.6/docs/userguide/java_plugin.html#N112B3 for
information about adding archives to a project.
Does anyone have an example of how to use Gradle to build typical
J2EE project - a .ear containing multiple .wars and .jars?
Thanks.
