You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by Suresh Marru <sm...@apache.org> on 2019/09/05 12:34:33 UTC
Upgrade Java Version
Hi All,
I noticed a travis build fail which complains minimum have required of 9 to 12 - “Expected feature release number in range of 9 to 14, but got: 8”.
Any thoughts on which version of JDK we should upgrade Airavata to before next release?
Cheers,
Suresh
Re: Upgrade Java Version
Posted by "Christie, Marcus Aaron" <ma...@iu.edu>.
Thanks for this summary of the work involved. Also kudos to you as well for making this possible.
> On Dec 6, 2019, at 5:10 PM, DImuthu Upeksha <di...@gmail.com> wrote:
>
> Hi Folks,
>
> We have upgraded java version to 11 with OpenJDK in development branch and successfully deployed it in development environment. Following changes were performed in the process
>
> 1. Upgrades of compiler plugin (3.5.1 -> 3.8.0) , surefire plugin (2.18.1 -> 3.0.0-M1), open jpa (2.4.3 -> 3.1.0). See PR 236 [3]
> 2. Adding javax dependencies explicitly as they were discontinued in default java 11 releases. See PR 234 [4]
> 3. Updating JDK to OpenJDK 11 [5]
> 4. Disabling Dozer mapper setter optimization [6]. This is a temporary fix and waiting for dozer team [7] to properly fix this.
> 5. Fixing remote debug [8]
> 6. Minor test failure fixes [9]
> 7. Upgrading Confluent/ Kafka version to (4.1.0 -> 5.3.0) [10]
>
> Travis build and develop environment are now stable :)
>
> Kudos to Isuru, Marcus and Suresh for pulling this off.
>
> [3] https://github.com/apache/airavata/pull/236/files <https://github.com/apache/airavata/pull/236/files>
> [4] https://github.com/apache/airavata/pull/234/files <https://github.com/apache/airavata/pull/234/files>
> [5] https://github.com/apache/airavata/commit/fd56623e303e579d7974b721ecd7f931498ad502 <https://github.com/apache/airavata/commit/fd56623e303e579d7974b721ecd7f931498ad502>
> [6] https://github.com/DImuthuUpe/dozer/commit/4d33729e866982cb7cee61065f0719c9c1212334 <https://github.com/DImuthuUpe/dozer/commit/4d33729e866982cb7cee61065f0719c9c1212334>
> [7] https://groups.google.com/forum/?fromgroups=#!topic/dozer-mapper/c1OPee1DwTw <https://groups.google.com/forum/?fromgroups=#!topic/dozer-mapper/c1OPee1DwTw>
> [8] https://github.com/apache/airavata/commit/5fb5629dfaaf503e1875737c58f703e5cdfad255 <https://github.com/apache/airavata/commit/5fb5629dfaaf503e1875737c58f703e5cdfad255>
> [9] https://github.com/apache/airavata/commit/7b1a2b3525f93a7057325b9df1e7251282e5294f <https://github.com/apache/airavata/commit/7b1a2b3525f93a7057325b9df1e7251282e5294f>
> [10] https://github.com/apache/airavata/commit/0859211fd8bfb8e2168e95d711fd27d83133c939 <https://github.com/apache/airavata/commit/0859211fd8bfb8e2168e95d711fd27d83133c939>
>
> Thanks
> Dimuthu
>
> On Tue, Oct 22, 2019 at 1:49 PM Suresh Marru <smarru@apache.org <ma...@apache.org>> wrote:
> Hi All,
>
> I posted a question for Apache Legal - https://issues.apache.org/jira/browse/LEGAL-484 <https://issues.apache.org/jira/browse/LEGAL-484>
>
> + 1 for moving to Java 11 and get the Travis build working again. We probably should try it against both OpenJDK and Oracle JDK latest 11 releases.
>
> Suresh
>
>> On Oct 21, 2019, at 4:34 PM, Christie, Marcus Aaron <machrist@iu.edu <ma...@iu.edu>> wrote:
>>
>> Might be good to ask Apache legal, but it's not like we're distributing Oracle JDK, so not sure what kind of guidance they could give.
>>
>> In the meantime, it would be great to get the Travis build working again.
>>
>>> On Oct 21, 2019, at 4:07 PM, DImuthu Upeksha <dimuthu.upeksha2@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> Hi Folks,
>>>
>>> What should we do about this? Should we contact Apache legal support to get things clarified about the licensing? We might need to stick to a decision before next release.
>>>
>>> Thanks
>>> Dimuthu
>>
>
Re: Upgrade Java Version
Posted by DImuthu Upeksha <di...@gmail.com>.
Hi Folks,
We have upgraded java version to 11 with OpenJDK in development branch and
successfully deployed it in development environment. Following changes were
performed in the process
1. Upgrades of compiler plugin (3.5.1 -> 3.8.0) , surefire plugin (2.18.1
-> 3.0.0-M1), open jpa (2.4.3 -> 3.1.0). See PR 236 [3]
2. Adding javax dependencies explicitly as they were discontinued in
default java 11 releases. See PR 234 [4]
3. Updating JDK to OpenJDK 11 [5]
4. Disabling Dozer mapper setter optimization [6]. This is a temporary fix
and waiting for dozer team [7] to properly fix this.
5. Fixing remote debug [8]
6. Minor test failure fixes [9]
7. Upgrading Confluent/ Kafka version to (4.1.0 -> 5.3.0) [10]
Travis build and develop environment are now stable :)
Kudos to Isuru, Marcus and Suresh for pulling this off.
[3] https://github.com/apache/airavata/pull/236/files
[4] https://github.com/apache/airavata/pull/234/files
[5]
https://github.com/apache/airavata/commit/fd56623e303e579d7974b721ecd7f931498ad502
[6]
https://github.com/DImuthuUpe/dozer/commit/4d33729e866982cb7cee61065f0719c9c1212334
[7]
https://groups.google.com/forum/?fromgroups=#!topic/dozer-mapper/c1OPee1DwTw
[8]
https://github.com/apache/airavata/commit/5fb5629dfaaf503e1875737c58f703e5cdfad255
[9]
https://github.com/apache/airavata/commit/7b1a2b3525f93a7057325b9df1e7251282e5294f
[10]
https://github.com/apache/airavata/commit/0859211fd8bfb8e2168e95d711fd27d83133c939
Thanks
Dimuthu
On Tue, Oct 22, 2019 at 1:49 PM Suresh Marru <sm...@apache.org> wrote:
> Hi All,
>
> I posted a question for Apache Legal -
> https://issues.apache.org/jira/browse/LEGAL-484
>
> + 1 for moving to Java 11 and get the Travis build working again. We
> probably should try it against both OpenJDK and Oracle JDK latest 11
> releases.
>
> Suresh
>
> On Oct 21, 2019, at 4:34 PM, Christie, Marcus Aaron <ma...@iu.edu>
> wrote:
>
> Might be good to ask Apache legal, but it's not like we're distributing
> Oracle JDK, so not sure what kind of guidance they could give.
>
> In the meantime, it would be great to get the Travis build working again.
>
> On Oct 21, 2019, at 4:07 PM, DImuthu Upeksha <di...@gmail.com>
> wrote:
>
> Hi Folks,
>
> What should we do about this? Should we contact Apache legal support to
> get things clarified about the licensing? We might need to stick to a
> decision before next release.
>
> Thanks
> Dimuthu
>
>
>
>
Re: Upgrade Java Version
Posted by Suresh Marru <sm...@apache.org>.
Hi All,
I posted a question for Apache Legal - https://issues.apache.org/jira/browse/LEGAL-484 <https://issues.apache.org/jira/browse/LEGAL-484>
+ 1 for moving to Java 11 and get the Travis build working again. We probably should try it against both OpenJDK and Oracle JDK latest 11 releases.
Suresh
> On Oct 21, 2019, at 4:34 PM, Christie, Marcus Aaron <ma...@iu.edu> wrote:
>
> Might be good to ask Apache legal, but it's not like we're distributing Oracle JDK, so not sure what kind of guidance they could give.
>
> In the meantime, it would be great to get the Travis build working again.
>
>> On Oct 21, 2019, at 4:07 PM, DImuthu Upeksha <di...@gmail.com> wrote:
>>
>> Hi Folks,
>>
>> What should we do about this? Should we contact Apache legal support to get things clarified about the licensing? We might need to stick to a decision before next release.
>>
>> Thanks
>> Dimuthu
>
Re: Upgrade Java Version
Posted by "Christie, Marcus Aaron" <ma...@iu.edu>.
Might be good to ask Apache legal, but it's not like we're distributing Oracle JDK, so not sure what kind of guidance they could give.
In the meantime, it would be great to get the Travis build working again.
> On Oct 21, 2019, at 4:07 PM, DImuthu Upeksha <di...@gmail.com> wrote:
>
> Hi Folks,
>
> What should we do about this? Should we contact Apache legal support to get things clarified about the licensing? We might need to stick to a decision before next release.
>
> Thanks
> Dimuthu
Re: Upgrade Java Version
Posted by DImuthu Upeksha <di...@gmail.com>.
Hi Folks,
What should we do about this? Should we contact Apache legal support to get
things clarified about the licensing? We might need to stick to a decision
before next release.
Thanks
Dimuthu
Re: Upgrade Java Version
Posted by DImuthu Upeksha <di...@gmail.com>.
Will this [2] be an issue for future releases? Seems like Oracle JDK/ JRE
11 no longer comes free for production deployments. I'm not sure how it
affects for open source projects
[2]
https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloads-5066655.html
Thanks
Dimuthu
On Fri, Sep 13, 2019 at 11:58 AM Christie, Marcus Aaron <ma...@iu.edu>
wrote:
> +1 for Java 11
>
> On Sep 12, 2019, at 10:28 AM, Suresh Marru <sm...@apache.org> wrote:
>
> + 1 for Java 11.
>
> Any objections to move forward to make Java 11 minimum requirement?
>
> Suresh
>
> On Sep 10, 2019, at 6:06 PM, DImuthu Upeksha <di...@gmail.com>
> wrote:
>
> Hi Suresh,
>
> I would vote for Java 11 as it's relatively mature and a LTS version [1]
>
> [1] https://www.oracle.com/technetwork/java/java-se-support-roadmap.html
>
> Thanks
> Dimuthu
>
> On Thu, Sep 5, 2019 at 8:34 AM Suresh Marru <sm...@apache.org> wrote:
>
>> Hi All,
>>
>> I noticed a travis build fail which complains minimum have required of 9
>> to 12 - “Expected feature release number in range of 9 to 14, but got: 8”.
>>
>> Any thoughts on which version of JDK we should upgrade Airavata to before
>> next release?
>>
>> Cheers,
>> Suresh
>
>
>
>
Re: Upgrade Java Version
Posted by "Christie, Marcus Aaron" <ma...@iu.edu>.
+1 for Java 11
> On Sep 12, 2019, at 10:28 AM, Suresh Marru <sm...@apache.org> wrote:
>
> + 1 for Java 11.
>
> Any objections to move forward to make Java 11 minimum requirement?
>
> Suresh
>
>> On Sep 10, 2019, at 6:06 PM, DImuthu Upeksha <dimuthu.upeksha2@gmail.com <ma...@gmail.com>> wrote:
>>
>> Hi Suresh,
>>
>> I would vote for Java 11 as it's relatively mature and a LTS version [1]
>>
>> [1] https://www.oracle.com/technetwork/java/java-se-support-roadmap.html <https://www.oracle.com/technetwork/java/java-se-support-roadmap.html>
>>
>> Thanks
>> Dimuthu
>>
>> On Thu, Sep 5, 2019 at 8:34 AM Suresh Marru <smarru@apache.org <ma...@apache.org>> wrote:
>> Hi All,
>>
>> I noticed a travis build fail which complains minimum have required of 9 to 12 - “Expected feature release number in range of 9 to 14, but got: 8”.
>>
>> Any thoughts on which version of JDK we should upgrade Airavata to before next release?
>>
>> Cheers,
>> Suresh
>
Re: Upgrade Java Version
Posted by Suresh Marru <sm...@apache.org>.
+ 1 for Java 11.
Any objections to move forward to make Java 11 minimum requirement?
Suresh
> On Sep 10, 2019, at 6:06 PM, DImuthu Upeksha <di...@gmail.com> wrote:
>
> Hi Suresh,
>
> I would vote for Java 11 as it's relatively mature and a LTS version [1]
>
> [1] https://www.oracle.com/technetwork/java/java-se-support-roadmap.html <https://www.oracle.com/technetwork/java/java-se-support-roadmap.html>
>
> Thanks
> Dimuthu
>
> On Thu, Sep 5, 2019 at 8:34 AM Suresh Marru <smarru@apache.org <ma...@apache.org>> wrote:
> Hi All,
>
> I noticed a travis build fail which complains minimum have required of 9 to 12 - “Expected feature release number in range of 9 to 14, but got: 8”.
>
> Any thoughts on which version of JDK we should upgrade Airavata to before next release?
>
> Cheers,
> Suresh
Re: Upgrade Java Version
Posted by DImuthu Upeksha <di...@gmail.com>.
Hi Suresh,
I would vote for Java 11 as it's relatively mature and a LTS version [1]
[1] https://www.oracle.com/technetwork/java/java-se-support-roadmap.html
Thanks
Dimuthu
On Thu, Sep 5, 2019 at 8:34 AM Suresh Marru <sm...@apache.org> wrote:
> Hi All,
>
> I noticed a travis build fail which complains minimum have required of 9
> to 12 - “Expected feature release number in range of 9 to 14, but got: 8”.
>
> Any thoughts on which version of JDK we should upgrade Airavata to before
> next release?
>
> Cheers,
> Suresh