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
Sort type completions differently #1100
Sort type completions differently #1100
Conversation
This small change makes it more comfortable to run the build script with additional Maven options. To do so, simply call the script like $ ADDITIONAL_MVN_OPTS="-DskipTests -U" ./build-all.sh
This limit makes sense because template proposals normally get a relevance of 90. Internally the relevance is calculated on a scale of 0 to 1000 though, to be more flexible. Fix #1002686
Test PASSed. |
MVN_ARGS="-Pscala-2.11.x -Peclipse-luna clean install" | ||
MVN_P2_ARGS="-Dtycho.localArtifacts=ignore -Pscala-2.11.x -Peclipse-luna clean verify" | ||
MVN_ARGS="-Pscala-2.11.x -Peclipse-mars $ADDITIONAL_MVN_OPTS clean install" | ||
MVN_P2_ARGS="-Dtycho.localArtifacts=ignore -Pscala-2.11.x -Peclipse-mars $ADDITIONAL_MVN_OPTS clean verify" |
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.
haha I was wonder who first loses his patience to add it. The previous solution impelled to write all options from scratch I guess
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.
Instead of the env varible you could just pass "$@"
at the end, that would forward all parameters from build-all.sh
to maven.
Cool stuff, LGTM |
Test PASSed. |
LGTM |
This PR addresses the problems explained in detail in #1002686. Note we might want to expose
ProposalRelevanceCfg
in the GUI so that users can tweak it individually in future versions. At the moment a hardcoded default configuration is used.