[
https://issues.apache.org/jira/browse/CASSANDRA-17294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484521#comment-17484521
]
Berenguer Blasi commented on CASSANDRA-17294:
---------------------------------------------
I had to fix this locally on some other ticket and just adding the closing
{{classpath}} entry fixes it. We might not need all those extra jar entries for
dev.
> Fix generate-eclipse-files
> --------------------------
>
> Key: CASSANDRA-17294
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17294
> Project: Cassandra
> Issue Type: Task
> Components: Build
> Reporter: Yash Ladha
> Assignee: Yash Ladha
> Priority: Normal
>
> I was doing the local setup of cassandra and using the
> [https://github.com/eclipse/eclipse.jdt.ls] for development. When i visited
> the `CassandraDaemon.java` greeted with an error that the file is not in
> classpath, which was very weird. Upon investigation found out that the
> `classpath` was not closed and due to which that error is occuring.
> This issue is to solve the generation of correct .{_}classpath{_} file and
> inclusion of correct libs.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
