Skip to content

Order classpath per Maven dependency resolution #27

@wtwhite

Description

@wtwhite

Currently (in #20 and #26) I gather transitive dependencies by running mvn dependency:copy-dependencies and then using shell globbing. As pointed out by @jensdietrich, this means the classpath will contain them in alphabetical order -- which, though deterministic, is not necessarily the order that Maven would have added them based on its shallowest-then-earliest rule.

Change both to take the correctly ordered classpath from mvn dependency-build-classpath instead, and check that we still reproduce all test errors.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions