Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Equinox Minutes - 20090120"

(New page: == Agenda == * The launcher should be more flexible about where it looks for framework extensions [http://bugs.eclipse.org/257178] * ECF Futures * Incubator graduation status)
 
 
(7 intermediate revisions by one other user not shown)
Line 1: Line 1:
 +
== Attendance ==
 +
* Tom Watson
 +
* Simon Kaegi
 +
* Andrew Niefer
 +
* Matthew Piggott
 +
* Oleg Besedin
 +
* Scott Lewis
 +
* John Arthorne
 +
* DJ Houghton
 +
* Pascal Rapicault
 +
* Jeff McAffer
 +
 
== Agenda ==
 
== Agenda ==
 
* The launcher should be more flexible about where it looks for framework extensions [http://bugs.eclipse.org/257178]
 
* The launcher should be more flexible about where it looks for framework extensions [http://bugs.eclipse.org/257178]
 +
** currently only looking in the same directory as framewor
 +
** will provide equivalent url support as for osgi.bundles
 +
 
* ECF Futures
 
* ECF Futures
 +
** likely will go ahead with an equinox bundle
 +
** some questions around package api and naming
 +
** no final conclusion however a provisonal/interanl package style might be prudent
 +
 +
* ECF 2.1 and the M build
 +
** Problems when using 2.1 in the M build. No idea why and for now have rolled back to 2.0.1.
 +
** Still investigating as there may be similar problems in 3.5 HEAD
 +
 
* Incubator graduation status
 
* Incubator graduation status
 +
** nothing blocking progress now. Just a matter of doing it.
 +
 +
* Graduation of extended logging  [http://bugs.eclipse.org/bugs/260672]
 +
** need to a graduation review
 +
** still need javadoc, tck check
 +
** API review from John and Tom
 +
** plan for m6 graduation
 +
 +
* Implementing RFC 119
 +
** some questions around when equinox will re-publish any updates to the api
 +
 +
* Equinox SDK builds
 +
** Need for an Equinox repo
 +
** Use a separate feature for each area in Equinox (Framework, p2, components)

Latest revision as of 12:38, 21 January 2009

Attendance

  • Tom Watson
  • Simon Kaegi
  • Andrew Niefer
  • Matthew Piggott
  • Oleg Besedin
  • Scott Lewis
  • John Arthorne
  • DJ Houghton
  • Pascal Rapicault
  • Jeff McAffer

Agenda

  • The launcher should be more flexible about where it looks for framework extensions [1]
    • currently only looking in the same directory as framewor
    • will provide equivalent url support as for osgi.bundles
  • ECF Futures
    • likely will go ahead with an equinox bundle
    • some questions around package api and naming
    • no final conclusion however a provisonal/interanl package style might be prudent
  • ECF 2.1 and the M build
    • Problems when using 2.1 in the M build. No idea why and for now have rolled back to 2.0.1.
    • Still investigating as there may be similar problems in 3.5 HEAD
  • Incubator graduation status
    • nothing blocking progress now. Just a matter of doing it.
  • Graduation of extended logging [2]
    • need to a graduation review
    • still need javadoc, tck check
    • API review from John and Tom
    • plan for m6 graduation
  • Implementing RFC 119
    • some questions around when equinox will re-publish any updates to the api
  • Equinox SDK builds
    • Need for an Equinox repo
    • Use a separate feature for each area in Equinox (Framework, p2, components)

Back to the top