Bug 982239 - Provide an user-friendly description why a git repository cannot be cloned
Summary: Provide an user-friendly description why a git repository cannot be cloned
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER5
: 6.0.0
Assignee: Alexandre Porcelli
QA Contact: Ivo Bek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-08 12:54 UTC by Ivo Bek
Modified: 2014-08-06 20:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:12:01 UTC
Type: Bug


Attachments (Terms of Use)

Description Ivo Bek 2013-07-08 12:54:57 UTC
Description of problem:

When a git repository, which we want to clone, requires username and password, business central shows a dialog with the following content:

Can't clone repository, please check error message. 
ToSubject=org.uberfire.backend.repositories.RepositoryService:RPC, CommandType=createRepository:java.lang.String:java.lang.String:java.util.Map:, MethodParms=[git, fsdfsdf, {username=, crypt:password=, origin=	git://git.app.eng.bos.redhat.com/bpms-assets.git}], ReplyTo=org.uberfire.backend.repositories.RepositoryService:RPC.createRepository:java.lang.String:java.lang.String:java.util.Map::RespondTo:34, ErrorTo=org.uberfire.backend.repositories.RepositoryService:RPC.createRepository:java.lang.String:java.lang.String:java.util.Map::Errors:34

But the user know nothing about what is wrong ... is it a connection issue, bad username and/or password or something else?

Only server log says in all the exceptions that Auth failed but it's still hard to find.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Alexandre Porcelli 2013-10-25 19:10:38 UTC
Just tested, but seems that this issue has been fixed for a while.

Comment 2 Ivo Bek 2013-12-04 11:57:18 UTC
Verified in BPMS 6.0.0.ER5

Comment 3 Ivo Bek 2014-03-18 10:55:47 UTC
This was just an enhancement and so it doesn't need a test.


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