Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Virgo/Community/Minutes-2016-02-24


Attendees

  • GianMaria Romanato
  • Daniel Marthaler
  • Florian Waibel

Discussion

  1. Scope of release 3.7.0

https://wiki.eclipse.org/Virgo/Future#3.7.0_.28Steel.29_Release Virgo Steel Bugtrain: https://bugs.eclipse.org/bugs/show_bug.cgi?id=396813

  1. Application configuration options:
* http://owner.aeonbits.org/ - Java properties reinvented
* http://javaeeconfig.blogspot.ch/2014/08/overview-of-existing-configuration.html
* http://constretto.org/
* https://tamaya.incubator.apache.org 
  1. Where to put the “kernel-tools repository”
  2. Various discussions about how to integrate 3rd party technology in Virgo
* traditional JNDI vs. Gemini Naming
* JPA with Eclipse Link (multi tenancy support) not working with GeminiDB
* Is Gemini JPA not production ready? (Instrumentation at build time)
* Embed ElasticSearch into Virgo (uses native library)
* Integrate with Netty and Zookeeper
* Integration with Hazelcast
* ConfigAdmin + MetaType
* Equinox Registry
* Virgo inside Docker -> Shutdown to slow (10 second timeout of Docker)
* Simple JMX (https://github.com/j256/simplejmx) vs. Jolokia Bridge
* Alternative DI: https://www.eclipse.org/sisu/

Actions

  1. *done* Merge new profile support into master (Virgo tooling / giamma)
  2. *done* Reproduce p2 resolver error (Virgo tooling / giamma)
  3. *done* Create Bugzilla as follow up of the "kernel-tools" discussion (giamma)

Next meeting

23 March 2016 at 9:30 p.m. (CET)

Back to the top