Details
-
Type: Task
-
Status: Closed (View Workflow)
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:0.25
-
Epic Link:
-
Sprint:Fall 3: Oct 12 - Oct 23
Description
IGB project uses JFlow library to display clickable genome version shortcut images on the IGB home screen. The IGB build process retrieves the JFlow artifact (a conventional jar file) from https://maven.bioviz.org/repo2, managed by us. It then wraps it into a larger bundle along with some other non-OSGi jar files, which exports its packages.
This is working fine, but we would also like to reduce our costs and make our project simpler. Toward this end, we would like to instead retrieve JFlow from a public repository used by many people, for greater longevity.
However, the JFlow artifact is not currently available in maven central.
For this task, export the JFlow code into a new bitbucket repository, preserving all the history of the project.
Reviewers:
- Please check that all files were migrated
- Please check that history is preserved for the files.
Attachments
Issue Links
Activity
Field | Original Value | New Value |
---|---|---|
Epic Link | IGBF-1531 [ 17617 ] |
Assignee | Ann Loraine [ aloraine ] |
Description |
Import JFlow code from github to bitbucket, preserving project history.
|
IGB project uses JFlow library to display clickable genome version shortcut images on the IGB home screen. The IGB build process retrieves the JFlow artifact (a conventional jar file) from https://maven.bioviz.org/repo2, managed by us. It then wraps it into a larger bundle along with some other non-OSGi jar files, which exports its packages.
This is working fine, but we would also like to reduce our costs and make our project simpler. Toward this end, we would like to instead retrieve JFlow from a public repository used by many people, for greater longevity. However, the JFlow artifact is not currently available in maven central. For this task, export the JFlow code into a new bitbucket repository, preserving all the history of the project. Reviewers: * Please check that all files were migrated * Please check that history is preserved for the files. |
Assignee | Sai Supreeth Segu [ ssegu ] |
Status | To-Do [ 10305 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
Assignee | Sai Supreeth Segu [ ssegu ] |
Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
Assignee | Sai Supreeth Segu [ ssegu ] |
Status | To-Do [ 10305 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
Assignee | Sai Supreeth Segu [ ssegu ] |
Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
Assignee | Sai Supreeth Segu [ ssegu ] |
Status | To-Do [ 10305 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
Assignee | Sai Supreeth Segu [ ssegu ] |
Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
Status | First Level Review in Progress [ 10301 ] | Needs 1st Level Review [ 10005 ] |
Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
Status | First Level Review in Progress [ 10301 ] | Ready for Pull Request [ 10304 ] |
Status | Ready for Pull Request [ 10304 ] | Pull Request Submitted [ 10101 ] |
Status | Pull Request Submitted [ 10101 ] | Reviewing Pull Request [ 10303 ] |
Status | Reviewing Pull Request [ 10303 ] | Merged Needs Testing [ 10002 ] |
Status | Merged Needs Testing [ 10002 ] | Post-merge Testing In Progress [ 10003 ] |
Resolution | Done [ 10000 ] | |
Status | Post-merge Testing In Progress [ 10003 ] | Closed [ 6 ] |
[~aloraine] Do I need to create the repository public or private and also do I need to add pom.xml as well used for publishing repository to Maven Central?