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 163648 - No java editor features enabled because unsufficient dependencies of JavaCard module
Summary: No java editor features enabled because unsufficient dependencies of JavaCard...
Status: RESOLVED FIXED
Alias: None
Product: javame
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: _ tboudreau
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-25 01:16 UTC by _ tboudreau
Modified: 2009-07-15 23:14 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Java card module (496.24 KB, application/octet-stream)
2009-04-25 01:17 UTC, _ tboudreau
Details
Validation module (52.84 KB, application/octet-stream)
2009-04-25 01:18 UTC, _ tboudreau
Details

Note You need to log in before you can comment on or make changes to this bug.
Description _ tboudreau 2009-04-25 01:16:45 UTC
1.  Start NB with ergonomics cluster enabled on a clean userdir.
2.  Install the attached NBMs.
3.  (SWAN only - sorry) Download a Java Card 3.0 SDK build from
http://cmsgweb.sfbay/re/builds/javacard/3.0.1/promoted/latest/bundles/ - get one that has "connected" in the JAR file
name (there are builds with and without sources, javadoc, encryption code - any will work if the name contains
"connected" - you don't want "classic", thats Java Card 2.0). 
4.  Set up a Java Card platform in Tools > Java Platforms (if it doesn't work, open $SDK/platform.properties and add
javacard.name=Java Card(tm) Platform
javacard.vendor=Sun Microsystems
to it - I don't know if they've fixed this in the SDK builds yet). 
5.  Create a new Java Card > Classic Applet project

PROBLEM 1:  When the Applet java class template opens in the editor, right click.  The only actions available Run File,
Cut, Copy, Paste, Select In - i.e. this is simple editor support + java syntax highlighting.  No code folding or
refactoring actions available in the editor or elsewhere.

PROBLEM 2:  Shut down and restart the IDE.  Still no real java editor support.  Go to New Project.  The "Java" category
is completely missing (most times but not always).

Problem 1 happens every time, and is bad;  I am guessing Problem 2 is some kind of load order issue or something.
Comment 1 _ tboudreau 2009-04-25 01:17:40 UTC
Created attachment 80896 [details]
Java card module
Comment 2 _ tboudreau 2009-04-25 01:18:16 UTC
Created attachment 80897 [details]
Validation module
Comment 3 Max Sauer 2009-04-27 09:22:29 UTC
Just to be sure -- does this work properly when you first open/create a j2se project before creating Java Card > Classic Applet project? Thanks.
Comment 4 _ tboudreau 2009-04-27 12:47:06 UTC
Yes, if you have created a J2SE project first, it works properly.
Comment 5 _ tboudreau 2009-04-27 12:48:56 UTC
Actually, that might also be relevant to issue 163649.  I discovered that issue because I had created a Java Card
project, restarted the IDE and all of the Java SE project templates were gone, so I tried creating a Web project to
enable Java support.
Comment 6 Max Sauer 2009-04-27 16:09:59 UTC
I think this is an ergonomics problem. It seems that java card support is dependent on just some java modules, which become activated along with java 
card modules. The rest rest of java modules however stay deactivated. I'm not sure how this can be solved, Jardo could you please shed some light on this 
problem? Thanks.
Comment 7 Jaroslav Tulach 2009-04-27 16:55:45 UTC
As far as I can tell, this is not bug visible to end users of 6.7 IDE. To reproduce it we need to install Tim's 
development modules which seem to really be in "development" state as far as I can tell. Tim where is your "kit" 
module? If you wanted to create real product, you would have a set of autoupdate-invisible modules and one "kit" 
depending on all of them. Such "kit" shall also have dependency on java.kit and other functionality that you really 
require.

Without such setup, it is unfair to report P1, P2 or even P3 bugs and pretend they represent a problem to be fixed in 
6.7.

In case your personal development is blocked, consider building "ant -Dcluster.config=basic" where you get a 
development environment suitable for testing individual modules without umbrella "kit". I'd be thankful if you could 
downprioritize or even close your bugs reproducible only with your development bits without proper "kit" module and 
appropriate dependencies. Thanks.
Comment 8 _ tboudreau 2009-04-27 17:24:00 UTC
> As far as I can tell, this is not bug visible to end users of 6.7 IDE. To reproduce it we need to install Tim's 
> development modules which seem to really be in "development" state as far as I can tell

The plan was to ship them with 6.7;  since moving the source code into hg is tied up in legal and there is not yet a
release of the Java Card SDK for users to use it with, and I am still waiting for build script templates from the JCDK
team which will work with their new Ant tasks, it may be that we won't ship *with* 6.7 - but we will soon after.

At that time, this will become a P1 bug in something we have already shipped, and will be a much bigger problem.  Java
Card support needs to work with 6.7.

More importantly, what *other* modules that we don't know about are out there which will cause similar problems, either
in the Java modules or elsewhere?  We will have enough problems like this once hundreds of thousands of developers are
using an ergonomic NetBeans daily.  We should fix the ones we know about already.
Comment 9 _ tboudreau 2009-04-27 18:52:04 UTC
There's not much point to a "kit" module until I can actually build the modules as part of the NetBeans source base.  If
you want me to send you an empty module, though, I can make one in about two minutes :-)

Same question, though:  How many other modules - on the update center, on the plugin portal, or available somewhere else
- will cause these same kinds of partial enablement problems, or make assumptions, right or wrong, about things that
won't necessarily be there?  It has taken us months to get everything working right with only the known set of modules
which we ship - and it is clear that it is not enough as soon as you begin introducing foreign modules.  How much of the
stuff out there has been tested with 6.7?  Any?
Comment 10 Petr Suchomel 2009-04-28 07:10:07 UTC
Jardo, I would not call it "really be in "development" state" as now. As far as intend is to finish ASAP - the legal got
stuck but hopefully get resolved, it still is intended to release soon as stable - due to delay probably not a part this
distribution, but as a stable.
If I understand correctly, this is pretty serious problem, when only part of modules, under one kit, got enabled? I am
right?
Comment 11 Marian Mirilovic 2009-04-28 08:33:07 UTC
> How much of the stuff out there has been tested with 6.7?  Any?
none ... and honestly it won't be
Comment 12 Jaroslav Tulach 2009-04-28 12:16:56 UTC
Tim, you have to provide kit module if you want your modules to be part of NetBeans distribution. If you don't have 
the kit module yet, you are in development mode (from my point of view). Your kit module needs to depend on java.kit 
(at least). If you can still reproduce your problem, when you do this, please come back. Meanwhile I want to reassign 
the bug to you (mobility/javacard?).
Comment 13 Jaroslav Tulach 2009-04-30 10:55:54 UTC
I have reported issue 164176 to capture PROBLEM 2.
Comment 14 _ tboudreau 2009-05-04 15:43:58 UTC
What is NO67?
Comment 15 _ tboudreau 2009-07-15 23:14:16 UTC
Kit module is there, and this is working now.