That's was quick answers.
* why not have a new slick project directly?
* Eclipse Helios works fine?
* your plugin works with Eclipse Galileo ?
I did this plugin in my last internship 2 days (because I haven't any work to do...
). So I do something simple, make a complete slick project would be maybe harder to do, and need more time. Sorry I compiled the plugin for Eclpse 3.6 Helios. You can maybe compile it to make it work with Galileo but I thing than go to Helios is better.
That is *very* handy. That would especially be very handy for new users. I'd be interested in having that plugin and seeing how it was done.
The plugin and the project source code are here:
To use the project with Ecplise, you must have the framework associated to plugin development (Help -> install new Feature -> Eclipse Platform SDK and Eclipse Platform, didn't remember well but you must have plugin development environment).
The project is of type: Plug-in Project
Now about the other directory (plugins) it contain the plugin jar and the resources (slick_plugin_resources). Both should be copy into your Eclipse plugins directory and Eclipse should be launched with the -clean command to install the plugin.
Example: C:\Program Files\Eclipse\eclipse.exe -clean
When transform a Java standard project into a Slick project the plugin is looking into the slick_plugin_resources, himself into your plugins directory. So to update lwjgl release or others jar you just need to replace them into the good directory in slick_plugin_resources.
That's also mean that you can add your own jar. The plugin catch all the file in the directory. The same thing for the generated directory, the plugin catch all file in core/states and utils directory, so you can add your own class, they will be added when using the plugin.
Pfiou lot of word