Deploy a NodeJs (FrontEnd) and a Spring (BackEnd) project as one artefact

continuous integrationJenkinsmavennode.js

I have a current project which consist out of two independently developed projects:

Spring REST as back end
Angular as front end

I do have a Jenkins instance available for building my projects and I'd would like to "marry" both of the projects in a CD job to a single deployable file (.jar)

Is this a job of jenkins, to copy all needed files together? Or is this usually solved with a maven plugin? I couldn't find much information about that, although it seems like a very common step to me.

Best Answer

Ant or Maven are usually used for this. For example, Apache Wicket calls npm and Grunt from within the pom.xml:

<artifactId>wicket-js-tests</artifactId>
<packaging>jar</packaging>
<name>Wicket JavaScript Tests</name>
<description>JavaScript tests for all Wicket modules</description>


<execution>
  <id>install node and npm</id>
  <goals>
    <goal>install-node-and-npm</goal>
  </goals>
  <phase>generate-resources</phase>
  <configuration>
    <npmVersion>5.6.0</npmVersion>
    <nodeVersion>v8.9.0</nodeVersion>
  </configuration>
</execution>

<execution>
  <id>npm install</id>
  <goals>
    <goal>npm</goal>
  </goals>
  <configuration>
    <arguments>install</arguments>
  </configuration>
</execution>

<execution>
  <id>grunt build</id>
  <goals>
    <goal>grunt</goal>
  </goals>
  <configuration>
    <!--<arguments> - -verbose </arguments>-->
  </configuration>
</execution>

And Apache Freemarker Docgen calls npm and Gulp from within build.xml:

  <!-- See README.md about installing node.js and Gulp! -->
  <target name="node-deps">
    <exec executable="npm" dir="${basedir}" failonerror="true" osfamily="unix">
      <arg line="install" />
    </exec>
    <exec executable="cmd" dir="${basedir}" failonerror="true" osfamily="windows">
        <arg line="/c npm install" />
    </exec>
  </target>

  <target name="gulp">
    <exec executable="node" failonerror="true" dir="${basedir}">
      <arg line="node_modules/gulp/bin/gulp.js"/>
    </exec>

    <!--
    <exec executable="${nodeJsCommand}" failonerror="true" dir="${basedir}">
      <arg value="node_modules/gulp/bin/gulp.js"/>
    </exec>
  -->
  </target>

References

Related Solutions

Java – Multi-module web project with Spring and Maven

well, i use to work with point 3, definining all dependencies at parent's pom, including dependencies form modules, like that:

<parent>
    <groupId>cat.base.baseframe</groupId>
    <artifactId>projecte-pare-baseframe</artifactId>
    <version>0.0.11.a</version>
</parent>

<properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>

<modules>
    <module>ogc.domini</module>
    <module>ogc.logica</module>
    <module>ogc.ejb</module>
    <module>ogc.ear</module>
    <module>ogc.ui</module>
    <module>ogc.assistent</module>
</modules>

<dependencies>
    <dependency>
        <groupId>cat.base.cuesfeina</groupId>
        <artifactId>cuesfeina.domini</artifactId>
        <version>0.0.3</version>
        <scope>provided</scope>
    </dependency>
    <dependency>
        <groupId>cat.base.gea</groupId>
        <artifactId>gea.domini</artifactId>
        <version>0.0.4</version>
        <scope>provided</scope>
    </dependency>
    <dependency>
        <groupId>baseOnline.ajudes</groupId>
        <artifactId>ajudes.domini</artifactId>
        <version>0.0.1-SNAPSHOT</version>
        <scope>provided</scope>
    </dependency>
    <dependency>
        <groupId>cat.base.tramitador</groupId>
        <artifactId>tramitador.domini</artifactId>
        <version>0.0.4</version>
        <scope>provided</scope>
    </dependency>
<dependency>
        <groupId>cat.base</groupId>
        <artifactId>mme.domini</artifactId>
        <version>1.3.3</version>
        <scope>provided</scope>
    </dependency>

-->

everything at pom's parent's it's easy to find what you need. if you need to call some service i i use to create a public jar with functions to call the service like ejb...

Methods for Separating Front and Back-End in Full Stack JavaScript

It's a front-end, back-end application, with a REST interface in between. You already have full separation.

My vote is for option # 3. You seem worried about configuration, but that's kinda the whole point. Configuration allows you to have full separation without requiring tightly-coupled code bindings. If you're worried about CORS, put everything on one domain. If you must have CORS, the best way to manage that is a configuration.

But there is no "best practice" here. The best practice is the one that is going to best meet your specific needs.

Best Answer

Related Solutions

Java – Multi-module web project with Spring and Maven

Methods for Separating Front and Back-End in Full Stack JavaScript

Related Topic