Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [corona-dev] Development Conference Call: Tuesday, Oct 10 @ 10:00 AM EDT

Corona Development Conference Call: Tuesday, October 10, 2006 @ 10:00 AM EDT

 

Meeting Minutes

  • Please reply to the dev mailing list for any updates or corrections.

 

Attendees

  • Dennis O'Flynn
  • Glenn Everitt
  • Joel Hawkins
  • Jim Wright
  • Edyta Kalka
  • Pawel Kaczmarek
  • Piotr Jaworowski

 

News

  • No news re: virtual server (corona.eclipse.org)
  • Marcin will be attending EclipseCon Europe this week.

 

Minutes

  • Development Environment
    • JDK 1.4 vs 1.5.  Development environment should be JDK 1.5.
      • Any components that are intended to be part of the core server-side (e.g. Muse components) must JDK 1.4 compatible.
    • Development Workbench IDE requirements posted on wiki
  • Community Building
    • Eclipse Collaboration Projects – a meeting is being proposed for Corona / ALF / ECF / Mylar / Apogee to identify common Eclipse collaboration needs.  A note will be posted to each project’s development mailing list.
  • Corona 1.0.0M5
    • Goal is to produce milestone that others can download and possibly begin to use.
      • The Corona team will begin to use 1.0.0M5 as soon as our virtual server is available.
      • Documentation, both Javadoc and wiki, need to be accurate.
        • Piotr suggested adding help to plugins.
    • Two more weeks before code freeze (thaw). 
    • Web Service Enablement
      • Web services are working for SDO, both for datagraphs and data objects.
      • Adding serialization for arrays, lists, and collections.  Should be available in the next couple of days.
      • Project Context Container being enabled for web services
        • Introducing new Workbench PC-Mgr Proxy plugin
          • PCMgr Proxy will initially attempt to connect to remote PCMgr via web services.  If not available, it will use locally cached PC definitions.
          • Future milestone will need to synch locally cached PC definition with remote PC definition.
        • Should be committed within the next week.
    • Release Engineering (releng)
      • Compuware internal machine has been setup.  It is a Redhat Fedora v5 machine.  This will be used as an internal build and test machine.
      • The production build process will eventually be hosted on either the Eclipse build server or Corona’s virtual server.
      • Build process currently supports building client-side (Workbench) plugins.
        • RSS feeds are being produced.  Not yet being published to public download area.
        • Javadoc is being generated
      • JUnit3 vs JUnit4
        • PDE build process does not support JUnit4, yet.
      • Work will continue on supporting server-side plugins
        • Need to be able to start (& stop) Corona server-side to run test cases against
      • 3rd party binaries (e.g. Apache Axis, etc…) that are needed by build, but not committed to Eclipse CVS, will be available on linux server and publicly available.
        • The “corona” account will be used to provide access to common libraries.
  • Corona 1.0.0M7
    • Planning has begun.  Initial scope is defined on wiki.
    • General theme is “fun with WSDM” (client and server side)
    • Work will not begin until M5 is finished.
  • JSR 170 – Jackrabbit
    • Edyta researching use of Jackrabbit as ContextContainer RepositoryDefinition
    • Schema definition has been created for ContextContainer types
    • Investigating how to get existing RepositoryDefinition’s into Jackrabbit
    • The use of Jackrabbit may be introduced in 1.0.0M7 and later.

 

Miscellaneous

  •  

 

Action Item

  • [Dennis] Created Bugz items for plugin help.
  • [Pawel] Document how to use releng process on wiki
  • [Pawel] Setup internal update site.
  • [Dennis] Create “corona” user account on linux server.  Populate with required 3rd libraries.

 

 

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

Back to the top