Recent changes to Building from Source Code

Building from Source Code modified by ryker aiden hill

ryker aiden hill — Tue, 01 Feb 2022 20:50:05 -0000

--- v5
+++ v6
@@ -4,10 +4,7 @@

 ### Building the jar file

-* `mvn clean`
 * `mvn install`
-
-The command `mvn clean` will actually install a dependency that is not available from a public maven repository to the local maven repository, so it is necessary to execute.

 This will place the jar file under `target/<filename>.jar`.

</filename>

Building from Source Code modified by ryker aiden hill

ryker aiden hill — Tue, 01 Feb 2022 20:50:03 -0000

--- v4
+++ v5
@@ -32,4 +32,4 @@

 ### Building with Travis CI

-Travis CI will execute the steps under **Building the jar file** for the regular build. It will also create the wrappers for Mac OS X and Windows when it create a new release.
+Travis CI will execute the steps under **Building the jar file** for the regular build. It will also create the wrappers for Mac OS X and Windows when it creates a new release.

Building from Source Code modified by ryker aiden hill

ryker aiden hill — Tue, 01 Feb 2022 20:49:59 -0000

Building Amidst from Source Code modified by ryker aiden hill

ryker aiden hill — Tue, 01 Feb 2022 20:49:57 -0000

--- v2
+++ v3
@@ -1,22 +1,28 @@
 The build process is configured via the file `src/main/resources/amidst/metadata.properties`. For example the `<filename>` is taken from the variable `amidst.build.filename`.

-Amidst uses maven for its build process. Here are the steps to build from source:
+Amidst uses maven for its build process.
+
+### Building the jar file

 * `mvn clean`
 * `mvn install`
- 
+
+The command `mvn clean` will actually install a dependency that is not available from a public maven repository to the local maven repository, so it is necessary to execute.
+
 This will place the jar file under `target/<filename>.jar`.

-To build the wrapper for mac, follow these steps:
+### Building the wrapper for Mac OS X

 * `mvn clean`
 * `mvn install`
 * `mvn package -DskipTests=true -f travis-ci/wrapper-for-mac/pom.xml`
 * `bash travis-ci/scripts/zip-and-move-wrapper-for-mac.sh`

+The `zip-and-move-wrapper-for-mac.sh` bash script simply creates a zip file from the directory located at `travis-ci/wrapper-for-mac/target/<filename>/`. You can also do this by yourself.
+
 This will place the zip file under `target/<filename>.zip`.

-To build the wrapper for windows, follow these steps:
+### Building the wrapper for Windows

 * `mvn clean`
 * `mvn install`
@@ -24,8 +30,6 @@

 This will place the exe file under `target/<filename>.exe`.

-The `zip-and-move-wrapper-for-mac.sh` bash script simply creates a zip file from the directory located at `travis-ci/wrapper-for-mac/target/<filename>/`. You can also do this by yourself.
+### Building with Travis CI

-All of these steps are also executed by travis-ci to create a new release. However the regular travis-ci build will not create the wrappers for mac and windows.
-
-The command `mvn clean` will actually install a dependency that is not available from a public maven repository to the local maven repository, so it is necessary to execute.
+Travis CI will execute the steps under **Building the jar file** for the regular build. It will also create the wrappers for Mac OS X and Windows when it create a new release.
</filename></filename></filename></filename></filename></filename>

Building Amidst from Source Code modified by ryker aiden hill

ryker aiden hill — Tue, 01 Feb 2022 20:49:57 -0000

--- v1
+++ v2
@@ -11,7 +11,6 @@

 * `mvn clean`
 * `mvn install`
-* `bash travis-ci/scripts/create-mac-icon.sh`
 * `mvn package -DskipTests=true -f travis-ci/wrapper-for-mac/pom.xml`
 * `bash travis-ci/scripts/zip-and-move-wrapper-for-mac.sh`

@@ -21,12 +20,11 @@

 * `mvn clean`
 * `mvn install`
-* `bash travis-ci/scripts/create-windows-icon.sh`
 * `mvn package -DskipTests=true -f travis-ci/wrapper-for-windows/pom.xml`

 This will place the exe file under `target/<filename>.exe`.

-You will need imagemagick installed to create the icons. Of course, you can also create the icon files by yourself and place them as `target/icon.icns` (mac) or  `target/icon.ico` (windows) to the expected location. The `zip-and-move-wrapper-for-mac.sh` bash script simply creates a zip file from the directory located at `travis-ci/wrapper-for-mac/target/<filename>/`. You can also do this by yourself.
+The `zip-and-move-wrapper-for-mac.sh` bash script simply creates a zip file from the directory located at `travis-ci/wrapper-for-mac/target/<filename>/`. You can also do this by yourself.

 All of these steps are also executed by travis-ci to create a new release. However the regular travis-ci build will not create the wrappers for mac and windows.

</filename></filename></filename>

Building Amidst from Source Code modified by ryker aiden hill

ryker aiden hill — Tue, 01 Feb 2022 20:49:56 -0000

The build process is configured via the file src/main/resources/amidst/metadata.properties. For example the <filename> is taken from the variable amidst.build.filename.

Amidst uses maven for its build process. Here are the steps to build from source:

mvn clean
mvn install

This will place the jar file under target/<filename>.jar.

To build the wrapper for mac, follow these steps:

mvn clean
mvn install
bash travis-ci/scripts/create-mac-icon.sh
mvn package -DskipTests=true -f travis-ci/wrapper-for-mac/pom.xml
bash travis-ci/scripts/zip-and-move-wrapper-for-mac.sh

This will place the zip file under target/<filename>.zip.

To build the wrapper for windows, follow these steps:

mvn clean
mvn install
bash travis-ci/scripts/create-windows-icon.sh
mvn package -DskipTests=true -f travis-ci/wrapper-for-windows/pom.xml

This will place the exe file under target/<filename>.exe.

You will need imagemagick installed to create the icons. Of course, you can also create the icon files by yourself and place them as target/icon.icns (mac) or target/icon.ico (windows) to the expected location. The zip-and-move-wrapper-for-mac.sh bash script simply creates a zip file from the directory located at travis-ci/wrapper-for-mac/target/<filename>/. You can also do this by yourself.

All of these steps are also executed by travis-ci to create a new release. However the regular travis-ci build will not create the wrappers for mac and windows.

The command mvn clean will actually install a dependency that is not available from a public maven repository to the local maven repository, so it is necessary to execute.