compile the application about remotesupporttool HOT 22 CLOSED

$ java -version
java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
$ javac -version
javac 1.8.0_92

from remotesupporttool.

You need at least Java 11 in order to compile the application. You can download it from BellSoft or AdoptOpenJDK.

from remotesupporttool.

By the way: Take a look at this wiki page for further notes about compiling the application for yourself.

from remotesupporttool.

I'll try now! thx a lot.

from remotesupporttool.

hello bro pinhead84 I was compiled successfully but the jars files not open the interface customer

whats the jar file is the correct after build, in target folder of customer any jar file is found, any idea?

from remotesupporttool.

Compilation is only the first step. You also need to obtain OpenJDK 11 for the different target platforms. Afterwards you need to prepare the release and create the application bundles (self extracting EXE launcher, macOS application bundle, SH launcher for Linux).

According to your screenshots it looks like you're using Windows? - We currently don't have any build scripts for Windows systems, that will do these tasks automatically. If possible I would suggest to use Linux or macOS, if you like to create the application bundles for all target platforms. In this case you only need to launch some scripts. The whole stuff is documented on the development wiki page.

But if you only like to do some testing, you can download the EXE files from the release page. These files are basically 7zip archives, which you can open and extract with 7zip. In the extracted folder you can put your modified / compiled JAR files into the modules subfolder and execute the applications via Start.exe in the bin subfolder. For simple testing this approach might be helpful.

Theoretically you can create your own EXE application bundles with 7zip after you've copied your modified JAR files into the extracted folder (as described here). It currently won't work automatically, but with some handwork you can also build these files on Windows systems.

from remotesupporttool.

great notes bro I have Debian here, I'll update jdk and test it on my Stretch

from remotesupporttool.

after compile mvn-install.sh
build done!

from remotesupporttool.

I was installed jdk 11 and mvn to work but now whats the jar file load app

my system break down after load some jars

from remotesupporttool.

In the first step launch release/openjdk-init.sh, which will download OpenJDK for the different platforms. You only need to run this command once.

Afterwards launch mvn-release.sh, which compiles the application and assembles the application folders in release/target/Customer and release/target/Staff (including previously downloaded OpenJDK).

In the last step launch the release/bundle-*.sh scripts, which will bundle the previously created application folders into single executable files. These are saved into release/target.

from remotesupporttool.

first of all I run install.sh next mvn-release.sh but in the release don't have openjdk-init.sh

from remotesupporttool.

running mvn-release.sh from release folder the process build bring me this error

from remotesupporttool.

In my last comment I've posted / linked the files, you are supposed to launch:

In the first step launch release/openjdk-init.sh, which will download OpenJDK for the different platforms. You only need to run this command once.

Afterwards launch mvn-release.sh, which compiles the application and assembles the application folders in release/target/Customer and release/target/Staff (including previously downloaded OpenJDK).

In the last step launch the release/bundle-*.sh scripts, which will bundle the previously created application folders into single executable files. These are saved into release/target.

By the way, you should use version 1.1.0. We've made some changes to the build process and not all of my comments may be valid for the older 1.0.1 version.

from remotesupporttool.

I tested now on version 1.0

is really need the secret key?

from remotesupporttool.

No. Use version 1.1.0 or the latest development branch. Build scripts have been significantly changed.

is really need the secret key?

In the old version you had to manually disable GPG signatures. This is not necessary anymore with the latest release / development branch.

from remotesupporttool.

I'll wait for new releases, but thanks you 4all helps bro. see yo

from remotesupporttool.

Read the documentation, follow the documentation, use the latest version and everything will be fine.

from remotesupporttool.

after update all dependencies whats the step by step... I was launched release/openjdk init.sh, than I launched mvn-release.sh and build

is this correct step?

I run mvn-install.sh first? I already try this proccess

from remotesupporttool.

I think that was missing...

from remotesupporttool.

after hours to download all files :/

from remotesupporttool.

The first steps were correct. You've already started release/openjdk-init.sh and don't need to bother about that anymore.

Your mistake was, that you should have run mvn-release.sh from the root directory of the repository - not from the release subfolder. This will compile the application and assemble all files required to start the application into the release/target/Customer and release/target/Staff folder.

• For example to start customer tool on Linux x86-64, you might launch release/target/Customer/linux-x86-64/bin/Start.sh.
• Or you can copy the folder release/target/Customer/windows-x86-64 to Windows 64bit and start the application via bin/Start.exe.

To create the application bundles, that contain all the application files and can easily be sent to other users, you can finally run the release/bundle-*.sh scripts. The created application bundles are stored into the release/target folder. These application bundles are also published on our release page.

As an alternative you can run all steps at once with this command:

export JAVE_HOME=/usr/lib/jvm/java-11-openjdk-amd64 && \
  rm -Rf RemoteSupportTool && \
  git clone https://github.com/OpenIndex/RemoteSupportTool.git && \
  cd RemoteSupportTool && \
  ./release/openjdk-init.sh && \
  ./mvn-release.sh && \
  ./release/bundle-linux.sh && \
  ./release/bundle-macos.sh && \
  ./release/bundle-windows.sh

Copy the whole command at once into your console, replace the path to your OpenJDK installation and press ENTER. The whole process might take a while, because once again all required OpenJDK versions have to be downloaded. Afterwards the application bundles are finally stored into the RemoteSupportTool/release/target folder.

from remotesupporttool.

I back dir folder and run mvn-release.sh again

Wow unbelievable!!

thanx a lot pinhead!! now lets try your tool! I was searching for something remote tools, like this. I think this tool can help me.

from remotesupporttool.