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.
Summary: | Option for a j2seproject to produce no JAR | ||
---|---|---|---|
Product: | java | Reporter: | Jesse Glick <jglick> |
Component: | Project | Assignee: | Tomas Zezula <tzezula> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | jrojcek, mclaassen, tboerkel |
Priority: | P2 | ||
Version: | 4.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | 104508 | ||
Bug Blocks: | 41537 |
Description
Jesse Glick
2004-07-28 22:50:34 UTC
*** Issue 46493 has been marked as a duplicate of this issue. *** *** Issue 50113 has been marked as a duplicate of this issue. *** The 'jar'ing step it not always just modest overhead. We use webstart for deployment and so do careful creation of the jar files. And, in any case, when doing incremental build of a just a few files the jar step would be a significant part percentage of the process. I like the idea of a toggle to create / not create the jar in the UI. This would be helpful for non-power users. For power (or half-power) users, I think it would be nice to able to choose the target that the "Build main project" does. I would like that to just to the compile the project, and not the jar. But I would like to keep the jar target intact so I can do that when I need to as well. I think this is the real solution to the problem. [Add yourself to CC when adding comments or you will never see replies.] It's not just about changing the default target run when you do Build - also affects whether dependent projects should build against your classes dir or JAR. Probably these things should be linked (with, I agree, always an option to produce a JAR if you really want). What about this issue in NB 4.2? It's really annoying for each and every new project to disable JAR creation by editing build.xml. "Just edit build.xml" cannot always be the answer for missing GUI options. These things are driving NB users away and to Eclipse. Not planned for 4.2, sorry. This is the kind of stuff that drives NB users away and to Eclipse. Creating a simple project (simple = without .jar creation) from existing sources should be as easy as possible. Making the user fiddling with build.xml is not an option. Fixed as part of issue #104508. |