Details
-
Type: Epic
-
Status: Closed (View Workflow)
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 10.0.0 Major Release
-
Labels:None
-
Epic Name:Implement r6 Annotations in IGB
Description
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit.
Development Workflow:
- Make or pick a ticket representing work on updating a module or set of modules. Assign it to yourself.
- Branch from the latest tip of main-JDK8-r6 (as usual) to create a topic branch for this task.
- Make code changes to new OSGI annotations.
- Delete the .m2 folder
- Delete the .igb folder (appData/igb folder on Windows).
- Run mvn clean install (Do not skip tests).
- If any test fails, do not commit changes to any branch. Instead, (1) create a new ticket documenting the error and (2) discard the changes on your local system. Later either you or someone else will attempt investigate.
- Start IGB, check log/standard output for any warnings/errors.
- If there are relevant warnings/errors make a new ticket, do not commit changes to branch. (See 6.)
- Check the Felix Web Console in your browser (link).
- If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. (See 6.)
- Click on the Arabidopsis genome.
- Test the individual module functionality. See "smoke testing documentation" for how to test a module.
- If unclear as to how to test module functionality, ask Dr. Loraine.
- If module functionality appears to be broken, make a new ticket, do not commit changes to branch. (See 6.)
- Reset preferences to default; doing this will quit IGB.
- Commit change for that specific module to your topic branch. Format your commit message following this example: Update annotations for Plugin - Graph Tab. Each module should be modified in a single commit.
- Push branch to your fork.
- Mark the module as completed below.
Git:
Branch: https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6
Create a pull request from your branch to main-JDK8-r6
Reference:
Smoke testing documentation: https://wiki.bioviz.org/confluence/display/ITD/How+to+test+-+read+this+first
Attachments
Activity
Nowlan Freese
created issue -
Nowlan Freese
made changes -
Field | Original Value | New Value |
---|---|---|
Epic Child |
|
Nowlan Freese
made changes -
Summary | stub | Implement r6 Annotations in IGB |
Nowlan Freese
made changes -
Description | Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB. |
Nowlan Freese
made changes -
Description | Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB. |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. Workflow: # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). # If any test fails, make a new ticket, do not commit changes to branch. # Start IGB, check log/standard output for any warnings/errors. If there are relevant warnings/errors make a new ticket, do not commit changes to branch. # Check the Felix Web Console in your browser (http://localhost:7080/system/console/bundles#). If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. # Click on the Arabidopsis genome. # Test the individual module functionality. # Reset preferences to default when closing IGB. # Commit change for that specific module using the following example: Update annotations for Plugin - Graph Tab # Push commit to your branch |
Nowlan Freese
made changes -
Description |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. Workflow: # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). # If any test fails, make a new ticket, do not commit changes to branch. # Start IGB, check log/standard output for any warnings/errors. If there are relevant warnings/errors make a new ticket, do not commit changes to branch. # Check the Felix Web Console in your browser (http://localhost:7080/system/console/bundles#). If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. # Click on the Arabidopsis genome. # Test the individual module functionality. # Reset preferences to default when closing IGB. # Commit change for that specific module using the following example: Update annotations for Plugin - Graph Tab # Push commit to your branch |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. Workflow: # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). # If any test fails, make a new ticket, do not commit changes to branch. # Start IGB, check log/standard output for any warnings/errors. If there are relevant warnings/errors make a new ticket, do not commit changes to branch. # Check the Felix Web Console in your browser (http://localhost:7080/system/console/bundles#). If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. # Click on the Arabidopsis genome. # Test the individual module functionality. # Reset preferences to default when closing IGB. # Commit change for that specific module using the following example: Update annotations for Plugin - Graph Tab # Push commit to your branch. # Mark the module as completed below. |
Nowlan Freese
made changes -
Description |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. Workflow: # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). # If any test fails, make a new ticket, do not commit changes to branch. # Start IGB, check log/standard output for any warnings/errors. If there are relevant warnings/errors make a new ticket, do not commit changes to branch. # Check the Felix Web Console in your browser (http://localhost:7080/system/console/bundles#). If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. # Click on the Arabidopsis genome. # Test the individual module functionality. # Reset preferences to default when closing IGB. # Commit change for that specific module using the following example: Update annotations for Plugin - Graph Tab # Push commit to your branch. # Mark the module as completed below. |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. Workflow: # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). ## If any test fails, make a new ticket, do not commit changes to branch. # Start IGB, check log/standard output for any warnings/errors. ## If there are relevant warnings/errors make a new ticket, do not commit changes to branch. # Check the Felix Web Console in your browser (http://localhost:7080/system/console/bundles#). ## If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. # Click on the Arabidopsis genome. # Test the individual module functionality. ## If unclear as to how to test module functionality, ask Dr. Loraine. ## If module functionality appears to be broken, make a new ticket, do not commit changes to branch. # Reset preferences to default when closing IGB. # Commit change for that specific module using the following example: Update annotations for Plugin - Graph Tab # Push commit to your branch. # Mark the module as completed below. |
Nowlan Freese
made changes -
Description |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. Workflow: # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). ## If any test fails, make a new ticket, do not commit changes to branch. # Start IGB, check log/standard output for any warnings/errors. ## If there are relevant warnings/errors make a new ticket, do not commit changes to branch. # Check the Felix Web Console in your browser (http://localhost:7080/system/console/bundles#). ## If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. # Click on the Arabidopsis genome. # Test the individual module functionality. ## If unclear as to how to test module functionality, ask Dr. Loraine. ## If module functionality appears to be broken, make a new ticket, do not commit changes to branch. # Reset preferences to default when closing IGB. # Commit change for that specific module using the following example: Update annotations for Plugin - Graph Tab # Push commit to your branch. # Mark the module as completed below. |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. Workflow: # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). ## If any test fails, make a new ticket, do not commit changes to branch. # Start IGB, check log/standard output for any warnings/errors. ## If there are relevant warnings/errors make a new ticket, do not commit changes to branch. # Check the Felix Web Console in your browser ([link|http://localhost:7080/system/console/bundles#]). ## If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. # Click on the Arabidopsis genome. # Test the individual module functionality. ## If unclear as to how to test module functionality, ask Dr. Loraine. ## If module functionality appears to be broken, make a new ticket, do not commit changes to branch. # Reset preferences to default when closing IGB. # Commit change for that specific module using the following example: Update annotations for Plugin - Graph Tab # Push commit to your branch. # Mark the module as completed below. |
Nowlan Freese
made changes -
Description |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. Workflow: # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). ## If any test fails, make a new ticket, do not commit changes to branch. # Start IGB, check log/standard output for any warnings/errors. ## If there are relevant warnings/errors make a new ticket, do not commit changes to branch. # Check the Felix Web Console in your browser ([link|http://localhost:7080/system/console/bundles#]). ## If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. # Click on the Arabidopsis genome. # Test the individual module functionality. ## If unclear as to how to test module functionality, ask Dr. Loraine. ## If module functionality appears to be broken, make a new ticket, do not commit changes to branch. # Reset preferences to default when closing IGB. # Commit change for that specific module using the following example: Update annotations for Plugin - Graph Tab # Push commit to your branch. # Mark the module as completed below. |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. Workflow: # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). ## If any test fails, make a new ticket, do not commit changes to branch. # Start IGB, check log/standard output for any warnings/errors. ## If there are relevant warnings/errors make a new ticket, do not commit changes to branch. # Check the Felix Web Console in your browser ([link|http://localhost:7080/system/console/bundles#]). ## If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. # Click on the Arabidopsis genome. # Test the individual module functionality. ## If unclear as to how to test module functionality, ask Dr. Loraine. ## If module functionality appears to be broken, make a new ticket, do not commit changes to branch. # Reset preferences to default when closing IGB. # Commit change for that specific module using the following example: Update annotations for Plugin - Graph Tab # Push commit to your branch. # Mark the module as completed below. |
Nowlan Freese
made changes -
Description |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. Workflow: # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). ## If any test fails, make a new ticket, do not commit changes to branch. # Start IGB, check log/standard output for any warnings/errors. ## If there are relevant warnings/errors make a new ticket, do not commit changes to branch. # Check the Felix Web Console in your browser ([link|http://localhost:7080/system/console/bundles#]). ## If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. # Click on the Arabidopsis genome. # Test the individual module functionality. ## If unclear as to how to test module functionality, ask Dr. Loraine. ## If module functionality appears to be broken, make a new ticket, do not commit changes to branch. # Reset preferences to default when closing IGB. # Commit change for that specific module using the following example: Update annotations for Plugin - Graph Tab # Push commit to your branch. # Mark the module as completed below. |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. Workflow: # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). ## If any test fails, make a new ticket, do not commit changes to branch. # Start IGB, check log/standard output for any warnings/errors. ## If there are relevant warnings/errors make a new ticket, do not commit changes to branch. # Check the Felix Web Console in your browser ([link|http://localhost:7080/system/console/bundles#]). ## If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. # Click on the Arabidopsis genome. # Test the individual module functionality. ## If unclear as to how to test module functionality, ask Dr. Loraine. ## If module functionality appears to be broken, make a new ticket, do not commit changes to branch. # Reset preferences to default when closing IGB. # Commit change for that specific module using the following example: Update annotations for Plugin - Graph Tab # Push commit to your branch. # Mark the module as completed below. Git: Branch: https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6 Once you have completed the above workflow steps for a module(s), create a pull request from your branch to [main-JDK8-r6|https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6] |
Nowlan Freese
made changes -
Description |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. Workflow: # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). ## If any test fails, make a new ticket, do not commit changes to branch. # Start IGB, check log/standard output for any warnings/errors. ## If there are relevant warnings/errors make a new ticket, do not commit changes to branch. # Check the Felix Web Console in your browser ([link|http://localhost:7080/system/console/bundles#]). ## If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. # Click on the Arabidopsis genome. # Test the individual module functionality. ## If unclear as to how to test module functionality, ask Dr. Loraine. ## If module functionality appears to be broken, make a new ticket, do not commit changes to branch. # Reset preferences to default when closing IGB. # Commit change for that specific module using the following example: Update annotations for Plugin - Graph Tab # Push commit to your branch. # Mark the module as completed below. Git: Branch: https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6 Once you have completed the above workflow steps for a module(s), create a pull request from your branch to [main-JDK8-r6|https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6] |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. Workflow: # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). ## If any test fails, make a new ticket, do not commit changes to branch. # Start IGB, check log/standard output for any warnings/errors. ## If there are relevant warnings/errors make a new ticket, do not commit changes to branch. # Check the Felix Web Console in your browser ([link|http://localhost:7080/system/console/bundles#]). ## If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. # Click on the Arabidopsis genome. # Test the individual module functionality. ## If unclear as to how to test module functionality, ask Dr. Loraine. ## If module functionality appears to be broken, make a new ticket, do not commit changes to branch. # Reset preferences to default when closing IGB. # Commit change for that specific module using the following example: Update annotations for Plugin - Graph Tab # Push commit to your branch. # Mark the module as completed below. Git: Branch: https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6 Create a pull request from your branch to [main-JDK8-r6|https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6] |
Karthik Raveendran
made changes -
Epic Child |
|
Karthik Raveendran
made changes -
Epic Child |
|
Karthik Raveendran
made changes -
Epic Child |
|
Ann Loraine
made changes -
Description |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. Workflow: # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). ## If any test fails, make a new ticket, do not commit changes to branch. # Start IGB, check log/standard output for any warnings/errors. ## If there are relevant warnings/errors make a new ticket, do not commit changes to branch. # Check the Felix Web Console in your browser ([link|http://localhost:7080/system/console/bundles#]). ## If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. # Click on the Arabidopsis genome. # Test the individual module functionality. ## If unclear as to how to test module functionality, ask Dr. Loraine. ## If module functionality appears to be broken, make a new ticket, do not commit changes to branch. # Reset preferences to default when closing IGB. # Commit change for that specific module using the following example: Update annotations for Plugin - Graph Tab # Push commit to your branch. # Mark the module as completed below. Git: Branch: https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6 Create a pull request from your branch to [main-JDK8-r6|https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6] |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. Workflow: # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). ## If any test fails, make a new ticket, do not commit changes to branch. # Start IGB, check log/standard output for any warnings/errors. ## If there are relevant warnings/errors make a new ticket, do not commit changes to branch. # Check the Felix Web Console in your browser ([link|http://localhost:7080/system/console/bundles#]). ## If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. # Click on the Arabidopsis genome. # Test the individual module functionality. ## If unclear as to how to test module functionality, ask Dr. Loraine. ## If module functionality appears to be broken, make a new ticket, do not commit changes to branch. # Reset preferences to default when closing IGB. # Commit change for that specific module using the following example: Update annotations for Plugin - Graph Tab # Push commit to your branch. # Mark the module as completed below. Git: Branch: https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6 Create a pull request from your branch to [main-JDK8-r6|https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6] **Reference:** Smoke testing documentation: https://wiki.bioviz.org/confluence/display/ITD/How+to+test+-+read+this+first |
Ann Loraine
made changes -
Description |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. Workflow: # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). ## If any test fails, make a new ticket, do not commit changes to branch. # Start IGB, check log/standard output for any warnings/errors. ## If there are relevant warnings/errors make a new ticket, do not commit changes to branch. # Check the Felix Web Console in your browser ([link|http://localhost:7080/system/console/bundles#]). ## If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. # Click on the Arabidopsis genome. # Test the individual module functionality. ## If unclear as to how to test module functionality, ask Dr. Loraine. ## If module functionality appears to be broken, make a new ticket, do not commit changes to branch. # Reset preferences to default when closing IGB. # Commit change for that specific module using the following example: Update annotations for Plugin - Graph Tab # Push commit to your branch. # Mark the module as completed below. Git: Branch: https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6 Create a pull request from your branch to [main-JDK8-r6|https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6] **Reference:** Smoke testing documentation: https://wiki.bioviz.org/confluence/display/ITD/How+to+test+-+read+this+first |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. Workflow: # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). ## If any test fails, make a new ticket, do not commit changes to branch. # Start IGB, check log/standard output for any warnings/errors. ## If there are relevant warnings/errors make a new ticket, do not commit changes to branch. # Check the Felix Web Console in your browser ([link|http://localhost:7080/system/console/bundles#]). ## If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. # Click on the Arabidopsis genome. # Test the individual module functionality. ## If unclear as to how to test module functionality, ask Dr. Loraine. ## If module functionality appears to be broken, make a new ticket, do not commit changes to branch. # Reset preferences to default when closing IGB. # Commit change for that specific module using the following example: Update annotations for Plugin - Graph Tab # Push commit to your branch. # Mark the module as completed below. Git: Branch: https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6 Create a pull request from your branch to [main-JDK8-r6|https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6] *Reference:* Smoke testing documentation: https://wiki.bioviz.org/confluence/display/ITD/How+to+test+-+read+this+first |
Ann Loraine
made changes -
Description |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. Workflow: # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). ## If any test fails, make a new ticket, do not commit changes to branch. # Start IGB, check log/standard output for any warnings/errors. ## If there are relevant warnings/errors make a new ticket, do not commit changes to branch. # Check the Felix Web Console in your browser ([link|http://localhost:7080/system/console/bundles#]). ## If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. # Click on the Arabidopsis genome. # Test the individual module functionality. ## If unclear as to how to test module functionality, ask Dr. Loraine. ## If module functionality appears to be broken, make a new ticket, do not commit changes to branch. # Reset preferences to default when closing IGB. # Commit change for that specific module using the following example: Update annotations for Plugin - Graph Tab # Push commit to your branch. # Mark the module as completed below. Git: Branch: https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6 Create a pull request from your branch to [main-JDK8-r6|https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6] *Reference:* Smoke testing documentation: https://wiki.bioviz.org/confluence/display/ITD/How+to+test+-+read+this+first |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. * Development Workflow:* # Make or pick a ticket representing work on updating a module or set of modules. Assign it to yourself. # Branch from the latest tip of main-JDK8-r6 (as usual) to create a topic branch for this task. # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). ## If any test fails, do not commit changes to any branch. Instead, (1) create a new ticket documenting the error and (2) discard the changes on your local system. Later either you or someone else will attempt investigate. # Start IGB, check log/standard output for any warnings/errors. ## If there are relevant warnings/errors make a new ticket, do not commit changes to branch. (See previous instruction.) # Check the Felix Web Console in your browser ([link|http://localhost:7080/system/console/bundles#]). ## If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. (See previous instruction.) # Click on the Arabidopsis genome. # Test the individual module functionality. (See "[smoke testing documentation|https://wiki.bioviz.org/confluence/display/ITD/How+to+test+-+read+this+first]" for how to test a module.) ## If unclear as to how to test module functionality, ask Dr. Loraine. ## If module functionality appears to be broken, make a new ticket, do not commit changes to branch. (See previous instruction.) # Reset preferences to default; doing this will quit IGB. # Commit change for that specific module to your topic branch. Format your commit message following this example: Update annotations for Plugin - Graph Tab. Each module should be modified in a single commit. # Push branch to your fork. # Mark the module as completed below. Git: Branch: https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6 Create a pull request from your branch to [main-JDK8-r6|https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6] *Reference:* Smoke testing documentation: https://wiki.bioviz.org/confluence/display/ITD/How+to+test+-+read+this+first |
Ann Loraine
made changes -
Description |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. * Development Workflow:* # Make or pick a ticket representing work on updating a module or set of modules. Assign it to yourself. # Branch from the latest tip of main-JDK8-r6 (as usual) to create a topic branch for this task. # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). ## If any test fails, do not commit changes to any branch. Instead, (1) create a new ticket documenting the error and (2) discard the changes on your local system. Later either you or someone else will attempt investigate. # Start IGB, check log/standard output for any warnings/errors. ## If there are relevant warnings/errors make a new ticket, do not commit changes to branch. (See previous instruction.) # Check the Felix Web Console in your browser ([link|http://localhost:7080/system/console/bundles#]). ## If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. (See previous instruction.) # Click on the Arabidopsis genome. # Test the individual module functionality. (See "[smoke testing documentation|https://wiki.bioviz.org/confluence/display/ITD/How+to+test+-+read+this+first]" for how to test a module.) ## If unclear as to how to test module functionality, ask Dr. Loraine. ## If module functionality appears to be broken, make a new ticket, do not commit changes to branch. (See previous instruction.) # Reset preferences to default; doing this will quit IGB. # Commit change for that specific module to your topic branch. Format your commit message following this example: Update annotations for Plugin - Graph Tab. Each module should be modified in a single commit. # Push branch to your fork. # Mark the module as completed below. Git: Branch: https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6 Create a pull request from your branch to [main-JDK8-r6|https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6] *Reference:* Smoke testing documentation: https://wiki.bioviz.org/confluence/display/ITD/How+to+test+-+read+this+first |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. *Development Workflow:* # Make or pick a ticket representing work on updating a module or set of modules. Assign it to yourself. # Branch from the latest tip of main-JDK8-r6 (as usual) to create a topic branch for this task. # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). ## If any test fails, do not commit changes to any branch. Instead, (1) create a new ticket documenting the error and (2) discard the changes on your local system. Later either you or someone else will attempt investigate. # Start IGB, check log/standard output for any warnings/errors. ## If there are relevant warnings/errors make a new ticket, do not commit changes to branch. (See previous instruction.) # Check the Felix Web Console in your browser ([link|http://localhost:7080/system/console/bundles#]). ## If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. (See previous instruction.) # Click on the Arabidopsis genome. # Test the individual module functionality. (See "[smoke testing documentation|https://wiki.bioviz.org/confluence/display/ITD/How+to+test+-+read+this+first]" for how to test a module.) ## If unclear as to how to test module functionality, ask Dr. Loraine. ## If module functionality appears to be broken, make a new ticket, do not commit changes to branch. (See previous instruction.) # Reset preferences to default; doing this will quit IGB. # Commit change for that specific module to your topic branch. Format your commit message following this example: Update annotations for Plugin - Graph Tab. Each module should be modified in a single commit. # Push branch to your fork. # Mark the module as completed below. Git: Branch: https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6 Create a pull request from your branch to [main-JDK8-r6|https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6] *Reference:* Smoke testing documentation: https://wiki.bioviz.org/confluence/display/ITD/How+to+test+-+read+this+first |
Ann Loraine
made changes -
Description |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. *Development Workflow:* # Make or pick a ticket representing work on updating a module or set of modules. Assign it to yourself. # Branch from the latest tip of main-JDK8-r6 (as usual) to create a topic branch for this task. # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). ## If any test fails, do not commit changes to any branch. Instead, (1) create a new ticket documenting the error and (2) discard the changes on your local system. Later either you or someone else will attempt investigate. # Start IGB, check log/standard output for any warnings/errors. ## If there are relevant warnings/errors make a new ticket, do not commit changes to branch. (See previous instruction.) # Check the Felix Web Console in your browser ([link|http://localhost:7080/system/console/bundles#]). ## If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. (See previous instruction.) # Click on the Arabidopsis genome. # Test the individual module functionality. (See "[smoke testing documentation|https://wiki.bioviz.org/confluence/display/ITD/How+to+test+-+read+this+first]" for how to test a module.) ## If unclear as to how to test module functionality, ask Dr. Loraine. ## If module functionality appears to be broken, make a new ticket, do not commit changes to branch. (See previous instruction.) # Reset preferences to default; doing this will quit IGB. # Commit change for that specific module to your topic branch. Format your commit message following this example: Update annotations for Plugin - Graph Tab. Each module should be modified in a single commit. # Push branch to your fork. # Mark the module as completed below. Git: Branch: https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6 Create a pull request from your branch to [main-JDK8-r6|https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6] *Reference:* Smoke testing documentation: https://wiki.bioviz.org/confluence/display/ITD/How+to+test+-+read+this+first |
Situation: In order to update the maven-bundle-plugin update to be compatible with JDK 11 we need to implement the new r6 declarative service component annotations in IGB.
Task: Update each module (core/plugin) in IGB to use the new annotations (see comments below). Each updated module should be its own commit. *Development Workflow:* # Make or pick a ticket representing work on updating a module or set of modules. Assign it to yourself. # Branch from the latest tip of main-JDK8-r6 (as usual) to create a topic branch for this task. # Make code changes to new OSGI annotations. # Delete the .m2 folder # Delete the .igb folder (appData/igb folder on Windows). # Run mvn clean install (Do not skip tests). ## If any test fails, do not commit changes to any branch. Instead, (1) create a new ticket documenting the error and (2) discard the changes on your local system. Later either you or someone else will attempt investigate. # Start IGB, check log/standard output for any warnings/errors. ## If there are relevant warnings/errors make a new ticket, do not commit changes to branch. (See 6.) # Check the Felix Web Console in your browser ([link|http://localhost:7080/system/console/bundles#]). ## If any bundles are listed as fragments/installed then make a new ticket, do not commit changes to branch. (See 6.) # Click on the Arabidopsis genome. # Test the individual module functionality. See "[smoke testing documentation|https://wiki.bioviz.org/confluence/display/ITD/How+to+test+-+read+this+first]" for how to test a module. ## If unclear as to how to test module functionality, ask Dr. Loraine. ## If module functionality appears to be broken, make a new ticket, do not commit changes to branch. (See 6.) # Reset preferences to default; doing this will quit IGB. # Commit change for that specific module to your topic branch. Format your commit message following this example: Update annotations for Plugin - Graph Tab. Each module should be modified in a single commit. # Push branch to your fork. # Mark the module as completed below. Git: Branch: https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6 Create a pull request from your branch to [main-JDK8-r6|https://bitbucket.org/lorainelab/integrated-genome-browser/commits/branch/main-JDK8-r6] *Reference:* Smoke testing documentation: https://wiki.bioviz.org/confluence/display/ITD/How+to+test+-+read+this+first |
Kaushik Gopu
made changes -
Epic Child |
|
Kaushik Gopu
made changes -
Status | To-Do [ 10305 ] | In Progress [ 3 ] |
Kaushik Gopu
made changes -
Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
Kaushik Gopu
made changes -
Epic Child |
|
Nowlan Freese
made changes -
Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
Nowlan Freese
made changes -
Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
Nowlan Freese
made changes -
Epic Child |
|
Nowlan Freese
made changes -
Comment |
[ Moving to first level review.
pull [this|https://bitbucket.org/kaushik-gopu/kgopu_integrated-genome-browser/branch/IGBF-3411] branch in order to test. ] |
Nowlan Freese
made changes -
Epic Child |
|
Karthik Raveendran
made changes -
Epic Child |
|
Karthik Raveendran
made changes -
Epic Child |
|
Nowlan Freese
made changes -
Epic Child |
|
Nowlan Freese
made changes -
Epic Child |
|
Nowlan Freese
made changes -
Status | To-Do [ 10305 ] | In Progress [ 3 ] |
Nowlan Freese
made changes -
Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
Nowlan Freese
made changes -
Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
Nowlan Freese
made changes -
Status | First Level Review in Progress [ 10301 ] | Needs 1st Level Review [ 10005 ] |
Nowlan Freese
made changes -
Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
Nowlan Freese
made changes -
Status | First Level Review in Progress [ 10301 ] | Ready for Pull Request [ 10304 ] |
Nowlan Freese
made changes -
Status | Ready for Pull Request [ 10304 ] | Pull Request Submitted [ 10101 ] |
Nowlan Freese
made changes -
Status | Pull Request Submitted [ 10101 ] | Reviewing Pull Request [ 10303 ] |
Nowlan Freese
made changes -
Status | Reviewing Pull Request [ 10303 ] | Merged Needs Testing [ 10002 ] |
Nowlan Freese
made changes -
Status | Merged Needs Testing [ 10002 ] | Post-merge Testing In Progress [ 10003 ] |
Nowlan Freese
made changes -
Resolution | Done [ 10000 ] | |
Status | Post-merge Testing In Progress [ 10003 ] | Closed [ 6 ] |
Paige Kulzer
made changes -
Fix Version/s | 10.0.0 Major Release [ 10900 ] |
'multiple = true, optional = false' :: cardinality = ReferenceCardinality.AT_LEAST_ONE
'multiple=false & optional = true' :: cardinality = ReferenceCardinality.OPTIONAL
'multiple = true' :: cardinality = ReferenceCardinality.AT_LEAST_ONE
'optional=false' :: cardinality = ReferenceCardinality.MANDATORY
'dynamic = true' :: policy = ReferencePolicy.DYNAMIC