In order to prevent Mylar from being
installed into an incompatible version of Eclipse (i.e. to help insulate users
from the fact that we use internal classes) the core Mylar feature always
specifies the platform version it is compatible with. For 0.5.0.1 that
was 3.2.0.v20060324, so the problem is that the nightly version is 3.2.0.N20060424
and it looks like the Update Manager sees “N” as being smaller than
“v”.
Practically speaking this isn’t a
problem because we’ll just put out a build with the right dependency
specified. However, it does bring up a few questions:
·
Is the
switch to the “N2006..” convention going to stay throughout the RCs?
If so we will adopt it for our dev build versioning.
·
Should
we be adopting the 4-part version number, e.g. 0.5.1.32_N2006..? I haven’t
noticed anyone the Callisto projects do it but it’s specified on the
Callisto requirements (http://www.eclipse.org/projects/callisto.php).
Note that the prefix is still listed and v2006 not N2006 on the corresponding
page: http://www.eclipse.org/eclipse/platform-core/documents/plugin-versioning.html
·
Do you
have a recommendation of the best way to specify the platform dependency?
Is making our core feature require “Greater or Equal” of 3.2.0.N20060424
the right approach? A case has been reported where someone had their
extension directory pointed at an incompatible version and the plug-ins loaded
anyway, so I assume we should additionally make each plug-in declare the
dependency? Is pointing at org.eclipse.platform the right approach?
Thanks!
Mik
From:
mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx] On Behalf Of Michael Valenta
Sent: Tuesday, April 25, 2006 2:32 PM
To: Mylar developer
discussions
Subject: RE: [mylar-dev]
compatibility with 3.2 builds
Mik,
What
do you mean by "refuse to install"? Are you strickly talking about
using the update manager to update from an Eclipse integration build to an
Eclipse nightly build? That won't work since the version qualiifers are
incompatible. However, you should still be able to download an Eclipse nightly
build and then install the latest Mylar into it.
Michael
|
"Mik Kersten"
<beatmik@xxxxxxx>
Sent
by: mylar-dev-bounces@xxxxxxxxxxx
04/25/2006
05:21 PM
|
Please
respond to
Mylar developer discussions
|
|
|
To
|
"'Mylar developer discussions'"
<mylar-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
|
RE: [mylar-dev] compatibility with 3.2 builds
|
|
0.5.0.1
should support the latest nightlies, the problem is that the version
numbering scheme changed (to
org.eclipse.platform_3.2.0.N20060424-0010
instead of 3.2.0.v2006..) so it will refuse to
install. Since everyone has
been encouraged to use the nightlies, we will put
up a dev build tonight
that understands the new version numbering.
For now you would have to use
HEAD or copy the plug-ins manually.
Mik
> -----Original Message-----
> From: mylar-dev-bounces@xxxxxxxxxxx
[mailto:mylar-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Eugene Kuleshov
> Sent: Tuesday, April 25, 2006 2:04 PM
> To: Mylar developer
discussions
> Subject: [mylar-dev] compatibility with 3.2
builds
>
> Mik,
>
> What version of Eclipse 3.2 can
be currently used with Mylar?
> I need to test some stuff on a
nightly builds and wondering if Mylar
> will work up there. For example:
>
http://download.eclipse.org/eclipse/downloads/drops/N20060425-
> 0010/index.php
>
> 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
