mx4j inherits java-pkg-opt-2 when there is nothing optional about java support

I am just in the process of migrating/setting up the javamail virtual
and came across dev-java/mx4j and discovered that it inherits
java-pkg-opt-2 eclass instead of java-pkg-2.

Is/Was there a explicit reason for doing this, currently it DEPENDS on
>=virtual/jdk-1.4, calls java-pkg_jar-from ~10 packages and has a nice
little pkg_postinst of

pkg_postinst() {
	elog "Although this package can be used directly with java-config,"
	elog "ebuild developers should use mx4j-core and mx4j-tools directly."
}

Please raise your voices to stop me changing the inherit to java-pkg-2
-- 
[email protected] mailing list