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: | Setting active configuration from Actions panel has no effect | ||
|---|---|---|---|
| Product: | projects | Reporter: | Jesse Glick <jglick> |
| Component: | Maven | Assignee: | Milos Kleint <mkleint> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | Keywords: | USABILITY |
| Priority: | P3 | ||
| Version: | 7.1 | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
|
Description
Jesse Glick
2011-08-17 18:17:46 UTC
Re:
> A possibly related problem is that selecting a configuration from the Actions
> panel has no effect. Who knows how long that has been broken. The action
> mapping / configuration code is rather complicated and did not originally come
> with any tests whatsoever.
What I have done.
1. in configurations panel create configs A and B
2. in actions panel, use the combo popup to select actions for configuration A
3. Select the Build actions and change the goal from "install" to "package"
4. change the combo value to configuration B
5. Note: the Build action definition has changed to the default value, change it to "deploy".
6. switch back to default configuration, note that build action still has "install", switch to A, build action now has "package".
7. clicking ok performs the save and upon examination, all nbactions files are correct (as entered in UI)
it's a bit unclear to me what the expectation is. Switching the combo in actions panel never changed the active configuration, that's in customizer done in configurations panel and elsewhere using the generic UI..
closing as worksforme, please reopen if you disagree.
(In reply to comment #1) > Switching the combo in actions panel never changed the active configuration OK. Just took me by surprise, since in the closest equivalent in a j2seproject - the Run panel - changing the combo _does_ set the active configuration. Of course that project type does not have a separate panel for configurations, but I guess I expected that picking a configuration in Actions would also activate it. |