| Team -> Import Project Set fails with "Invalid project description..." [message #1386977] |
Mon, 23 June 2014 11:25  |
 Matthias Niehoff
Messages: 6
Registered: February 2014 |
Junior Member |
|
|
Hi!
When i use import->team->team project set to import a psf file, it reports
"Invalid project description overlaps the location of annother project ". The clone operation works fine. It seems that the import of the project fails. If i manually import the project via import -> projects from git -> local repo -> the cloned repo it works fine.
Also cloning a repo in the Git Perspective with an import of the projects works fine.
My Configuration: Eclipse Kepler SR1, eGit 3.2.0.201312181205
Is it maybe a problem, that the repo is cloned into the workspace directory?
Thank You
[Updated on: Mon, 23 June 2014 11:52] Report message to a moderator |
|
|
|
| Re: Team -> Import Project Set fails with "Invalid project description..." [message #1393940 is a reply to message #1386977] |
Fri, 04 July 2014 14:17  |
Matthias Niehoff
Messages: 6
Registered: February 2014 |
Junior Member |
|
|
Hi,
i tried v3.4.1 and the nightly of 3.5. The same error occurs.
I've configured the workspace_loc as directory for git repo in preferences -> team -> git
The psf file is attached. It has 2 git projects and a few CVS projects. The import of the CVS projects works fine.
After importing the project set, there is a directory for the first git project inside the workspace dir but, not for the second one. The second git project isn't even cloned.
When importing the project these step are executeing in the following order:
1. Clone first git repo
2. Checkout and import CVS Projects
3. Try to import the first git Repo. This fails.
Following Error:
The following errors occurred while importing projects. Some projects may not be loaded.
Invalid project description.
Invalid project description.
OK
C:\Entwicklung\projekte\git\Provinzial-Service-Verzeichnis overlaps the location of another project: 'Provinzial-Service-Verzeichnis'
C:\Entwicklung\projekte\git is the workspace dir.
You say that cloning in the workspace may affect the performance. Whats your recommendation for the repository location, if we need the repository per workspace (Not a shared repo between different workspaces). If it should be outside the workspace, there is missing a configuration for the import project set, where to clone the repo (i thinkt it automatically clones in the workspace and atm there is no chance to change this).
Thanks for your help so far!
Regards
[Updated on: Fri, 04 July 2014 14:22] Report message to a moderator |
|
|
|
|
| Re: Team -> Import Project Set fails with "Invalid project description..." [message #1397510 is a reply to message #1397320] |
Wed, 09 July 2014 20:55 |
Matthias Sohn
Messages: 1072
Registered: July 2009 |
Senior Member |
|
|
Matthias Niehoff wrote on Wed, 09 July 2014 10:48Hi,
v02_00_00_03 are Tags (old cvs style...)
So this layout:
workspace
-> .git
-> Project1
-> Project2
is not good, but this:
workspace
-> Project1
----> .git
-> Project2
----> .git
is ok? If so, we are fine, because we are using the second way. And as you said the project set import works this way too.
With this layout you cannot add additional eclipse projects if this need comes up. To avoid this
you can use the layout which EGit uses when you import a psf file of a repository containing multiple projects:
workspace
-> foo
---> .git
-----> Project1
-----> Project2
Matthias Niehoff wrote on Wed, 09 July 2014 10:48Hi,
Back to the problem with the Import:
I've discovered that the import fails if the <projectDescription><name> in the .project file doesn't match the actual name of the project. if they are both equal, everything works fine.
Nevertheless it's quite interesting, that the import project set fails but the "import projects" on the same git repo in the git perspective is working fine.
Please file a bug for this problem
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02276 seconds
Search
Help
Register
Login
Home
