-
Notifications
You must be signed in to change notification settings - Fork 308
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move to bdg-formats #280
Move to bdg-formats #280
Conversation
@@ -284,6 +283,11 @@ | |||
<dependencyManagement> | |||
<dependencies> | |||
<dependency> | |||
<groupId>org.bdgenomics.bdg-formats</groupId> | |||
<artifactId>bdg-formats</artifactId> | |||
<version>0.1.1-SNAPSHOT</version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was assuming that we'd never depend on a snapshot release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe snapshots make sense as development; definitely if I am currently modifying bdg-formats, and testing changes to ADAM, I want to use the latest.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All automated tests passed. |
@@ -17,7 +17,7 @@ | |||
*/ | |||
package org.bdgenomics.adam.cli | |||
|
|||
import org.bdgenomics.adam.avro.ADAMGenotype | |||
import org.bdgenomics.bdg_formats.avro.ADAMGenotype |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would rather just have "formats" as the namespace, "bdg_formats" is...underscore-y...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also don't like bdg_formats in the package name very much.
I thought perhaps I'd look elsewhere for guidance, and e.g. ga4gh calls its project schemas, then uses ga4gh-format as its artifactId, and just org.ga4gh for the package name. So not much help there. :)
What about org.bdgenomics.avro for the package name and bgd-formats or bgd-schemas for the artifactId and project name?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm with @carlyeks . I like 'formats' over 'bdg_formats' and submitted a pull request to change it (before I saw this comment thread).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@massie I've just merged bigdatagenomics/bdg-formats#7 and will update this PR as soon as the new snapshot is pushed.
I've updated this after @massie's PR to change the bdg-formats path from bdg_formats to formats. Additionally, I've made a few changes to clean up build warnings. |
All automated tests passed. |
Ping... |
Carl and I are checking this out right now -- but can you rebase off of master? |
Consider it done @tdanford! |
@fnothaft how would you feel, about splitting out the two sets of changes here into two PRs?
|
All automated tests passed. |
…pom.xmls for bdg-formats move.
I've just split out the cleanup; I'll rebase that and open a new PR once this merges. |
All automated tests passed. |
Glad to see we've finally moved over. Thanks, @fnothaft! |
Deletes the adam-format module, and moves the project to build off of the bdg-formats project.