Does anyone have any experience getting WSAD 5.1 and Maven to play nice
together and stop fighting over the J2EE modules in an application? I
am thinking here more of silly little things like WSAD wanting your EJB
modules to have all java code, ejb-jar.xml, and generated deployment
code in the source directory...or WSAD complaining about me wanting to
put my web content in src/web and not in WebContent, etc. Any good
reads anyone is aware of for such problems? I will be complaining to
IBM shortly, but... wanted to see if there are work-arounds in WSAD for
best practices that would allow the app to be more Maven-compliant.
jeff
--
jeff bonevich
mailto: [EMAIL PROTECTED]
"Any sufficiently advanced technology is indistinguishable from magic."
Arthur C. Clarke
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the Universe trying
to produce bigger and better idiots. So far, the Universe is winning."
Rich Cook
"All programmers are playwrights and all computers are lousy actors."
Unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
