Deprecate platform-detective-maven-plugin
-----------------------------------------
Key: CBUILDS-44
URL: http://jira.codehaus.org/browse/CBUILDS-44
Project: Mojo C Builds
Issue Type: Improvement
Components: Cleanup Items
Affects Versions: 1.0-alpha-6, 1.0-alpha-5
Reporter: Lee Thompson
Fix For: 1.0-beta-1
The detect goal in platform-detector-maven-plugin binds to the initialize
phase. Move this to a new validate phase implemented in the
rpm-cbuild-maven-plugin. Deprecate the injection of platform patterns as the
testers are not testing that functionality and I don't believe it works anyway.
The validate phase will also be the the place where RPM versions and build
numbers will be determined.
The validate goal/phase of rpm-cbuild-maven-plugin will attempt to set the
osProperty and archProperty dynamically if those properties are not defined.
This allows the project to inject the arch/os into the build which is what the
platform properties was attempting to accomplish. If undefined, the plugin
will look at the operating system and try to guess what the platform is. This
detection will be a simple case statement, if/then/else logic, not a plexus
component java reflection mechanism. The reason for the old school code is to
allow for readability for build maintainers who typically are script
developers, not java developers. The detectors will need updates from time to
time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
