This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 153882 - Setting jython version to current from older version is troublesome
Summary: Setting jython version to current from older version is troublesome
Status: RESOLVED FIXED
Alias: None
Product: python
Classification: Unclassified
Component: Projects (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Lou Dasaro
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-25 18:38 UTC by tonybeckham
Modified: 2015-05-18 01:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description tonybeckham 2008-11-25 18:38:22 UTC 
Situation:
I have several projects created with early versions of nbpython and the jython version for them is 2.5a3+  When I try
and run them I get notification that I need to change the python platform.

Problem:
When try to set correct version, properties shows the version of jython that is bundled so it appears to be the choice.
 Press OK to dismiss and one would assume select but the project property for python version is not changed.

Work around:
To resolve expand the drop down for platform selection then choose one of the options.

System:
Product Version: NetBeans IDE 6.5 (Build 20081122210531)
Java: 1.5.0_16; Java HotSpot(TM) Client VM 1.5.0_16-133
System: Mac OS X version 10.5.5 running on i386; MacRoman; en_US (nb
Comment 1 Lou Dasaro 2015-04-08 04:48:50 UTC 

*** This bug has been marked as a duplicate of bug 152753 ***
Comment 2 Lou Dasaro 2015-04-30 06:17:41 UTC 
Thank you for your report. 
This was incorrectly marked as a duplicate of bug 152753; this is a valid bug on its own merits.

We are in the process of bundling Jython 2.7 
and Autodetect is being enhanced to discover alternate Jython platforms and correctly store their properties.
Comment 3 Lou Dasaro 2015-05-18 01:40:36 UTC 
Tested successfully. Appears to have been fixed, possibly as a result of updates to PythonPlatformManager.