Mike,
It looks I was getting happy too early.
Indeed creating a fake directory seems to please Eclipse CVS plugin on refresh
of the project.
Still when I attempt to do anything CVS
related (commit a file for example) from the sub-module I get a warning pop-up
saying “the operation is not enabled” and all my cvs directories
get cleaned up!
To clarify the situation and I guess this
may be the problem root – the sub-modules are originally stored in cvs as
separate Repositories (CVSROOT/sub-module1 for example).
I guess that when I am attempting to
commit Eclipse looks at the parent directory (?!) sees that parent Repository
is different and cleans up the marker directories below…
Though I understand the merit of this “mass”
oriented behaviour is there a way to disable this or overcome it?
Best regards,
Eduard Letifov
Analyst/Programmer
Information Services
Metservice
30 Salamanca Road,
Kelburn
Wellington
PO Box 722
Wellington
+64 4 470 0842
http://www.metservice.com
From:
platform-team-dev-bounces@xxxxxxxxxxx
[mailto:platform-team-dev-bounces@xxxxxxxxxxx] On Behalf Of Michael Valenta
Sent: Monday, 20 February 2006
1:52 p.m.
To: Generic team support framework
Subject: Re: [platform-team-dev]
Marker CVS directories get deleted on"Refresh" in Eclipse
Ed,
There
are several reasons why orphaned CVS folders are pruned. The main reason is
that, if the user copies or moves shared content, they expect the CVS folders
to be purged (there are other reasons as well but they are more complex). It
becomes difficult to differentiate the case where the user copied or moved
content (in which case the CVS folders should be purged) from the case where
the user checked out out additional content from the repository and wants the
CVS folders to remain.
Is
the project that contains the sub-modules shared with CVS through Eclipse. It
should be the case that orphaned CVS folders are only pruned in projects that
are shared with CVS. One option would be to disconnect the project from CVS and
see if that helps. I can't guarantee that it will since this is not something
we test for. If CVS folders are pruned from an unshared project, this is
definitely a bug. Please log a bug report if this is the case.
If
you want to keep the project shared with CVS, there are a couple of ways to
prevent the CVS folders from being purged from the sub-modules.
1)
Is the content all from the same repository? If so, the best way to deal with
this would be to define one or more modules in the CVSROOT/modules file that
would allow you to checkout everything at once as a project shared from the
root. This would ensure that the sub-modules are not orphaned and would have
the added benefit that you could perform CVS operations on the sub-modules from
within Eclipse.
2)
If it is not possible to define an appropriate module but the content is from
the same repository, you can use the Eclipse CVS Checkout wizard to specifiy
that you want to checkout content into an existing project. This will create
the necessary CVS folders in the parent folders and project to enable CVS
operation on the sub-modules. This would not be possible if you have an
automated process for checking out the sub-modules. However, if this is the
case, you could modify your checkout process to create the required CVS folders
and content. This would require that your checkout process create the
appropriate files in the CVS folders (just like the CVS Checkout wizard does).
3)
If neither of the above two approaches are appropriate, another option would be
to add the sub-modules as links (i.e. check them each out as projects and then
create the submodules in your build project as Eclipse links. The CVS plugin
totally ignores the conteht in links.
If
none of these work for you, it may be best to log a bug report about this.
Michael
|
"Ed Letifov" <ed.letifov@xxxxxxxxxxxxxx>
Sent
by: platform-team-dev-bounces@xxxxxxxxxxx
02/19/2006 03:49 PM
|
Please
respond to
Generic team support framework
|
|
|
To
|
<platform-team-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
|
[platform-team-dev] Marker CVS directories
get deleted on "Refresh" in Eclipse
|
|
Hello,
After
looking for quite long on the Eclipse site I’ve only found this list to
communicate to “team” developers…
I
am trying to make Eclipse usable with a build system we have or vice versa if
you wish J
The
build system is based on Ant and CVS.
Once
you checkout the top level module, the build system checks out the sub-modules
from separate CVS modules into the directory structure described below.
The
“modules” sub-directory does not contain CVS directories.
Sub-modules do. Now here is the problem – the moment I press refresh
project in Eclipse, all CVS directories in the sub-modules get deleted…
From
my view this should not be so. These are my directories; Eclipse didn’t
have to do anything with them, why does it delete them?
+Top-Level
CVS module
+CVS
+Lib
+Modules
+sub-module1
+CVS
+sub-module2
+CVS
+Src
Build.xml
Can
anyone please provide a hint how to disable this behaviour?
Best
regards,
Eduard
Letifov
Analyst/Programmer
Information
Services
Metservice
30
Salamanca Road,
Kelburn
Wellington
PO Box
722
Wellington
+64 4
470 0842
http://www.metservice.com
_______________________________________________
platform-team-dev mailing list
platform-team-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-team-dev
