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.

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

Classpath modification #45

Closed
sriksrid opened this issue Mar 19, 2015 · 2 comments
Closed

Classpath modification #45

sriksrid opened this issue Mar 19, 2015 · 2 comments

Comments

@sriksrid
Copy link

Hi

I noticed that when I debug/run a file, a classpath is being specified (the jar file built), and this is causing my existing classpath to be ignored (I even added an extra cp command to the command line options, but that doesn't work either). Is there I way I can append entries to the classpath override for debug/run? I'm willing to edit the configuration files, if necessary.

The build works fine if I specify the libraries in References; however they do not get carried over to debug - which is why I want to modify the classpath.

Thank you

@sharwell
Copy link
Member

Hi @sriksrid,

Thank you for taking time to report this. I believe this was fixed in one of my experimental branches (specifically commit b2abfcd). I intend for a solution to this to be available for the next release.

@sharwell
Copy link
Member

Hi @sriksrid,

Today I separated the Java support extension from this repository to make it easier for the community to get involved with the project. I moved this issue to the new repository; you can find it at tunnelvisionlabs/JavaForVS#14. The invalid label you see just means this issue is now in the wrong repository (even though it was correct when you posted it).

Thanks again for reporting the issue, and you should see a new release very soon containing this fix. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants