[
https://issues.apache.org/jira/browse/MATH-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658355#comment-13658355
]
Gilles commented on MATH-974:
-----------------------------
More specifically, I would like to be able to also retrieve the "test" JAR with
"ivy".
The following retrieves the sources, javadoc, and "main" artefacts but not
"commons-math3-3.2-tests.jar" file:
{noformat}
<ivy:install organisation="org.apache.commons"
module="commons-math3"
revision="3.2"
from="apache"
to="local-auto"
transitive="true"
overwrite="true"
haltonfailure="false"/>
{noformat}
That's probably an ivy problem. :(
But what I'd really like is that _tools_ (currently) implemented in the "test"
repository be as easy to depend on as the "main" code.
Considering the "tests" JAR as another "type" of dependency does not look like
the way to go.
Ivy users who need to depend on Commons Math have this in their dependencies
file:
{noformat}
<dependency org="org.apache.commons" name="commons-math3" rev="3.2"/>
{noformat}
Being able to use the benchmarking code should be as simple as adding a line
like:
{noformat}
<dependency org="org.apache.commons" name="commons-math3-tools" rev="3.2"/>
{noformat}
> Move "PerfTestUtils" to "src/main" repository
> ---------------------------------------------
>
> Key: MATH-974
> URL: https://issues.apache.org/jira/browse/MATH-974
> Project: Commons Math
> Issue Type: Wish
> Affects Versions: 3.2
> Reporter: Gilles
> Assignee: Gilles
> Priority: Trivial
> Labels: benchmark, test
> Fix For: 4.0
>
>
> The class "org.apache.commons.math3.PerfTestUtils" is in the "src/test" part
> of the code repository.
> It was intended to perform micro-benchmarks and compare alternative
> implementations. However its location makes it difficult to use by users that
> rely on automatic dependency resolution.
> Having it more visible will hopefully lead to useful suggestions for
> improving the benchmarking methodology.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
