[
https://issues.apache.org/jira/browse/CASSANDRA-18204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17683986#comment-17683986
]
David Capwell commented on CASSANDRA-18204:
-------------------------------------------
Testing out IntelliJ integration, so you can do cross cutting changes in one
UI. This was rather easy to setup, but had a side effect that needs to be
thought about; what happens if you switch between branches/commits and forget
to commit in the submodule?
Here is some feedback from [~benedict]
* have a pre-commit hook that bails if we haven’t yet committed a submodule
* Or maybe even have commits auto-apply to both?
* "Probably better to bail, and offer some scripts for easy management during
development "
> CEP-15: (C*) Add git submodule for Accord
> -----------------------------------------
>
> Key: CASSANDRA-18204
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18204
> Project: Cassandra
> Issue Type: Task
> Components: Accord
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: 4.x
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> As talked about in dev@ thread "Intra-project dependencies”, we talked about
> adding git submodules but before doing this had to work out a few issues
> first; this ticket is to track this work.
> Goals
> * when checking out an older commit, or pulling in newer commits, the
> submodule should also be updated automatically
> * release artifact must include the submodule and must be able to build
> without issue
> * build.xml must be updated to build the submodule
> * build.xml must be updated to release the submodule jar
--
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
