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: | Move project fails for Java EE 5 project (not Java EE 6) | ||
---|---|---|---|
Product: | projects | Reporter: | viggonavarsete <viggonavarsete> |
Component: | Maven | Assignee: | Jesse Glick <jglick> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | Keywords: | RANDOM |
Priority: | P2 | ||
Version: | 7.0 | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
viggonavarsete
2011-02-14 09:27:42 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? 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! thanks for update Viggo! Marking with RANDOM keyword. If you agree, I'd make this P2. Sure Tomas, no problem! I find the issue with the profiler to be more urgent than this issue:) 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. |