[
https://issues.apache.org/jira/browse/CASSANDRA-20868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-20868:
------------------------------------------
Fix Version/s: 4.0.19
4.1.10
5.0.6
5.1
(was: 4.1.x)
Source Control Link:
https://github.com/apache/cassandra/commit/29e45b5d826f85692e222cc5a619c238d05a9a18
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Increase memory for javadoc building
> ------------------------------------
>
> Key: CASSANDRA-20868
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20868
> Project: Apache Cassandra
> Issue Type: Task
> Components: Build
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 4.0.19, 4.1.10, 5.0.6, 5.1
>
>
> I was about to stage 4.1.10 and I failed to do so as I was not able to pass
> "ant publish". It will eventually try to build javadocs and this step behaves
> completely randomly, sometimes it passes, sometimes it does not.
> What I suspect is happening is that, based on empirical testing I conducted,
> more memory we assign to javadoc generation, more successful it is /
> probability of that failing is lower.
> For now, it is 256m, I will increase it to 1024m. Tricky part about releasing
> is that changes have to be there so I need to commit this before deploying.
> If it does not work, we will just skip javadoc completely.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
