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 12190 - [Exec/Compile] Cannot set execution properties for a source file
Summary: [Exec/Compile] Cannot set execution properties for a source file
Alias: None
Product: java
Classification: Unclassified
Component: Project (show other bugs)
Version: 3.x
Hardware: PC Windows 3.1/NT
: P3 blocker with 1 vote (vote)
Assignee: Jesse Glick
Depends on: 12238 17826
  Show dependency tree
Reported: 2001-05-15 06:53 UTC by tkellerer
Modified: 2004-11-12 23:54 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description tkellerer 2001-05-15 06:53:39 UTC
When trying to set the execution properties e.g. Compiler I cannot assign
a different compiler because when clicking into the property (where it
read "External compilation" I do not get the dropdown to select a different
compiler. Pressing the button with "..." gives me a list of defined
compiler types but here I can't select one. This is on a CVS filesystem 
(command line support)

This is with 3.2 build 38 
I have disabled some modules (Bean Patterns, Form Editor, JNDI and RMI, New 
Module Wizard)
Comment 1 Svata Dedic 2001-05-15 06:59:14 UTC
Just for records: is the file itself, the directory it is inside and the
.nbattrs file located in that directory all writeable ? Is it just the external
compiler which cannot be modified or the other execution properties are also r/o
Comment 2 tkellerer 2001-05-15 07:10:00 UTC
That's the solution! The file itself is read-only (because I'm using a 
read only check out with CVS) when I change it to read write I can 
set the compiler. 

But I think even if a file is read-only the compiler property (and the
execution and debuggin property as well) should be changeable 

Comment 3 Svata Dedic 2001-05-15 07:19:53 UTC
Yes, this is a known issue with associating info with files in general and
*WILL* be addressed in 3.3 version (new project system, eliminating .nbattrs
thing at all). The problem is that the physical storage of such extended
information (bound to a specific file) is handled internally by the filesystem
and there's no API how to distinguish between the file and its associated info.

I'll keep this issue as a part of list of things that need to be "projectized".
Comment 4 Svata Dedic 2001-05-17 10:36:30 UTC
The ultimate solution depends on a library for base java handling (and also on 
projects, of cours)
Comment 5 Svata Dedic 2001-08-16 17:43:35 UTC
Since the project redesign slipped in 3.4+, I can't keep it as a 
bug. It works as currently specified, but the solution is not good. 
Changing to an enhancement & resetting milestone
Comment 6 Svata Dedic 2002-05-21 17:48:36 UTC
Cleaning up before 4.0 planning
Comment 7 Marek Grummich 2002-07-19 16:43:11 UTC
Target milestone was changed from not determined to TBD
Comment 8 Jesse Glick 2004-11-12 23:54:44 UTC
Inapplicable in 4.0.