Bug 1011376 - String for MavenRepoCheckPanel.settings.invalid is missing in langpacks
Summary: String for MavenRepoCheckPanel.settings.invalid is missing in langpacks
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Installer
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ER3
: EAP 6.2.0
Assignee: Francisco Canas
QA Contact: Petr Kremensky
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-24 07:40 UTC by Petr Kremensky
Modified: 2014-09-03 04:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-15 16:13:47 UTC
Type: Bug

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

Description Petr Kremensky 2013-09-24 07:40:42 UTC 
Description of problem:
MavenRepoCheckPanel.settings.invalid is missing in custom langpacks. In 6.1.1 it has value "Please specify a local location for the settings.xml."

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

Steps to Reproduce:
Choose to install quickstarts during installation and enter "http://www.redhat.com" as maven settings.xml location. Press next. Warning dialog is thrown.

Actual results:
Message in dialog is "MavenRepoCheckPanel.settings.invalid"

Expected results:
Message in dialog is "Please specify a local location for the settings.xml."
Comment 1 Francisco Canas 2013-09-24 17:25:38 UTC 
I've restored the warning message to the MavenRepoCheckPanel. Entering a url into the settings.xml field now throws this warning:
"Please specify a local location for the settings.xml."

See commit for details:
http://git.app.eng.bos.redhat.com/?p=jbossas-installer.git;a=commit;h=48ec310fb9bb02ae5143f247944ccfdc0a791edf
Comment 2 Petr Kremensky 2013-09-26 12:04:02 UTC 
Please move all BZs ready for verification to ON_QA once the target milestone was released, thanks. 

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