-
Notifications
You must be signed in to change notification settings - Fork 597
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
Upgrade to Picard 2.23.3 #6717
Upgrade to Picard 2.23.3 #6717
Conversation
…ry for Picard tools".
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.
Does this mean picard tools in gatk will start accepting old style picard commands now?
Yes, it does. Would you call that a bug or a feature ? |
|
||
// Turn off the Picard legacy parser and opt in to Barclay syntax for Picard tools. This should be replaced | ||
// with a config setting once PR https://github.com/broadinstitute/gatk/pull/3447 is merged. | ||
System.setProperty("picard.useLegacyParser", "false"); |
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.
Do we actually want to allow users to run Picard tools via GATK using the legacy syntax @cmnbroad ?
I'd call it a bug since we would like to remove the legacy parser at some point but I could be convinced either way. |
I was hoping to get rid of the remaining code in Picard that supports this, but I've reverted it for now. Back to you @droazen . |
No description provided.