Skip to content

[JUnit] Add module-info for cucumber-junit-platform-engine #1867

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jan 25, 2020

Conversation

mpkorstanje
Copy link
Contributor

@mpkorstanje mpkorstanje commented Jan 23, 2020

Summary

Adds module-info for Cucumber Junit Platform Engine implementation.
This allows Java to ensure that all dependencies are available at
boot time.

To ensure backwards compatibility down to Java 8 we are using
multi-release jar files which will contain both Java 8 and
Java 9 class files.

To ensure the right JDK (OpenJDK 11) is used to build the project
the Maven Toolchains plugin will verify that this JDK is used.
This does require adding a toolchains.xml file to the ~/.m2/
folder.

Example:

<?xml version="1.0" encoding="UTF8"?>
<toolchains>
    <toolchain>
        <type>jdk</type>
        <provides>
            <version>11</version>
            <vendor>openjdk</vendor>
        </provides>
        <configuration>
            <jdkHome>/path/to/openjdk11</jdkHome>
        </configuration>
    </toolchain>
</toolchains>

@mpkorstanje mpkorstanje force-pushed the try-openjdk-for-javadoc branch 2 times, most recently from 9673390 to 98d1e01 Compare January 24, 2020 01:54
@mpkorstanje mpkorstanje changed the title [Build] Use openjdk to build javadoc [JUnit] Add module-info.java Jan 24, 2020
@mpkorstanje mpkorstanje force-pushed the try-openjdk-for-javadoc branch 2 times, most recently from b1eab6b to 0abd5bc Compare January 25, 2020 15:29
@mpkorstanje
Copy link
Contributor Author

No tool-chain.xml provided by Travis CI.

travis-ci/travis-ci#2727

@mpkorstanje
Copy link
Contributor Author

https://travis-ci.community/t/add-support-for-maven-toolchain-plugin/5004

it is extremely difficult to maintain toolchains by project in travis for the simple reason that the locations of the installed jdks are not obvious and they do keep changing.

Looks like it is time to drop Travis for something else.

@mpkorstanje
Copy link
Contributor Author

The first mvn install -DskipTests=true -Dmaven.javadoc.skip=true -B -V doesn't help either because travis is not providing tool chains.

https://stackoverflow.com/questions/31945809/skip-first-mvn-install-in-travis-ci

@mpkorstanje mpkorstanje added this to the 5.x.x milestone Jan 25, 2020
@mpkorstanje mpkorstanje changed the title [JUnit] Add module-info.java [JUnit] Add module-info.java for cucumber-junit-platform-engine Jan 25, 2020
@mpkorstanje mpkorstanje changed the title [JUnit] Add module-info.java for cucumber-junit-platform-engine [JUnit] Add module-info for cucumber-junit-platform-engine Jan 25, 2020
Adds module-info for Cucumber Junit Platform Engine implementation.
This allows Java to ensure that all dependencies are available at
boot time.

To ensure backwards compatibility down to Java 8 we are using
multi-release jar files which will contain both Java 8 and
Java 9 class files.

To ensure the right JDK (OpenJDK 11) is used to build the project
the Maven Toolchains plugin will verify that this JDK is used.
This does require adding a `toolchains.xml` file to the ~/.m2/
folder.

Example:

```xml
<?xml version="1.0" encoding="UTF8"?>
<toolchains>
    <toolchain>
        <type>jdk</type>
        <provides>
            <version>11</version>
            <vendor>openjdk</vendor>
        </provides>
        <configuration>
            <jdkHome>/path/to/openjdk11</jdkHome>
        </configuration>
    </toolchain>
</toolchains>
```
@mpkorstanje mpkorstanje force-pushed the try-openjdk-for-javadoc branch from 7603a28 to bfd7342 Compare January 25, 2020 19:43
@mpkorstanje mpkorstanje merged commit 1859f52 into master Jan 25, 2020
@mpkorstanje mpkorstanje deleted the try-openjdk-for-javadoc branch January 25, 2020 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant