Make sure Hibernate Search can be used without relying on JBoss's Nexus repo

Description

Currently our jobs use a specific Maven settings.xml which includes JBoss's Nexus.
The thing is, this repository will only be needed for WildFly-related sub-projects (mainly when we rely on WildFly feature packs whose dependencies are only published in JBoss's Nexus).
For every other sub-project, we actually don't want to rely on anything that isn't in Maven central.

One way to solve this would be to:

  • Not use any specific settings.xml in at least some of our CI jobs

  • Hard-code the JBoss repository only in those sub-projects that require it

Activity

Fixed

Details

Assignee

Reporter

Components

Fix versions

Priority

Created January 16, 2018 at 4:33 PM
Updated January 26, 2018 at 3:56 PM
Resolved January 23, 2018 at 2:49 PM

Flag notifications