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.
Java Card classic projects may not contain more than one package, with one caveat - for generated proxy classes (see issue 170644 re this), the project must contain only one package, e.g. a.b - however for generated proxies it may contain an additional a.b.proxy package (normally generated by the packager but optionally user-editable). This means that New Package and New Folder templates should be disabled from Classic style projects. It also means that Paste functionality should be disabled to block users from pasting a into an existing java package. This requires API changes in the Filesystems API, Project API (provide some sort of "BlockedTemplates" API to block certain templates from visibility); yet it also has to allow refactoring to create short-lived new packages before copying files into them in the case of a package rename.
No way to fix for 6.9 w/o support from other modules
This is incorrect. The javacard 2.2.1 sample code for JavaPurse/SampleLibrary/JavaLoyalty is split over multiple packages, with the shareable interface JavaLoyaltyInterface defined in com.sun.javacard.samples.SampleLibrary, and an implementation of that interface in package com.sun.javacard.samples.JavaLoyalty , with class name JavaLoyalty.java All sample code in the Java Card Development Kit 2.2.1 from Oracle must be compilable under NetBeans IDE using Java Card 3.0 classic edition. https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_Developer-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=java_card_kit-2.2.1-oth-JPR@CDS-CDS_Developer Please fix this problem.
Reassigning a bunch of bugs still assigned to me - I haven't worked for Oracle in almost a year.
Uy... I *am* the default assignee for javacard...
changing owner