[
https://issues.apache.org/jira/browse/CASSANDRA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977071#action_12977071
]
Zhijie Shen commented on CASSANDRA-1926:
----------------------------------------
Oh, I used to think I have to use "foreach" task to enumerate all the jars.
However, "foreach" doesn't belong the the core tasks of Ant and requires
additional lib. Therefore, to avoid introduce more lib into the project, I
hard-coded the jars in build.xml. Now T Jake's solution looks nice. I haven't
noticed this before.
> Add Ant target to generate the project description files for running
> Cassandra in Eclipse
> -----------------------------------------------------------------------------------------
>
> Key: CASSANDRA-1926
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1926
> Project: Cassandra
> Issue Type: Improvement
> Environment: Eclipse 3.5
> Reporter: Zhijie Shen
> Assignee: T Jake Luciani
> Priority: Minor
> Fix For: 0.6.9, 0.7.1, 0.8
>
> Attachments:
> 0001-CASSANDRA-1926-added-auto-generated-classpath-and-unit.txt,
> trunk-1926.patch
>
>
> "http://wiki.apache.org/cassandra/RunningCassandraInEclipse"; has demonstrated
> the procedure to manually configure Eclipse to make Cassandra runnable in it.
> But why not doing this automatically by adding an Ant target that is
> responsible the generation of Eclipse project description files? Actually,
> another Apache project, Hive, has done the similar things.
> Moreover, the aforementioned setup guide has the defects, which was learned
> from my experience of building Cassandra in Eclipse:
> 1) The "bin/" directory of Cassandra contains the executable scripts while it
> is the output destination of Eclipse project build by default. Therefore,
> unintentionally using Eclipse project build will break the original
> executable scripts in the "bin/" directory.
> 2) The default builder cannot build the project correctly. Instead, a
> customized builder based Ant builder should be created.
> For these reasons, I suggest to add a new Ant target in "build.xml" to
> generate the project description files. Meanwhile, another target is required
> to clean these files.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
