The usual eclipse development process with CQ5 uses maven to build the OSGI bundles and content packages. These are the deployment artifacts which can be deployed to CQ5.
WAR is a format suited for application servers, but CQ5 itself is not an application server in a J2E sense.
Thank you for the response Jorg!
Doesnt the Publish instance offer app server-like capabilities? What else can I do to structure the "ui" part of my maven project in a WAR format?
It doesn't make sense to create a deployment package in a WAR format, as you cannot deploy a WAR file to CQ5.
CQ5 itself is a webapplication, and you can get in a WAR format to deploy it to J2E application servers. But you cannot deploy WAR files into CQ5, as CQ5 itself is not a servlet container or something like that.
Thank you Jorg. That was helpful.
My concern was regarding 'exporting' the application that I create using CQ in a WAR format not importing a war file onto CQ5.
But I think what you are saying is, since CQ5 doesnt have the functionality to import a project in war format, it doesnt provide the capability to export one.