You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stefan Miklosovic (Jira)" <ji...@apache.org> on 2025/08/28 09:28:00 UTC

[jira] [Updated] (CASSANDRA-20868) Exclude javadoc building from release process

     [ https://issues.apache.org/jira/browse/CASSANDRA-20868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Miklosovic updated CASSANDRA-20868:
------------------------------------------
    Change Category: Operability
         Complexity: Low Hanging Fruit
      Fix Version/s: 4.1.x
             Status: Open  (was: Triage Needed)

> Exclude javadoc building from release process
> ---------------------------------------------
>
>                 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.1.x
>
>
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org