DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20315>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20315 [PATCH] Updated Maven Plugin Documentation ------- Additional Comments From [EMAIL PROTECTED] 2003-05-28 23:02 ------- Mark, I can definitly wait until you are done, just trying to document some of the build processes we use. At any rate, what seems to be really needed is a clearinghouse of links to plugins. However, for most projects, I think the plugin should be based with the project it goes with. That way the committers are the same. I looked at your code, but didn't want to dig into changing it willy nilly! However, here are a couple points... It seems that the org.apache.jetspeed.util.ant.OverwritePropertiesTask task should have the same name throughout! Not, overwriteproperties and props_override. Also, I think it could be definied externally from a goal.. The only other question I have, would the usecase for jetspeed:war to be for a user to build their own jetspeed war file? Or is it because th default war:war task doesn't do everything needed by jetspeed? If it is just to enhance war:war, and only used to build the jetspeed.war file, then it may make more sense to have it in the maven.xml file? Not sure though if my understanding is totally 100%. At any rate, the key I think is to just get the binary plugin online someplace, and the nice maven docs up on jakarta.apache.org/jetspeed! Eric --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
