It's great to here of the contribution and the progress you are
making. One thing we can talk about on the call is starting to
align m2e-wtp with the WTP schedule. As what I hope becomes a part
of the larger WTP offering, we will likely need to get m2e-wtp
aligned with the general WTP release schedule. This will ideally
involve offerings for the yearly simultaneous release, as well as
specific maintenance releases to support the SR's. Having an active
maintenance stream and a dev stream for the next major release is
part of the standard process, and is necessary for the stability of
the released codebase.
As a result, I would think that 0.17.0 should be an Eclipse Juno
based release, and should not be concerned with the Kepler code base
at this time. I understand that this may not be possible yet, but
we can discuss on the proposed call.
This is part of the consequences/trade-offs of Dali's evolving
provisional API. There are many benefits, but also a cost. The
Dali team is ready to assist in any provisional API migration when
the need arises. I also planned to notify of these changes on
milestones on dali-dev@xxxxxxxxxxx but have missed the last two
milestones. Tune into dali-dev for additional change notification.
For what it is worth, my intention is that the Kepler release will
be the last major evolution of the provisional API's.
On 12/4/2012 3:56 PM, Fred Bricon wrote:
earlier today I submitted JBoss Tools' JAXRS, JSF and JPA m2e
project configurators as a new contribution to m2e-wtp .
I cleaned up the original code, using the org.eclipse.m2e.wtp
namespace. The 3 configurators come as 3 separate, optional
features to m2e-wtp.
Hopefully, the contribution is IP clean so I'm expecting
it'll be vetted rapidly by the EMO team.
All was good and well until, right before I submitted the
code contribution, I tested my local build against Kepler (JBoss
Tools hasn't started migrating to Kepler yet).
Turns out the JPA configurator contribution is unusable
without major modifications, due to Dali breaking pretty
much *all* the provisional API JBoss Tools depended upon .
It's certainly my fault if I wasn't aware of the breaking
changes earlier. Well, I understand provisional API means it can
be broken from one minor version to another, but still, I think
it would have been less painful if the code was marked as
deprecated instead, for at least 1 version increment.
I really, really don't want to maintain several maintenance
streams so, it looks like the JPA support won't be made
available until after we release m2e-wtp 0.17.0 in february.
I propose we discuss the subject and Kepler M4 this Thursday Dec
be unavailable friday and the following week),
at 11am-12am EST / 17pm-18pm CET on a status call
**International Toll Free Numbers are subject to change.
Before each conference, refer to the numbers above for the
most current information. Always use your Toll number as a
*0 Operator assistance - conference
00 Operator assistance-individual
*1 Dial-out to a participant - leader only
*2 Begin/end conference record (leader only)
*3 Change entry/exit method (recorded names, tones,
silence) - leader only
*4 Private roll call
*5/#5 Mute/unmute all participant lines - leader only
*6/#6 Mute/unmute your own line
*7/#7 Lock/unlock conference (including operator) - leader
*8 Allow/disallow conference continuation - leader
*9 Start/join sub-conferencing
11 Third-party conference start - bypass hold music to
start call as leader
*51/#51 Lecture mode on/off – leader only
#99 Disconnect all lines except leader’s – leader only
*# Participant count
** List available keypad commands
"Have you tried turning it off and on again" - The IT Crowd