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 Eclipse classpath refer to lib_managed dir #42

Closed
GoogleCodeExporter opened this issue Jun 3, 2015 · 3 comments
Closed

Make Eclipse classpath refer to lib_managed dir #42

GoogleCodeExporter opened this issue Jun 3, 2015 · 3 comments
Labels
auto-migrated Component-Eclipse Milestone-Release1.0 Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

At the moment the classpath refers to each of the JARs in lib_managed, but this 
is fragile since the 
exact jars in there will vary depending on the transitive dependencies of the 
libraries that we use 
directly.  If possible, make the .classpath file just refer to the directory so 
we don't have to update it 
all the time.

Original issue reported on code.google.com by inkytonik on 24 Nov 2009 at 2:30
@GoogleCodeExporter
Copy link
Author 

Done (r3a71b8b3be) but remains to be tested.

Original comment by inkytonik on 26 Nov 2009 at 4:26

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author

Original comment by inkytonik on 14 Jan 2010 at 2:18

  • Changed state: Resolved

@GoogleCodeExporter
Copy link
Author 

Actually, the final change was to use the sbt-eclipse-plugin which takes care 
of everything in a nice way.  The 
change was in r79778e96aafa.

Original comment by inkytonik on 14 Jan 2010 at 2:22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Component-Eclipse Milestone-Release1.0 Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter