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 239765 - Can not remove "OracleSolarisStudio" tool collection
Summary: Can not remove "OracleSolarisStudio" tool collection
Status: NEW
Alias: None
Product: cnd
Classification: Unclassified
Component: Toolchain (show other bugs)
Version: 7.4
Hardware: All All
: P4 normal (vote)
Assignee: Alexander Simon
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-24 13:44 UTC by Alexander Pepin
Modified: 2016-07-22 09:46 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 Alexander Pepin 2013-12-24 13:44:16 UTC 
Steps to reproduce:
- add a new build host with a Studio tool collection 
- create a remote project
- try to remove any of tool collection e.g. SunStudio from Services/C/C++ Build Hosts/<host_name>/Tool Collections/SunStudio using the toool collection context menu
Result: Nothing happens.
Comment 1 Vladimir Kvashin 2013-12-24 14:23:23 UTC 
Studio is an alias that refers to the most recent (I believe) Studio tool chain. It can not be removed by design.

This design can be revisited, but that's a matter of a separate discussion and enhancement rather than bug, I believe.

However the fact that "Remove Tool Collection" menu item for this toolchain exists, is enabled, but does nothing (just moves selection from "Studio" toolchain to parent "Tools Collections" folder), is a bug.
Comment 2 Vladimir Kvashin 2013-12-24 14:41:39 UTC 
In a way it's remote issue - at least menu item resides in cnd,remote (RemoveToolchainAction class). However toolchain API does not provide information whether the given toolchain is such an alias.

It could be added into CompilerSet interface; the code that "knows" whether it is an alias, is in CompilerSetManagerImpl.completeSunStudioCompilerSet (CompilerSetManagerImpl.java:869).

(the key point is the call getToolchainDescriptor().getAliases())

But is it really a P3? I think it's rather a P4 :)
Comment 3 Alexander Pepin 2013-12-24 14:45:32 UTC 
Does it mean that the bug won't be fixed? :)
Comment 4 Alexander Simon 2013-12-24 14:49:47 UTC 
(In reply to Alexander Pepin from comment #3)
> Does it mean that the bug won't be fixed? :)
IMHO it is a path of studio tools refactoring:
- remove aliases at all (as it supported for GNU: one GNU flavor for any concrete GNU)