You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metamodel.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/12/01 21:25:00 UTC

[jira] [Commented] (METAMODEL-1205) Make MetaModel build work with JDK versions 9, 10, 11

    [ https://issues.apache.org/jira/browse/METAMODEL-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16706008#comment-16706008 ] 

ASF GitHub Bot commented on METAMODEL-1205:
-------------------------------------------

GitHub user kaspersorensen opened a pull request:

    https://github.com/apache/metamodel/pull/199

    METAMODEL-1205: Enabled all the Travis JDKs (and solving small build issues)

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kaspersorensen/metamodel travis-jdks

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/metamodel/pull/199.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #199
    
----
commit ab7098534d191692ecbad8a1aa04287ceb8b6893
Author: Kasper Sørensen <i....@...>
Date:   2018-12-01T21:18:42Z

    METAMODEL-1205: Enabling all the JDKs in Travis CI
    
    ... to find out what works on which JDK.

commit 3faebed1eff0f075038719037df6c7464c752bbe
Author: Kasper Sørensen <i....@...>
Date:   2018-12-01T21:23:01Z

    Fixed overlapping JAR file issue for activation-api

----


> Make MetaModel build work with JDK versions 9, 10, 11
> -----------------------------------------------------
>
>                 Key: METAMODEL-1205
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-1205
>             Project: Apache MetaModel
>          Issue Type: Improvement
>            Reporter: Kasper Sørensen
>            Assignee: Kasper Sørensen
>            Priority: Major
>
> I've been trying a few times to get the build for MetaModel to work on newer JDKs, and have been facing a few issues; first with ElasticSearch, then with Neo4j and such. I think it's time that we create a proper JIRA ticket where we can note the things preventing us from running on the latest JDKs, and hopefully resolve those issues.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)