https://github.com/vinetos/java-portable

Install a portable version of the JDK (and bundled JRE) and run it everywhere without admin rights on Windows.
https://github.com/vinetos/java-portable

java jdk jre portable powershell

Last synced: 2 days ago
JSON representation

Install a portable version of the JDK (and bundled JRE) and run it everywhere without admin rights on Windows.

• Host: GitHub
• URL: https://github.com/vinetos/java-portable
• Owner: Vinetos
• License: gpl-3.0
• Created: 2017-12-07T19:25:59.000Z (almost 7 years ago)
• Default Branch: master
• Last Pushed: 2022-08-14T11:31:36.000Z (about 2 years ago)
• Last Synced: 2024-09-25T01:41:50.948Z (2 days ago)
• Topics: java, jdk, jre, portable, powershell
• Language: PowerShell
• Homepage:
• Size: 27.3 KB
• Stars: 45
• Watchers: 7
• Forks: 15
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Java Portable (JDK and JRE)

Install a **portable version** of the JDK (and bundled JRE) and **run it everywhere** without **admin rights** on **Windows**.  

**The scripts don't touch your project files in any way or form.**

### You can: 

* **Install the JDK (+ JRE)** on a removable device (like USB key).

* **Run and compile** application on every computer which can run Java.  

**Works without internet** (only setup need an internet connection).

# Prerequisite

 - **Windows 7 and higher**.

 - **Powershell 2.0** or highter (see [get powershell](https://github.com/PowerShell/PowerShell#get-powershell)\) \(installed by default on Windows\).

# Installation

Before run, make sure that you have **an active internet connection**.

Run ``Setup.ps1`` with **powershell** to download, create and setup the jdk files.

# Run everywhere

Once you have done the installation,  

**Run** ``start.bat`` on **the computer you want** to use the JRE/JDK. It will set environment variables for applications which needs Java.

# That's It

Type ``java -version`` and ``javac -version`` into CMD to see if all works fine !

# Shortcomings

In an environment with a ``Restricted`` PowerShell execution policy, you have to start scripts in the following way

 ```PowerShell.exe -ExecutionPolicy Bypass -File ```