Hi, > I'd suggest you should also be providing a custom packaging > "my-rar" or something more specific :) In your own words you > want to create your "own packaging"
Yes. This is what I want. But, my own packaging will also be "rar" since "my-rar" will be a "rar" specific for OC4J as an example. If I renamed as <packaging>my-rar</package> instead of "rar", I'll assume that "Ear Plugin" will not consume it since it is not a "RarModule". Even though I might have to write both Ear Plugin and Rar Plugin under my specific requirement. I still think that would be a bad idea that I have to write all the J2EE packaging plugins just because I have to do some specific thing in one type of J2EE Component. More, in general, it should be configurable or customizable by wiring build life cycle phase or packaging type with default plugin executed. It is the same that you might want to use your own XML Parser instead of the default xml parser from JAXP. Maven should enforce a rigid build life cycle but not a list of maven plugins should be executed. My two cents:-) Jian -- View this message in context: http://www.nabble.com/Should-all-maven--x--plugin-have-skip-parameter-like-surefire-plugin--t1358571.html#a3641687 Sent from the Maven - Dev forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
