Mailing-List: contact dev-help@polygene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@polygene.apache.org
Date: Sat, 25 Mar 2017 08:56:41 +0000 (UTC)
From: "Niclas Hedhman (JIRA)" <jira@apache.org>
To: dev@polygene.apache.org
Message-ID: <JIRA.13044173.1487384391000.120504.1490432201542@Atlassian.JIRA>
In-Reply-To: <JIRA.13044173.1487384391000@Atlassian.JIRA>
References: <JIRA.13044173.1487384391000@Atlassian.JIRA> <JIRA.13044173.1487384391579@jira-lw-us.apache.org>
Subject: [jira] [Resolved] (POLYGENE-227) Configuration perfTest should
 resolve in IDEA
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 25 Mar 2017 08:56:46 -0000


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

Niclas Hedhman resolved POLYGENE-227.
-------------------------------------
    Resolution: Fixed
      Assignee: Niclas Hedhman

This is a 'flaw' in IDEA's handling of Gradle, and nothing we can do anything about. 
However, by using the default "Create separate module per sourceset" when importing the Gradle project, the problem goes away.

> Configuration perfTest should resolve in IDEA
> ---------------------------------------------
>
>                 Key: POLYGENE-227
>                 URL: https://issues.apache.org/jira/browse/POLYGENE-227
>             Project: Polygene
>          Issue Type: Bug
>            Reporter: Niclas Hedhman
>            Assignee: Niclas Hedhman
>
> The test/performance has a "perfTest" configuration, which doesn't resolve in IDEA and results in either having to take the module out, which affects refactoring or having compile errors inside the IDE. Neither is very practical.
> Either the configuration should be wrapped into "Compile" dependencies in IDEA or remove the configuration and figure out how to solve whatever problem it tries to solve, in some other fashion.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)