You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Zhijie Shen (JIRA)" <ji...@apache.org> on 2011/01/02 17:22:45 UTC
[jira] Created: (CASSANDRA-1926) Add Ant target to generate the
project description files for running Cassandra 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
"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.
[jira] Updated: (CASSANDRA-1926) Add Ant target to generate the
project description files for running Cassandra in Eclipse
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-1926:
--------------------------------------
Fix Version/s: (was: 0.8)
> 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
>
> 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.
[jira] Commented: (CASSANDRA-1926) Add Ant target to generate the
project description files for running Cassandra in Eclipse
Posted by "T Jake Luciani (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976795#action_12976795 ]
T Jake Luciani commented on CASSANDRA-1926:
-------------------------------------------
I selfishly would like to see this in build.xml, I'm working on a patch to do the *.jar for includes. Eclipse project files don't support this so its not straight forward.
> 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.
[jira] Commented: (CASSANDRA-1926) Add Ant target to generate the
project description files for running Cassandra in Eclipse
Posted by "T Jake Luciani (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976849#action_12976849 ]
T Jake Luciani commented on CASSANDRA-1926:
-------------------------------------------
Added a way to autogenerate the classpath entries and added the unit tests to be included. works for me.
> 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: 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.
[jira] Updated: (CASSANDRA-1926) Add Ant target to generate the
project description files for running Cassandra in Eclipse
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-1926:
--------------------------------------
Remaining Estimate: 4h
Original Estimate: 4h
> 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
>
> Attachments: 0001-CASSANDRA-1926-added-auto-generated-classpath-and-unit.txt, trunk-1926.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> "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.
[jira] Updated: (CASSANDRA-1926) Add Ant target to generate the
project description files for running Cassandra in Eclipse
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Evans updated CASSANDRA-1926:
----------------------------------
Reviewer: urandom
> 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: 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.
[jira] Updated: (CASSANDRA-1926) Add Ant target to generate the
project description files for running Cassandra in Eclipse
Posted by "T Jake Luciani (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
T Jake Luciani updated CASSANDRA-1926:
--------------------------------------
Attachment: 0001-CASSANDRA-1926-added-auto-generated-classpath-and-unit.txt
> 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: 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.
[jira] Commented: (CASSANDRA-1926) Add Ant target to generate the
project description files for running Cassandra in Eclipse
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976834#action_12976834 ]
Jonathan Ellis commented on CASSANDRA-1926:
-------------------------------------------
I think in-tree is probably better for this than github, if we have enough people familiar with both eclipse and ant, that it won't become outdated.
> 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.
[jira] Commented: (CASSANDRA-1926) Add Ant target to generate the
project description files for running Cassandra in Eclipse
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CASSANDRA-1926) Add Ant target to generate the
project description files for running Cassandra in Eclipse
Posted by "Zhijie Shen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhijie Shen updated CASSANDRA-1926:
-----------------------------------
Attachment: trunk-1926.patch
This is the patch for adding the Ant targets of generating and cleaning Eclipse project description files.
> 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.
[jira] Commented: (CASSANDRA-1926) Add Ant target to generate the
project description files for running Cassandra in Eclipse
Posted by "Zhijie Shen (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (CASSANDRA-1926) Add Ant target to generate the
project description files for running Cassandra in Eclipse
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Evans resolved CASSANDRA-1926.
-----------------------------------
Resolution: Fixed
Fix Version/s: 0.8
0.7.1
0.6.9
Assignee: T Jake Luciani
commited to 0.6, 0.7, and trunk
> 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.
[jira] Commented: (CASSANDRA-1926) Add Ant target to generate the
project description files for running Cassandra in Eclipse
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976786#action_12976786 ]
Gary Dusbabek commented on CASSANDRA-1926:
------------------------------------------
I think it would be better to include all of lib/*.jar instead of a separate entry for each jar.
Also, would git-hub be a better place to put this kind of thing?
> 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.
[jira] Commented: (CASSANDRA-1926) Add Ant target to generate the
project description files for running Cassandra in Eclipse
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976945#action_12976945 ]
Hudson commented on CASSANDRA-1926:
-----------------------------------
Integrated in Cassandra-0.6 #44 (See [https://hudson.apache.org/hudson/job/Cassandra-0.6/44/])
autogenerate eclipse project files
Patch by T Jake Luciani; reviewed by eevans for CASSANDRA-1926
> 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.
[jira] Commented: (CASSANDRA-1926) Add Ant target to generate the
project description files for running Cassandra in Eclipse
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976797#action_12976797 ]
Eric Evans commented on CASSANDRA-1926:
---------------------------------------
Is there a way to have ant enumerate the jars in lib/ and write the classpath entries, instead of hard-coding them? This would be great to have so long as it doesn't create one more place to manage dependency information.
> 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.
[jira] Commented: (CASSANDRA-1926) Add Ant target to generate the
project description files for running Cassandra in Eclipse
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976934#action_12976934 ]
Hudson commented on CASSANDRA-1926:
-----------------------------------
Integrated in Cassandra-0.7 #142 (See [https://hudson.apache.org/hudson/job/Cassandra-0.7/142/])
autogenerate eclipse project files
Patch by T Jake Luciani; reviewed by eevans for CASSANDRA-1926
> 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.