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 24652 - Disable possibility to instantiate templates in Output folder
Summary: Disable possibility to instantiate templates in Output folder
Status: CLOSED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-06-11 16:06 UTC by Jan Becicka
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Becicka 2002-06-11 16:06:25 UTC
Projects Prototype's contiuous build [20020611-1518]

User can create class in e.g. Sample Project |
Output | Compiled Classes | out folder. It should
be disabled IMO.
Comment 1 David Konecny 2002-10-03 09:51:49 UTC
The "out" folder below the Compiled Classes is regular folder with all
actions which regular folder can have. Before I will evaluate whether
it is possible to restrict it or not (probably by a look, but might be
difficult, because Compiled Classes is provided by a module and not by
infrastructure) I would like to hear opinion of UI. Assigning to Dirk.
Do you agree with it or not Dirk? (not an urgent problem)
Comment 2 Milan Kubec 2002-10-03 10:35:37 UTC
Allowing user to create objects in out (or whatever output) folder can
be quite confusing even more if user let the classes to be compiled
into the same folder where are sources. It also mixes Sources and
Output nodes usage.

But on the other side user could want to have in output folder
something which cannot be created by regular build. 

Let HIE decide :-)
Comment 3 Vitezslav Stejskal 2002-12-01 16:18:37 UTC
I think Svata is working on something similar.
Comment 4 Dirk Ruiz 2002-12-02 19:10:04 UTC
In general, the workflow should be that the user creates
a build target (usually, one script or recipe or 
makefile or whatever) and then that build target is
responsible for creating things in the output folder.
I agree with David that being able to create things in
there is potentially quite confusing.  In addition, it
may be the case that the user might create something
important in the output folder, and then lose it when
she does a clean or rebuild.  Not good!  The only way
to prevent such data loss would be to tag things that
the user has created, and to treat them differently from
things that were generated by the build target.  That
sounds like a pretty unpleasant way to go....

I think it would be desirable to restrict what can and
cannot be created in these folders.  Hopefully it won't
be too difficult. ;-)
Comment 5 Tomas Zezula 2003-01-14 15:15:51 UTC
Fixed.
The NewTemplate action has been removed as well as Rename action on
folder which is also very dangerous.
Comment 6 Jan Becicka 2003-02-18 14:00:21 UTC
VERIFIED
Comment 7 Jan Becicka 2003-11-25 14:24:22 UTC
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 CLOSED.