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 195444 - Move project fails for Java EE 5 project (not Java EE 6)
Summary: Move project fails for Java EE 5 project (not Java EE 6)
Status: RESOLVED WORKSFORME
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 7.0
Hardware: PC Linux
: P2 normal (vote)
Assignee: Jesse Glick
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2011-02-14 09:27 UTC by viggonavarsete
Modified: 2011-02-14 20:37 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description viggonavarsete 2011-02-14 09:27:42 UTC
* Problems
- Unable to properly load project:

1 problem was encountered while building the effective model

[FATAL] Non-readable POM /home/viggo/NetBeansProjects/tmp/QuickstartPrj_JavaEE5/pom.xml: input contained no data @ 

 for project  at /home/viggo/NetBeansProjects/tmp/QuickstartPrj_JavaEE5/pom.xml

- Broken nb-configuration.xml file:

The $project_basedir/nb-configuration.xml file cannot be parsed. The information contained in the file will be ignored until fixed. This affects several features in the IDE that will not work properly as a result.
 The parsing exception follows:

Premature end of file.

See http://wiki.netbeans.org/STS_70_Maven#Test_suite:_Project_operations, "Move project", for details how to reproduce.
Comment 1 Tomas Danek 2011-02-14 11:16:29 UTC
When i try these scenarios from scratch, it depends on version of EE which i select:

1) Java EE5
- create new Maven Webapp project (javaEE5)
- move it
-> everything is fine, project is moved ok

2) Java EE6 
- create new Maven Webapp project (javaEE6)
- move it
-> project is moved, but RANDOMLY gets misconfigured in some cases:
1 problem was encountered while building the effective model
[FATAL] Non-readable POM /tmp/m/mavenproject3/pom.xml: input contained no data @ 
 for project  at /tmp/m/mavenproject3/pom.xml

but it gets easily fixed by invoking revalidate action.
Can you conform this behavior?
Comment 2 viggonavarsete 2011-02-14 11:33:15 UTC
I've tried to create 3 Java EE 5 and 3 Java EE 6 projects now, but none of them failed when I moved them. I have to conclude, as Tomas did, that this must happen only randomly!
Comment 3 Tomas Danek 2011-02-14 12:46:32 UTC
thanks for update Viggo! Marking with RANDOM keyword.
If you agree, I'd make this P2.
Comment 4 viggonavarsete 2011-02-14 12:53:30 UTC
Sure Tomas, no problem! I find the issue with the profiler to be more urgent than this issue:)
Comment 5 Jesse Glick 2011-02-14 20:37:15 UTC
Working for me reliably. Can't really guess what is going on in your case.

BTW core-main #ad1957b48169 should improve reliability of Rename Project when Rename Folder is checked, but this is discussing Move Project which goes through a different code path due to the different dialog prompting for input.