Bug 528955 - [9] UI for defining the main class of a modular project
Summary: [9] UI for defining the main class of a modular project
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.7.1a   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-19 09:05 EST by Stephan Herrmann CLA
Modified: 2023-03-31 08:42 EDT (History)
0 users

See Also:

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 Stephan Herrmann CLA 2017-12-19 09:05:29 EST 
Since bug 516377 we have the option to respect IClasspathAttribute.MODULE_MAIN_CLASS while creating module-info.class.

We should provide UI for this as a project property, perhaps as a new entry on Java Build Path > Source, but I'm open to other locations.

If the classpath attribute is set, then exporting a runnable jar (bug 518445) wouldn't have to worry about a main class, but still has the option to override the (default) main class - if different entry points exist in the same module.
Comment 1 Eclipse Genie CLA 2021-04-01 00:25:04 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2023-03-31 08:42:21 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.