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

["Robert Varga" <robert.varga@xxxxxxxxxxxxxxxxxxxx>]

Tags could be used for something like this.

In CVS files can have an arbitrary number of tags associated with them.

You can come up with a tag naming scheme which would work alright for you.

The unfortunate point is, that the Eclipse CVS plugin is not really usable
for administering tags
(ie. it is not able to help you with adding tags in the repository, you are
only able to add
tags to a local checkout, therefore for each new version to be defined, you
have to check
out that version to a separate directory tree, and make the tagging there).

Afterwards you are able to check out files with a specific version, without
a problem.

And about the naming scheme.

You need to name the interesting tags the following way:

p_<packagenameconverted>_<versionconverted> for package non-recursive
c_<productnameconverted>_<versionconverted> for composite

Package-composite tags would designate versions containing more than one
package.

package release and version names need to be converted so that it contain
only the characters
allowed in a tag name. I think that for example the dot character is not
allowed in a tag name.

There also may be a limit on the length of the tag name, so you may need to
come up with some
two-way substitutions for package and product names.

Regards,

Robert Varga


"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.
>