Proper organization of the project structure in java and using gradle as a build system?

Question

Java

Gentlemen, I decided to take it on and rework the project structure in java (web application on jboss).
Now the situation is such there is a project for eclipse (it has several "subprojects"), the libraries are in the lib ass (does not use any mavens). the whole thing lies in St. Accordingly, such a structure does not allow the use of various IDEs for development. The project is built with ant scripts, and due to the large limitations of the ant script itself, this scripts are low-functional and confusing.
What you want:
1) make it possible to use different IDEs on the project and store the source code directly in the svn.
2) switch to a new build system to streamline settings and expand deployment options.
I would be very glad to constructive advice on the organization of the project. It is planned to use gradle as a system build, if I declare dependencies in gradle scripts, will IDEs pull them up and apply them (Ecplise, Idea) How is it most convenient to implement support for working in different IDEs?