1. create a new maven project
2. open project properties dialog
3. in the general tab try to change any value
=> the pom.xml is not affected, only way how to change project properties is to modify pom.xml manually it's P3 issue
Marking as P2 due to consistency. User is being learned in whole IDE he cannot modify configuration files manually -> for almost every functionality he has
some kind of editor or designer
Btw, this bug had to be here for more than a year, it seems that nearly nobody is using customizer for changing Maven
Integrated into 'main-golden', will be available in build *200910280201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Dafe Simonek <firstname.lastname@example.org>
Log: #175081: corrected parameter for markAsModified(...) call, added assertion to check param type
I'm experiencing some problems with pom.xml not updating in build 200911220201, both in the Project Properties and when adding / removing dependencies. The projects are J6EE webapps, but I can't replicate with a new project. Are there any logging options I can turn on?
jpleed3, it's another bug. This bug was about solely about project properties and they were never propagated to the pom.
What you describe is random bug that we're experiencing for a long time, but as we have no reproducible steps to make the error happen, we were not able to fix it.
Please, if you have reproducible steps and/or project on which it happens regularly and that you can share with us, file new bug and attach mentioned project there, thanks.