spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Cornell (JIRA)" <>
Subject [jira] [Commented] (SPARK-4442) Move common unit test utilities into their own package / module
Date Tue, 20 Jan 2015 19:22:35 GMT


Matthew Cornell commented on SPARK-4442:

I agree they should be the same, but I got different results for whatever reason. Maybe I'll
try it again, but the commands were the same.

I looked in the POM because I thought that's were 'mvn jar:test-jar' goes. I've never used
maven before, so I was just trying to figure it out before asking. I guess it's a command
to a Maven jar plugin, but I don't understand how it knows where the test sources are.

Because the core module isn't passed explicitly to the jar command, I'm guessing it's a default
somewhere (in the POM?) How would I tell the jar command to run on the graphx module? Thank

> Move common unit test utilities into their own package / module
> ---------------------------------------------------------------
>                 Key: SPARK-4442
>                 URL:
>             Project: Spark
>          Issue Type: Improvement
>            Reporter: Josh Rosen
>            Priority: Minor
> We should move generally-useful unit test fixtures / utility methods to their own test
utilities set package / module to make them easier to find / use.
> See for one example
of this.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message