Bug 131525 - [javadoc wizard] can't be finished if no valid Ant script is configured
Summary: [javadoc wizard] can't be finished if no valid Ant script is configured
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-13 10:10 EST by chris CLA
Modified: 2022-09-06 04:03 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 chris CLA 2006-03-13 10:10:44 EST 
Create new java project. Create some class. Choose Project/Generate Javadoc..., click next and next. Select "Save the settings of this..." and clear the "Ant script:" field. A warning "Not a valid Ant file name." will be shown at the top of the wizard, and the "Finish" button will be grayed out. Unselect "Save the settings of this...". The warning will still be shown, and and it's still not possible to finish the wizard, which probably isn't the supposed behavior (at least finishing the wizard should be possible imho).

Eclipse version: Callisto M5
Comment 1 Eclipse Genie CLA 2020-09-12 20:19:10 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 2022-09-06 04:03:33 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.