Home » Eclipse Projects » Mylyn » Re: Subclipse, Mylyn, Galileo
| Re: Subclipse, Mylyn, Galileo [message #71123] |
Fri, 24 July 2009 15:42  |
Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
Copying this to the Mylyn newsgroup (eclipse.tools.mylyn). You probably
should ask on the Subclipse forums, too. It sounds like a possible
version conflict to me.
Michael Rehse wrote:
> Hello all,
> New to forums, been using Eclipse for a while.
>
> I had a slow day at work, so decided to update to Galileo.
>
> I downloaded the Java Developer version, and set about installing my
> plugins. Subclipse installed just fine, but as soon as I installed the
> Trac plugin for Mylyn, Subclipse suddenly stopped working: my projects
> no longer showed the icons for being under version control, and I could
> not check out new projects from subversion.
>
> I looked in the error log and found this for all of my projects:
>
> org.eclipse.team.core.TeamException: Could not instantiate provider
> org.tigris.subversion.subclipse.core.svnnature for project (...).
> at
> org.eclipse.team.core.RepositoryProvider.mapNewProvider(Repo sitoryProvider.java:165)
>
> at
> org.eclipse.team.core.RepositoryProvider.mapExistingProvider (RepositoryProvider.java:235)
>
> at
> org.eclipse.team.core.RepositoryProvider.getProvider(Reposit oryProvider.java:507)
>
> at
> org.eclipse.team.internal.ccvs.ui.CVSLightweightDecorator.is MappedToCVS(CVSLightweightDecorator.java:192)
>
> at
> org.eclipse.team.internal.ccvs.ui.CVSLightweightDecorator.de corate(CVSLightweightDecorator.java:147)
>
> at
> org.eclipse.ui.internal.decorators.LightweightDecoratorDefin ition.decorate(LightweightDecoratorDefinition.java:263)
>
> at
> org.eclipse.ui.internal.decorators.LightweightDecoratorManag er$LightweightRunnable.run(LightweightDecoratorManager.java: 81)
>
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at
> org.eclipse.ui.internal.decorators.LightweightDecoratorManag er.decorate(LightweightDecoratorManager.java:365)
>
> at
> org.eclipse.ui.internal.decorators.LightweightDecoratorManag er.getDecorations(LightweightDecoratorManager.java:347)
>
> at
> org.eclipse.ui.internal.decorators.DecorationScheduler$1.ens ureResultCached(DecorationScheduler.java:371)
>
> at
> org.eclipse.ui.internal.decorators.DecorationScheduler$1.run (DecorationScheduler.java:331)
>
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>
> I assume this is where to post this question... Can anyone give me a
> clue as to where to go from here? All my projects use Subclipse already,
> and I don't believe the Mylyn Trac Connector supports subversive...
>
> Any help is appreciated.
>
> -Michael Rehse
> Arc90
>
>
|
|
| |
| Re: Subclipse, Mylyn, Galileo [message #71164 is a reply to message #71143] |
Fri, 24 July 2009 18:39  |
 Andre Costa
Messages: 21
Registered: July 2009 |
Junior Member |
|
|
Hi,
I've just spent a couple of hours chasing this as well. Pretty annoying =/
I'm not sure, but I think it could be related to Mylyn 3.2.1. Here's what
I found so far:
- vanilla Eclipse 3.5 (Mylyn 3.2.0): check for updates says everything is
updated (it doesn't try to upgrade Mylyn to 3.2.1)
- installing only Subclipse 1.4 on vanilla Eclipse 3.5 --> OK
- installing only FindBugs on vanilla Eclipse 3.5 --> OK
- installing Atlassian Connector through Mylyn Connector Discovery: Mylyn
3.2.1 is installed automatically (?!). Aftet the usual restart, *all*
plugins seem to be disabled -- FindBugs, Subclipse, even Atlassian
Connector
Atlassian connector tries to pull Mylyn Task List 3.2.1, and this might be
causing Mylyn 3.2.1 to be (partially) installed.
I looked closely and it seems that when I try to install Subclipse the
"Subclipse integration for Mylyn" tries to pull a couple of Mylyn 3.2.1
updates along, and this seems to screw the installation. If I uncheck the
"contact all updates sites" on the installation dialog, then Mylyn is left
alone at 3.2.0, and Subclipse is properly installed.
My (wild) guess is that the dependencies resolution is bringing partial
Mylyn updates (I remember seeing a couple of Mylyn 3.2.0 features still
around after one of the failed updates), and this is messing with the
whole plugin management.
So, until this is sorted out, I recommend disabling the "contact all
updates sites" feature and stay away from Mylyn 3.2.1 until it appears as
a regular Eclipse update, and not as a "subupdate" from some other plugin.
Unfortunately, it seems that I'll have to stay away from JIRA Connector as
well, which is really annoying because I use it a lot.
I hope this info helps someone understand what's going on, and helps avoid
some further problems.
|
|
|
| Re: Subclipse, Mylyn, Galileo [message #71322 is a reply to message #71164] |
Mon, 27 July 2009 18:19 |
Steffen Pingel
Messages: 706
Registered: July 2009 |
Senior Member |
|
|
Andre,
can you please file a bug report and include the steps below to reproduce the
problem: http://eclipse.org/mylyn/support ?
All Mylyn features should have proper dependencies set to prevent partial
updates. We'll have to verify that this is the case for the 3.2.1 stream.
Steffen
Andre Costa wrote:
> Hi,
>
> I've just spent a couple of hours chasing this as well. Pretty annoying =/
>
> I'm not sure, but I think it could be related to Mylyn 3.2.1. Here's what
> I found so far:
>
> - vanilla Eclipse 3.5 (Mylyn 3.2.0): check for updates says everything is
> updated (it doesn't try to upgrade Mylyn to 3.2.1)
> - installing only Subclipse 1.4 on vanilla Eclipse 3.5 --> OK
> - installing only FindBugs on vanilla Eclipse 3.5 --> OK
> - installing Atlassian Connector through Mylyn Connector Discovery: Mylyn
> 3.2.1 is installed automatically (?!). Aftet the usual restart, *all*
> plugins seem to be disabled -- FindBugs, Subclipse, even Atlassian
> Connector
>
> Atlassian connector tries to pull Mylyn Task List 3.2.1, and this might be
> causing Mylyn 3.2.1 to be (partially) installed.
>
> I looked closely and it seems that when I try to install Subclipse the
> "Subclipse integration for Mylyn" tries to pull a couple of Mylyn 3.2.1
> updates along, and this seems to screw the installation. If I uncheck the
> "contact all updates sites" on the installation dialog, then Mylyn is left
> alone at 3.2.0, and Subclipse is properly installed.
>
> My (wild) guess is that the dependencies resolution is bringing partial
> Mylyn updates (I remember seeing a couple of Mylyn 3.2.0 features still
> around after one of the failed updates), and this is messing with the
> whole plugin management.
>
> So, until this is sorted out, I recommend disabling the "contact all
> updates sites" feature and stay away from Mylyn 3.2.1 until it appears as
> a regular Eclipse update, and not as a "subupdate" from some other plugin.
> Unfortunately, it seems that I'll have to stay away from JIRA Connector as
> well, which is really annoying because I use it a lot.
>
> I hope this info helps someone understand what's going on, and helps avoid
> some further problems.
--
Steffen Pingel
Committer, http://eclipse.org/mylyn
Senior Developer, http://tasktop.com
|
|
| | |
| Re: Subclipse, Mylyn, Galileo [message #598351 is a reply to message #71143] |
Fri, 24 July 2009 18:39 |
Andre Costa
Messages: 21
Registered: July 2009 |
Junior Member |
|
|
Hi,
I've just spent a couple of hours chasing this as well. Pretty annoying =/
I'm not sure, but I think it could be related to Mylyn 3.2.1. Here's what
I found so far:
- vanilla Eclipse 3.5 (Mylyn 3.2.0): check for updates says everything is
updated (it doesn't try to upgrade Mylyn to 3.2.1)
- installing only Subclipse 1.4 on vanilla Eclipse 3.5 --> OK
- installing only FindBugs on vanilla Eclipse 3.5 --> OK
- installing Atlassian Connector through Mylyn Connector Discovery: Mylyn
3.2.1 is installed automatically (?!). Aftet the usual restart, *all*
plugins seem to be disabled -- FindBugs, Subclipse, even Atlassian
Connector
Atlassian connector tries to pull Mylyn Task List 3.2.1, and this might be
causing Mylyn 3.2.1 to be (partially) installed.
I looked closely and it seems that when I try to install Subclipse the
"Subclipse integration for Mylyn" tries to pull a couple of Mylyn 3.2.1
updates along, and this seems to screw the installation. If I uncheck the
"contact all updates sites" on the installation dialog, then Mylyn is left
alone at 3.2.0, and Subclipse is properly installed.
My (wild) guess is that the dependencies resolution is bringing partial
Mylyn updates (I remember seeing a couple of Mylyn 3.2.0 features still
around after one of the failed updates), and this is messing with the
whole plugin management.
So, until this is sorted out, I recommend disabling the "contact all
updates sites" feature and stay away from Mylyn 3.2.1 until it appears as
a regular Eclipse update, and not as a "subupdate" from some other plugin.
Unfortunately, it seems that I'll have to stay away from JIRA Connector as
well, which is really annoying because I use it a lot.
I hope this info helps someone understand what's going on, and helps avoid
some further problems.
|
|
|
| Re: Subclipse, Mylyn, Galileo [message #598398 is a reply to message #71164] |
Mon, 27 July 2009 18:19 |
Steffen Pingel
Messages: 706
Registered: July 2009 |
Senior Member |
|
|
Andre,
can you please file a bug report and include the steps below to reproduce the
problem: http://eclipse.org/mylyn/support ?
All Mylyn features should have proper dependencies set to prevent partial
updates. We'll have to verify that this is the case for the 3.2.1 stream.
Steffen
Andre Costa wrote:
> Hi,
>
> I've just spent a couple of hours chasing this as well. Pretty annoying =/
>
> I'm not sure, but I think it could be related to Mylyn 3.2.1. Here's what
> I found so far:
>
> - vanilla Eclipse 3.5 (Mylyn 3.2.0): check for updates says everything is
> updated (it doesn't try to upgrade Mylyn to 3.2.1)
> - installing only Subclipse 1.4 on vanilla Eclipse 3.5 --> OK
> - installing only FindBugs on vanilla Eclipse 3.5 --> OK
> - installing Atlassian Connector through Mylyn Connector Discovery: Mylyn
> 3.2.1 is installed automatically (?!). Aftet the usual restart, *all*
> plugins seem to be disabled -- FindBugs, Subclipse, even Atlassian
> Connector
>
> Atlassian connector tries to pull Mylyn Task List 3.2.1, and this might be
> causing Mylyn 3.2.1 to be (partially) installed.
>
> I looked closely and it seems that when I try to install Subclipse the
> "Subclipse integration for Mylyn" tries to pull a couple of Mylyn 3.2.1
> updates along, and this seems to screw the installation. If I uncheck the
> "contact all updates sites" on the installation dialog, then Mylyn is left
> alone at 3.2.0, and Subclipse is properly installed.
>
> My (wild) guess is that the dependencies resolution is bringing partial
> Mylyn updates (I remember seeing a couple of Mylyn 3.2.0 features still
> around after one of the failed updates), and this is messing with the
> whole plugin management.
>
> So, until this is sorted out, I recommend disabling the "contact all
> updates sites" feature and stay away from Mylyn 3.2.1 until it appears as
> a regular Eclipse update, and not as a "subupdate" from some other plugin.
> Unfortunately, it seems that I'll have to stay away from JIRA Connector as
> well, which is really annoying because I use it a lot.
>
> I hope this info helps someone understand what's going on, and helps avoid
> some further problems.
--
Steffen Pingel
Committer, http://eclipse.org/mylyn
Senior Developer, http://tasktop.com
|
|
| |
Goto Forum:
Current Time: Thu Dec 26 22:08:36 GMT 2024
Powered by FUDForum. Page generated in 0.04393 seconds |
] 
Search
Help
Register
Login
Home
