this is a nice thread ... i think, what adam writes, gives a clear answer to the initial question.
IMO gradle should have an ear-task that makes the use of Ant's Ear/Zip task obsolete and there should be added an example for building the ear on base of the sample-multi-project-build. not much to do besides that for supporting j2ee. gruesse Adam Murdoch-2 wrote: > > 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. >> >> > > -- View this message in context: http://www.nabble.com/Is-there-an-example-for-migrating-a-J2EE-project-from-Ant-to-Gradle--tp23675660p23800086.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
