PromucFlow_constructor/app/server/build.sh

#!/bin/bash

# Remove previous dist directory
rm -rf dist/

# Build the code. $@ accepts all the parameters from the input command line and uses it in the maven build command
mvn clean package "$@"

if [ $? -eq 0 ]
then
  echo "mvn Successfull"
else
  echo "mvn Failed"
  exit 1
fi

# Create the dist directory
mkdir -p dist/plugins

# Copy the server jar
cp -v ./appsmith-server/target/server-*.jar dist/

# Copy all the plugins
rsync -av --exclude "original-*.jar" ./appsmith-plugins/*/target/*.jar dist/plugins/
Convert the project into a multi-module structure We are moving to a multi-module structure so that different parts of the codebase can be exposed to the public while others can remain private. Using pf4j for plugin framework. Also adding a build script `build.sh` which compiles the code and creates the `dist` folder for distribution purposes. Now we can build the code via ``` $ ./build.sh -DskipTests ``` 2019-09-16 11:21:57 +00:00			`#!/bin/bash`

			`# Remove previous dist directory`
Experimenting with maven-shade-plugin to create a fat-jar of the postgres dependency. Will have to do this for all plugins. Currently, it's not registering the plugin with the SpringPluginManager 2020-06-10 11:11:23 +00:00			`rm -rf dist/`
Convert the project into a multi-module structure We are moving to a multi-module structure so that different parts of the codebase can be exposed to the public while others can remain private. Using pf4j for plugin framework. Also adding a build script `build.sh` which compiles the code and creates the `dist` folder for distribution purposes. Now we can build the code via ``` $ ./build.sh -DskipTests ``` 2019-09-16 11:21:57 +00:00
			`# Build the code. $@ accepts all the parameters from the input command line and uses it in the maven build command`
			`mvn clean package "$@"`

Added mvn failure check (#6107) 2021-07-26 00:07:10 +00:00			`if [ $? -eq 0 ]`
			`then`
			`echo "mvn Successfull"`
			`else`
			`echo "mvn Failed"`
			`exit 1`
			`fi`

Convert the project into a multi-module structure We are moving to a multi-module structure so that different parts of the codebase can be exposed to the public while others can remain private. Using pf4j for plugin framework. Also adding a build script `build.sh` which compiles the code and creates the `dist` folder for distribution purposes. Now we can build the code via ``` $ ./build.sh -DskipTests ``` 2019-09-16 11:21:57 +00:00			`# Create the dist directory`
			`mkdir -p dist/plugins`

			`# Copy the server jar`
Fix jar name in build script 2021-09-21 10:29:14 +00:00			`cp -v ./appsmith-server/target/server-*.jar dist/`
Convert the project into a multi-module structure We are moving to a multi-module structure so that different parts of the codebase can be exposed to the public while others can remain private. Using pf4j for plugin framework. Also adding a build script `build.sh` which compiles the code and creates the `dist` folder for distribution purposes. Now we can build the code via ``` $ ./build.sh -DskipTests ``` 2019-09-16 11:21:57 +00:00
			`# Copy all the plugins`
Experimenting with maven-shade-plugin to create a fat-jar of the postgres dependency. Will have to do this for all plugins. Currently, it's not registering the plugin with the SpringPluginManager 2020-06-10 11:11:23 +00:00			`rsync -av --exclude "original-.jar" ./appsmith-plugins//target/*.jar dist/plugins/`