Update to EclipseLink 2.7.0

[benoitf]

What does this PR do?

Update to EclipseLink 2.7.0

dependencies used are

[INFO] +- org.eclipse.persistence:javax.persistence:jar:2.2.0:test
[INFO] +- org.eclipse.persistence:org.eclipse.persistence.core:jar:2.7.0:test
[INFO] |  +- org.eclipse.persistence:org.eclipse.persistence.asm:jar:2.7.0:test
[INFO] |  \- org.glassfish:javax.json:jar:1.0.4:test
[INFO] +- org.eclipse.persistence:org.eclipse.persistence.jpa:jar:2.7.0:test
[INFO] |  +- org.eclipse.persistence:org.eclipse.persistence.antlr:jar:2.7.0:test
[INFO] |  \- org.eclipse.persistence:org.eclipse.persistence.jpa.jpql:jar:2.7.0:test

CQ for org.glassfish:javax.json:jar:1.0.4:test is https://dev.eclipse.org/ipzilla/show_bug.cgi?id=14311
the other are eclipse dependencies.

What issues does this PR fix or reference?

eclipse-che/che#5326

Require also

• Update EclipseLink to v2.7.0 che#6377
  and
• Update to EclipseLink 2.7 codenvy/codenvy#2429

[benoitf]

as we're at the beginning of sprint, it's a good time ;-)

[benoitf]

hello, any news why it's blocked ? All PRs are building successfully

[skabashnyuk]

As for me, I would say if there is no strong need - postpone this task to Che6. Too scary to merge.
@riuvshin wdyt?

[benoitf]

I would say the sooner is the better as we have 3 weeks of testing it (as release is happening in the end of the sprint). Also it's easy to revert this kind of update

[benoitf]

note that EclipseLink 2.6.2 Release has been released on December 22, 2015

[vparfonov]

@benoitf Did you run integration test for this changes?

[benoitf]

@vparfonov you mean the profile -Pintegration ?

[vparfonov]

I mean our daily selenium tests

[benoitf]

if it's about the profile it has been checked there
https://ci.codenvycorp.com/job/che-pullrequests-build/3782/

19:04:43 Executing Maven:  -B -f /home/codenvy/workspace/che-pullrequests-build/pom.xml -Dmaven.repo.local=/home/codenvy/workspace/che-pullrequests-build/.repository clean install -U -Pintegration

[benoitf]

@vparfonov we can run daily selenium tests on top of a PR by jenkins ?

[vparfonov]

yes add comment ci-test

[vparfonov]

but i think you can't do it with your changes in case you Che should depend on not merged changes in che-dependencies, maybe will be better start it on some acceptance server

[benoitf]

@vparfonov I added on top of the PR a "commit to be removed" to not require external dependencies (this commit contains the versions added in this PR)

[benoitf]

@vparfonov here is the result: https://ci.codenvycorp.com/job/che-pullrequests-test/29//Selenium_tests_report
(jenkins job being https://ci.codenvycorp.com/job/che-pullrequests-test/29/)

[vparfonov]

@musienko-maxim can you check report

[musienko-maxim]

The stable part of tests is not broken

[benoitf]

so is it ok to merge that PR ?

[skabashnyuk]

In general, I'm +1. But if it has any, event theoretical, chances to delay eclipse-che/che#5362 I would say we should merge it after 5632

[benoitf]

AFAIK this PR is ready to merge while other is still a work in progress.

[benoitf]

This pr is delayed in an artifical manner.
The PR that you reference was not yet submitted the time this PR has been submitted. Also this other CQ has cqs not approved yet
About trying to make some PR more important than others, I don't see the rule on https://www.eclipse.org/projects/dev_process/development_process.php#2_1_Open_Source_Rules_of_Engagement
If some people are not working with short-live branch process, there is also no reason to block the work from other people.

[skabashnyuk]

up2you

[benoitf]

ok, I will check multi user branch after

[riuvshin]

up to you, if this does not break something Im OK with this