| Using CVS features with existing tree [message #136129] |
Wed, 21 January 2004 14:19  |
Eclipse User |
|
|
|
Originally posted by: lind.ucar.edu
Hi,
We have a complex cvs tree and a script to check out all the bits needed
to build the project. Instead of going through the trouble of checking out
the many needed bits via Eclipse's cvs repositories view, I'd like to be
able to convince Eclipse to work with the tree that our script checks out.
I can work with the project in Eclipse but I don't get any of the cvs
features.
I'm working on an Ant build script to do the cvs checkouts but Eclipse
wasn't any happier about accepting these files as cvs capable even when
the ant build is run within Eclipse. Is any work being done here to better
couple ant's cvs abilities?
We have an issue with tool buy-in here. I'd like to make this as easy as
possibly to attract other users without munging our current environment to
work with Eclipse. Any suggestions?
BTW, I'm using 2.1.1.
Thanks,
Doug
|
|
|
| Re: Using CVS features with existing tree [message #136154 is a reply to message #136129] |
Wed, 21 January 2004 15:38  |
| Eclipse User |
|
|
|
There's no general problem using a project that is already on disk and
has CVS metadata. Do an import of the project, and then do a
'Team|Share' to share it to CVS. It will detect the CVS metadata and ask
if you want to use that. Also, it is generally a good rule to have the
CVS perspective already open before you ever do the first import, since
it will know what the CVS metadata is, and not consider it part of the
build resources it needs to copy during the build.
Now my comment about there not being a problem is not quite true, in
that it is quite tedious for 20-30 projects already on your filesystem,
to go through the above steps. There are a few enhancement requests in
Bugzilla for doing multiple imports and multiple shares at a time...
Doug Lindholm wrote:
> Hi,
>
> We have a complex cvs tree and a script to check out all the bits needed
> to build the project. Instead of going through the trouble of checking out
> the many needed bits via Eclipse's cvs repositories view, I'd like to be
> able to convince Eclipse to work with the tree that our script checks out.
> I can work with the project in Eclipse but I don't get any of the cvs
> features.
>
> I'm working on an Ant build script to do the cvs checkouts but Eclipse
> wasn't any happier about accepting these files as cvs capable even when
> the ant build is run within Eclipse. Is any work being done here to better
> couple ant's cvs abilities?
>
> We have an issue with tool buy-in here. I'd like to make this as easy as
> possibly to attract other users without munging our current environment to
> work with Eclipse. Any suggestions?
>
> BTW, I'm using 2.1.1.
>
> Thanks,
> Doug
>
|
|
|
Powered by
FUDForum. Page generated in 0.02268 seconds
Home