AppEngine Project Structure

Answered

Hey Guys,

I was hoping someone could help me with my AppEngine project setup in Intelli-J. In Idea 15, everything seemed a little more straightforward, but now I'm updating to 16 and I'm also breaking my project into modules. My directory structure is as follows:

project\
---- ear\
-----------src\main\application\META-INF
---- common\
----------src\main\java
----------src\test\java
---- server\
----------src\main\java
----------src\main\resources
----------src\main\webapp
----------src\test\java
---- web\
----------src\main\java
----------src\main\resources
----------src\main\webapp
----------src\test\java
build.gradle
settings.gradle

Each of the sub-projects has their own build.gradle as well. Web and Server have their own appengine-web.xml and web.xml files. ear has the definition files.

When I import the into Intelli-J, I get A TON of modules. For instance, my server module has:

server
server_endpointsSrc
server_functionalTest
server_main
server_test

All the other modules (ear, common, web, project) have a similar layout. What are all these modules for, especially endpointsSrc and functionalTest. Do I add my facets (such as AppEngine and GWT) to the module root or to the main? How do I create the dependencies?

I'm just a little turned around.

Thanks!

E

3 comments
Comment actions Permalink

In the latest version a new module is created per Gradle source set, there is an option to control it when importing:

See https://youtrack.jetbrains.com/issue/IDEA-153231 for details.

0
Comment actions Permalink

Hi Serge,

What advantages are there to the super many module structure?

Thanks,

E

0
Comment actions Permalink

You can check the ticket I've linked, it mentions what issues this feature fixes.

0

Please sign in to leave a comment.