[news.eclipse.tools] Re: Eclipse & CVS -- package level versioninng as i

["Mikkel Heisterberg" <m_heisterberg@xxxxxxxxxxx>]

I don't think there is a simple answer to this question, since it touches on
configuration management which is a hard topic. To answer your questions -
no CVS doesn't support versioning of packages since CVS isn't a Java
versioning tool per say but a general versioning tool. CVS tags files and
creates the directories needed to store the files. The way versioning
work(ed)/s in Visual Age is Java specific and hence they can make some
assumptions as to how versioning is best done.

The way we use CVS via Eclipse (we also made the move from Visual Age) is to
separate the different packages that isn't interconnected into different
jars and tag them independently when versions occur. If you combine this
with standardized Ant builds it allows you to extract the different jars at
the required versions in order to build your product at any given point in
time. I agree that this takes more planning but my opinion after having
tried it is that it results in better code since you learn to better
separate responsibilities between packages.

That's my 5 cents....

Mikkel Heisterberg,
IT-Inspiration ApS

"Sundar Narasimhan" <sundar@xxxxxxxxxx> wrote in message
news:b8abn2$7o2$1@xxxxxxxxxxxxxxxx
> Hi, I'd like to know if Eclipse supports "package" level versions or
> could be made to support such a concept w/ CVS.
>
> In VisualAge we could collect say version 1.0 of com.company.x.A and 3.0
> of com.company.x.B and call that the version "My Release 1.0" of
> com.company.x package.
>
> Since our products are comprised of several packages it helps to know a
> product release 7.0 is built up of say
> com.company.base 1.0
>          com.company.util 17.0
> etc.
>
> Is it possible to version (or simulate versioning of directories) in CVS
> .. I guess the straightforward answer would be "no" -- CVS does not
> support such a thing. But what I was wondering was if people had
> invented ways around it.
>
> How do you actually support complex products out in the field.. do you
> tag the entire hierarchy and just use cvs tags sparingly?
>
> In VisualAge since versioning is supported at both the package level
> (and at the project level which is a collection of packages), it is
> extremely simple to get one's workspace to a state that corresponds to a
> release.. how do people do this in CVS when the package structure is
> several directories spread out over several jars?
>
> Thanks.
>