That's too bad. Ant is such a commonly used tool (even for non-java projects) that I was hoping to have direct integration of Ant just like IntelliJ does. It would be very convenient to have the Ant Support plugin that breaks down all the Ant tasks in your build xml file.
The point is that WI will not include IDEA's Ant support. Fill free to file a feature request to http://youtrack.jetbrains.net/issues/wi and describe your (concrete) use case(s) i.e. "launch ant tasks, ..." etc.
The use case is in testing and deployment of large apps that rely heavily on external libraries: in almost all our major projects, the source tree consists of different libraries in different versions (production vs. debug), possibly multiple content roots, and also different resources and settings files, depending on the actual test or deployment scenario at hand.
Managing all these artifacts manually is a tedious and at times error-prone task. So it would actually be very nice to have the ability to run a custom build process which collects the artifacts required, bundles the appropriate version of each library, possibly builds PHARs from selected subtrees etc. Sometimes required tasks may also include transformation of a PEAR-style class tree into a single flat file or precompilation of PHP bytecode.
I acknowledge that for ANT to be really useful during deployment of PHP apps one would probably need to implement some specialized tasks (which is where we are currently heading). But the basic makings of a great build system are all there, so why not use them?
I assumed that it would be rather simple to provide ANT support in Web IDE, which leads me to believe that your decision to exclude it is a political rather than a technical one?
Nope, reasons are purely technical. Ant plugin is tightly integrated with Java plugin and from user our perspective decoupling effort is too big, judging the low amount of user requests. We do plan to eventually have general parts of the IDEA Artifacts plugin adding PHP specifics, however its out of WI 1.0 timeframe. I highly recommend you to file PEAR/PHAR support and all related feature requests to tracker so we can consider them while planning post 1.0 activity. Mind that we are Java developers and can miss some importand yet relatively easy-to-implement stuff that may help you.
No, this was not planned. However you still can edit ant XML files and run it as an external tool from IDE. Why are you need 'exact' integration?
That's too bad. Ant is such a commonly used tool (even for non-java projects) that I was hoping to have direct integration of Ant just like IntelliJ does. It would be very convenient to have the Ant Support plugin that breaks down all the Ant tasks in your build xml file.
The point is that WI will not include IDEA's Ant support. Fill free to file a feature request to http://youtrack.jetbrains.net/issues/wi and describe your (concrete) use case(s) i.e. "launch ant tasks, ..." etc.
The use case is in testing and deployment of large apps that rely heavily on external libraries: in almost all our major projects, the source tree consists of different libraries in different versions (production vs. debug), possibly multiple content roots, and also different resources and settings files, depending on the actual test or deployment scenario at hand.
Managing all these artifacts manually is a tedious and at times error-prone task. So it would actually be very nice to have the ability to run a custom build process which collects the artifacts required, bundles the appropriate version of each library, possibly builds PHARs from selected subtrees etc. Sometimes required tasks may also include transformation of a PEAR-style class tree into a single flat file or precompilation of PHP bytecode.
I acknowledge that for ANT to be really useful during deployment of PHP apps one would probably need to implement some specialized tasks (which is where we are currently heading). But the basic makings of a great build system are all there, so why not use them?
I assumed that it would be rather simple to provide ANT support in Web IDE, which leads me to believe that your decision to exclude it is a political rather than a technical one?
Nope, reasons are purely technical. Ant plugin is tightly integrated with Java plugin and from user our perspective decoupling effort is too big, judging the low amount of user requests.
We do plan to eventually have general parts of the IDEA Artifacts plugin adding PHP specifics, however its out of WI 1.0 timeframe. I highly recommend you to file PEAR/PHAR support and all related feature requests to tracker so we can consider them while planning post 1.0 activity. Mind that we are Java developers and can miss some importand yet relatively easy-to-implement stuff that may help you.