Meeting Date: 

        1/11/07 11:00 a.m. EST

Attendees:

        Barry Atkins
        Andrew Eberbach
        Joel Hawkins
        Dan Jemiolo
        Balan Subramanian

Topics:

1. Status of current JIRA items. (5 min)

2. Status of J2ME port and any development problems. (10-15 min)

        a. Enumerate additions or changes that will need to be made to the 

code and documentation.

        b. Agree on SDK Dan/Andrew should use when making and testing 
these changes.


News & Decisions:

1. Dan's JIRA items (as of yesterday) are finished, pending confirmation 
by reporters. This does not include MUSE-65, which should be 'unscheduled' 
rather than '2.2.0'.

2. Andrew has completed many of his JIRA items, but is still working on 
MUSE-118. Since MUSE-118 affects the the general stability of muse-tools, 
he will complete that item before committing his current work.

3. Barry has Muse samples running on J2ME/OSGi foundation profile. Details 
are in Barry's last message to muse-dev ("Muse J2ME Status").

4. Team discussed build options for J2ME - to change the current /trunk so 
that it always compiles for J2ME and J2SE, or to create a fork for J2ME. 
All parties agreed that the former was preferable, so we will make the 
compilation changes outlined by Barry and update the build to ensure J2ME 
compliance.

5. Team discussed lack of java.util.logging.* package on J2ME. This 
package is referenced in muse-core APIs, which cannot change for versions 
2.x.

        a. Options for adding logging support on J2ME include 1) 
implementing LCD of java.util.logging.Logger that pushes down on Equinox 
logging system, 2) replacing java.util.logging usage with Apache Commons 
Logging, and 3) creating a generic logging interface that delegates to the 
appropriate logging APIs (similar to #2).

        b. Team agreed to discuss options in detail on muse-dev and 
resolve the issue before committing any code changes related to Barry's 
J2ME port. This will ensure that the build is not in a half-way/broken 
state during the development cycle.

6. Andrew has not received a response from Apache Infrastructure team, so 
nightly builds are still being placed on minotaur. 


Action Items:

1. Barry will start a new thread on muse-dev concerning the J2ME logging 
issue. Contributors will send code/ideas for proposed solutions so we can 
pick the most appropriate one. Balan is looking into Apache Commons 
Logging, Dan into java.util.logging.* support.

2. Once logging issue is resolved, Barry will provide a patch that makes 
the necessary changes for Muse to compile on J2ME. He will also help with 
any minor documentation updates needed to reflect J2ME support.

3. Andrew will be responsible for enhancing the build to check for J2ME 
compliance.



If you have any questions or clarifications about these minutes, please 
send them along!




Dan Jemiolo
IBM Corporation
Research Triangle Park, NC


+++ I'm an engineer. I make slides that people can't read. Sometimes I eat 
donuts. +++



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to