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.
[ BUILD # : 200910071658 ] [ JDK VERSION : 1.6.* ] When I open a group of maven projects, two of the projects are marked as "<Badly formed Maven project>". In the "Show Problems" dialog, accessed via "Show and Resolve Problems..." in the projects' context menus, the problem is "Project model validation failed" with description "'dependencies.dependency.version' is missing for ...". In fact the version is specified in the dependencyManagement section of the parent pom. When I reload the projects using their context menus, the projects load correctly - showing that there is nothing wrong with the projects.
is it reliably reproducible? are the projects publicly available? The fact that without any changes the projects load later correctly would signal some kind of threading issue within the embedder (which it is known to contain a bunch)
It seems to not be consistent. I opened the IDE several times (>5) before reporting this defect and it occurred every time. I have now made some changes to code and performed a number of builds; the changes are not pom related. The projects seem to be opening correctly each time now. The projects belong to a client and are not publicly available.
I have one project that started doing the same thing this morning. The same error is displayed, in my case missing version for com.sun.facelets:jsf-facelets (I keep the version number in a property and it's provided scope if it matters). If I reload the project from the project's context menu, it will now show as valid. Wish I could give you a reproducable case...
I've just experienced this (complete with the "Reload Project" menu item fixing it). The project I experienced it with is Apache Camel: svn co https://svn.apache.org/repos/asf/camel/trunk camel Try that to see if it works for a repro - most of the (many) child projects failed for me.
Created attachment 96866 [details] messages.log with InvalidProjectModelException
Had this happen again on an EJB Module. All I did to resolve was a Reload Project from the context menu. See the messages.log I just attached.
Reassigning to default owner.
(In reply to comment #4) > The project I experienced it with is Apache Camel: > svn co https://svn.apache.org/repos/asf/camel/trunk camel > Try that to see if it works for a repro - most of the (many) child projects > failed for me. So I just did a clean checkout of Apache Camel trunk, built it (from command line: mvn -DskipTests), then opened all 127 (!) projects in a 6.10 dev build. Scanning obviously took a while. I did not see any "<Badly formed Maven project>" entries. There were some Java error badges, mostly bug #189134. Also some errors from src/main/resources/archetype-resources/src/main/java/**/*.java (bug #189037). (In reply to comment #6) > Had this happen again on an EJB Module. All I did to resolve was a Reload > Project from the context menu. See the messages.log I just attached. InvalidProjectModelException: Failed to validate POM for project ... at ...\pom.xml Sounds like a malformed POM?