| Summary: | Command line metaVar NLS not working | ||
|---|---|---|---|
| Product: | [Technology] JGit | Reporter: | Robin Rosenberg <robin.rosenberg> |
| Component: | JGit | Assignee: | Project Inbox <jgit.core-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | caniszczyk, sop |
| Version: | unspecified | ||
| Target Milestone: | 1.1 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | 329136 | ||
| Bug Blocks: | |||
|
Description
Robin Rosenberg
I think this has already been fixed. diff was just an example. Diff operates without args so it does not display the message, but here is another $ ./org.eclipse.jgit.pgm/target/jgit clone fatal: Argument "metaVar_uriish" is required $ ./org.eclipse.jgit.pgm/target/jgit rm fatal: Argument "metaVar_path" is required and so on The problem here is in args4j. Its formatting the error message without allowing the metaVar property in the @Argument or @Option annotation to be resolved through the property bundle. We need to upgrade args4j to fix this bug. We might need to patch this upstream in args4j first too. :) 2.0.12 is the latest and that's what we have... nothing released since 2009... Then we'll have to patch it, and see if upstream will take it. Or face a fork. Fixed in I05d4ecf6bd25deec7fb2efbfa61913f4ec4e04e5 |