[ http://jira.codehaus.org/browse/CONTINUUM-777?page=comments#action_72319 ] Carlos Sanchez commented on CONTINUUM-777: ------------------------------------------
refactored architecture to handle this. Errors that must be presented to the user don't throw exceptions, they are added to a ContinuumProjectBuildingResult. ContinuumProjectBuildingResult has constants with the keys of the errors. We use keys so it can be i18n later on the web layer. Errors to be shown to the user are (but not limited to): - xml errors in pom - host unknown - url doesn't exist - pom has missing info (scm, groupId, artifactId...) Anything unexpected must be thrown as an exception to be catched by the upper layers http://svn.apache.org/viewvc?view=rev&revision=431403 > Handle filesystem problems when adding a pom > -------------------------------------------- > > Key: CONTINUUM-777 > URL: http://jira.codehaus.org/browse/CONTINUUM-777 > Project: Continuum > Issue Type: Sub-task > Reporter: Carlos Sanchez > Assigned To: Lester Ecarma > Attachments: CONTINUUM-777.patch, CONTINUUM-777_2.patch > > > I see in the logs > 61589439 [SocketListener0-5] INFO org.apache.maven.continuum.Continuum - > Could not download > https://svn.simulalabs.net/svn/repos/BEA-DotNet/trunk/pom.xml: /tmp/continuum/ > svn/repos/BEA-DotNet/trunk/pom.xml (No such file or directory) > 6 > we should check that file error and show an internal error page instead of > current > Could not download > https://svn.simulalabs.net/svn/repos/BEA-DotNet/trunk/pom.xml: > /tmp/continuum/svn/repos/BEA-DotNet/trunk/pom.xml (No such file or directory) > Check the logs for more details. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
