Jian.Wu wrote: > 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".
I'm pretty sure that the rars generated can still have a dependency type of rar - the type != packaging. > 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. I agree - the RAR plugin should be extensible enough to do what you want, rather than be replaced. What exactly is it that you need to do that it can't? > Maven should enforce a rigid build life cycle but not a list of maven > plugins should be executed. That's why you can specify alternate packagings. We can consider some sort of replacement mechanism in 2.1 as we are taking another look at how the lifecycle is specified. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
