Bug 802402
| Summary: | Arquillian BOM file has no enterprise variant | ||
|---|---|---|---|
| Product: | [Retired] JBoss Enterprise WFK Platform 2 | Reporter: | Karel Piwko <kpiwko> |
| Component: | Arquillian | Assignee: | Marek Novotny <mnovotny> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.0.0.ER3 | CC: | mnovotny, rnewton |
| Target Milestone: | --- | ||
| Target Release: | 2.0.0.ER4 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, users willing to use jboss-javaee-6.0-with-tools with JBoss Enterprise Platform had to combine two different BOMs.
JBoss Web Framework Kit 2.0.0 now distributes jboss-javaee-6.0-with-tools in enterprise version.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-04-11 08:48:06 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Users willing to use jboss-javaee-6.0-with-tools with JBoss Enterprise Platform
cannot easily switch from community to enterprise variant adding a "-redhat-1" prefix to the version of artifact, because no such variant exists.
To workaround that, import following BOMs in given order in your project pom.xml file:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.jboss.spec</groupId>
<artifactId>jboss-javaee-6.0</artifactId>
<version>3.0.0.Beta1-redhat-1</version>
<type>pom</type>
<scope>import</scope>
<dependency>
<dependency>
<groupId>org.jboss.bom</groupId>
<artifactId>jboss-javaee-6.0-with-tools</artifactId>
<version>1.0.0.M3</version>
<type>pom</type>
<scope>import</scope>
<dependency>
</dependencies>
</dependencyManagement>
Marek Novotny <mnovotny> made a comment on jira JBPAPP-8418 This issue is only for tracking, right now the work will be done in WFK 2 and the missing BOM will be in WFK2 Maven repository. Paul Gier <pgier> updated the status of jira JBPAPP-8418 to Resolved Paul Gier <pgier> made a comment on jira JBPAPP-8418 All the boms are now included in the Maven repo zip. Yes, mentioned BOM are in EAP 6 maven repository only version is different from previous comment #1. <dependency> <groupId>org.jboss.bom</groupId> <artifactId>jboss-javaee-6.0-with-tools</artifactId> <version>1.0.0.M12-redhat-1</version> <type>pom</type> <scope>import</scope> <dependency> Forgot to mention first BOM version too
<dependency>
<groupId>org.jboss.spec</groupId>
<artifactId>jboss-javaee-6.0</artifactId>
<version>3.0.0.Final-redhat-1</version>
<type>pom</type>
<scope>import</scope>
<dependency>
Arquillian Enterprise BOM is in WFK 2.0.0.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1,23 +1,3 @@
-Users willing to use jboss-javaee-6.0-with-tools with JBoss Enterprise Platform
-cannot easily switch from community to enterprise variant adding a "-redhat-1" prefix to the version of artifact, because no such variant exists.
+Previously, users willing to use jboss-javaee-6.0-with-tools with JBoss Enterprise Platform had to combine tow different BOMs.
-To workaround that, import following BOMs in given order in your project pom.xml file:
+JBoss Web Framework Kit 2.0.0 now distributes jboss-javaee-6.0-with-tools in enterprise version.-
-<dependencyManagement>
- <dependencies>
- <dependency>
- <groupId>org.jboss.spec</groupId>
- <artifactId>jboss-javaee-6.0</artifactId>
- <version>3.0.0.Beta1-redhat-1</version>
- <type>pom</type>
- <scope>import</scope>
- <dependency>
- <dependency>
- <groupId>org.jboss.bom</groupId>
- <artifactId>jboss-javaee-6.0-with-tools</artifactId>
- <version>1.0.0.M3</version>
- <type>pom</type>
- <scope>import</scope>
- <dependency>
- </dependencies>
-</dependencyManagement>
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1,3 +1,3 @@
-Previously, users willing to use jboss-javaee-6.0-with-tools with JBoss Enterprise Platform had to combine tow different BOMs.
+Previously, users willing to use jboss-javaee-6.0-with-tools with JBoss Enterprise Platform had to combine two different BOMs.
JBoss Web Framework Kit 2.0.0 now distributes jboss-javaee-6.0-with-tools in enterprise version.
|
Description of problem: Users willing to use jboss-javaee-6.0-with-tools with JBoss Enterprise Platform cannot easily switch from community to enterprise variant adding a "-redhat-1" prefix to the version of artifact. Version-Release number of selected component (if applicable): 1.0.0.M3 How reproducible: Always. Steps to Reproduce: 1. Include following: <dependencyManagement> <dependencies> <groupId>org.jboss.bom</groupId> <artifactId>jboss-javaee-6.0-with-tools</artifactId> <version>1.0.0.M3</version> <type>pom</type> <scope>import</scope> </dependencies> </dependencyManagement> 2. Change version to 1.0.0.M3-redhat-1 Actual results: It fails, there is no such artifact Expected results: It works. Additional info: