[
https://jira.jboss.org/jira/browse/DNA-483?page=com.atlassian.jira.plugin...
]
Brian Carothers updated DNA-483:
--------------------------------
Attachment: DNA-483.patch
This patch just stores the set of startup problems as an instance variable that can be
queried after the startup is complete.
I'm throwing this out there for review rather than committing it directly as there may
well be other, better ways to solve this problem.
RepositoryService Doesn't Expose Problems from startService
-----------------------------------------------------------
Key: DNA-483
URL:
https://jira.jboss.org/jira/browse/DNA-483
Project: DNA
Issue Type: Feature Request
Components: Graph
Affects Versions: 0.5
Reporter: Brian Carothers
Priority: Minor
Attachments: DNA-483.patch
The repository service will work around problems with repository sources when it starts
up, logging those problems to a local variable and not creating the corresponding
repositories. However, this variable is not exposed, so callers cannot see why some
repositories failed to start.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira