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

Possibility to access internal command line ? #5

Closed
DrDaleks opened this Issue Feb 19, 2012 · 5 comments

Comments

Projects
None yet
2 participants
@DrDaleks
Copy link

DrDaleks commented Feb 19, 2012

If you work on one of the libraries included in icy4eclipse's path, there can be a conflict between your eclipse code (in Run or Debug mode) and the "official" jar currently residing in the Icy installation (used in "Update" mode).
To avoid the conflict, I tried removing the official jar file to leave only my "live" code, but then you can't run Icy anymore (icy4eclipse fails saying the jar file is missing).
Right now as a workaround I replaced the "official" jar file by an empty file with same name. But would it be possible to access icy4eclipse's launch command line to remove the reference to the library I work on ?

Thx !

@nrv

This comment has been minimized.

Copy link
Owner

nrv commented Feb 20, 2012

Which jar ?

@DrDaleks

This comment has been minimized.

Copy link
Author

DrDaleks commented Feb 20, 2012

In my case it's EzPlug, but it could just as well be anyone from the kernel...

@nrv

This comment has been minimized.

Copy link
Owner

nrv commented Feb 20, 2012

The launch command line is generated dynamically at each start. I would rather add a field in the main Icy preferences panel where you could add as many jar files as you wish that will be ignored and not added to the classpath. In fact it would act exactly as the "load icy.jar" check box.

@nrv

This comment has been minimized.

Copy link
Owner

nrv commented Feb 21, 2012

The problem appears because you have in your workbench both the EzPlug dev project and at least a plugin dev project that refers to the .jar file instead of the EzPlug eclipse project directly. I had the same issue with my toolbox and prefered to have all my plugins pointing to the eclipse project so as to see immediately any impact on the plugins that a modification in the toolbox may induce. I'll add the option to bypass the loading of any given .jar file but I'm not convinced this is the best way to work on a toolbox.

nrv added a commit that referenced this issue Feb 21, 2012

@nrv

This comment has been minimized.

Copy link
Owner

nrv commented Feb 21, 2012

Update to version 0.3.4 and have a look at the documentation : http://www.herve.name/pmwiki.php/Main/Icy4Eclipse

@nrv nrv closed this Feb 21, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.