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.
Currently (in Netbeans 3.2 Beta build 13) if you add a JAR file to your filesystem and you want to execute a class in the JAR, passing it some arguments, you cannot use the Build->Set Arguments menu option. This seems to be a pretty basic requirement, as there are many java programs that require arguments to be passed to them. It is especially confusing for new users who see the "Set Arguments" menu option.
Also if you right click on the executable class in the JAR you can bring up the properties sheet, but it does not have the execution tab on it. Therefore it seems that you cannot set the type of executor for a class in a JAR (probably due to the same reason you can't set arguments).
Won't be fix for 3.2.
I would vote to make this a feature request for jarpackager, not for core.
Making a feature request for jarpackager: writable JAR FSs. I don't see any reason why the core should provide this functionality.
Target milestone 3.3
Being able to set arguments for classes in a readonly filesystem is a projects feature, isn't it? The WJFS will solve this for writeable jars.
I agree with the comment from Mike Schilling that for one to be able to set arguments for a class in a read only file system, the argument data needs to be stored seperately from the read only file system (e.g in project information). Why should one have to pollute a third party JAR with netbeans files just so they can execute a class in the JAR, passing arguments.
Won't be fix for 3.3 as a major changes in project's system were deffered to 4.0.
This is solved in new projects system (Nb 4.0), please check out the preliminary version from: http://www.netbeans.org/download/prj40_prototype/
As described in http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss the current work on projects prototype has been stopped. Marking issue as VERIFIED --->
---> CLOSED