Apache Drill
  1. Apache Drill
  2. DRILL-126

Standardize settings for various IDEs - Intellij and Eclipse

    Details

      Description

      Several build issues have been brought up on the list about integrating with various IDEs to get builds working. One example is the issue of the mockit dependency needing to be specified before JUnit in the .iml file to get Intellij to run some tests. We should have a way of sharing configurations to prevent these types of problems in the future, especially for new community members.

        Activity

        Tony Stevenson made changes -
        Workflow no-reopen-closed, patch-avail, testing [ 12860466 ] Drill workflow [ 12933955 ]
        Jacques Nadeau made changes -
        Issue Type Bug [ 1 ] New Feature [ 2 ]
        Jacques Nadeau made changes -
        Fix Version/s Future [ 12326743 ]
        Jacques Nadeau made changes -
        Issue Type New Feature [ 2 ] Bug [ 1 ]
        Jake Farrell made changes -
        Workflow no-reopen-closed, patch-avail [ 12807536 ] no-reopen-closed, patch-avail, testing [ 12860466 ]
        Jake Farrell made changes -
        Field Original Value New Value
        Workflow jira [ 12796266 ] no-reopen-closed, patch-avail [ 12807536 ]
        Hide
        Lisen Mu added a comment -

        +1 on the simple build process.

        However +1 if a little help could come to Intellij. Everytime intellij auto-imports some changes in pom.xml, I have to modify the library dependency order. Today again. Not a very big issue though.

        Show
        Lisen Mu added a comment - +1 on the simple build process. However +1 if a little help could come to Intellij. Everytime intellij auto-imports some changes in pom.xml, I have to modify the library dependency order. Today again. Not a very big issue though.
        Hide
        Timothy Chen added a comment -

        For Jmockit, unfortunately it looks like only Intellij is having this problem, eclipse seems to be fine. I do however still prefer using Intellij over eclipse though.

        Show
        Timothy Chen added a comment - For Jmockit, unfortunately it looks like only Intellij is having this problem, eclipse seems to be fine. I do however still prefer using Intellij over eclipse though.
        Hide
        Ted Dunning added a comment -

        +1 on the simple build process.

        But it is still nice to have settings files available to help compliance with coding standards.

        Show
        Ted Dunning added a comment - +1 on the simple build process. But it is still nice to have settings files available to help compliance with coding standards.
        Hide
        Julian Hyde added a comment -

        Intellij can do a lot from just the pom.xml. No need to check in an .iml or .ipr file.

        There is a lot to be said for keeping the dev environment very, very simple. ("git clone" followed by "mvn install".) If a new technology such as jmockit makes that process more complex, maybe we shouldn't use that technology.

        Show
        Julian Hyde added a comment - Intellij can do a lot from just the pom.xml. No need to check in an .iml or .ipr file. There is a lot to be said for keeping the dev environment very, very simple. ("git clone" followed by "mvn install".) If a new technology such as jmockit makes that process more complex, maybe we shouldn't use that technology.
        Hide
        Jacques Nadeau added a comment -

        This is what I start with using Eclipse: https://issues.apache.org/jira/browse/HBASE-3678

        • Apache license should head every file.
        • Logging is done using slf4j. Logger declaration: static final org.slf4j.Logger logger = org.slf4j.LoggerFactory.getLogger(ClassName.class);
        • 2 space indents, no tabs
        • 120 characters before a wrap.
        Show
        Jacques Nadeau added a comment - This is what I start with using Eclipse: https://issues.apache.org/jira/browse/HBASE-3678 Apache license should head every file. Logging is done using slf4j. Logger declaration: static final org.slf4j.Logger logger = org.slf4j.LoggerFactory.getLogger(ClassName.class); 2 space indents, no tabs 120 characters before a wrap.
        Jason Altekruse created issue -

          People

          • Assignee:
            Unassigned
            Reporter:
            Jason Altekruse
          • Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

            • Created:
              Updated:

              Development