| Summary: | Fix Byteman dependency scope | ||
|---|---|---|---|
| Product: | [Retired] JBoss Enterprise WFK Platform 2 | Reporter: | Karel Piwko <kpiwko> |
| Component: | HibernateSearch | Assignee: | Strong Liu <stliu> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Karel Piwko <kpiwko> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 2.0.0.DR4 | CC: | sjacobs |
| Target Milestone: | --- | ||
| Target Release: | 2.0.0.DR06 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 4.0.0.CR2 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-04-05 13:48:18 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Tracking for https://hibernate.onjira.com/browse/HSEARCH-980 Verified in WFK 2.0.0.ER3 (a.k.a. 2.0.0.Beta1). |
The <dependencyManagement> section hibernate-search-parent contains following: <dependency> <groupId>org.jboss.byteman</groupId> <artifactId>byteman</artifactId> <version>${bytemanVersion}</version> <scope>test</scope> </dependency> <dependency> <groupId>org.jboss.byteman</groupId> <artifactId>byteman-install</artifactId> <version>${bytemanVersion}</version> <scope>test</scope> </dependency> <dependency> <groupId>org.jboss.byteman</groupId> <artifactId>byteman-bmunit</artifactId> <version>${bytemanVersion}</version> <scope>test</scope> </dependency> Following modules reference it: hibernate-search-orm hibernate-search-engine The former correctly specifies scope to test, the latter however pushed it to compile and therefore byteman becomes a hibernate-search dependency. As byteman is NOT synced to Maven Central, this renders project unusable. Please correct dependency management in your project. There should be no scopes in depedencyManagement section and every module should specify the scope. This actually renders distributed hibernate-search unusable, as there is no byteman in the enterprise repositories nor Maven Central.