locationtech / locationtech/geomesa
Build CLI autocomplete functions during/after compile rather than at runtime.
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Build CLI autocomplete functions during/after compile rather than at runtime.
Maven exec plugin does not yet have a way to add compile and runtime scope deps to the classpath when executing a jar. This feature should be in version 1.6.0 when that releases.
https://github.com/mojohaus/exec-maven-plugin/issues/60
The pom code so far:
org.codehaus.mojo exec-maven-plugin 1.5.0 generate-auto-complete package exec java true runtime -classpath org.locationtech.geomesa.accumulo.tools.AccumuloRunner "help --autocomplete-function" target/autocomplete.sh
The idea here is to run Runner for the tool set being build with the "help --autocomplete-function" parameters and saving the output in a file that can then be copied to conf/. Update scripts to load autocomplete from new location.
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-1574
Key: GEOMESA-1574
Type: Improvement
Priority: Minor
Status: To Do
Resolution: Unresolved
Reporter: Austin Heyne
Created: Mon, 12 Dec 2016 14:14:02 -0500
Updated: Mon, 12 Dec 2016 14:16:26 -0500
Component(s): Command Line Tools
Parent: GEOMESA-230
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the pom configuration and the command that runs AccumuloRunner with "help --autocomplete-function"; then inspect the scripts that currently load autocomplete functions. Generate the autocomplete output during or after the build, place it in conf/, and update the scripts to load it from that location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala, shell
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100