Finish v1.0.0

Author: pinhead84

.env.example

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+#
+# Environment variables for build scripts.
+# Copy this file to ".env" and enter your custom environment variables.
+#
+
+GO="${HOME}/go/go1.16.2/bin/go"
+export GOPATH="${HOME}/go"

.gitignore

@@ -0,0 +1,76 @@
+/.env
+/target
+/testing/Contents/MacOS
+
+
+#
+# Default entries for IntelliJ IDEA
+# based on https://github.com/github/gitignore/blob/master/Global/JetBrains.gitignore
+#
+
+# Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio and WebStorm
+# Reference: https://intellij-support.jetbrains.com/hc/en-us/articles/206544839
+
+# User-specific stuff
+.idea/**/workspace.xml
+.idea/**/tasks.xml
+.idea/**/usage.statistics.xml
+.idea/**/dictionaries/*
+.idea/**/shelf
+
+# Generated files
+.idea/**/contentModel.xml
+
+# Sensitive or high-churn files
+.idea/**/dataSources/
+.idea/**/dataSources.ids
+.idea/**/dataSources.local.xml
+.idea/**/sqlDataSources.xml
+.idea/**/dynamic.xml
+.idea/**/uiDesigner.xml
+.idea/**/dbnavigator.xml
+
+# Gradle
+.idea/**/gradle.xml
+.idea/**/libraries
+
+# Gradle and Maven with auto-import
+# When using Gradle or Maven with auto-import, you should exclude module files,
+# since they will be recreated, and may cause churn.  Uncomment if using
+# auto-import.
+.idea/modules.xml
+.idea/*.iml
+.idea/modules
+
+# CMake
+cmake-build-*/
+
+# Mongo Explorer plugin
+.idea/**/mongoSettings.xml
+
+# File-based project format
+*.iws
+
+# IntelliJ
+out/
+
+# mpeltonen/sbt-idea plugin
+.idea_modules/
+
+# JIRA plugin
+atlassian-ide-plugin.xml
+
+# Cursive Clojure plugin
+.idea/replstate.xml
+
+# Crashlytics plugin (for Android Studio and IntelliJ)
+com_crashlytics_export_strings.xml
+crashlytics.properties
+crashlytics-build.properties
+fabric.properties
+
+# Editor-based Rest Client
+.idea/httpRequests
+
+# Android studio 3.1+ serialized cache file
+.idea/caches/build_file_checksums.ser

.idea/.gitignore

@@ -0,0 +1,8 @@
+Changelog for JavaMacLauncher
+=============================
+
+
+1.0.0 (18 Mar 2021)
+-------------------
+
+-   first public release

.idea/runConfigurations/build.xml

@@ -0,0 +1,39 @@
+# Contributing
+
+
+## Notes about branches
+
+This project follows the principles of the [GitFlow branching model](http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/) as [proposed by Vincent Driessen](http://nvie.com/posts/a-successful-git-branching-model/). According to this model you will find these branches at the GitHub project page:
+
+-   The [master branch](https://github.com/OpenIndex/JavaMacLauncher/tree/master) contains the current stable releases. No development is directly taking place in that branch.
+     
+-   The [develop branch](https://github.com/OpenIndex/JavaMacLauncher/tree/develop) represents the current state of development. Changes from this branch are merged into [master](https://github.com/OpenIndex/JavaMacLauncher/tree/master) when a new version is released.
+    
+-   For more complex features you may also find different feature branches. These are derived from [develop branch](https://github.com/OpenIndex/JavaMacLauncher/tree/develop) and are merged back / removed as soon as the feature is ready for release.
+
+> **Notice:** If you like to provide changes to this project, you should always use the [develop branch](https://github.com/OpenIndex/JavaMacLauncher/tree/develop) as basis for your customization. Feel free to create separate feature branches for any custom feature you like to share. 
+
+
+## Create a pull request
+
+We love pull requests. Here's a quick guide.
+
+-   Fork this project into you GitHub profile.
+
+-   Clone the [develop branch](https://github.com/OpenIndex/JavaMacLauncher/tree/develop) of the repository to your 
+    local disk:
+    ```
+    git clone -b develop git@github.com:your-username/JavaMacLauncher.git
+    ```
+    
+-   Do your changes to the local repository and push the changes back into your fork at GitHub.
+ 
+-   [Submit a pull request](https://github.com/OpenIndex/JavaMacLauncher/compare/) with the changes from your fork.
+
+At this point you're waiting on us. We like to comment on pull requests as soon as possible. We may suggest some changes or improvements or alternatives.
+
+Some things that will increase the chance that your pull request is accepted:
+
+-   Test your changes.
+
+-   Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).