Community
Participate
Working Groups
We have a small requirement on EGit/JGit for some copyright unit tests (which are not ran, in production, but are compiled into a releng bundle). We currently have version "4.3" in our prereq targets, but just noticed they contributed 4.4.0.201605250940-rc1 to Sim. Release repo, so I suggest we update to that (or, next one) just to make sure our bit of code still compiles with "the latest". (We do use some of their internal, non-API methods -- at least for tests, not sure of copyright tool).
I'll try to update "today", but may want to next week too, assuming they will have another RC closer to "final".
*** Bug 492841 has been marked as a duplicate of this bug. ***
I've committed their "close to final" version. http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=97b847e800c9de995a471dd432c2a4c693998e24 But suspect there will be another next week.
Looks like their "4.4 rc2" will be what is in our final build. http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=ed0c2a09ae544249d29827e321f3046f259b6536 But, I have left this open and targeted to "4.6" because I'd like to deviate a little from the normal "final tagging" and update this prereq to use its final URL. The idea is people will be using our "parent pom" to build other Neon things for for some time, and I'd hate to have this "temp directory" in there tagged as the final version. (And, I am only doing that since it is a small dependency, not like EMF or something).
EGit has made their final "release" URL available in b3 aggregation, so I have updated our pre-req for it, so that once we tag with "Neon", we will have (relatively) persistent URLs for a while. (And, I confirmed our few unit tests still compile and "pass" on it in my workspace). http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=4a6b3b4e8c9603e9588de3295145bb834dc44646
