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:||Action on j2seproject to make everything sharable and ready for command-line usage|
|Product:||java||Reporter:||Jesse Glick <jglick>|
|Component:||Project||Assignee:||Milos Kleint <mkleint>|
|Severity:||blocker||CC:||dkonecny, mkrauskopf, pjiricka|
|Issue Type:||ENHANCEMENT||Exception Reporter:|
|Bug Depends on:||44035|
|Bug Blocks:||41537, 56684, 89629|
Description Jesse Glick 2004-09-28 16:38:10 UTC
Currently some kinds of GUI configuration will result in a j2seproject configuration that requires $userdir/build.properties to be referred to, or the user to manually set up these properties. Should be a GUI wizard that looks for any unshared properties or file references in the project that would prevent out-of-the-box building from working, and tries to correct them. Should e.g. offer to move required libraries inside the project dir (or to some collocated position) and refer to them with relative paths.
Comment 1 Jesse Glick 2004-12-02 16:00:50 UTC
See e.g. issue #45284. One problem: no current way to override paths in build.properties without either overriding some targets in build.xml (undesirable), or using private.properties (not acceptable for a sharable project). Would need an additional sharable properties file loaded before build.properties, perhaps.
Comment 2 Petr Jiricka 2005-08-24 23:13:47 UTC
I would like to have something more than this action. I'd like to have a way of saying "make everything sharable, and from now on, make sure that everything I do is sharable". So when I for example use a global library bundled with the IDE, the IDE will detect that this is a non-sharable library and offer me to make it shareable, by, say, copying the library jar files to some sharable "lib" directory, and then using this sharable copy. Or, when I try to create a new project in a non-sharable location, it will warn me about it. Or, when I want to use a jar file in from a non-sharable location, it will warn me about it. Also, sharability should be a more coarse-grained concept than project, because users usually work at the level of collections of projects, and want to make these collections sharable - a single project is too granular for that.
Comment 3 Jesse Glick 2005-08-25 01:40:51 UTC
I would say that making the option global per userdir is too broad, but at least the IDE should remember that within some context (e.g. CVS checkout) all projects must be 100% sharable, and that it should offer to resolve any unsharable references immediately if they come up within this root.
Comment 4 Petr Jiricka 2005-08-25 09:59:12 UTC
Agreed, this is a reasonable approach. So if I understand correctly, there would be multiple sharable contexts active at the same time, and the user could still create and work with projects outside the sharable contexts.
Comment 5 Jesse Glick 2005-08-25 17:56:39 UTC
Right. Something like that. Would need some thought about how to make the UI work well - preferably should happen with very little user intervention.
Comment 6 Jesse Glick 2005-09-09 18:25:17 UTC
*** Issue 63971 has been marked as a duplicate of this issue. ***
Comment 7 Jesse Glick 2006-02-08 18:47:39 UTC
*** Issue 71279 has been marked as a duplicate of this issue. ***
Comment 8 Jesse Glick 2007-04-11 21:58:53 UTC
Comment 9 Jesse Glick 2007-06-07 17:09:08 UTC
Not in 6.0.
Comment 10 Jesse Glick 2008-02-25 17:48:48 UTC
Would you say this is now implemented for 6.1M2?
Comment 11 Milos Kleint 2008-02-26 05:00:21 UTC