Source vs Test libraries

jetbrains: Are there plans to distinguish which libraries should be
aviliable for source vs test classes? Just to ensure that non-test
classes do not creep dependenties into libraries.

We do this with our ant build scripts, but it would be nice to have an
earilier warning when this occurs.

3 comments
Comment actions Permalink

We may implement that if there will be enough wishes for that. Not in Aurora
though.

--
Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

"Barry Kaplan" <bkaplan@integratedtrading.com> wrote in message
news:bst248$9kl$1@is.intellij.net...

jetbrains: Are there plans to distinguish which libraries should be
aviliable for source vs test classes? Just to ensure that non-test
classes do not creep dependenties into libraries.

>

We do this with our ant build scripts, but it would be nice to have an
earilier warning when this occurs.

>


0
Comment actions Permalink

Barry Kaplan wrote:

jetbrains: Are there plans to distinguish which libraries should be
aviliable for source vs test classes? Just to ensure that non-test
classes do not creep dependenties into libraries.

>

We do this with our ant build scripts, but it would be nice to have an
earilier warning when this occurs.

>

I think it's strongly related to :
http://www.intellij.net/forums/thread.jsp?forum=22&thread=53611
Note: it's a - silent - discussion, not a request (yet).

Alain

0
Comment actions Permalink

I'd add that it's related to the various requests for having libraries only used for running/debugging, but not for compiling (e.g. JDBC drivers). In short, a project/module may use a library in various ways, something not supported in the current modules data-model.

0

Please sign in to leave a comment.