Bug 802390 - RichFaces Showcase has Tomcat profile as default
Summary: RichFaces Showcase has Tomcat profile as default
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: RichFaces, Examples
Version: 2.0.0.ER2
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 2.0.0.ER6
Assignee: Marek Novotny
QA Contact: Pavol Pitonak
URL:
Whiteboard: showcase
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-12 12:59 UTC by Karel Piwko
Modified: 2012-09-24 14:57 UTC (History)
3 users (show)

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.
Clone Of:
Environment:
Last Closed: 2012-09-24 14:57:09 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Karel Piwko 2012-03-12 12:59:57 UTC 
Description of problem:

There are various profiles for RichFaces Showcase. By default, there should be jbas7 only and this should be selected by default. All other are not related to WFK product.

Version-Release number of selected component (if applicable):

RichFaces Showcase 

How reproducible:

Always

Steps to Reproduce:
1. mvn clean package
  
Actual results:

There's a -tomcat6.war in target directory.

Expected results:

There's a -jbas7.war in target directory


Additional info:
Comment 1 Karel Piwko 2012-03-12 19:59:25 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.
Comment 2 Rebecca Newton 2012-03-13 06:23:23 UTC 
    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.
Comment 3 Karel Piwko 2012-05-16 08:28:15 UTC 
This should be solved by deleting all profiles which are not related to EAP6.
Comment 4 Pavol Pitonak 2012-05-16 08:43:56 UTC 
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
Comment 5 Marek Novotny 2012-05-22 14:21:26 UTC 
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
Comment 6 Pavol Pitonak 2012-06-21 13:52:48 UTC 
    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.
Comment 8 Karel Piwko 2012-06-22 11:17:44 UTC 
    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.
Comment 9 Karel Piwko 2012-09-24 14:57:09 UTC 
Fixed in WFK 2.0.0.GA.
Note You need to log in before you can comment on or make changes to this bug.