Support of Maven Multi Module Project

[zicheee]

I have the same problem as asked in #562, but this issue was closed without further information. My multi module maven project has the following structure:

Project

• database
  ejb packaged project for communicating with the database holding hibernate classes ...
• common
  ejb packaged project with common code like StringUtil, DateUtil ...
• admin
  war project (JSF / PrimeFaces admin-interface)
• frontend
  war project (JSF frontend for public users)
• api
  war project offering REST-APIs for external apps
• ear
  maven ear project bundling admin, frontend and api to a single ear file. All war projects are using the common / database project.

When I open the project in Eclipse I can deploy the ear project and everything is deployed in a folder called e.g. "project.ear":

I tried to use this plugin for VS Code but I am not sure how I should deploy the ear correctly. After some testing I have this setup:

deployables": {
    "c:\\Temp\\Project\\ear\\target\\ear-1.0.0-SNAPSHOT": {
      "label": "c:\\Temp\\Project\\ear\\target\\ear-1.0.0-SNAPSHOT",
      "path": "c:\\Temp\\Project\\ear\\target\\ear-1.0.0-SNAPSHOT",
      "options": {
        "option": {
          "deployment.output.name": "project.ear"
        }
      }
    }
  }

The server starts and everything is working again, but I have a main problem compared to Eclipse: Whenever I change a file (e.g. index.html in admin.war) nothing is redeployed. The deployment is done as compiled files:

When I manually call "Publish Server (Incremental)" the files are undeployed and redeployed. This takes very long time and is not necessary for debugging.

So far I could not find any documentation showing how a project like this should be deployed. For Eclipse it is very easy and no documentation is needed as it is straight forward. But here I am having trouble to understand what needs to be done.

[robstryker]

I'll look into this, but I'm going to be honest: a lot of the infrastructure needed for dependent projects nad nested projects that was provided by eclipse is missing in this ecosystem. I'm trying to do what I can to discover how to bridge these gaps without being disruptive, but it's a challenge for sure.

I'll try to investigate this but there's really no promise of a fast timeline on this issue at the moment =/ I have some ideas but... they'll take time to work out.

[zicheee]

Hi robstryker,
thank you for your reply. If I can do anything to assist, let me know. I was not aware, that this "feature" was a special Eclipse thing. I thought this is standard Maven and I just don't have enough knowledge about this topic.

[lzcjames]

Hello, I have the same problem, I will continue to follow up on this issue