Bug 953048 - no run configurations after pydev update
Summary: no run configurations after pydev update
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse-pydev
Version: 18
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Sami Wagiaalla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-17 09:01 UTC by Daniel
Modified: 2016-06-07 22:46 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-05-03 23:57:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
"eclipse -clean -debug -consoleLog" output (23.01 KB, text/plain)
2013-04-17 09:01 UTC, Daniel
no flags Details

Description Daniel 2013-04-17 09:01:11 UTC
Created attachment 736735 [details]
"eclipse -clean -debug -consoleLog" output

Description of problem:
PyDev plugin is not functioning after latest update to 2.7.3-1.  Eclipse loads fine and the PyDev plugin is present under Preferences but no Python programs can be run even after setting up an interpreter.  (PyDev doesn't show up under Run Configurations at all.)

Version-Release number of selected component (if applicable):
2.7.3-1

How reproducible:


Steps to Reproduce:
1. Update to 2.7.3-1
2. Select an interpreter (this should actually be remembered after a simple update)
3. Try running any Python program with the PyDev plugin.
  
Actual results:
PyDev isn't listed under Run Configurations so any attempt to run a Python program will result in the "Unable to Launch - The selection cannot be launched and there are no recent launches" error message.

Expected results:


Additional info:
I attached the output from running "eclipse -clean -debug -consoleLog".  The "!MESSAGE Could not get internal extension for: org.python.pydev.pydev_interpreter_info_builder" looks to be relevant to the problem.

This bug has affected all of my workstations so on one of them I removed eclipse-pydev-2.7.3-1.fc18.noarch and manually installed the 2.7.3 PyDev plugin inside of Eclipse under "Install New Software...".  The manual install worked great and fixed the problem but it would be great to figure out what is wrong with the eclipse-pydev-2.7.3-1.fc18.noarch update.

Comment 1 Matt Chan 2013-04-18 02:30:21 UTC
I can confirm this bug. Can you change the title to something more descriptive, for example, "no run configurations after pydev update"?

I also solved it by moving to an out-of-repo version of pydev.

Thanks!

Comment 2 Sami Wagiaalla 2013-04-23 19:58:21 UTC
Thanks for the report and the confirmation.

I had a hard time reproducing this but the clue was

!MESSAGE Missing optionally required bundle org.eclipse.jdt.ui_0.0.0.

It turns out that org.eclipse.jdt.ui is not an optional requirement.

Do you guys have eclipse-jdt intalled? If not can you try
yum install eclipse-jdt.

I'll investigate the requirement.

Comment 3 Daniel 2013-04-23 20:32:43 UTC
Installing eclipse-jdt fixed the problem for me; thanks for helping us figure out what was wrong!

Comment 4 Sami Wagiaalla 2013-04-23 20:49:51 UTC
Thanks for confirming Daniel. I'll confirm that this is a hard requirement and if its I'll post a fix upstream and patch the rpm.

Comment 5 Fedora Update System 2013-04-25 13:49:34 UTC
eclipse-pydev-2.7.3-2.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/eclipse-pydev-2.7.3-2.fc18

Comment 6 Fedora Update System 2013-04-26 00:59:05 UTC
Package eclipse-pydev-2.7.3-2.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing eclipse-pydev-2.7.3-2.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-6640/eclipse-pydev-2.7.3-2.fc18
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2013-05-03 23:57:45 UTC
eclipse-pydev-2.7.3-2.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.