[JBoss JIRA] Created: (JBIDE-6356) Hibernate mapping file editor sometime shows old content
by Jiri Peterka (JIRA)
Hibernate mapping file editor sometime shows old content
--------------------------------------------------------
Key: JBIDE-6356
URL: https://jira.jboss.org/browse/JBIDE-6356
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.1
Reporter: Jiri Peterka
Fix For: 3.2.next
Sometimes old hbm.xml file is shown in Hibernate editor after class modification and hbm.xml regenerating (even after close all, and refresh).
I don't know if it's Eclipse problem or some Hibernate Tools problem but I've noticed that several times. After restart content is ok. It's question of editor content refresh, hbm.xml generation is ok and file system has proper file content.
Steps:
1. Create some POJOs
2. Create hbml.xml mapping file
3. Open hbm.xml
4. Update created POJOs
5. Delete hbml.mxl files
6. Generate hbm.xml again
7. Open generated hbm.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBIDE-6343) Create a "sanity check plugin/feature" tool for running on integration builds
by Max Rydahl Andersen (JIRA)
Create a "sanity check plugin/feature" tool for running on integration builds
-----------------------------------------------------------------------------
Key: JBIDE-6343
URL: https://jira.jboss.org/browse/JBIDE-6343
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Max Rydahl Andersen
Fix For: LATER
I keep seeing the following antipatterns or oversights happening in our codebase, most of them I believe we could mechanically check for.
No duplicate names in .project since it makes it impossible to import into Eclipse
bin folders should be svn:ignored and not be committed (causes problems when doing svn synchronization and all the .class files are showing up and some even commits it)
things in svn:ignore should be committed (either someone overrode svn:ignore or the svn:ignore were added later)
if pom.xml file exists target should be svn:ignored too.
Execution environment should be specified in manifest.mf's
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months