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 23342 - Define "Execute" project action in the new projects and its API
Summary: Define "Execute" project action in the new projects and its API
Status: CLOSED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Projects UI (show other bugs)
Version: 3.x
Hardware: PC Windows 3.1/NT
: P1 blocker (vote)
Assignee: Torbjorn Norbye
URL:
Keywords: API
Depends on:
Blocks:
 
Reported: 2002-05-10 15:37 UTC by Pavel Buzek
Modified: 2003-12-11 14:25 UTC (History)
0 users

See Also:
Issue Type: TASK
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Buzek 2002-05-10 15:37:47 UTC 
In 3.4 projects it is possible to set the project main class which is a starting point for execution 
and debugging. Something similar should be possible in 4.0. It should not be called "class" in 
non-java projects. There could be different entry points for debugger and executor.
Comment 1 Vitezslav Stejskal 2002-05-31 17:34:53 UTC 
I think we should implement entry-points separately in each project type, there is no need to think about 
generic UI provided by infrastruture. Java-project would have Main class, C++project would have 
Executable, both can provide ExecCookie with proper implementation and the same Execute Project Action 
can be used in UI.
Comment 2 Pavel Buzek 2002-06-03 13:10:12 UTC 
True. Actually some projects do not need to be executable at all. The only reason why I was thinking 
about something general was that some of the UI should look same in Java and C++, e.g. if you do not 
select any executable and try to execute the project the same dialog asking you to select the 
executable could popup in C++ and Java.
Comment 3 Marek Grummich 2002-07-22 12:29:49 UTC 
Set target milestone to TBD
Comment 4 Marek Grummich 2002-07-22 12:33:16 UTC 
Set target milestone to TBD
Comment 5 Pavel Buzek 2002-07-26 13:37:52 UTC 
reassigning to Tor for implementation
Comment 6 Torbjorn Norbye 2002-07-29 22:12:06 UTC 
A couple of questions are not clear to me after reading
the UI spec 
(http://projects.netbeans.org/proposals/executeui/Execute.html)

1. We're using the same UI for debugging as for execution, right?
   In other words, if you set the "Execution Startup" property
   to "Foo.class", this is also the class which will be used
   in the debugger.   That's because debugging is a type of
   execution.

2. The execution property will be added by the projects 
   infastructure, right?  Meaning that execution is as important
   to projects as building - this wasn't the implication of
   some of the opinions regarding execution configurations
   late last week. If not - who adds this property? (Hint:
   it should not be java -- cpp needs the same property.)
Comment 7 Pavel Buzek 2002-07-30 13:20:10 UTC 
Must-have features for milestone3, have impact on APIs (at least potential).
Comment 8 Torbjorn Norbye 2002-08-02 20:08:06 UTC 
I'm working on this, I had forgotten to mark it started.
Comment 9 Pavel Buzek 2002-08-07 11:08:45 UTC 
adding the API keyword
Comment 10 Torbjorn Norbye 2002-08-15 23:19:01 UTC 
Implemented. See issue 26540 for corresponding changes to be
made in the Java module.
Comment 11 Pavel Buzek 2003-07-02 09:59:18 UTC 
done, closing