Stephane, Thanks for the reply, I didn't know that the defaults were smart enough.. I'll be able to erase half the pom.xml file :)
But I'm still unsure of a few things: 1. What does the pom.xml for a WSR project look like? There is neither a WSR packaging type nor a plugin, that I have found, that manages it. (I'm thinking of something similar to the jboss-sar type that the jboss-packaging-plugin manages) 2. Right now, I'm under the impression that I need to add a dependency to my "ear/pom.xml." Something like this: > > <dependency> > > <groupId>com.company</groupId> > > <artifactId>awesomeArtifact</artifactId> > > <version>1.0-SUPER</version> > > <type>wsr</type> <-- Intuitively, I'd use this. > > </dependency? And then further down, optionally add the following to my <configuration>'s <modules> section: > > <wsrModule> > > <groupId>com.company</groupId> > > <artifactId>awesomeArtifact</artifactId> > > <bundleDir>/</bundleDir> > > </wsrModule> This doesn't work (obviously) since there's no WSR type. In other words how do I depend on an WSR-type project? I've spent a bit of time thinking about this, and I'm leaning towards the opinion that this simply can' t be done, but that doesn't make any sense (why offer <wsrModule> if you can't depend on a wsr packaging type?), so I'm probably missing something simple. 1. Do I even need to add the WSR type? Is it another type? Perhaps I need to mess around with the <artifactTypeMapping>? 2. I'm currently generating a JBoss web-services.xml file in "ejbs/pom.xml" using ejbdoclet. Perhaps I could bundle the web-services.xml file in that JAR instead. Anyway, I'm basically trying out different ideas at this point, since I'm personally new to Web Service aRchives. Thanks for reading, -Marc On 7/31/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote: > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
