RE: [mylar-dev] mylar 0.7.0 and support for Eclipse 3.3M2

["Mik Kersten" <beatmik@xxxxxxx>]

Eugene, in order to make it possible to use the 3.3-based dev build from 3.2
for as long as possible I left the platform dependency specified as 3.2.
This means that you should be able to install yesterday's dev build into
your 3.2/WTP setup.  The only limitation you should notice for the time
being is that the automatic Context Test Suites can't be used.  

Please let me know what your experiences using the dev build in 3.2 are,
since we should update the wiki with the precise requirements and
limitations that the dev builds have.

Mik

> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Mik Kersten
> Sent: Friday, September 22, 2006 5:36 PM
> To: 'Mylar developer discussions'
> Subject: RE: [mylar-dev] mylar 0.7.0 and support for Eclipse 3.3M2
> 
> Yes, my message said that there will be a build tonight and it will
> support
> 3.3M3.
> 
> I was assuming that early adopters would be on the WTP 2.0 milestones.  Is
> that problematic for you, do you see it being problematic for others?
> 
> I can't see an obvious alternative other than not moving HEAD to the 3.3
> stream until later, but I know from experience that this would result in a
> flurry of complaints.
> 
> Mik
> 
> > -----Original Message-----
> > From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-
> bounces@xxxxxxxxxxx]
> > On Behalf Of Eugene Kuleshov
> > Sent: Friday, September 22, 2006 5:16 PM
> > To: Mylar developer discussions
> > Subject: 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
> > >>
> > >>
> >
> > _______________________________________________
> > mylar-dev mailing list
> > mylar-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/mylar-dev
> 
> _______________________________________________
> mylar-dev mailing list
> mylar-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylar-dev