Hibernate version: 3.0.4

I need to be able to create indexes on multiple columns in a manner
that is independent of the property declaration in a mapping document,
in order to dictate the order of the columns in the index.

To that end, since Hibernate did not support this directly, I've made
minor modifications to Hibernate to allow me to do this (I ended up
making a modification in the dtd to allow the new <index> element
within a class and allow me to specify the index name and whether
it is unique, and to HbmBinder.java)

My questions (to the Hibernate team) are:

0. How can I check that I have covered the necessary areas to ensure
that I have not inadvertently broken something I am not aware of?

1. How do I get to submit this change to get a team member to have
a look at it; and finally

2. How do I get to get someone from the team to integrate it to the
code base?

Surely someone from the Hibernate team has an opinion?

A scenario I have is: my mapping files use XML includes to include
some base class property information since I use a combination
of table per hierarchy and table per class mappings in addition
to using the <any> construct. Some columns in the included set
of properties may need to be used in indices/constraints,
but not always and not always in the same type of index/constraint,
not to mention that some indices include a particular property in
different ordinal position, but currently this is determined by the order
in which these properties appear in the mapping files.

I'd really appreciate some response that either tells me that this is
already implemented in some manner (which I cannot reveal from the
docs) or that there is a way to incorporate the changes I propose into
a version of Hibernate so I do not have to keep maintaining my patched
version into the future (and which I think is a useful addition).

I am also interested in this work. From what I can tell from the online PDF and the Hibernate in Action book, functionality in this area is somewhat lacking. If there appears to be a straightforward solution to this problem, I'd love to use it.

There is a patch in JIRA about that feature