Hi,
I wonder if there was already a discussion on Eclipse 4.2?
" As of
the Juno release, Eclipse 4 is
going to be the base platform for the
Eclipse ecosystem. This means that our download page will only
have Eclipse 4.2-based packages. Eclipse 3.8 will also ship as
part of the Juno release, but currently there are no 3.x
releases planned after that. Although an enormous investment
has gone into the backwards compatibility layer for Eclipse 4,
it is obviously going to take testing and effort by the
Eclipse projects and the many Eclipse adopters to migrate to
Eclipse 4.2. So if you haven’t started testing with the Juno
builds, now’s the time to start planning for it. Eclipse 4 is
a complete re-write of the platform user interface, and brings
a lot of value to the ecosystem, including a lot of improved
APIs, more flexibility and a refreshed user interface. And its
API is 100% binary compatible with the 3.x platform."
[1]
[1]
http://mmilinkov.wordpress.com/2012/01/06/its-going-to-be-an-exciting-year/
Regarding the minimum version: I also propose to go ahead with the
first option. There are two other important tools that we may want
to integrate with. In both projects there was already the discussion
to move to Eclipse 4.2.
Best regards,
Lukas
Am 10.02.2012 09:17, schrieb Michael Jastram:
Hi Mark,
Eclipse:
The current and
the previous release.
Since the Juno
Release will com soon, I don't think we should invest effort
for Eclipse 3.6 support.
This would
become deprecated at the end of June 2012. Thus I think we
should concentrate on:
* Eclipse 3.7
(Indigo)
* Eclipse 3.8
(Juno)
Somehow I missed this message. If we only support 3.7 and up,
then we're pretty much done. Personally, I am not aware of any
important tool that we may want to integrate with and that still
runs on 3.6 (I thought that was the case with Topcased, but I just
checked, and they run on 3.7 as well).
On the other hand, if we can make 3.6 and EMF 2.8 the minimum
requirement, wouldn't that be even better? Can anybody think of
any drawbacks? Obviously, things are less than perfect as long as
2.8 is only available as a nightly build. But that will change
soon.
So to summarize, the two options we have are:
- Java 5 / Eclipse 3.7 / EMF 2.7
- Java 5 / Eclipse 3.6 / EMF 2.8
I am ready to toss a coin. Mark suggests the first option.
Unless there are any strong advantages of the second, I propose
to go ahead with the first.
Thoughts?
Best,
- Michael
On 02/09/2012 10:15 AM, Michael Jastram wrote:
Hi Ed,
We're just setting up builds so that EMF 2.8 will work with
Eclipse 3.5:
Sweet - this is obviously a much better solution. I was not
aware of this. I take it that I have to wait until #370942 is
resolved? The 2.8 on the Juno update site still has
dependencies to 3.8.
Best,
- Michael
https://bugs.eclipse.org/bugs/show_bug.cgi?id=370942
Working with recent version is a much better way to ensure
you'll get support for your problems. We're highly unlike to
fix problems in EMF 2.6 and I'm sure you'll never get fixes
for Eclipse 3.6 problems other than in 4.2 or maybe, if you're
lucky, in Eclipse 3.8.
Cheers,
Ed
On 08/02/2012 2:33 PM, Michael Jastram wrote:
Hello RMF Committers,
The other day we had a telco where we discussed what the minimum
requirements for RMF should be. In order to support as many other
projects as possible, we proposed Java 1.5 and Eclipse 3.6.
I already downgraded Java to 1.5, which was not problematic.
Switching to Eclipse 3.6, however, also requires us to downgrade to EMF
2.6 (from 2.7). This in turn will require regenerating code (mainly due
to EMF 2.6 missing the Switch class). All in all it doesn't look like a
big deal. Still, before I proceed: Does anybody have comments or concerns?
@Ed (and all others): Are there any important features that we would
loose by downgrading to EMF 2.6?
If there are no objections, I'll refactor on Friday (Feb. 10).
Thanks,
- Michael
--
Michael Jastram (http://www.jastram.de, +49 (162) 274 83 94)
Geschäftsführer, Formal Mind GmbH (http://formalmind.com)
Wissenschaftler, Heinrich Heine Universität Düsseldorf (http://www.stups.uni-duesseldorf.de)
1. Vorsitzender, rheinjug e.V. (http://www.rheinjug.de)
_______________________________________________
rmf-dev mailing list
rmf-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/rmf-dev
--
Michael Jastram (http://www.jastram.de, +49 (162) 274 83 94)
Geschäftsführer, Formal Mind GmbH (http://formalmind.com)
Wissenschaftler, Heinrich Heine Universität Düsseldorf (http://www.stups.uni-duesseldorf.de)
1. Vorsitzender, rheinjug e.V. (http://www.rheinjug.de)
_______________________________________________
rmf-dev mailing list
rmf-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/rmf-dev
|
