OASP integrated Build with JavaScript Client

[ivanderk]

Based on a mail send by Jörg Hohwiller,

We should use frontend-maven-plugin to build the client integrated with the server. This should happen in the regular build of the SAMPLE application. The change should integrate the OASP4js client dist directly into the WAR file. There should also be a profile to integrate the sencha app.

Profiles should be:

• jsclient - oasp4j + oasp4js
• senchaclient - oasp4j + sencha client
• servicelayer - oasp4j

while using jsclient by default (activeProfile)

https://github.com/oasp/oasp4j/blob/develop/samples/server/pom.xml#L30

To get started:
…

<js.build.tool>npm</js.build.tool>
<js.node.version>v5.12.0</js.node.version>
<js.npm.version>3.5.2</js.npm.version>
<js.yarn.version>v0.21.3</js.yarn.version>

…



com.github.eirslett
frontend-maven-plugin

${js.client.dir}



js-client-install-tools
generate-sources

install-node-and-${js.build.tool}



${js.node.version}
${js.npm.version}
${js.yarn.version}



js-client-install-dependencies
generate-sources

${js.build.tool}


install



js-client-gulp-clean
generate-sources

gulp


clean



js-client-gulp-build
generate-sources

gulp


build:dist

[ivanderk]

See: #214

[ivanderk]

When closing, please close #214 as well

[kiran-vadla]

As discussed in the Architects meet today , because of the time constraints and complexity , this is being moved to oasp4j-3.0.0 release.

Thanks,
@kiran-vadla

[hohwille]

IMHO for restaurant sample this makes no sense any more. For MTS this is more or less already in place.
The only thing left to go is IMHO to redesign the archetypes with this in mind so we could offer an archetype for full-stack development with oasp4js + oasp4j in combination.
IMHO we should clarify this, create a new story issue for that and close all this.
WDYT?

[hohwille]

I have created #619 as a replacement and close this issue as duplicate.