You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stefan Podkowinski (JIRA)" <ji...@apache.org> on 2016/08/16 14:13:20 UTC

[jira] [Updated] (CASSANDRA-12466) Use different build directories for Eclipse and Ant

     [ https://issues.apache.org/jira/browse/CASSANDRA-12466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Podkowinski updated CASSANDRA-12466:
-------------------------------------------
    Fix Version/s: 3.x
           Status: Patch Available  (was: Open)

> Use different build directories for Eclipse and Ant
> ---------------------------------------------------
>
>                 Key: CASSANDRA-12466
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12466
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Stefan Podkowinski
>            Assignee: Stefan Podkowinski
>            Priority: Trivial
>             Fix For: 3.x
>
>
> Currently {{ant generate-eclipse-files}} will create an Eclipse project that will write compile classes into the {{build/classes/main/}} output directory, just as ant does. This causes some issues in practice:
> * Eclipse doesn't recognize changes to compiled classes when compiling with ant. You'll have to manually refresh the project and Eclipse acts weird if you forget to do so.
> * Cleaning the project from Eclipse will remove the {{hotspot_compile}} file and {{ant jar}} won't work any longer as this file is required with ant. Eclipse will be happy to delete it during clean but won't be able to generate it.
> * Tests run by ant may pick up classes compiled by Eclipse that may use different build settings and produce different results for testing
> My suggestion is to simply configure Eclipse to use {{build/classes/eclipse}} instead and leave the ant classes alone. See trivial patch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)