Uploaded image for project: 'Gradle'
  1. Gradle
  2. GRADLE-1846

Idea plugin: allow to define compiler excludes and resource patterns

    Details

    • Type: New Feature
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: 1.0-milestone-4
    • Fix Version/s: None

      Description

      Please allow to configure compiler resource patterns and excludes. More details about that settings can be found here

        Activity

        Hide
        szczepiq Szczepan Faber added a comment -

        Those are the IDEA settings, e.g. not project or module settings, right?

        Show
        szczepiq Szczepan Faber added a comment - Those are the IDEA settings, e.g. not project or module settings, right?
        Hide
        denis.zhdanov Denis Zhdanov added a comment -

        No, that is a part of project settings.

        Show
        denis.zhdanov Denis Zhdanov added a comment - No, that is a part of project settings.
        Hide
        szczepiq Szczepan Faber added a comment -

        Can you tell me where can one configure it per project?

        Show
        szczepiq Szczepan Faber added a comment - Can you tell me where can one configure it per project?
        Hide
        denis.zhdanov Denis Zhdanov added a comment -

        Project Settings | Compiler | Resource patterns
        Project Settings | Compiler | Excludes

        Show
        denis.zhdanov Denis Zhdanov added a comment - Project Settings | Compiler | Resource patterns Project Settings | Compiler | Excludes
        Hide
        szczepiq Szczepan Faber added a comment -

        Got it. Makes sense now.

        Show
        szczepiq Szczepan Faber added a comment - Got it. Makes sense now.
        Hide
        bmuschko Benjamin Muschko added a comment -

        As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

        We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

        Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

        • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
        • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

        We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

        Show
        bmuschko Benjamin Muschko added a comment - As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub. We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to. Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by: Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines . Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete. We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

          People

          • Assignee:
            Unassigned
            Reporter:
            denis.zhdanov Denis Zhdanov
          • Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:

              Development