dcapwell commented on code in PR #170:
URL: https://github.com/apache/cassandra-website/pull/170#discussion_r961014402


##########
site-content/source/modules/ROOT/pages/development/dependencies.adoc:
##########
@@ -12,13 +12,26 @@ As Cassandra is an Apache product, all included libraries 
must follow
 Apache's https://www.apache.org/legal/resolved.html[software license
 requirements].
 
+=== Changes to dependency management in Cassandra 4.1

Review Comment:
   you mean 4.2 right?  only applied to trunk



##########
site-content/source/modules/ROOT/pages/development/dependencies.adoc:
##########
@@ -12,13 +12,26 @@ As Cassandra is an Apache product, all included libraries 
must follow
 Apache's https://www.apache.org/legal/resolved.html[software license
 requirements].
 
+=== Changes to dependency management in Cassandra 4.1
+
+Before Cassandra 4.1, dependencies were managed in `build.xml` and managed with
+Maven Ant Tasks. In Cassandra 4.1 and onwards, dependencies are managed in POM
+templates in `.build/`. New dependencies should be added to the parent POM

Review Comment:
   please flesh this out more, such as what are the files to modify. "read the 
JIRA" isn't good for our docs...



##########
site-content/source/modules/ROOT/pages/development/dependencies.adoc:
##########
@@ -12,13 +12,26 @@ As Cassandra is an Apache product, all included libraries 
must follow
 Apache's https://www.apache.org/legal/resolved.html[software license
 requirements].
 
+=== Changes to dependency management in Cassandra 4.1
+
+Before Cassandra 4.1, dependencies were managed in `build.xml` and managed with

Review Comment:
   don't need `,`



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to