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: | Changes at configuiration properties directly at nb-configuration.xml file are not propagated automatically | ||
---|---|---|---|
Product: | projects | Reporter: | Michel Graciano <hmichel> |
Component: | Maven | Assignee: | Milos Kleint <mkleint> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 8.0 | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | sample project |
Description
Michel Graciano
2014-02-03 13:28:00 UTC
reloading a project after nb-configuration.xml file (or pom.xml) change is an async operation. Does waiting help? Does a manual "Reload POM" popup action execution fix the problem? does rerun mean clicking the action in output toolbar or right click on project in Project's view (or main menu action) Created attachment 144734 [details]
sample project
I've tried to create a sample project where pom.xml's <name> element contains ${foo} which in turn is defined in a nb-configuration.xml. When I activate the configuration, I see the expression being evaluated to "bar", when I change that manually in the nb-configuration.xml file, it changes in the view as well. (macosx + jdk 1.7 + latest dev sources)
BTW Do you see your property at the beginning of the build output?
http://hg.netbeans.org/core-main/rev/152f2b48e55f we've reset the list of configurations, but still used the old instance for active configuration Integrated into 'main-silver', will be available in build *201402070001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/152f2b48e55f User: Milos Kleint <mkleint@netbeans.org> Log: #241337 when configurations get reloaded, we forgot that the active instance was not reset as well, thus holding still the old values. |