fix: cds build now generates the correct output folder structure for Node.js and Java apps.

[LotharBender]

• identical output folder structure for node.js and java as documented in Capire
• use existing package.json from db folder instead of generated one

[LotharBender]

We should add some tests for the cds build plugin functionality - currently it isn't tested at all...

[johannes-vogel]

We should add some tests for the cds build plugin functionality - currently it isn't tested at all...

@swaldmann @LotharBender @patricebender

I'd propose to add tests after we've released that hotfix or is that something you can do quivkly within that PR?
I'd like to ship the fix asap.

[patricebender]

fine by me if we add the test later (as soon as possible) if you are certain that this change is correct.

[LotharBender]

fine by me if we add the test later (as soon as possible) if you are certain that this change is correct.

Deployment layout is now generated according to Capire doc.

• Node.js

project
  - gen
    - pg
      package.json
      - db 
        csn.json
        - data

• Java
  For Java there is currently only a Liquibase, but no cds deployer based sample app.

project
  - gen
    - pg
      package.json
      - db 
        csn.json
        - data

[johannes-vogel]

@swaldmann could you please also have a look?

[johannes-vogel]

@LotharBender The changes in cap-js/postgres are independent of Java. Hence, I think we can merge and release, don't we?

[LotharBender]

@LotharBender The changes in cap-js/postgres are independent of Java. Hence, I think we can merge and release, don't we?

Yesterday we had a meeting with @mofterdinger and agreed to go for the same deployment folder structure for Java and Node.js as described in Capire - let's merge this PR.