Bug 1027350 - EAP quickstarts pom.xml files reference "JBoss AS 7"
Summary: EAP quickstarts pom.xml files reference "JBoss AS 7"
Keywords:
Status: CLOSED DUPLICATE of bug 1025766
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Quickstarts
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: sgilda
QA Contact: Nikoleta Hlavickova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-06 15:47 UTC by Nikoleta Hlavickova
Modified: 2017-10-10 00:09 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-06 16:11:50 UTC
Type: Bug


Attachments (Terms of Use)

Description Nikoleta Hlavickova 2013-11-06 15:47:54 UTC
Description of problem:
EAP quickstarts pom.xml files reference "JBoss AS 7" instead of "JBoss EAP 6".

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

How reproducible:
always

Steps to Reproduce:
1. unzip jboss-eap-6.2.0.ER7-quickstarts.zip
2. grep "JBoss AS 7" . -R

Actual results:
Several lines with string "JBoss AS 7".
For example, in jboss-eap-6.2.0.GA-quickstarts/ejb-security/pom.xml:
<!-- Import the CDI API, we use provided scope as the API is included in JBoss AS 7 -->

Expected results:
No "JBoss AS 7" references. "JBoss EAP 6" references instead.

Additional info:
Some files reference both "JBoss AS 7" and "EAP 6", like jboss-eap-6.2.0.GA-quickstarts/kitchensink/pom.xml:
<description>A starter Java EE 6 webapp project for use on JBoss AS 7 / EAP 6, generated from the jboss-javaee6-webapp archetype</description>
These should be changed too to "JBoss EAP 6" and not mention "JBoss AS 7"

Comment 1 sgilda 2013-11-06 16:11:50 UTC
This is a duplicate of bug 1025766.

These were fixed in this commit: https://github.com/jboss-developer/jboss-eap-quickstarts/commit/612324764846ea3f9d50977b4ffc0e8b9addac02

*** This bug has been marked as a duplicate of bug 1025766 ***


Note You need to log in before you can comment on or make changes to this bug.