RE: [WDSCI-L] Newbie Question Number One

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: Mark Phippard
>
> As far as I know, the WSAD tooling does not provide access to these
> sort of advanced EAR file features.

"advanced"  <shaking head>  Common code between two applications - that's
advanced, eh?  And some people wonde why I say that the J2EE model is
inadequate for production application development.  Oh well, I'll try to be
non-negative.


> All that aside, if you are using any kind of version control,
> even CVS, it
> is very easy to manage this (at least for JAR's like JTOpen, Struts,
> Xerces etc. where they change slowly).  You just connect to the
> repository
> and add your project and everything comes in all configured.

Okay, this is where it gets seriously interesting.  First off, I'll
understand if you don't want to help me with this next bit, because it's
directly impinging on your market niche, but I'm going to ask anyway, and
maybe if you'd rather not answer, someone else will.

The idea here is to do this for free (or at best a $100 utility).  I don't
want to spend thousands of dollars for a project management system YET.
Long term, that may be the right answer, and it really depends on your shop.
But let's say I am comfortable today with simply saving libraries to CD-ROM
for backup and using file compares for version control.  CDs are cheap, file
compare is free.

Okay, now I need to set up CVS.  First off, from what I've read the open
source CVS server for Windows (CVSNT) isn't exactly up to snuff (and I've
tried to use it, and it's been a little weird).  So what do I need to do?
Get a Linux machine just in order to keep my WDSC workstations in sync?

Do you see how this is becoming a little more complicated?



> If you have some internal projects you want to package it sounds
> like you have already
> discovered that you can define the Java Project in which you develop that
> code as a "Library Project" to your Web Project and its code is then
> automagically kept updated in the Web Project.

Yeah, this kicks butt!  I just wish they'd have put the same thought into
the concept of true external JAR files.

Joe