[
https://issues.apache.org/jira/browse/CASSANDRA-20130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905310#comment-17905310
]
Michael Semb Wever commented on CASSANDRA-20130:
------------------------------------------------
bq. your other comment above, what is the concern with churn? is it that we
have to maintain that file? fwiw, using an older release of a specific version
isn't generally a problem for development
yeah, it encourages maintenance and ongoing edits to the file. while it's not
a problem to specify an out-of-date jdk patch version, that's going to annoy
folk, and they will want to update the file, and that's just an unnecessary
noise/churn and not really a concern to the code repo. that jenv and pyenv
would work without the patch versions was something i checked before creating
the ticket.
> jenv .java-version and pyenv .python-version defaults
> -----------------------------------------------------
>
> Key: CASSANDRA-20130
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20130
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Build
> Reporter: Michael Semb Wever
> Assignee: Michael Semb Wever
> Priority: Normal
> Labels: lhf
>
> Commit in-tree both the .java-version and .python-version files.
> Each branch has a default java version and python version. We can honour
> that, and make life one less command when switching branches for those using
> jenv and/or pyenv.
> For those that do not have either jenv or pyenv installed, no harm.
> It will need run… (as .gitignore won't work here) …so devs can still
> customise both…
> {code}
> git update-index --assume-unchanged .java-version .python-version
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
