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 46721 - Option for a j2seproject to produce no JAR
Summary: Option for a j2seproject to produce no JAR
Alias: None
Product: java
Classification: Unclassified
Component: Project (show other bugs)
Version: 4.x
Hardware: All All
: P2 blocker (vote)
Assignee: Tomas Zezula
: 46493 50113 (view as bug list)
Depends on: 104508
Blocks: 41537
  Show dependency tree
Reported: 2004-07-28 22:50 UTC by Jesse Glick
Modified: 2007-10-04 20:57 UTC (History)
3 users (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2004-07-28 22:50:34 UTC
Off by default. If requested, remove that target
from the build script, disable the JAR creation
panel. Would export build/classes/ as an Ant
artifact for superprojects instead. Helpful for
users who wish to avoid the (modest) overhead of
JAR creation in case some superproject does not
require it anyway (e.g. in case of specialized
ad-hoc packaging, or rare packaging).
Comment 1 Jesse Glick 2004-08-04 03:11:53 UTC
*** Issue 46493 has been marked as a duplicate of this issue. ***
Comment 2 Jesse Glick 2004-10-07 18:54:18 UTC
*** Issue 50113 has been marked as a duplicate of this issue. ***
Comment 3 mclaassen 2004-12-10 14:02:29 UTC
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.
Comment 4 Jesse Glick 2004-12-10 21:32:33 UTC
[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).
Comment 5 tboerkel 2005-08-29 07:23:46 UTC
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.
Comment 6 Jesse Glick 2005-08-29 18:26:58 UTC
Not planned for 4.2, sorry.
Comment 7 tboerkel 2005-10-05 17:13:04 UTC
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.
Comment 8 Jesse Glick 2007-10-04 20:57:28 UTC
Fixed as part of issue #104508.