Hibernate version:

2.1.6
2.1.2 extensions

Mapping documents:

1) file:

<hibernate-mapping package="test">
<class name="ClassA" table="CLASS_A" lazy="true">

<id name="id" type="long" column="CLASS_A_ID" >
<generator class="native"/>
</id>

<many-to-one name="myClassB" class="ClassB"/>

</class>
</hibernate-mapping>

2) file:

<hibernate-mapping package="test">
<class name="ClassB" table="CLASS_B" lazy="true">

<id name="id" type="long" column="CLASS_B_ID">
<generator class="native"/>
</id>

</class>
</hibernate-mapping>



After running hbm2java (as ant task) on the given mapping files the ClassA.java file contains an import statement for ClassB without the proper package name "test."

Since both classes are members of package "test" as defined in the mappings, there should be no import statement OR a correct import statement containing the fully qualified name "test.ClassB"

Generated file for ClassA:

package test;

import ClassB; <-- BAD !!!
import java.io.Serializable;
import org.apache.commons.lang.builder.ToStringBuilder;


/** @author Hibernate CodeGenerator */
public class ClassA implements Serializable {

...

}


Where is my mistake or is this a bug in the CodeGenerator?

TIA

The package="xxx" construct is fairly new, so the released hbm2java doesn't support it yet. Please use the cvs version or use fully qualiifed names in the class name.