lawrie wrote:It is not very clear what you are trying to do from your description.
I want my EV3 project to deploy from my PC to the EV3 and run on the unit as per normal, but also to specify the args to the main method, and it would need to access classes in external jar file.
If you have requirements for deployment that are not supported by the Eclipse plugin, the best thing to do is to write an ant build file. That can do whatever you want, including using scp and ssh tasks.
Ok, that might be the way to go. How do I create that? Or can I just copy a sample one into my project?
However, it looks like you are using the Eclipse export to export a runnable jar file. I have not tried that, and I don't know if anyone else has, but it should be possible to make it work.
Isn't that what is done as standard?
One issue is that a launch configuration file is needed. The leJOS Eclipse plugin uses a custom launch configuration file that has different options to the normal Java launch configuration, and does not include run time parameters or class path entries. However, you can create a normal Java launch configuration and use that.
How would the package be deployed to the EV3 in this case?
I don't know what you mean by "Eclipse does not use the manifest file". I think the issue with parameters is that the manifest file of Java runnable jar files does not support them. You will need to find a different solution for parameters, depending on how you plan to run your application.
Although there are options in eclipse for creating a custom manifest file, in which I put arguments, this seems to be ignored and the old one is still gererated.