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 76669 - Support for somekind of device limitation database
Summary: Support for somekind of device limitation database
Status: NEW
Alias: None
Product: javame
Classification: Unclassified
Component: Fragmentation (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Karol Harezlak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-22 10:53 UTC by ieising
Modified: 2009-10-01 13:24 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ieising 2006-05-22 10:53:52 UTC
Hi,

It would be nice to have somekind of updatable database containing device
limitations. For example the Nokia 6230 supports JAR-files up to 115Kb, this
would be in the device database. Now if I set an ability in a configuration
"DEVICE=Nokia 6230" and the JAR file would exceed the 115Kb, the build would
fail. Preferably this database would have an export and import or something so
you can update it through the update-center or something like it.

Iwan
Comment 1 ieising 2006-05-22 13:38:01 UTC
This is a new feature, sorry about the confusion.

Iwan
Comment 2 Lukas Hasik 2006-06-23 15:28:15 UTC
moving to mobility component
Comment 3 Lukas Hasik 2007-01-09 14:12:49 UTC
reassigning
Comment 4 Adam Sotona 2007-04-10 15:15:58 UTC
Implemented a new SPI to easily plug any device database (J2MEPolish, WURFL, SND
Device List, etc...)

Implementation of NetBeans-provided device database is postponed.
Comment 5 Lukas Hasik 2007-06-06 10:49:46 UTC
the general policy for issuezilla is "do not use the LATER/REMIND" resolution.
(http://qa.netbeans.org/bugzilla/issue-lifecycle.html).
These states are confusing and should be removed from issuezilla (unfortunately
colabnet doesn't know how to do it). Bug shouldn't be in RESOLVED state until it
is really resolved. IMO, that's not the case of LATER/REMIND.

Please, reevaluate the issue
1, When you don't plan to fix the issue close it as WONTFIX
2, you don't want to fix it now -> use TM=future

thank you for understanding
Comment 6 Jiri Prox 2007-09-17 20:52:11 UTC
Obsolete milestone, please reevaluate