Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mylar-dev] mylar 0.7.0 and support for Eclipse 3.3M2

Mik,

I understand this. But it still going to kick out early adopters from weekly Mylar builds.

 BTW, are we getting one tonight?

 regards,
 Eugene


Mik Kersten wrote:
I may not have been clear: the plan is to do what we did with 3.1/3.2: have
the Mylar release support *both* 3.2 and 3.3 up until 3.3 goes final (June),
at which point the 3.2 support goes into maintenance mode.

While we're forced to use plenty of internal 'APIs', we've become very good
at finessing that so won't use them as an excuse.
Fyi, we have to for M2 because the launch configuration stuff that we depend
on is no longer internal (I've updated the marker view filtering to be 3.3
common for 3.2 and 3.3).  Also, there is a benefit to forking as long as the
merge back doesn't get too painful, since it gives us the freedom to push
for and use additional the additional extensibility we need from Platform.

Mik

-----Original Message-----
From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
On Behalf Of Eugene Kuleshov
Sent: Friday, September 22, 2006 5:02 PM
To: Mylar developer discussions
Subject: Re: [mylar-dev] mylar 0.7.0 and support for Eclipse 3.3M2

Mik,

  That will make certain things more complicated. Not sure if you are
aware of that, but WTP 1.5 does not work on Eclipse 3.3. Those guys made
WTP to require strict Eclipse 3.2 version, using internal API's as an
excuse.

  So, those who need WTP are have to use Eclipse 3.2 and will be stuck
with old mylar release (0.6.2 and below).

  regards,
  Eugene




Back to the top