Community
Participate
Working Groups
When a registered epackage contains an eclass with the same name as one of the ETypes epackage, CDO Hibernate throws a duplicated annotation exception and prevents the server to re-start until the colliding epackage is manually deleted from the database.
Moving all open bug reports to 4.1 because the release is very near and it's hghly unlikely that there will be spare time to address 4.0 problems. Please make sure that your patches can be applied against the master branch and that your problem is not already fixed there!!!
Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master.
The solution is to annotated the colliding EClass with an @Entity(name="uniqueName") annotation.
Mass update. Don't worry if this bug is already closed!