Eric,
There is the long and short answer, as there always seems to be.
The short answer is Maynstall as it stands today does not have an active
contribution base and is not what I would consider an active project.
For the long answer, there are aspects of Maynstall, specifically
regarding a way of accessing a remote JPA data model that we make use of
on our own commercial product and once every six months have a small CVS
commit to keep it going. This area I believe has interesting value to
the community though the Maynstall project as it stands now does not
represent that correctly -- the data model access was a fall out
technology from the integration, not a key component to the initial
contribution. I previously spoke at EclipseWorld/EclipseCon with Doug
Clark over on EclipseLink to see about the possibility of aligning a
subset of the services in Maynstall over in that area. The provisioning
side of Maynstall was largely displaced with the introduction of p2;
even on my own commercial offering we needed to stop using Maynstall for
any provisioning and switch entirely to p2 for consistency with the
community.
As always I'm open to suggestions from others who were originally named
committers on the project.
Cheers,
Tim
On Thu, Aug 6, 2009 at 2:55 PM, Eric Rizzo <eclipse-mail@xxxxxxxxxxxx
<mailto:eclipse-mail@xxxxxxxxxxxx>> wrote:
Hi, this is Eric Rizzo of the Technology PMC. While reviewing the
projects under the Technology umbrella, I've noticed that Maynstall
seems to be inactive. The newsgroup has no messages for almost a year
and the web site and wiki do not appear to have been updated in quite a
while. The mailing list has not responded to recent inquiries, either.
What is the status of the project? We need to have a response from the
project lead and/or other team members ASAP.
Thanks,
Eric