Re: [m2]Is Plugin associated with Packaging but type is used for dependency?

Hi Stephane, I just reveiwed MEAR-26, it should solve my problem. And, I assume that the value of "mapping" element could be any standard j2ee component type like ejb and war. Thanks a lot for your help! Jian -- View this message in context: http://www.nabble.com/-m2-Is-Plugin-associated-wi

Re: [m2]Is Plugin associated with Packaging but type is used for dependency?

Hi Brett, Thanks a lot for your reply! I followed the "Introduction to the Build Lifecycle" and created "my-rar" package and I had problem using "my-rar" with maven-ear-plugin. At first, I thought it is the problem of dependency resolution of maven. Later on, I realized that it is maven-ear-plug

Re: Should all maven-[x]-plugin have skip parameter like surefire-plugin

Hi Brett, > Did you first do mvn install on the first project? Where did it end up? No. I don't want to do "mvn install". Both rar and ear are two module project under the same parent pom project. Actually, I end-up create my own "my-rar" package type and since maven-ear-plugin could not recog

[m2]Is Plugin associated with Packaging but type is used for dependency?

Hi, I just tried to get a general understanding of Maven2 Runtime behavior. Please correct me if I'm wrong. It looks like that Maven Plugin is associated with packaging and Maven2 Runtime is invoking the associated Plugins for the packaging defined in pom.xml. Is this correct? And, is the plu

Re: Should all maven-[x]-plugin have skip parameter like surefire-plugin

Hi Brett, Sorry to misspell your name in the previous emails. > > Would you suggest that I can specify a packaging "my-rar" in my rar > pom.xml, > > but in my ear pom.xml, I can specify type as "rar" when I define my rar > > project > > as a dependency project? > > Yes, I think so. I did give

Re: Should all maven-[x]-plugin have skip parameter like surefire-plugin

Sorry for the typo. "this is not a bug of Rar Plugin since Par Plugin only executes rar goal at package phase" should be "this is not a bug of Rar Plugin since Rar Plugin only executes rar goal at package phase" -- View this message in context: http://www.nabble.com/Should-all-maven--x--plugi

Re: Should all maven-[x]-plugin have skip parameter like surefire-plugin

Hi Brat, > > Would you suggest that I can specify a packaging "my-rar" in my rar > pom.xml, > > but in my ear pom.xml, I can specify type as "rar" when I define my rar > > project > > as a dependency project? > > Yes, I think so. Thanks a lot for the tip! I'll definitely give a try. > > 2). A

Re: Should all maven-[x]-plugin have skip parameter like surefire-plugin

Hi Brat, Thanks a lot for your quick reply! > I'm pretty sure that the rars generated can still have a dependency type > of rar - the type != packaging. Would you suggest that I can specify a packaging "my-rar" in my rar pom.xml, but in my ear pom.xml, I can specify type as "rar" when I define

Re: Should all maven-[x]-plugin have skip parameter like surefire-plugin

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 examp

Should all maven-[x]-plugin have skip parameter like surefire-plugin?

Hi, I intended to develop my own rar-plugin and/or ear plugin for my own packaging. What I found was that Maven2 runtime by default will always invoke maven-rar-plugin for a rar project at package phase, the same as maven-ear-plugin for a ear project which will overlap with my rar/ear-plugin exe