Contact uk.ac.imperial.glycosciences.glycanarray developers

[ReneRanzinger]

No description provided.

[ReneRanzinger]

Dear Yukie,

I hope you are doing well. Recently, we have decided to move the GRITS Toolbox source code into the public domain and make it open source. For this purpose, we create a public GitHub organization that hosts all plugin and bundle repositories:

https://github.com/GritsToolbox

As part of this migration to GitHub, we also migrated to a recent Java (JDK 17) and Eclipse version (2022-06: 4.24). Please note that this migration was done for the GitHub code only, the SVN code is not affected. Also note that we have not migrated your source code. You will have to decide what to do (see below).

What you should do:

1. Make a backup of your current code including all GRITS code (either from your Workspace or from the entire SVN).
2. Download and install the new Java + Eclipse versions. Documentation can be found here: https://github.com/GritsToolbox/org.grits.toolbox/wiki/Java-and-Eclipse-setup
3. Start Eclipse by creating a new empty workspace.
4. Download and import the source code for GRITS from GitHub into the workspace. Documentation can be found here: https://github.com/GritsToolbox/org.grits.toolbox/wiki/Source-code-development
5. Add your plugin to the workspace.

There will probably be a few errors in your code related to the migration to Java 17. They can be fixed by adding the corresponding dependencies. If you run into issues, please let us know and we can try to help you. There are also instructions how to make a build with the new Eclipse and Java version. Documentation can be found here:
https://github.com/GritsToolbox/org.grits.toolbox/wiki/Building-GRITS-Toolbox

Lastly you need to decide what happens with your plugin. Mid term we will discontinue the SVN source code repository. Here are a few options:

1. If you are ready to make your code open source, we can host it as part of the public GitHub GRITS Toolbox organization and make you a member of the organization.
2. Alternatively, if you prefer to have the code associated with you, you can also create your own public GitHub repository under your account.
3. If you are not ready/willing to go open source, you can create a private GitHub repository under your account. Only you and invited collaborators will have access to the code.

Please let us know what you decide and if you need help or have any questions.

Best,
René & Sena