[ 
https://issues.apache.org/jira/browse/CASSANDRA-20391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933797#comment-17933797
 ] 

Stefan Miklosovic edited comment on CASSANDRA-20391 at 3/10/25 9:58 AM:
------------------------------------------------------------------------

[~mck] [~bschoeni]  should not we keep at least native-protocol.adoc?

There is doc/native_protocol_v5.spec manually changed when protocol changes. So 
when corresponding adoc is committed, then on local building (ant artifacts), a 
developer sees how it looks like rendered.


was (Author: smiklosovic):
[~mck] [~bschoeni]  should not we keep at least native-protocol.adoc? I think 
this is regenerated every time when building the website but one can at least 
see adoc rendered in e.g. IDEA when opening that file in the editor. There is 
also rendered adoc visible too. It is comfortable for a developer to see 
something like this.

 

There is doc/native_protocol_v5.spec manually changed when protocol changes. So 
when corresponding adoc is committed, then on local building (ant artifacts), a 
developer sees how it looks like rendered.

> Add generated native-protocol.adoc to .gitignore
> ------------------------------------------------
>
>                 Key: CASSANDRA-20391
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20391
>             Project: Apache Cassandra
>          Issue Type: Improvement
>            Reporter: Ling Mao
>            Assignee: Ling Mao
>            Priority: Low
>             Fix For: 5.0.x
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> _*ant artifacts*_ to build the C* source code locally, but it generates the 
> following file every time, which should be exempted form GIT.
> {code:java}
> doc/modules/cassandra/pages/reference/native-protocol.adoc {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]

Reply via email to