Hi,
> As the Maven version already exists as a property set by Maven Core
starting in 3.0.4 (or possibly 3.0.3) I don't think we should have that
from a plugin as well.
Yes but it's only available for Maven 3.0.X (whatever) but the
build-metadata-plugin is IMHO also interesting for builds which will be
made with Maven 2.2.1 ....
Apart from that the idea of the build-metadata-plugin is to provide also
things like the called goals, the active profiles as well, cause such
things influence the build. So it's not only the maven-version.
Will only cause confusion as it will be a
different property. I also think that very useful things that are used
by Maven (timestamp?), we should move towards having Maven Core provide
instead.
But this will work only for the future not for the current state...This
kind of function can be currently be provided and later marked as
deprecated and removed from the
plugin....after retiring Maven 2.2.1 til 3.0.3... ;-)
From my understanding, build-metameta is designed to host mojos
that should only provide some kind of informations during the build.
That was exactly the idea i had mind....
So my thinking of the dedicated list of goals for the
build-helper-maven-plugin (current state of the plugin):
Goals:
add-source Add more source directories to the POM.
add-test-source Add test source directories to the POM.
add-resource Add more resource directories to the POM.
add-test-resource Add test resource directories to the POM.
attach-artifact Attach additional artifacts to be
installed and deployed.
reserve-network-port Reserve a list of random and unused
network ports.
local-ip Retrieve current host IP address.
regex-property Sets a property by applying a regex
replacement rule to a supplied value.
timestamp-property Sets a property based on the current
date and time.
released-version Resolve the latest released version
of this project.
parse-version Set properties containing the parsed
components of a version string.
Whereas the list of for the build-metadata-maven-plugin:
goals (duplicated from the build-helper-maven-plugin):
released-version Resolve the latest released
version of this project.
parse-version Set properties containing the parsed
components of a version string.
timestamp-property Sets a property based on the current
date and time.
goals (new):
maven Provide information about maven-version,
called goals and active profiles
during the build and the command line
(security?).
java Provide information about the java
runtime. JAVA_OPTS? (Security?)
os Provide information about the
operation system (name, family,
architecture, version).
hostname Provide the build hostname.
username Provide the user under which the build
has been executed.
metadata Combine the above goals for convenience
(maven, java, os, hostname, username).
May be released-version and parse-version
can used as well.
metadata-report Create a report of what has been
combined in metadata goal.
I would suggest to hold the state of the goals for the
build-helper-maven-plugin at the moment and mark some as deprecated as
suggested and after a few versions to really remove the appropriate goals.
This means that currently the goals (maven-version, released-version,
parse-version and timestamp-property) will be duplicated in the
build-metadata-maven-plugin...
Kind regards
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
