Re: [platform-vcm-dev] Ignoring CVS directories in the JDT Builder...

[Kevin_McGuire@xxxxxxx]

Hi Tom,

We are aware of the problem and are looking at different solutions to 
prevent the builder from treating these files/folders as source and thus 
prevent their copying.

I'm not sure which build you are on.  The last integration build contained 
a change to JDT so that duplicates would only be a warning, as opposed to 
a critical build error.  I am guessing from note that you have this 
version.

So the short answer is you will need to live with the build warnings for 
the time being.  Or of course go back to using the VCM plugins.

Kevin McGuire






Tom Palmer <tomp@xxxxxxxxx>
Sent by: platform-vcm-dev-admin@xxxxxxxxxxx
02/01/2002 12:34 PM
Please respond to platform-vcm-dev

 
        To:     "'platform-vcm-dev@xxxxxxxxxxx'" <platform-vcm-dev@xxxxxxxxxxx>
        cc: 
        Subject:        [platform-vcm-dev] Ignoring CVS directories in the JDT Builder...

Hi,

  I thought I'd ask this question on this list rather than the jdt-core 
list
as someone must have come across this problem and (hopefully) come up with 
a
fix. I have several projects that I'm trying team 2.0 out on. They all 
have
a similar directory structure:

  project ->
          src ->
              main                               (Main application code)
              testcases                  (Unit test code)

  Both source directories usually contain the same packages (not a problem
with the pre-team 2.0 code) but different classes e.g. in the main 
directory
there may be an app.Application class with a corresponding unit test class
of app.ApplicationTest located in the testcases directory. The problem 
with
this setup in the team 2.0 code is the CVS directories: the java builder 
is
complaining of duplicate resources in the CVS directories (e.g.
main/CVS/Entries and testcases/CVS/Entries being duplicates of one 
another).
Obviously on a large project you end up with a large amount of warnings in
the task list that you have to filter through to find real problems with 
the
code.

  Has anyone else hit this problem? I noticed that some of the jdt code
reports the same warnings. I could just disable the relevant line in
org.eclipse.jdt.internal.core.newbuilder.BatchImageBuilder but then I 
won't
learn of any real duplicates :(

  Regards,

  Tom

  Tom Palmer 
  Web Systems Developer 
  WorldCom 
  332 Science Park, Cambridge, CB4 0BZ, UK 
  Tel: +44 (0)1223 250246 
 
_______________________________________________
platform-vcm-dev mailing list
platform-vcm-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev