Home » Eclipse Projects » Mylyn » Automatic upgrade from 3.2.0 to 3.2.1?
|
Re: Automatic upgrade from 3.2.0 to 3.2.1? [message #71242 is a reply to message #71223] |
Mon, 27 July 2009 14:53 |
Mark Phippard Messages: 129 Registered: July 2009 |
Senior Member |
|
|
On 2009-07-27 08:49:30 -0400, costa@tecgraf.puc-rio.br (Andre Costa) said:
> I'm using Galileo with Mylyn 3.2.0. I know that Mylyn 3.2.1 has been
> released a couple of days ago, and I was expecting Eclipse would
> automatically realize this and offer me to upgrade it (I have
> "automatic updates" enabled). However, not only it does not offer me to
> upgrade but manually checking for updates seems to only detect
> Subclipse updates (which BTW I *don't* want to upgrade, since I'm
> currently stuck with Subversion 1.5).
>
> Is Subclipse 1.6 required for Mylyn 3.2.1? If not, shouldn't the
> upgrade be automatically suggested? How do I workaround this?
There is no direct relationship between Subclipse release and Mylyn
releases. The fact that a Subclipse upgrade is available to you has
nothing to do with Mylyn not showing.
BTW, why are you stuck with Subversion 1.5? Any SVN 1.x client can
talk to any 1.x server, so you should be able to run any version on the
client that you want to. That said, you do need a way to get the SVN
1.6 binaries for JavaHL. If you are on Linux, perhaps you are waiting
for your distro to upgrade you?
There are details on this wiki for doing it yourself:
http://subclipse.tigris.org/wiki/JavaHL
Mark
|
|
|
Re: Automatic upgrade from 3.2.0 to 3.2.1? [message #71262 is a reply to message #71242] |
Mon, 27 July 2009 15:08 |
Andre Costa Messages: 21 Registered: July 2009 |
Junior Member |
|
|
Mark Phippard wrote:
> On 2009-07-27 08:49:30 -0400, costa@tecgraf.puc-rio.br (Andre Costa) said:
[...]
> There is no direct relationship between Subclipse release and Mylyn
> releases. The fact that a Subclipse upgrade is available to you has
> nothing to do with Mylyn not showing.
Yes, I thought so. This is why I don't understand why Eclipse doesn't
realize Mylyn can be upgraded as well. AFAICS it should ask me to upgrade
both Subclipse and Mylyn, not because they're related somehow, but simply
because there are upgrades for both of them.
So, the core question is: why isn't Mylyn 3.2.1 picked by Eclipse updater?
Do I need to do anything on my own?
> BTW, why are you stuck with Subversion 1.5? Any SVN 1.x client can
> talk to any 1.x server, so you should be able to run any version on the
> client that you want to. That said, you do need a way to get the SVN
> 1.6 binaries for JavaHL. If you are on Linux, perhaps you are waiting
> for your distro to upgrade you?
> There are details on this wiki for doing it yourself:
> http://subclipse.tigris.org/wiki/JavaHL
Yes, that's precisely my problem: latest subversion CLI client available
on Ubuntu Jaunty is 1.5.4, and I do use it a lot on the same workspace I
use Subclipse. If I upgrade Subclipse to 1.6 I will not be able to use
1.5.x CLI client any longer, which is unacceptable.
Regards,
Andre
|
|
|
Re: Automatic upgrade from 3.2.0 to 3.2.1? [message #71282 is a reply to message #71262] |
Mon, 27 July 2009 16:45 |
Mark Phippard Messages: 129 Registered: July 2009 |
Senior Member |
|
|
On 2009-07-27 11:08:00 -0400, costa@tecgraf.puc-rio.br (Andre Costa) said:
> Mark Phippard wrote:
>
>> On 2009-07-27 08:49:30 -0400, costa@tecgraf.puc-rio.br (Andre Costa) said:
>
> [...]
>> There is no direct relationship between Subclipse release and Mylyn
>> releases. The fact that a Subclipse upgrade is available to you has
>> nothing to do with Mylyn not showing.
>
> Yes, I thought so. This is why I don't understand why Eclipse doesn't
> realize Mylyn can be upgraded as well. AFAICS it should ask me to
> upgrade both Subclipse and Mylyn, not because they're related somehow,
> but simply because there are upgrades for both of them.
>
> So, the core question is: why isn't Mylyn 3.2.1 picked by Eclipse
> updater? Do I need to do anything on my own?
Perhaps Mylyn 3.2.1 has not been published to the update sites Eclipse
is checking. For example, maybe the updates are configured to only
check the Galileo/Ganymeded (whatever) update site and 3.2.1 is not on
that site?
>> BTW, why are you stuck with Subversion 1.5? Any SVN 1.x client can
>> talk to any 1.x server, so you should be able to run any version on the
>> client that you want to. That said, you do need a way to get the SVN
>> 1.6 binaries for JavaHL. If you are on Linux, perhaps you are waiting
>> for your distro to upgrade you?
>> There are details on this wiki for doing it yourself:
>
>> http://subclipse.tigris.org/wiki/JavaHL
>
> Yes, that's precisely my problem: latest subversion CLI client
> available on Ubuntu Jaunty is 1.5.4, and I do use it a lot on the same
> workspace I use Subclipse. If I upgrade Subclipse to 1.6 I will not be
> able to use 1.5.x CLI client any longer, which is unacceptable.
Well, you can upgrade your CLI yourself if you choose to. But I
understand wanting to get it from Ubuntu. They do have 1.6 on the
Karmic site:
http://packages.ubuntu.com/karmic/subversion
Mark
|
|
|
Re: Automatic upgrade from 3.2.0 to 3.2.1? [message #71302 is a reply to message #71282] |
Mon, 27 July 2009 17:24 |
Andre Costa Messages: 21 Registered: July 2009 |
Junior Member |
|
|
Mark Phippard wrote:
>> Yes, I thought so. This is why I don't understand why Eclipse doesn't
>> realize Mylyn can be upgraded as well. AFAICS it should ask me to
>> upgrade both Subclipse and Mylyn, not because they're related somehow,
>> but simply because there are upgrades for both of them.
>>
>> So, the core question is: why isn't Mylyn 3.2.1 picked by Eclipse
>> updater? Do I need to do anything on my own?
> Perhaps Mylyn 3.2.1 has not been published to the update sites Eclipse
> is checking. For example, maybe the updates are configured to only
> check the Galileo/Ganymeded (whatever) update site and 3.2.1 is not on
> that site?
Mmmh... could be, but then there's something else wrong here. The URL
published on Mylyn's site for updates is the one registered on Eclipse:
http://download.eclipse.org/tools/mylyn/update/e3.4
My first guess was that it was not officially available, for whatever
reason (despite the fact that it is announced as released), and that would
explain it not being pulled by the updater.
However, when I try to install Atlassian Connector through Mylyn Connector
Discovery the installer tries to fetch some (all?) Mylyn 3.2.1 JARs, and
that's what's puzzling me (and maybe what's confusing Eclipse, please
refer to the other thread for more details). It doesn't make sense to be
the latest version if you go one path but not if you follow another.
>> Yes, that's precisely my problem: latest subversion CLI client
>> available on Ubuntu Jaunty is 1.5.4, and I do use it a lot on the same
>> workspace I use Subclipse. If I upgrade Subclipse to 1.6 I will not be
>> able to use 1.5.x CLI client any longer, which is unacceptable.
> Well, you can upgrade your CLI yourself if you choose to. But I
> understand wanting to get it from Ubuntu. They do have 1.6 on the
> Karmic site:
> http://packages.ubuntu.com/karmic/subversion
Yeah, it sucks, I never understood why subversion *client* always lags
behind on updates on Linux distros (I use Fedora 10 at home and I have the
same problem there as well), AFAIK there are no fancy dependencies that
could justify that, but...
Regards,
Andre
|
|
| |
Re: Automatic upgrade from 3.2.0 to 3.2.1? [message #92582 is a reply to message #71302] |
Mon, 27 July 2009 18:39 |
Marco Maccaferri Messages: 147 Registered: July 2009 |
Senior Member |
|
|
On 27/07/2009 19:24 Andre Costa ha scritto:
> Yeah, it sucks, I never understood why subversion *client* always lags
> behind on updates on Linux distros (I use Fedora 10 at home and I have the
> same problem there as well), AFAIK there are no fancy dependencies that
> could justify that, but...
Maybe I can help with F10. Subversion 1.6.2 is available from quite some
time in the updates/testing repository, you can easily grab the rpm from
there and do a yum localinstall (if you don't want to enable the testing
repositories which may bring in some unwanted updates). Why it is still
in testing since april 27th is unknown.
To get the latest subversion (1.6.3) you can grab the 1.6.2 source rpm,
replace the source package with the one downloaded from tigris, change
the version number in the specs file and recompile. Works well, I'm on
F10 too and I'm using svn 1.6.3 with javahl and subclipse.
Regards,
Marco.
|
|
|
Re: Automatic upgrade from 3.2.0 to 3.2.1? [message #136218 is a reply to message #71302] |
Mon, 27 July 2009 19:21 |
Mark Phippard Messages: 129 Registered: July 2009 |
Senior Member |
|
|
On 2009-07-27 13:24:39 -0400, costa@tecgraf.puc-rio.br (Andre Costa) said:
> Mark Phippard wrote:
>
>>> Yes, I thought so. This is why I don't understand why Eclipse doesn't
>>> realize Mylyn can be upgraded as well. AFAICS it should ask me to
>>> upgrade both Subclipse and Mylyn, not because they're related somehow,
>>> but simply because there are upgrades for both of them.
>>>
>>> So, the core question is: why isn't Mylyn 3.2.1 picked by Eclipse
>>> updater? Do I need to do anything on my own?
>
>> Perhaps Mylyn 3.2.1 has not been published to the update sites Eclipse
>> is checking. For example, maybe the updates are configured to only
>> check the Galileo/Ganymeded (whatever) update site and 3.2.1 is not on
>> that site?
>
> Mmmh... could be, but then there's something else wrong here. The URL
> published on Mylyn's site for updates is the one registered on Eclipse:
>
> http://download.eclipse.org/tools/mylyn/update/e3.4
>
> My first guess was that it was not officially available, for whatever
> reason (despite the fact that it is announced as released), and that
> would explain it not being pulled by the updater.
>
> However, when I try to install Atlassian Connector through Mylyn
> Connector Discovery the installer tries to fetch some (all?) Mylyn
> 3.2.1 JARs, and that's what's puzzling me (and maybe what's confusing
> Eclipse, please refer to the other thread for more details). It doesn't
> make sense to be the latest version if you go one path but not if you
> follow another.
There is a difference between "Discovery Sites" and "Update Sites".
When you get an EPP package the updates all come from one master sites,
but individual plugins like Mylyn can still install their discovery
sites so that you can find additional plugins.
The check for updates only checks the update sites.
Mark
|
|
| |
Re: Automatic upgrade from 3.2.0 to 3.2.1? [message #360096 is a reply to message #136218] |
Tue, 28 July 2009 13:36 |
Andre Costa Messages: 21 Registered: July 2009 |
Junior Member |
|
|
Mark Phippard wrote:
> There is a difference between "Discovery Sites" and "Update Sites".
> When you get an EPP package the updates all come from one master sites,
> but individual plugins like Mylyn can still install their discovery
> sites so that you can find additional plugins.
> The check for updates only checks the update sites.
Thks, that indeed explains the current behavior. However, I think it makes
room for confusion and -- worse -- glitches.
Eg. I am at home now and I've installed subversion 1.6.2 according to
Marco's suggestion. When I ask Eclipse to check for updates, it finds
Subclipse 1.6 (so far, so good). However, along with its own packages it
tries to pull these as well (all from 3.2.1 release):
- Mylyn Bridge: Eclipse IDE
- Mylyn Bridge: Java Development
- Mylyn Bridge: Team Support
- Mylyn Connector: Bugzilla
- Mylyn Task List
- Mylyn Task-Focused Interface
- Mylyn WikiText (1.1.1)
If I accept and proceed with the installation, I end up with the dreadful
"no-plugins" problem
[ http://www.eclipse.org/newsportal/article.php?id=1915&gr oup=eclipse.tools.mylyn#1915].
Major fail :(
In order to fix this, I have to:
- close Eclipse
- remove ~/.eclipse/org.eclipse.platform_3.5.0_1729844414 (I thought
-clean should do this, but apparently it doesn't; is there any better way?)
- restart Eclipse
- reinstall Subclipse (and any other plugins I had before) *with "contact
other updates sites" DISABLED*. Now this is weird: AFAICS when I am
INSTALLING a feature I can disable the "contact other sites" feature, but
when I'm UPGRADING I can't do it.
So, IMHO there's a problem somewhere that deserves a bug report, I just
don't know whose fault this is. Where should I file it? Subclipse? Mylyn?
Eclipse itself?
Regards,
Andre
|
|
| | |
Re: Automatic upgrade from 3.2.0 to 3.2.1? [message #369105 is a reply to message #361782] |
Tue, 28 July 2009 15:32 |
Andre Costa Messages: 21 Registered: July 2009 |
Junior Member |
|
|
Mark Phippard wrote:
> On 2009-07-28 09:42:11 -0400, costa@tecgraf.puc-rio.br (Andre Costa) said:
>> Thks. I realized the problem is the other way around (it's Subclipse
>> that tries to install Mylyn 3.2.1 if "check other updates sites" is
>> enabled).
> As you know, the install/update code is entirely owned by Eclipse.
> Plugins can just declare their requirements. Subclipse does not
> require Mylyn and does not force it to be installed. However, the
> Subclipse update site does host a plugin that provides the integration
> between Subclipse and Mylyn. This plugin obviously requires Mylyn (it
> just specifies 3.0.0 or greater).
> Since you apparently do not have Mylyn installed already, the Eclipse
> installer is trying to find it on one of the sites it knows about.
But I *do* have Mylyn 3.2.0 "installed" (at least I use the one that comes
with Galileo by default), and the integration with Subclipse *is* working.
Since Subclipse declares that it depends on Mylyn >= 3.0.0 Eclipse
shouldn't try to pull Mylyn 3.2.1 considering there's no hard dependency
on this particular version and since Eclipse itself doesn't see Mylyn
3.2.1 as an eligible upgrade. This behavior is inconsistent IMHO.
However, that's not the biggest problem. If Mylyn 3.2.1 could be installed
I wouldn't care how it was pulled. But, for some reason I can't install
Mylyn 3.2.1 on Galileo, no matter how I try it, the result is always the
same: once it is installed other plugins (FindBugs, Subclipse etc.) stop
working. They don't even appear on the Preferences settings. I even tried
starting from scratch -- removing
~/.eclipse/org.eclipse.platform_3.5.0_1729844414/ -- and installing Mylyn
3.2.1 from a local zipped archive, before trying to install any additional
plugins; once I install the others, they simply don't work.
It could be something specific to my installation (Linux), but since
Michael Rehse had the same problem on Vista
[ http://www.eclipse.org/newsportal/article.php?id=1915&gr oup=eclipse.tools.mylyn#1915],
I tend to think it's something else.
|
|
|
Re: Automatic upgrade from 3.2.0 to 3.2.1? [message #598380 is a reply to message #71223] |
Mon, 27 July 2009 14:53 |
Mark Phippard Messages: 129 Registered: July 2009 |
Senior Member |
|
|
On 2009-07-27 08:49:30 -0400, costa@tecgraf.puc-rio.br (Andre Costa) said:
> I'm using Galileo with Mylyn 3.2.0. I know that Mylyn 3.2.1 has been
> released a couple of days ago, and I was expecting Eclipse would
> automatically realize this and offer me to upgrade it (I have
> "automatic updates" enabled). However, not only it does not offer me to
> upgrade but manually checking for updates seems to only detect
> Subclipse updates (which BTW I *don't* want to upgrade, since I'm
> currently stuck with Subversion 1.5).
>
> Is Subclipse 1.6 required for Mylyn 3.2.1? If not, shouldn't the
> upgrade be automatically suggested? How do I workaround this?
There is no direct relationship between Subclipse release and Mylyn
releases. The fact that a Subclipse upgrade is available to you has
nothing to do with Mylyn not showing.
BTW, why are you stuck with Subversion 1.5? Any SVN 1.x client can
talk to any 1.x server, so you should be able to run any version on the
client that you want to. That said, you do need a way to get the SVN
1.6 binaries for JavaHL. If you are on Linux, perhaps you are waiting
for your distro to upgrade you?
There are details on this wiki for doing it yourself:
http://subclipse.tigris.org/wiki/JavaHL
Mark
|
|
|
Re: Automatic upgrade from 3.2.0 to 3.2.1? [message #598385 is a reply to message #71242] |
Mon, 27 July 2009 15:08 |
Andre Costa Messages: 21 Registered: July 2009 |
Junior Member |
|
|
Mark Phippard wrote:
> On 2009-07-27 08:49:30 -0400, costa@tecgraf.puc-rio.br (Andre Costa) said:
[...]
> There is no direct relationship between Subclipse release and Mylyn
> releases. The fact that a Subclipse upgrade is available to you has
> nothing to do with Mylyn not showing.
Yes, I thought so. This is why I don't understand why Eclipse doesn't
realize Mylyn can be upgraded as well. AFAICS it should ask me to upgrade
both Subclipse and Mylyn, not because they're related somehow, but simply
because there are upgrades for both of them.
So, the core question is: why isn't Mylyn 3.2.1 picked by Eclipse updater?
Do I need to do anything on my own?
> BTW, why are you stuck with Subversion 1.5? Any SVN 1.x client can
> talk to any 1.x server, so you should be able to run any version on the
> client that you want to. That said, you do need a way to get the SVN
> 1.6 binaries for JavaHL. If you are on Linux, perhaps you are waiting
> for your distro to upgrade you?
> There are details on this wiki for doing it yourself:
> http://subclipse.tigris.org/wiki/JavaHL
Yes, that's precisely my problem: latest subversion CLI client available
on Ubuntu Jaunty is 1.5.4, and I do use it a lot on the same workspace I
use Subclipse. If I upgrade Subclipse to 1.6 I will not be able to use
1.5.x CLI client any longer, which is unacceptable.
Regards,
Andre
|
|
|
Re: Automatic upgrade from 3.2.0 to 3.2.1? [message #598388 is a reply to message #71262] |
Mon, 27 July 2009 16:45 |
Mark Phippard Messages: 129 Registered: July 2009 |
Senior Member |
|
|
On 2009-07-27 11:08:00 -0400, costa@tecgraf.puc-rio.br (Andre Costa) said:
> Mark Phippard wrote:
>
>> On 2009-07-27 08:49:30 -0400, costa@tecgraf.puc-rio.br (Andre Costa) said:
>
> [...]
>> There is no direct relationship between Subclipse release and Mylyn
>> releases. The fact that a Subclipse upgrade is available to you has
>> nothing to do with Mylyn not showing.
>
> Yes, I thought so. This is why I don't understand why Eclipse doesn't
> realize Mylyn can be upgraded as well. AFAICS it should ask me to
> upgrade both Subclipse and Mylyn, not because they're related somehow,
> but simply because there are upgrades for both of them.
>
> So, the core question is: why isn't Mylyn 3.2.1 picked by Eclipse
> updater? Do I need to do anything on my own?
Perhaps Mylyn 3.2.1 has not been published to the update sites Eclipse
is checking. For example, maybe the updates are configured to only
check the Galileo/Ganymeded (whatever) update site and 3.2.1 is not on
that site?
>> BTW, why are you stuck with Subversion 1.5? Any SVN 1.x client can
>> talk to any 1.x server, so you should be able to run any version on the
>> client that you want to. That said, you do need a way to get the SVN
>> 1.6 binaries for JavaHL. If you are on Linux, perhaps you are waiting
>> for your distro to upgrade you?
>> There are details on this wiki for doing it yourself:
>
>> http://subclipse.tigris.org/wiki/JavaHL
>
> Yes, that's precisely my problem: latest subversion CLI client
> available on Ubuntu Jaunty is 1.5.4, and I do use it a lot on the same
> workspace I use Subclipse. If I upgrade Subclipse to 1.6 I will not be
> able to use 1.5.x CLI client any longer, which is unacceptable.
Well, you can upgrade your CLI yourself if you choose to. But I
understand wanting to get it from Ubuntu. They do have 1.6 on the
Karmic site:
http://packages.ubuntu.com/karmic/subversion
Mark
|
|
|
Re: Automatic upgrade from 3.2.0 to 3.2.1? [message #598392 is a reply to message #71282] |
Mon, 27 July 2009 17:24 |
Andre Costa Messages: 21 Registered: July 2009 |
Junior Member |
|
|
Mark Phippard wrote:
>> Yes, I thought so. This is why I don't understand why Eclipse doesn't
>> realize Mylyn can be upgraded as well. AFAICS it should ask me to
>> upgrade both Subclipse and Mylyn, not because they're related somehow,
>> but simply because there are upgrades for both of them.
>>
>> So, the core question is: why isn't Mylyn 3.2.1 picked by Eclipse
>> updater? Do I need to do anything on my own?
> Perhaps Mylyn 3.2.1 has not been published to the update sites Eclipse
> is checking. For example, maybe the updates are configured to only
> check the Galileo/Ganymeded (whatever) update site and 3.2.1 is not on
> that site?
Mmmh... could be, but then there's something else wrong here. The URL
published on Mylyn's site for updates is the one registered on Eclipse:
http://download.eclipse.org/tools/mylyn/update/e3.4
My first guess was that it was not officially available, for whatever
reason (despite the fact that it is announced as released), and that would
explain it not being pulled by the updater.
However, when I try to install Atlassian Connector through Mylyn Connector
Discovery the installer tries to fetch some (all?) Mylyn 3.2.1 JARs, and
that's what's puzzling me (and maybe what's confusing Eclipse, please
refer to the other thread for more details). It doesn't make sense to be
the latest version if you go one path but not if you follow another.
>> Yes, that's precisely my problem: latest subversion CLI client
>> available on Ubuntu Jaunty is 1.5.4, and I do use it a lot on the same
>> workspace I use Subclipse. If I upgrade Subclipse to 1.6 I will not be
>> able to use 1.5.x CLI client any longer, which is unacceptable.
> Well, you can upgrade your CLI yourself if you choose to. But I
> understand wanting to get it from Ubuntu. They do have 1.6 on the
> Karmic site:
> http://packages.ubuntu.com/karmic/subversion
Yeah, it sucks, I never understood why subversion *client* always lags
behind on updates on Linux distros (I use Fedora 10 at home and I have the
same problem there as well), AFAIK there are no fancy dependencies that
could justify that, but...
Regards,
Andre
|
|
| |
Re: Automatic upgrade from 3.2.0 to 3.2.1? [message #598412 is a reply to message #71302] |
Mon, 27 July 2009 18:39 |
Marco Maccaferri Messages: 147 Registered: July 2009 |
Senior Member |
|
|
On 27/07/2009 19:24 Andre Costa ha scritto:
> Yeah, it sucks, I never understood why subversion *client* always lags
> behind on updates on Linux distros (I use Fedora 10 at home and I have the
> same problem there as well), AFAIK there are no fancy dependencies that
> could justify that, but...
Maybe I can help with F10. Subversion 1.6.2 is available from quite some
time in the updates/testing repository, you can easily grab the rpm from
there and do a yum localinstall (if you don't want to enable the testing
repositories which may bring in some unwanted updates). Why it is still
in testing since april 27th is unknown.
To get the latest subversion (1.6.3) you can grab the 1.6.2 source rpm,
replace the source package with the one downloaded from tigris, change
the version number in the specs file and recompile. Works well, I'm on
F10 too and I'm using svn 1.6.3 with javahl and subclipse.
Regards,
Marco.
|
|
|
Re: Automatic upgrade from 3.2.0 to 3.2.1? [message #598423 is a reply to message #71302] |
Mon, 27 July 2009 19:21 |
Mark Phippard Messages: 129 Registered: July 2009 |
Senior Member |
|
|
On 2009-07-27 13:24:39 -0400, costa@tecgraf.puc-rio.br (Andre Costa) said:
> Mark Phippard wrote:
>
>>> Yes, I thought so. This is why I don't understand why Eclipse doesn't
>>> realize Mylyn can be upgraded as well. AFAICS it should ask me to
>>> upgrade both Subclipse and Mylyn, not because they're related somehow,
>>> but simply because there are upgrades for both of them.
>>>
>>> So, the core question is: why isn't Mylyn 3.2.1 picked by Eclipse
>>> updater? Do I need to do anything on my own?
>
>> Perhaps Mylyn 3.2.1 has not been published to the update sites Eclipse
>> is checking. For example, maybe the updates are configured to only
>> check the Galileo/Ganymeded (whatever) update site and 3.2.1 is not on
>> that site?
>
> Mmmh... could be, but then there's something else wrong here. The URL
> published on Mylyn's site for updates is the one registered on Eclipse:
>
> http://download.eclipse.org/tools/mylyn/update/e3.4
>
> My first guess was that it was not officially available, for whatever
> reason (despite the fact that it is announced as released), and that
> would explain it not being pulled by the updater.
>
> However, when I try to install Atlassian Connector through Mylyn
> Connector Discovery the installer tries to fetch some (all?) Mylyn
> 3.2.1 JARs, and that's what's puzzling me (and maybe what's confusing
> Eclipse, please refer to the other thread for more details). It doesn't
> make sense to be the latest version if you go one path but not if you
> follow another.
There is a difference between "Discovery Sites" and "Update Sites".
When you get an EPP package the updates all come from one master sites,
but individual plugins like Mylyn can still install their discovery
sites so that you can find additional plugins.
The check for updates only checks the update sites.
Mark
|
|
| |
Re: Automatic upgrade from 3.2.0 to 3.2.1? [message #598443 is a reply to message #136218] |
Tue, 28 July 2009 13:36 |
Andre Costa Messages: 21 Registered: July 2009 |
Junior Member |
|
|
Mark Phippard wrote:
> There is a difference between "Discovery Sites" and "Update Sites".
> When you get an EPP package the updates all come from one master sites,
> but individual plugins like Mylyn can still install their discovery
> sites so that you can find additional plugins.
> The check for updates only checks the update sites.
Thks, that indeed explains the current behavior. However, I think it makes
room for confusion and -- worse -- glitches.
Eg. I am at home now and I've installed subversion 1.6.2 according to
Marco's suggestion. When I ask Eclipse to check for updates, it finds
Subclipse 1.6 (so far, so good). However, along with its own packages it
tries to pull these as well (all from 3.2.1 release):
- Mylyn Bridge: Eclipse IDE
- Mylyn Bridge: Java Development
- Mylyn Bridge: Team Support
- Mylyn Connector: Bugzilla
- Mylyn Task List
- Mylyn Task-Focused Interface
- Mylyn WikiText (1.1.1)
If I accept and proceed with the installation, I end up with the dreadful
"no-plugins" problem
[ http://www.eclipse.org/newsportal/article.php?id=1915&gr oup=eclipse.tools.mylyn#1915].
Major fail :(
In order to fix this, I have to:
- close Eclipse
- remove ~/.eclipse/org.eclipse.platform_3.5.0_1729844414 (I thought
-clean should do this, but apparently it doesn't; is there any better way?)
- restart Eclipse
- reinstall Subclipse (and any other plugins I had before) *with "contact
other updates sites" DISABLED*. Now this is weird: AFAICS when I am
INSTALLING a feature I can disable the "contact other sites" feature, but
when I'm UPGRADING I can't do it.
So, IMHO there's a problem somewhere that deserves a bug report, I just
don't know whose fault this is. Where should I file it? Subclipse? Mylyn?
Eclipse itself?
Regards,
Andre
|
|
| | |
Re: Automatic upgrade from 3.2.0 to 3.2.1? [message #598462 is a reply to message #361782] |
Tue, 28 July 2009 15:32 |
Andre Costa Messages: 21 Registered: July 2009 |
Junior Member |
|
|
Mark Phippard wrote:
> On 2009-07-28 09:42:11 -0400, costa@tecgraf.puc-rio.br (Andre Costa) said:
>> Thks. I realized the problem is the other way around (it's Subclipse
>> that tries to install Mylyn 3.2.1 if "check other updates sites" is
>> enabled).
> As you know, the install/update code is entirely owned by Eclipse.
> Plugins can just declare their requirements. Subclipse does not
> require Mylyn and does not force it to be installed. However, the
> Subclipse update site does host a plugin that provides the integration
> between Subclipse and Mylyn. This plugin obviously requires Mylyn (it
> just specifies 3.0.0 or greater).
> Since you apparently do not have Mylyn installed already, the Eclipse
> installer is trying to find it on one of the sites it knows about.
But I *do* have Mylyn 3.2.0 "installed" (at least I use the one that comes
with Galileo by default), and the integration with Subclipse *is* working.
Since Subclipse declares that it depends on Mylyn >= 3.0.0 Eclipse
shouldn't try to pull Mylyn 3.2.1 considering there's no hard dependency
on this particular version and since Eclipse itself doesn't see Mylyn
3.2.1 as an eligible upgrade. This behavior is inconsistent IMHO.
However, that's not the biggest problem. If Mylyn 3.2.1 could be installed
I wouldn't care how it was pulled. But, for some reason I can't install
Mylyn 3.2.1 on Galileo, no matter how I try it, the result is always the
same: once it is installed other plugins (FindBugs, Subclipse etc.) stop
working. They don't even appear on the Preferences settings. I even tried
starting from scratch -- removing
~/.eclipse/org.eclipse.platform_3.5.0_1729844414/ -- and installing Mylyn
3.2.1 from a local zipped archive, before trying to install any additional
plugins; once I install the others, they simply don't work.
It could be something specific to my installation (Linux), but since
Michael Rehse had the same problem on Vista
[ http://www.eclipse.org/newsportal/article.php?id=1915&gr oup=eclipse.tools.mylyn#1915],
I tend to think it's something else.
|
|
|
Goto Forum:
Current Time: Wed May 01 22:00:52 GMT 2024
Powered by FUDForum. Page generated in 0.07385 seconds
|