The EMF Query project has two components,
1) the original EMF Query component
contributed by IBM when the project was started.
2) a new EMF Query 2 component contributed
by SAP.
As I said below, EMF Query and EMF Query2
are two completely separate components in one project with separate committers,
bugzillas, builds and IP.
EMF Query is doing a release in Indigo.
EMF Query2 did not do a release in Indigo
but now wants to do a post Indigo release.
How is this going to work when EMF Query
is one project from the EMO perspective? Maybe a restructure of EMF Query2
into a separate project is the only way?
Cheers...
Anthony
From:
Anthony Hunter/Ottawa/IBM@IBMCA
To:
Eclipse Modelling Framework
<emf-dev@xxxxxxxxxxx>,
Date:
06/03/2011 09:38 AM
Subject:
Re: [emf-dev]
EMF Query2 release
Sent by:
emf-dev-bounces@xxxxxxxxxxx
Hi Ashwani,
I really think it is time to consider a restructure. EMF Query and EMF
Query2 are two completely separate components in one project with separate
committers, bugzillas, builds and IP.
It would be so much easier if we separated them.
What do you all think?
Cheers...
Anthony
From: Ashwani
Sharma <ashw.kumar@xxxxxxxxx>
To: Eclipse
Modelling Framework <emf-dev@xxxxxxxxxxx>,
Date: 06/03/2011
12:48 AM
Subject: [emf-dev]
EMF Query2 release
Sent by: emf-dev-bounces@xxxxxxxxxxx
Hi,
I am a committer for EMF Query2.
Currently, EMF Query2 sources are under EMF Query cvs project location.
We have made EMF Query2 sources ready for release.
Since EMF Query2 was decided to be part of EMF Query with different namespace,
having them under same update site will be better. This change should happen
after indigo release is completed, since we don't want to contribute in
simultaneous release of indigo.
Can you please guide us on how we should proceed with this ?
We want to get ready, so that we can make a release once the indigo release
is done by eclipse.