Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <3361283.110061294070805493.JavaMail.jira@thor>
Date: Mon, 3 Jan 2011 11:06:45 -0500 (EST)
From: "Eric Evans (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Commented: (CASSANDRA-1926) Add Ant target to generate the
 project description files for running Cassandra in Eclipse
In-Reply-To: <29242341.98151293985365942.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976791#action_12976791 ] 

Eric Evans commented on CASSANDRA-1926:
---------------------------------------

bq. I think it would be better to include all of lib/*.jar instead of a separate entry for each jar.

I'm not sure you can add a directory of jars in Eclipse.

> 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
>            Priority: Minor
>         Attachments: 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.