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.

Bug 227498 - java.io.IOException: No application project found to correspond to Maven[Z:/NetBeans/validation-manager/Client/Client-UI/pom.xml]
Summary: java.io.IOException: No application project found to correspond to Maven[Z:/N...
Status: RESOLVED FIXED
Alias: None
Product: apisupport
Classification: Unclassified
Component: Templates (show other bugs)
Version: 7.3
Hardware: All All
: P3 normal (vote)
Assignee: Martin Kozeny
URL:
Keywords:
: 209774 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-03-14 20:57 UTC by javydreamercsw
Modified: 2014-01-14 10:17 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 183400

Attachments
stacktrace (5.54 KB, text/plain)
2013-03-14 20:57 UTC, javydreamercsw 		Details
stacktrace (5.59 KB, text/plain)
2013-04-21 06:46 UTC, Exceptions Reporter 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description javydreamercsw 2013-03-14 20:57:56 UTC 
Build: NetBeans IDE 7.3 (Build 201302132200)
VM: Java HotSpot(TM) Client VM, 23.7-b01, Java(TM) SE Runtime Environment, 1.7.0_15-b03
OS: Windows 7

User Comments:
javydreamercsw: Tried the Window Position redefine.

Monezz: Create a new Window component in a nested module  (root/suite/module) and press redefine.

Monezz: Create new Window component in a module directly in the project root (ie non nested /root/module) and press redefine.
application module is present in root/application

gbivins: redifine modes




Stacktrace: 
java.io.IOException: No application project found to correspond to Maven[Z:/NetBeans/validation-manager/Client/Client-UI/pom.xml]
   at org.netbeans.modules.maven.apisupport.MavenExecProject.execute(MavenExecProject.java:68)
   at org.netbeans.modules.apisupport.project.ui.wizard.winsys.DesignSupport.invokeDesignMode(DesignSupport.java:151)
   at org.netbeans.modules.apisupport.project.ui.wizard.winsys.DesignSupport.invokeDesignMode(DesignSupport.java:118)
   at org.netbeans.modules.apisupport.project.ui.wizard.winsys.BasicSettingsPanel.redefineActionPerformed(BasicSettingsPanel.java:347)
   at org.netbeans.modules.apisupport.project.ui.wizard.winsys.BasicSettingsPanel.access$700(BasicSettingsPanel.java:73)
   at org.netbeans.modules.apisupport.project.ui.wizard.winsys.BasicSettingsPanel$3.actionPerformed(BasicSettingsPanel.java:326)
Comment 1 javydreamercsw 2013-03-14 20:57:58 UTC 
Created attachment 132626 [details]
stacktrace
Comment 2 Milos Kleint 2013-03-26 12:36:54 UTC 
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
Comment 3 Milos Kleint 2013-03-26 12:37:41 UTC 
I don't see much of a fix, apart from improving the error message (and prevent it showing as reportable exception)
Comment 4 Exceptions Reporter 2013-04-21 06:46:13 UTC 
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
Comment 5 Milos Kleint 2013-05-15 11:44:45 UTC 
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.
Comment 6 Martin Kozeny 2013-05-16 08:09:20 UTC 
https://hg.netbeans.org/core-main/rev/6e50d7c9761f
Comment 7 Martin Kozeny 2013-05-16 09:19:44 UTC 
https://hg.netbeans.org/core-main/rev/226a81a7aa93
Comment 8 Quality Engineering 2013-05-17 09:51:43 UTC 
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
Comment 9 Martin Kozeny 2014-01-14 10:17:32 UTC 
*** Bug 209774 has been marked as a duplicate of this bug. ***