What steps will reproduce the problem?
1. run MetaModelProcessor from maven
2. run MetaModelProcessor from eclipse
3. compare results
What is the expected output? What do you see instead?
expected is same result from both :)
* it is not only the problem of order of fields, but different result is
generated
* to prevent cycles, processed field names are stored in hierarchyTypes, but
different classes which reference each other can have different properties with
same names and also one class can have more fields of same type
* first processed class is not added to hierarchyTypes
Original issue reported on code.google.com by psenicka...@gmail.com on 28 Sep 2011 at 1:06
Original issue reported on code.google.com by
psenicka...@gmail.com
on 28 Sep 2011 at 1:06