| Summary: | RichFaces Showcase has Tomcat profile as default | ||
|---|---|---|---|
| Product: | [Retired] JBoss Enterprise WFK Platform 2 | Reporter: | Karel Piwko <kpiwko> |
| Component: | RichFaces, Examples | Assignee: | Marek Novotny <mnovotny> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Pavol Pitonak <ppitonak> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.0.0.ER2 | CC: | mnovotny, ppitonak, rnewton |
| Target Milestone: | --- | ||
| Target Release: | 2.0.0.ER6 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | showcase | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, the jbas7 profile needed to be enabled in Maven in order to use the JBoss Enterprise Application Platform profile. This issue is fixed, and the RichFaces Showcase can be deployed to the application server without any need for Maven profiles.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-09-24 14:57:09 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Karel Piwko
2012-03-12 12:59:57 UTC
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:
In order to select JBoss Enterprise Application Platform profile, enable jbas71 profile in Maven.
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 +1 @@
-In order to select JBoss Enterprise Application Platform profile, enable jbas71 profile in Maven.+Enable the jbas7 profile in Maven in order to use the JBoss Enterprise Application Platform profile.
This should be solved by deleting all profiles which are not related to EAP6. It should be safe to remove profiles that are not related to EAP6, i.e. "jee6", "jbas7", "gae" and "unpack-gae-sdk". You have to leave at least jbas71 and openshift. In profile "release" you can remove execution "jee6", "jbas7", and "default-war". Change execution "default-war" to be the same as jbas71 I would say that release profile doesn't have to build war file as we don't distribute that in distribution neither in maven repository
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 +1 @@
-Enable the jbas7 profile in Maven in order to use the JBoss Enterprise Application Platform profile.+This issue was fixed. Showcase can now be deployed to the JBoss Enterprise Application Platform without using any Maven profiles.
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 +1 @@
-This issue was fixed. Showcase can now be deployed to the JBoss Enterprise Application Platform without using any Maven profiles.+Previously, the jbas7 profile needed to be enabled in Maven in order to use the JBoss Enterprise Application Platform profile. This issue is fixed, and the RichFaces Showcase can be deployed to the application server without any need for Maven profiles.
Fixed in WFK 2.0.0.GA. |