<commit_before>test-editor-xtext
=================

[![License](http://img.shields.io/badge/license-EPL-blue.svg?style=flat)](https://www.eclipse.org/legal/epl-v10.html)
[![Build Status](https://ci.testeditor.org/buildStatus/icon?job=test-editor-xtext_develop)](https://ci.testeditor.org/job/test-editor-xtext_develop)

An Xtext based editor to specify domain-driven acceptance tests.

## Users

The latest released version can be found on [bintray](https://bintray.com/test-editor/test-editor/testeditor-app).

The latest development version can be downloaded [here](https://ci.testeditor.org/job/test-editor-xtext/job/develop/lastSuccessfulBuild/artifact/rcp/org.testeditor.rcp4.product/target/products/).



## Developers

Prerequisites:

- Maven 3.2.5
- JDK 1.8

After checking out the source code we first need to build the Eclipse target platform:

    mvn clean install -f "target-platform/pom.xml"
    
This will take some time for the first run but should be fast afterwards.

After building the target platform, we can simply build the test editor with:

    mvn clean install

For building the full RCP product we simply add the Maven profile "`product`":

    mvn clean install -Pproduct<commit_msg>TE-400 add a small troubleshooting section to the readme<commit_after>test-editor-xtext
=================

[![License](http://img.shields.io/badge/license-EPL-blue.svg?style=flat)](https://www.eclipse.org/legal/epl-v10.html)
[![Build Status](https://ci.testeditor.org/buildStatus/icon?job=test-editor-xtext_develop)](https://ci.testeditor.org/job/test-editor-xtext_develop)

An Xtext based editor to specify domain-driven acceptance tests.

## Users

The latest released version can be found on [bintray](https://bintray.com/test-editor/test-editor/testeditor-app).

The latest development version can be downloaded [here](https://ci.testeditor.org/job/test-editor-xtext/job/develop/lastSuccessfulBuild/artifact/rcp/org.testeditor.rcp4.product/target/products/).



## Developers

Prerequisites:

- Maven 3.2.5
- JDK 1.8

After checking out the source code we first need to build the Eclipse target platform:

    mvn clean install -f "target-platform/pom.xml"
    
This will take some time for the first run but should be fast afterwards.

After building the target platform, we can simply build the test editor with:

    mvn clean install

For building the full RCP product we simply add the Maven profile "`product`":

    mvn clean install -Pproduct

## Troubleshooting

### The downloaded application won't start

 The editor requires a JDK 1.8 in order to start. If you default system JVM is different, you can set the path to the JDK by opening the `eclipse.ini` file and placing the following at the end:
 
    -vm
    <pathToYourJDK8>
    
The path depends on your operating system as described [here](https://wiki.eclipse.org/index.php?title=Eclipse.ini&redirect=no#Specifying_the_JVM). For example (Windows):

    C:\tools\jdk1.8.0_92\bin\javaw.exe
{'fraction_non_alphanumeric': 0.11645910467855941, 'fraction_numerical': 0.009087849209020532, 'mean_word_length': 4.364620938628159, 'pattern_counts': {'":': 2, '<': 4, '<?xml version=': 0, '>': 4, 'https://': 11, 'lorem ipsum': 0, 'www.': 2, 'xml': 2}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 5, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '31080', 'n_tokens_mistral': 956, 'n_tokens_neox': 897, 'n_words': 274}