We're updating the issue view to help you get more done. 

Use mvn install instead of mvn verify in the Travis build

Description

'mvn verify' is theoretically the way to go, but in practice it leads to some issues.

In particular, Maven plugins that need to retrieve artifacts (such as those used to add our modules to the WildFly server) usually don't know about the artifacts packaged during the current build, and they end up looking for the required artifacts in the local Maven repository.
If we use 'mvn verify', the artifacts used for testing will then be retrieved from a remote repository, and we'll end up executing WildFly ITs against a nightly build...
Using 'mvn install' solves the issue by populating the local repository with the version currently being built.

Environment

None

Status

Assignee

Yoann Rodière

Reporter

Yoann Rodière

Labels

None

Worked in

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Community Help Wanted

None

Suitable for new contributors

None

Requires Release Note

None

backportDecision

None

backportReEvaluate

None

Components

Fix versions

Priority

Major