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: | java.io.IOException: No application project found to correspond to Maven[Z:/NetBeans/validation-manager/Client/Client-UI/pom.xml] | ||
---|---|---|---|
Product: | apisupport | Reporter: | javydreamercsw <javydreamercsw> |
Component: | Templates | Assignee: | Martin Kozeny <mkozeny> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gbivins, mienamoo, monezz |
Priority: | P3 | ||
Version: | 7.3 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 183400 |
Attachments: |
stacktrace
stacktrace |
Description
javydreamercsw
2013-03-14 20:57:56 UTC
Created attachment 132626 [details]
stacktrace
the general way of finding Application project for the Module project is vague in Maven (unlike the ant projects that always have a hard reference to it). The current algorithm to find the project is as follows: 1. get coordinates (GAV) of the Module project 2. Among the opened projects, find the Application projects 3. In these, find the dependencies with the correct GAV -> if match found, declare victory.. So the failure can appear at multiple levels a. project is unloadable and gav will be wrong b. the right application project is not opened. c. the app project's dependencies are not fully loaded and some transitive ones are missing I don't see much of a fix, apart from improving the error message (and prevent it showing as reportable exception) Created attachment 133630 [details]
stacktrace
On creating a new Window developing a MAVEN CRUD Netbeans APP example.
Trying to set explorer instead of editor position
http://hg.netbeans.org/core-main/rev/183dc41d3eaf changes the message the exception. In the long term similar approach that the ReactorChecker.findReactor() method has taken could be used. Eg. first find the reactor root and then attempt to find the application project in it's modules. There is however a severe performance hit here, given that up to all projects in the reactor tree would be loaded to find the right one. reassigning to general apisupport to make sure the error doesn't show as problem to be reported back at netbeans, but rather an error message that user should act on. Integrated into 'main-golden', will be available in build *201305170640* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/183dc41d3eaf User: Milos Kleint <mkleint@netbeans.org> Log: #227498 improve error message *** Bug 209774 has been marked as a duplicate of this bug. *** |