-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Wendy Smoak wrote:
> A coworker is converting a WebSphere project to build with Maven.
> Neither of us is one of the project developers, so we're working
> directly with the code in svn on a branch, and not with the IDE at
> all.
> 
> I'll start with a couple of questions, but general advice from someone
> who's worked with WSAD [1] and Maven is greatly appreciated.
> 
> Will WSAD work with Maven's standard src/main/java and src/main/webapp
> directory structures?

WSAD or whatever IBM is calling it these days is just eclipse with IBM
plugins.  The plugins make turn eclipse into WSAD and turn up the price.
 ;-)  So the maven plugin, http://maven.apache.org/eclipse-plugin.html,
will take the maven directory and map it to the correct dot files and
project file for the eclipse/WASD/myeclipse world.

> 
> How do you deal with the third-party jars?  Of course we'll install
> them in the internal remote repository, but there are conflicting
> opinions about which jars you really need for building projects.  The

See if some of those jars aren't already available in the default maven
repository.  If so, then just declare a dependency to 'em.   Those jars
that aren't in the maven repo can be put in internal repo.  The benefit
here is that you'll finally know if the project requires 3 or 40 jars.

> architects say only three are necessary, another group says they
> needed about 40 of them, and the group I'm working with now just wants
> to point Maven at the entire lib directory they way they did with Ant.
> 
> [1] WebSphere Studio Application Developer
> 
> Thanks,
> Wendy
> 

Regards,
Greg

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFGQdrTxyxe5L6mr7IRAgUuAJ9cRj9NQJjo1ceDIHjZtsBzg1cvYQCgjYmn
6DQhRFUfca3iLxqrvgu/orE=
=uYLd
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to