Hey, wsrModule or any module configuration is *ONLY* necessary if you want to customize the way the artifact is bundled in the EAR. If you're happy with the defaults, you don't need any special configuration at all (except the dependencies).
How is it doing with only the WSR dependency in your EAR project? Regards, Stéphane On 7/31/07, Marc Chung <[EMAIL PROTECTED]> wrote: > Hi folks, > > I'm trying to include a WSR (Web Service aRchive; JBoss) in my EAR. > > Has anybody ever used the WsrModule documented over at the > maven-ear-plugin? I don't know how to do a few things: > > 1. Reference a dependency to a WSR module > > <dependency> > <groupId>com.company</groupId> > <artifactId>awesomeArtifact</artifactId> > <version>1.0-SUPER</version> > <type>wsr</type> <-- Intuitively, I'd use this. > </dependency? > > 2. Bundle up the WSR module into the final EAR > > <wsrModule> > <groupId>com.company</groupId> > <artifactId>awesomeArtifact</artifactId> > <bundleDir>/</bundleDir> > </wsrModule> > > I've searched the following: > > - Sonatype's website > - Google > - Google Code Search > - Krugle > > But believe it or not, I haven't see/found a single pomxml file that > uses wsrModule. > > I'd also be happy to consider alternative approaches to EAR file creation. > > Kind regards, > > --Marc Chung > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck" -- S.Yegge --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
