Make JaCaVi a product

[Fabian Rohn]

The Plugin.xml isn't the only file for configuration. A product file gives the developer the chance to specify things like About Dialogs, Splash Screens, Welcome Pages, Applicaton Icons and so on.
Furthermore it allows to export our application from the Eclipse workspace into an own Application folder with an own Executable in severeal Operation Systems.

[SVN]

New commit by frohn (revision [248]):
[Partial Fix for ticket #87] Initial product-file added

The build properties had to be adapted a bit.

[SVN]

New commit by frohn (revision [249]):
[Partial Fix for ticket #87] Added a a splash-screen and about image

[SVN]

New commit by frohn (revision [259]):
[Fix for ticket #87] Removed warnings in plugin.xml and added jre support into product file

[SVN]

New commit by frohn (revision [430]):
[Fix for ticket #87] Launch Configuration

[SVN]

New commit by hheimbuerger (revision [460]):
[Partial fix for ticket #87] Fixed bugs causing a crash in the InputDeviceSettingsDialog when the native libraries can't be loaded.

[SVN]

New commit by hheimbuerger (revision [461]):
[Partial fix for ticket #87] Added cars/ subdirectory to the build properties, so are they exported into the JACAVI.jar

[SVN]

New commit by hheimbuerger (revision [462]):
[Partial fix for ticket #87] Fixed a few issues with the product configuration.

• only the .jars are now included in the exported JACAVI.jar (but no .dll or .so)
• the product now uses a relative path (libs/) for the java.library.path property

Note: the current state expects you to manually create a libs/ directory next to the JaCaVi.exe that contains all .dll's and .so's.

[SVN]

New commit by frohn (revision [470]):
[Fix for ticket #87] Now the 'PATH' Property is also logged

[SVN]

New commit by frohn (revision [472]):
[Fix for ticket #87] PATH Logging displaced to Application startup

[SVN]

New commit by frohn (revision [474]):
[Related to ticket #87] DLL's and SO's now loaded by OSGi

We solved the problem of dependent libraries by calling System.loadLibrary(), when the application starts. We assume, that the ClassLoader? register the dll from this time on and so other dll's which depends on it have no problems anymore.

This has the effect, that we do not need to set the java.library.path and PATH in our Run Configurations anymore.

Further informations about OSGi and Native Librarys at ​http://www.rcpapps.org/articles/Eclipse2VM.html#Native_code_and_classloaders

[SVN]

New commit by frohn (revision [475]):
[Related to ticket #87] Related to the last Commit - WiiUseJ deleted

[SVN]

New commit by hheimbuerger (revision [477]):
[Partial fix for ticket #87] Removed WiiUseJ.dll. (WiiuseJ.dll is still in the repo, but they can't coexist on Windows!)

[SVN]

New commit by hheimbuerger (revision [487]):
[Partial fix for ticket #87] Removed 'no external libs' launch configuration, because this can no longer be tested that way ('accelerated' doesn't require any envvars to be set either).

[SVN]

New commit by hheimbuerger (revision [491]):
[Partial fix for ticket #87] Unified the application and project name.

The application and project name and ID is now all-around 'JaCaVi', the two exceptions are:

• the base directory is still 'JACAVI'
• all view, editor and perspective IDs are still prefixed 'JACAVI.'

Also fixed the manifest to include the native libraries under Linux.

Additionally, fixed the wiiuse preloading. (Although it doesn't work as expected on Linux.)

NOTE: the product may now be missing important plugins under Windows.

[SVN]

New commit by hheimbuerger (revision [492]):
[Partial fix for ticket #87] Unified the application and project name.

The application and project name and ID is now all-around 'JaCaVi', the two exceptions are:

• the base directory is still 'JACAVI'
• all view, editor and perspective IDs are still prefixed 'JACAVI.'

Also fixed the manifest to include the native libraries under Linux.

Additionally, fixed the wiiuse preloading. (Although it doesn't work as expected on Linux.)

NOTE: the product may now be missing important plugins under Windows.

[SVN]

New commit by hheimbuerger (revision [493]):
[Partial fix for ticket #87] Fixed the launched configurations to point to the new application/product name and removed the 'clean' launch config because it wasn't working very well anyway.

[SVN]

New commit by hheimbuerger (revision [494]):
[Partial fix for ticket #87] Modified product file to support the first successful Windows->Linux cross-build.

(And also added the presumably necessary MacOS files for good measure.)

[Henrik Heimbuerger]

Tests on MacOS were unsuccessful (#177), but the product is ready and cross-building mostly works.