David wrote:
Snapshot available:
http://snapshots.repository.codehaus.org/org/codehaus/mojo/hibernate3-maven-plugin/2.2-SNAPSHOT/
0, not using it. Notes:
The POM does not define the <prerequisites> element such that it
defaults to Maven 2.0. However, the plugins has deps to Maven APIs in
version 2.0.4 and at least a transitive dependency on plexus-utils !=
1.1 which would require Maven 2.0.6
mvn dependency:analyze reports several undeclared deps.
The POM defines three profiles: "jdk14", "jdk15" and "jdk16", the latter
ones being equal in content. In case these profiles were meant to
distinguish Java 1.4 and Java 1.5+, an alternative approach for the
profile activations might be
<jdk>1.4</jdk>
and
<jdk>!1.4</jdk>
The negation would theoretically also be triggered on Java 1.3- but
that's outside the practical scope for any Maven build. However, !1.4
would match Java 1.5, 1.6 and also 1.7, without additional XML duplication.
<publishDate> and <version> could be removed from the site.xml in favor
of inheritance from the parent.
The usage.apt says the JDBC driver needs to be added as an extension.
Doesn't it work if users add the driver as a regular plugin dependency?
IIRC, Maven 3.x aims at removing extensions, so the sketched usage might
not work in the future.
Benjamin
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
