EAR creation in Roo

[jbbarquero]

We need to create Java EE applications (EAR files) in order to deploy them in Java Application Servers (WebSphere Application Server, for instance)

Why Roo doesn't allow within the command line to create a Maven project for creating an EAR file?

We could use the Maven EAR plug-in, but we would like to delegate all the stuff to Roo, as we do with the web projects (WAR files)

Thank you.

[Andrew Swan]

Can't Websphere deploy a WAR file? Or is there some other reason you have to have an EAR file?

[jbbarquero]

Can't Websphere deploy a WAR file? Or is there some other reason you have to have an EAR file?

Thank you for your interest.

It is not a matter of WebSphere, but a requirement of the application to be deployed within the enterprise.

We have to provide an ear with its war and particular business jars (although there are shared libraries like spring or log4j)

[Stefan Schmidt]

Maybe the maven ear plugin can help you here? http://maven.apache.org/plugins/maven-ear-plugin/ I have not used that one though as I have not seen any need for it. Roo generated applications run in all web containers so your requirement is quite unusual.

-Stefan

[jbbarquero]

Maybe the maven ear plugin can help you here? http://maven.apache.org/plugins/maven-ear-plugin/ I have not used that one though as I have not seen any need for it. Roo generated applications run in all web containers so your requirement is quite unusual.

-Stefan

I will try.

However, I'd rather to obtain all the Java artifacts via Roo than using external tools for some Java parts.

The use of EARs is very natural for us.

According SUN, the EAR is the natural way to provide a complete Java EE application.

IBM thinks the same, and all their tools (RAD, WAS...) are oriented to manage EARs (in fact they use EAR enhanced, but we try to avoid them in order to achieve a real WORA application)

Is it totally out of schedule to create EAR artifacts within Roo?

Thank you very much.

[Stefan Schmidt]

Well actually, if you want Roo to create a war file you would use the maven war plugin which is installed for you by Roo in the project pom. So the ear plugin would simply be another maven plugin which you paste into the pom file yourself rather than Roo doing it. That would be about the only difference I can think of.