You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Jeffrey Bonevich <je...@bonevich.com> on 2005/02/01 23:41:28 UTC
Reconciling WSAD and Maven
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: jeff@bonevich.com
"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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Reconciling WSAD and Maven
Posted by Jeffrey Bonevich <je...@bonevich.com>.
Thomas Recloux wrote:
>On Tue, 01 Feb 2005 17:41:28 -0500, Jeffrey Bonevich <je...@bonevich.com> wrote:
>
>My experience : On my project, all the team (20 developpers) is using
>WSAD 5.1 with maven, we are not using the J2E2 Modules of WSAD, all
>our projects are Java projects.
>
>
>
So I take it you do not use the WAS test environments inside WSAD
either? I can see this working ok if you work with Tomcat (or some
other appserver) or are deploying to a test-bed using maven. My team
uses the embedded WAS 5.1 test environment exclusively during active
development. This is part of what is restricting me. I may have to
separate development preparation from automated build/test/deploy to
work around it, but would prefer not to.
jeff
--
jeff bonevich
mailto: jeff@bonevich.com
"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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Reconciling WSAD and Maven
Posted by Thomas Recloux <th...@gmail.com>.
On Tue, 01 Feb 2005 17:41:28 -0500, Jeffrey Bonevich <je...@bonevich.com> wrote:
> 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?
My experience : On my project, all the team (20 developpers) is using
WSAD 5.1 with maven, we are not using the J2E2 Modules of WSAD, all
our projects are Java projects.
--
Thomas Recloux
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org