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: | Disable "Finish" button if additional properties UI is not yet shown | ||
---|---|---|---|
Product: | projects | Reporter: | Denis Anisimov <ads> |
Component: | Maven | Assignee: | Tomas Stupka <tstupka> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 7.4 | ||
Hardware: | PC | ||
OS: | Windows 7 | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Denis Anisimov
2014-02-10 12:47:45 UTC
I agree this is suboptimal, but do we want to really stop people finish the wizard until we manage to download and parse the archetype descriptor? Most archetypes don't have any additional props and if they do, they mostly have (IMHO should have) default values. The maven failure output is somewhat descriptive (see my comment in issue 241637) Next time around when user selects the archetype, the panel will load the props immediately. So I'm not entirely sure that for the good of few we should make the experience worse for everyone. (by waiting for the archetype to download) (In reply to Milos Kleint from comment #1) > I agree this is suboptimal, but do we want to really stop people finish the > wizard until we manage to download and parse the archetype descriptor? > > Most archetypes don't have any additional props and if they do, they mostly > have (IMHO should have) default values. > The maven failure output is somewhat descriptive (see my comment in issue > 241637) > Next time around when user selects the archetype, the panel will load the > props immediately. > > So I'm not entirely sure that for the good of few we should make the > experience worse for everyone. (by waiting for the archetype to download) Well, yes. That's also true. But as I've commented in the issue #241637: unexperienced user is not able to understand the reason of the failure. But I'm not sure about the best approach here.... This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss |