Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EGit » Team -> Import Project Set fails with "Invalid project description..."
Team -> Import Project Set fails with "Invalid project description..." [message #1386977] Mon, 23 June 2014 11:25 Go to next message
Matthias Niehoff is currently offline Matthias NiehoffFriend
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 #1393069 is a reply to message #1386977] Thu, 03 July 2014 07:32 Go to previous messageGo to next message
Matthias Sohn is currently offline Matthias SohnFriend
Messages: 612
Registered: July 2009
Senior Member
Can you share the psf file ?
Can you retry with latest 3.5 version from http://download.eclipse.org/egit/updates-nightly ?
Cloning the repository into the workspace directory may affect performance but should work.
Re: Team -> Import Project Set fails with "Invalid project description..." [message #1393940 is a reply to message #1386977] Fri, 04 July 2014 14:17 Go to previous messageGo to next message
Matthias Niehoff is currently offline Matthias NiehoffFriend
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 #1397303 is a reply to message #1393940] Wed, 09 July 2014 14:24 Go to previous messageGo to next message
Matthias Sohn is currently offline Matthias SohnFriend
Messages: 612
Registered: July 2009
Senior Member
Are v02_00_00_03 etc. tags or branches ?

If you want them in the workspace put them into a folder below the workspace.
If you import a team project set EGit does this automatically.

You'll see performance degradation if you have projects located directly under the workspace,
multi-select a couple of them and create a git repository for them using the Team > Share with Git
wizard and check the option "Create repository in parent folder of project" the new .git folder
is at the root of the workspace. The performance problems are caused by the fact that the
.metadata folder containing the workspace's metadata is then located in the working tree of this
repository. Hence git will also scan the folder to detect changes. Since this folder is a huge tree
this can degrade performance.
Re: Team -> Import Project Set fails with "Invalid project description..." [message #1397320 is a reply to message #1386977] Wed, 09 July 2014 14:48 Go to previous messageGo to next message
Matthias Niehoff is currently offline Matthias NiehoffFriend
Messages: 6
Registered: February 2014
Junior Member
Hi,

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.

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.

Re: Team -> Import Project Set fails with "Invalid project description..." [message #1397510 is a reply to message #1397320] Wed, 09 July 2014 20:55 Go to previous messageGo to next message
Matthias Sohn is currently offline Matthias SohnFriend
Messages: 612
Registered: July 2009
Senior Member
Matthias Niehoff wrote on Wed, 09 July 2014 10:48
Hi,

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:48
Hi,
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
Re: Team -> Import Project Set fails with "Invalid project description..." [message #1397511 is a reply to message #1397510] Wed, 09 July 2014 20:56 Go to previous messageGo to next message
Matthias Sohn is currently offline Matthias SohnFriend
Messages: 612
Registered: July 2009
Senior Member
I meant this layout:

workspace
-> foo
---> .git
---> Project1
---> Project2
Re: Team -> Import Project Set fails with "Invalid project description..." [message #1397825 is a reply to message #1386977] Thu, 10 July 2014 07:57 Go to previous message
Matthias Niehoff is currently offline Matthias NiehoffFriend
Messages: 6
Registered: February 2014
Junior Member
Thanks for your help. I created bug 439317 and also voted for Bug 395143.
Previous Topic:Doubt about git repositories inside Eclipse project folders
Next Topic:Unable to upgrade Eclipse Luna due to missing repositories
Goto Forum:
  


Current Time: Mon Dec 22 02:16:51 GMT 2014

Powered by FUDForum. Page generated in 0.01996 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software