Hi John, >From the websphere_tasks project (a pom-only project that is using an antrun plugin. There is no jar.) I am inheriting the WebSphere admin functionality (WebSphere deploy, install, uninstall, etc.) in EAR module only.
>From the parent distributionProject pom, I am inheriting the common dependencies. Thanks, Sandeep -----Original Message----- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 07, 2006 10:48 AM To: Maven Users List Subject: Re: Using <extensions> In general, Maven follows the Java-ish single-inheritance model. What you're trying to do is multiple inheritance of POMs, which we don't support. What specifically is in your websphere tasks project that you want inherited here? Maybe there is another approach that will solve your problem, but I cannot tell from this little information... -john Dixit, Sandeep (ProSource Solutions) wrote: > Here is my project structure: > > - websphere tasks project (deployed in the rep) > - distributionProject > - EJB module : pom inherits distributionProject pom > - WEB module : pom inherits distributionProject pom > - EAR module : pom inherits distributionProject pom; I ALSO WANT > inherit websphere tasks here. However my websphere project is non-jar, > POM only project. > > Could you please provide me some pointers on how to achieve this? I was > thinking of using <build><extensions><extension> to achieve this... > > Thanks, > Sandeep > > > > -----Original Message----- > From: John Casey [mailto:[EMAIL PROTECTED] > Sent: Monday, February 06, 2006 4:53 PM > To: Maven Users List > Subject: Re: Using <extensions> > > Not sure what the end goal is here, but I assume you're saying you're > trying to do something like: > > <build> > <extensions> > <extension> > <groupId>some.group.id</groupId> > <artifactId>some-artifact</artifactId> > <version>1.1.1.1</version> > <type>pom</type> > </extension> > </extensions> > </build> > > Other than playing the trick of having that POM's dependencies all > included in the core classloader of Maven, I'm not sure what this would > acoomplish. BTW, it's entirely possible that the <type/> element isn't > allowed here, I don't remember for sure. It would seem to make some > amount of sense not to allow this, though... > > -john > > Dixit, Sandeep (ProSource Solutions) wrote: >> Is there a way to extend a POM only project using >> <build><extensions><extenstion>... tag? >> >> I am not able to do so as by default extension is looking for JAR type >> project. And mine is POM. Extension tag is not allowing defining of >> <type> tag. >> >> Thanks, >> Sandeep >> >> >> > ------------------------------------------------------------------------ > ------------------- >> ***National City made the following annotations >> > ------------------------------------------------------------------------ > ------------------- >> This communication is a confidential and proprietary business > communication. It is intended solely for the use of the designated > recipient(s). If this communication is received in error, please > contact the sender and delete this communication. > ======================================================================== > =================== >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
