Meeting
Minutes
- Please
reply to the dev mailing list for any updates or corrections.
Corona Development Conference Call: Tuesday,
September 26, 2006 at 10:00 AM EDT
Attendees
- Dennis
O’Flynn
- Glenn
Everitt
- Jim
Wright
- Joel
Hawkins
- Marcin
Okraszewski
- Edyta
Kalka
- Pawel Kaczmarek
- Piotr
Jaworowski
Minutes
- Development
Environment
- CVS
Clean Up
- Jim
and Dennis to begin looking into cleanup of collaboration plugins
- Piotr
to finish up consolidation of exemplary implementation plugins (PCC)
- Obsolete
plugins will moved to an “attic” folder within the CVS
repository
- Build
- Started
refactoring build and works on a limited set of plugins
- Use
of new template from Eclipse releng
- EMFT
templates may be too complex for use by Corona build
- Dennis
noted that the EMFT build process is considered one of the “best
practices” of an Eclipse build process. The Corona build
should continue to model there build process after EMFT’s.
- Will
need to generate RSS feeds to be compatible with Europa
- How
do you build with snapshots from dependent technologies (i.e. Apache)?
- Corona’s
build process does not support this yet.
- For
dependent Eclipse technologies, they should (eventually) provide RSS
feeds to notify when dependent component is available.
- The
build process should be performed on a Linux machine. We will have
a choice of using an Eclipse virtual server (when allocated), the
Eclipse build server, or use an internal build machine.
- Recommendation
is to use the virtual server.
- Committer
nomination of Piotr has been approved.
- Misc
Items
- committer
passwords do expire and will need to be changed. You will need to
use Eclipse Committer Tools to change your password.
- Use
Bugzilla to record the history of an item. Update the comments so
that it contains knowledge that can be used later by others.
- Code
should be committed per Bugzilla item. Try not to make big changes
to source code to implement multiple issues.
- Corona
1.0.0M4
- Update
to demo shown at EclipseWorld to allow it to be downloaded and used by
the general public.
- Goal
to make available by Oct 2, 2006
- The
demo will use a customer configuration of a PCC for Corona. This will support CVS
pserver access
- Corona
1.0.0M5
- Theme
is remote accessibility. Enabling OSGi Bundle services to be
exposed as web services.
- Objective:
downloadable binaries, demo
- Objective:
the Corona
development team will begin to use the Corona plugins as
part of the development environment.
- ContextContainer
– RepositoryDescriptors
- Dev
mailing list posting introduced the idea of renaming “RepositoryDescriptor”
to “ContextProvider”.
- Need
exists for both RespositoryDescriptor and ContextProvider.
- Could
Corona leverage
the work from Apogee?
- Will
Apogee be available prior to EclipseCon 2007?
- Corona couse
use Apache JackRabbit and migrate to Apogee in the future.
- Joel
to be committing code to provide the initial SOA web service framework by
end of week.
- Support
for RPC plain, RPC+SDO, Document
- Security
via WSS4J
- JAX-WS
will not be supported yet since Apache Axis does not support annotations
– yet.
Action Items
- Edyta/Glenn to research use of
Apache JackRabbit (http://jackrabbit.apache.org/).
If possible, decision to use JackRabbit (or not) is needed by Oct 1.
- Joel to submit request to PMC
re: use of Apache Axis
From:
corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of O'Flynn, Dennis
Sent: Tuesday, September 26, 2006
6:12 AM
To: Corona
development
Subject: [corona-dev] Development
Conference Call: Tuesday Sep 26 @ 10:00 AMEDT
The next Corona development
conference call has been scheduled for Tuesday, Sep 26, at 10:00 AM EDT.
Conference call details:
- Date / Time: Sep 26, 2006,
10:00 AM EDT
- Dial-in Number: (866)
213-1962 (609) 454-9912
- Access code: 2277433
Agenda:
- Development Environment
- CVS Repository clean up
- Plugin renaming
- Build process
- Committer nomination: Piotr
Jaworowski
- 1.0.0M4 – Demo download
- 1.0.0M5 – Remote
Accessibility
- Bugzilla issues
- RepositoryDescriptor
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.
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.
|
