Share project in Eclipse

[GrahamLabdon]

Hi
I am trying to share a project from Eclipse but get an error
'Could not resources due to null' see attached
I have also attached the vault log file

Please can you explain why I am getting this error

Thanks

[Beth]

Are you on Windows, Mac, or Linux?

I couldn't seem to read the VaultError.txt file. What was that created in?

Do you have a Vault GUI client installed on the same machine? If so, open it up and take a look at your pending change set tab at the bottom. Do you see any deletes sitting in there? If so, can you commit them?

[GrahamLabdon]

Hi
OS is Windows 7
There are no pending deletes - I created a new repository and still cannot share the project in Eclipse
The VaultError.txt file is a word document - if you rename it docx you should be able to read it

This error seems to have manifested itself since upgrading to v 6.1

When I try to share the project I can see that a folder for the project has been created in the Vault Client.
If I manually add the files Eclipse is now bound to the project - i.e. I can import the project from Eclipse. However, if I edit files in eclipse they show as edited in the Vault Client, but on check in they are marked as 'Needs Merge' - see attached (word doc saved as .txt)

Thanks

[Beth]

1) Is anyone else working on the code and checking in changes? If so, that is where the needs merge is coming from.

2) If you're alone and have a needs merge, you might have Vault and Eclipse using two different baseline locations.

You can get the statuses to line up between Vault and Eclipse if you set each of them to place the baselines in the working folder. In Vault that is done in the Tools - Options - Local Files - Cache Location. In Eclipse you go to Window - Preferences - VaultPro - Cache Location. Once both are set, you can perform a Get with the option "Do not overwrite/Merge later" in Vault and then a Get Latest in Eclipse and they will line themselves up.

Having them both place their baselines in the working folder works better normally than other locations.

[GrahamLabdon]

Hi
Thanks for the reply
Things are still not working correctly and I think this must stem from the face that we are unable to add an eclipse project to vault
I set up a test repository and a new eclipse project but still get the same error message -

'Could not resources due to null'

What else can you suggest that I try

Thanks

[Beth]

I would try a new workspace.

Does this happen just on one machine or all machines?

What type of projects are you working with?

[GrahamLabdon]

Hi
I have tried with different workspaces and different users
The project we are trying to add is a simple hello world c++ project compiled with the mingw compiler

[Beth]

Could you send an email to support at sourcegear.com (attn: Beth) with with your hello world program? I'll get the C++ version of Eclipse set up in the meantime.

[GrahamLabdon]

email sent

[GrahamLabdon]

I have got to the bottom of this problem!

On our server I have set the file exclusions to include Makefile -

*.clw; *.config; *.dca; *.Debug; *.dll; *.dsw; *.exe; *.hlp; *.incr; *.ncb; *.opt; *.pdb; *.plg; *.Release; *.scc; *.suo; *.user; *.vbw; *.webuser; Makefile

This causes a crash in the Eclipse Vault Pro plugin; although not in the VS Studio plugin

It seems that the plugin expects a string in the form *.<ext>

[Beth]

Great catch!! That does fit with what we discussed offline.