Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make the source 'Eclipse ready' (.classpath project name missmatch) [moved] #59

Closed
lvca opened this issue Dec 10, 2012 · 0 comments
Closed

Make the source 'Eclipse ready' (.classpath project name missmatch) [moved] #59

lvca opened this issue Dec 10, 2012 · 0 comments

Comments

@lvca
Copy link
Member

lvca commented Dec 10, 2012

This is Issue 59 moved from a Google Code project.
Added by 2010-07-11T16:39:06.000Z by jmlug...@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Closed (Fixed).

Original labels: Type-Enhancement, Priority-Low, v0.9.24

Original description

Currently the .classpath files refer to project named like orient-database-core, orient.... while the directory names are just core, ....
This requires to manually change the dependencies when importing in Eclise. If the same name were used, an imported project would compile immediately without change.

Example of reference in .classpath:
<classpathentry combineaccessrules=&quot;false&quot; kind=&quot;src&quot; path=&quot;/orient-database-core&quot;/>
@lvca lvca closed this as completed Dec 10, 2012
@henryzhao81 henryzhao81 mentioned this issue May 15, 2015
Closed
@martingg88 martingg88 mentioned this issue Jun 6, 2015
Closed
@jamieb22 jamieb22 mentioned this issue Jan 10, 2017
Closed
@giggs131400 giggs131400 mentioned this issue Aug 22, 2017
Closed
@KluSe KluSe mentioned this issue Mar 19, 2018
Closed
@CyprienGottstein CyprienGottstein mentioned this issue May 29, 2018
Closed
@madmac2501 madmac2501 mentioned this issue Apr 1, 2020
Closed
@madmac2501 madmac2501 mentioned this issue Jun 7, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lvca