[
https://jira.jboss.org/jira/browse/JBIDE-2555?page=com.atlassian.jira.plu...
]
Julien Kronegg commented on JBIDE-2555:
---------------------------------------
I got this issue under Seam 2.0.0.GA, but could not determine a reproducible cause. The
components were stored once in a JAR file, then later removed.
I solved it by:
1. exiting Eclipse
2. replacing all instances of the incrimined JAR file by a freshed version
3. launching "eclipse -clean"
4. cleaning all projects
Step 3 was required (simply exiting Eclipse was not enough)
Moving Seam component yields persistent, incorrect validation error
-------------------------------------------------------------------
Key: JBIDE-2555
URL:
https://jira.jboss.org/jira/browse/JBIDE-2555
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 2.1.0.CR1
Environment: JBoss Developer Studio 1.1.0.CR1
Seam 2.0.2.SP1
Ubuntu Feisty
Reporter: Tim Otten
Assignee: Alexey Kazakov
Fix For: 3.0.0.alpha
When moving a Seam component from one Java package to another Java package, the Seam
validator erroneously reports the error "Duplicate component name." Cleaning the
project does not remove the error. Eclipse must be restarted.
Steps to reproduce:
1. Create a new EAR-based project
2. Generate an entity, entityhome, etc.
3. Move one of the Seam components to a new Java package, e.g.
3.a. In the "Package Explorer" tab, locate the entity's home component.
3.b. Right-click -> Refactor -> Move
3.c. Designate a new package
3.d. Click "OK"
4. Clean/Rebuild project
4.a. In the Eclipse menu bar, choose Project -> Clean
4.b. Choose any/all applicable projects
4.c. Enable "Start a build immediately"
4.d. Click "OK"
5. In the "Problems" tab, an error appears twice: "Duplicate component
name"
After repeated attempts to clean/build the project(s), the error message persists.
The error can be removed by:
6. Close Eclipse
7. Open Eclipse
8. Clean/Rebuild project
At this point, the error message goes away. The project will now build and deploy, and
the refactored component functions appropriately.
(Note: I'm using the current stable release of JBoss Developer Studio 1.1.0.CR1 with
JBoss Tools 2.1.0.CR1. I've checked the list of open tickets and the release notes for
JBoss Tools 2.1.1 and 2.1.2 -- I couldn't identify any related issues.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira