| [ee4j-build] EE4J Build Team Meeting notes (10/03/2018) |
|
My notes from today's EE4J Build Team meeting: Anand problems with UDDI based tests. UDDI server only runs with
JDK 1.4. File bug please. Admins are investigating if this can be
fixed at their end. Server does run with JDK 1.5, but there are
errors. (Presumably does not run on newer JDK versions.) Jan things are well in progress, working through a couple of test/compatibility errors. Tomas, ibid. Questions about IP log and sign-off. Admins will
confirm. Werner -- issues with OpenMQ -- also notes some jobs are running on old infra. Eventually, they will be migrated (by the end of the year) to jenkins.eclipse.org. New: jenkins.eclipse.org. Old: ci.eclipse.org Projects using the old CI are identified in provisioning
table. (OpenMQ, WebSocket, EclipseLink, EE4JParent (ee4j),
Grizzly, JAX-RS, JSONB, JSONP, Tyrus, Yasson). Everything else is
provisioned at jenkins.eclipse.org. Instance provisioning is proceeding well. Current status is available at provisioning table. The reason that Jenkins access is limited to committers is due to the initial TM agreement restrictions. Ed will try to find out of we can remove that limitation and take that to PMC and/or Steering Committee. Ed noted that we (Oracle) is working on guidelines for publishing
artifacts -- Preliminary, and released. Will be circulating
recommendations shortly for review. Eclipse Admins need group-id for OpenMQ (for publishing to Maven
Central). Get answer from Open MQ Dev team for moving forward. (group-id
table). Ed to follow up. Do we still need the dash instance? Will post note to the EE4J build list: unless there is feedback that this is still needed, these will be taken down after a week. Mikael will send message. That's what I captured. If you have additions, corrections, or changes, please reply. Thanks, -- Ed
|