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 58615 - inheritance in configurations
Summary: inheritance in configurations
Status: RESOLVED WONTFIX
Alias: None
Product: javame
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 4.x
Hardware: All All
: P2 blocker (vote)
Assignee: Adam Sotona
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-05 12:35 UTC by rubesm
Modified: 2006-10-23 16:41 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
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 rubesm 2005-05-05 12:35:42 UTC 
It would be a great improvement to allow inheritance in configurations. Now
there is only on possible "predecessor" of all other configurations named
"Default configuration". It would be very useful to inherit from any existing
configuration. E.g. configuration "nokia_60" should inherit from "nokia"
configuration. 

And it will be very useful to setup every item whether it inherits its value
from predecessor or not. This means checkbox in every attribute in manifest or
every item in library/resources indicating whether it is inherited from its
predecessor or not.
Comment 1 Martin Ryzl 2005-05-05 22:54:35 UTC 
note that in 4.1 many things can be done using duplication of configurations and
abilities. This RFE is definitely interesting but I'm afraid that UI complexity
might be too high :(.
Comment 2 Adam Sotona 2005-08-18 11:01:31 UTC 
yes, this is too complicated to implement and also the UI would get more complex

-you can now easily use project configuration templates (custom or provided by
each istalled device)
-you can easily setup a new project with several configurations from several
configuration templates