https://github.com/sebthom/open-with-eclipse-plugin
Eclipse plugin to register a Windows "Open with Eclipse" context menu entry for Eclipse.
https://github.com/sebthom/open-with-eclipse-plugin
eclipse-plugin java
Last synced: 6 months ago
JSON representation
Eclipse plugin to register a Windows "Open with Eclipse" context menu entry for Eclipse.
- Host: GitHub
- URL: https://github.com/sebthom/open-with-eclipse-plugin
- Owner: sebthom
- License: epl-2.0
- Created: 2021-10-26T19:54:51.000Z (over 4 years ago)
- Default Branch: main
- Last Pushed: 2025-08-01T15:17:56.000Z (6 months ago)
- Last Synced: 2025-08-01T17:36:04.781Z (6 months ago)
- Topics: eclipse-plugin, java
- Language: Java
- Homepage: https://buymeacoffee.com/vegardit
- Size: 1.54 MB
- Stars: 4
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE.txt
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# "Open with Eclipse" plugin for Eclipse
[](https://github.com/sebthom/open-with-eclipse-plugin/actions/workflows/build.yml)
[](CODE_OF_CONDUCT.md)
[](LICENSE.txt)
[](https://marketplace.eclipse.org/content/open-eclipse-plugin)
**Feedback and high-quality pull requests are highly welcome!**
1. [What is it?](#what-is-it)
1. [Installation](#installation)
1. [Building from Sources](#building)
1. [License](#license)
This plugin allows you to register a Windows Explorer "Open with Eclipse" menu entry for your Eclipse installation.
To install the plugin into an existing Eclipse installation do:
1. Within Eclipse go to: Help -> Install New Software...
1. Enter the following update site URL: https://raw.githubusercontent.com/sebthom/open-with-eclipse-plugin/updatesite
1. Select the `Open with Eclipse` feature to install.
1. Ensure that the option `Contact all update sites during install to find required software` is enabled.
1. Click `Next` twice.
1. Read/accept the license terms and click `Finish`.
1. Eclipse will now download the necessary files in the background.
1. When the download has finished, Eclipse will ask about installing unsigned content. You need to accept if you want to
1. After installation you will be prompted for a restart of Eclipse, which is recommended.
To ensure reproducible builds this Maven project inherits from the [vegardit-maven-parent](https://github.com/vegardit/vegardit-maven-parent)
project which declares fixed versions and sensible default settings for all official Maven plug-ins.
The project also uses the [maven-toolchains-plugin](http://maven.apache.org/plugins/maven-toolchains-plugin/) which decouples the JDK that is
used to execute Maven and it's plug-ins from the target JDK that is used for compilation and/or unit testing. This ensures full binary
compatibility of the compiled artifacts with the runtime library of the required target JDK.
To build the project follow these steps:
1. Download and install a Java 17 SDK, e.g. from:
- https://adoptium.net/releases.html?variant=openjdk17
- https://www.azul.com/downloads/?version=java-17-lts&architecture=x86-64-bit&package=jdk
1. Download and install the latest [Maven distribution](https://maven.apache.org/download.cgi).
1. In your user home directory create the file `.m2/toolchains.xml` with the following content:
```xml
jdk
17
default
[PATH_TO_YOUR_JDK_17]
```
Set the `[PATH_TO_YOUR_JDK_17]` parameter accordingly.
1. Checkout the code using one of the following methods:
- `git clone https://github.com/sebthom/open-with-eclipse-plugin`
- `svn co https://github.com/sebthom/open-with-eclipse-plugin open-with-eclipse-plugin`
1. Run `mvn clean verify` in the project root directory. This will execute compilation, unit-testing, integration-testing and
packaging of all artifacts.
If not otherwise specified (see below), files in this repository fall under the [Eclipse Public License 2.0](LICENSE.txt).
Individual files contain the following tag instead of the full license text:
```
SPDX-License-Identifier: EPL-2.0
```
This enables machine processing of license information based on the SPDX License Identifiers that are available here: https://spdx.org/licenses/.
An exception is made for:
1. files in readable text which contain their own license information, or
2. files in a directory containing a separate `LICENSE.txt` file, or
3. files where an accompanying file exists in the same directory with a `.LICENSE.txt` suffix added to the base-name of the original file.
For example `foobar.js` is may be accompanied by a `foobar.LICENSE.txt` license file.