Bug 724479 (BRMS-424) - Bad container name in comment in modeshape build.xml file
Summary: Bad container name in comment in modeshape build.xml file
Keywords:
Status: CLOSED NEXTRELEASE
Alias: BRMS-424
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: Tooling (JBDS), Modeshape
Version: 5.1.0.ER3
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: future
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-02 14:51 UTC by Petr Široký
Modified: 2010-12-21 09:53 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-21 09:54:00 UTC
Type: Bug

Attachments (Terms of Use)
modeshape-build-typo.png (33.52 KB, image/png)
2010-11-02 14:51 UTC, Petr Široký 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-424 0 None None None Never

Description Petr Široký 2010-11-02 14:51:01 UTC 
securitylevel_name: Public

Comment in modeshape.xml file contains invalid 'SOA-P' string (line 16). There should be name that corresponds to used container.

Relevant part of build.xml:

<!--
	This is used to install ModeShape into a SOA-P server
	                                                              ^^^^^^
	run:   ant     (and will be prompted for profile to install)
	or
	
	to automate installation, run passing the argumments
	
	run:   ant -Dprofile=<profile>  

-->
Comment 1 Petr Široký 2010-11-02 14:51:31 UTC 
Attachment: Added: modeshape-build-typo.png
Comment 2 Anne-Louise Tangring 2010-11-09 16:14:16 UTC 
This is not a blocker for BRMS 5.1.0
Comment 3 Van Halbert 2010-12-08 20:51:13 UTC 
Release Notes Text: Added: Committed to SOA build
Comment 4 Petr Široký 2010-12-21 09:53:59 UTC 
Verified fixed in modeshape distributed with SOA 5.1.0 ER6.
Note You need to log in before you can comment on or make changes to this bug.