Feedback and high-quality pull requests are highly welcome!
Haxe4E is an extension for the Eclipse IDE to support development using the Haxe general purpose programming language.
- Syntax Highlighting
- Source Code Formatting
- Auto Completion
- Code Refactoring
- Running and debugging of Haxe Eval programs
- Display project dependencies in project outline
If you don't have Eclipse installed you can install Haxe Studio - a custom Eclipse distribution - which has this plugin preinstalled.
To install Haxe4E into an existing Eclipse installation do:
- Within Eclipse go to: Help -> Install New Software...
- Enter the following update site URL: https://raw.githubusercontent.com/haxe4e/haxe4e/updatesite
- Select the
Haxe4E
feature to install. - Ensure that the option
Contact all update sites during install to find required software
is enabled. - Click
Next
twice. - Read/accept the license terms and click
Finish
. - Eclipse will now download the necessary files in the background.
- When the download has finished, Eclipse will ask about installing unsigned content. You need to accept if you want to
- 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 project, which declares fixed versions and sensible default settings for all official Maven plugins.
The project also uses the maven-toolchains-plugin, which decouples the JDK used to execute Maven and its plugins from the target JDK used for compilation and 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:
-
Install a Java 17 JDK
Download and install a Java 17 SDK, e.g. from:
-
Configure Maven Toolchains
In your user home directory, create the file
.m2/toolchains.xml
with the following content:<?xml version="1.0" encoding="UTF8"?> <toolchains xmlns="http://maven.apache.org/TOOLCHAINS/1.1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/TOOLCHAINS/1.1.0 https://maven.apache.org/xsd/toolchains-1.1.0.xsd"> <toolchain> <type>jdk</type> <provides> <version>17</version> <vendor>default</vendor> </provides> <configuration> <jdkHome>[PATH_TO_YOUR_JDK_17]</jdkHome> </configuration> </toolchain> </toolchains>
Replace
[PATH_TO_YOUR_JDK_17]
with the path to your JDK installation. -
Clone the Repository
git clone https://github.com/haxe4e/haxe4e.git
-
Build the Project
Run
mvnw clean verify
in the project root directory. This will execute compilation, unit testing, integration testing, and packaging of all artifacts.
Haxe4E was created by Sebastian Thomschke and is sponsored by Vegard IT GmbH.
Haxe4E would not have been possible without the following technologies and learning resources:
Technologies/Libraries
- Haxe Language Server
- Haxe TextMate Grammar
- Haxe Formatter
- Eclipse Platform
- Eclipse LSP4E - Language Server Protocol for Eclipse
- Eclipse TM4E - TextMate support for Eclipse
- Eclipse Tycho - tools to build Eclipse plug-ins with Maven
- Eclipse RedDeer - UI testing framework
Tutorials
- https://eclipse.org/articles
- https://blogs.itemis.com
- https://www.vogella.com/tutorials
- http://blog.eclipse-tips.com
If not otherwise specified (see below), files in this repository fall under the Eclipse Public License 2.0.
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:
- files in readable text which contain their own license information, or
- files in a directory containing a separate
LICENSE.txt
file, or - 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 examplefoobar.js
is may be accompanied by afoobar.LICENSE.txt
license file.