[ http://jira.codehaus.org/browse/MNG-2294?page=comments#action_69932 ] Brett Porter commented on MNG-2294: -----------------------------------
this is by design. If the relativePath doesn't exist, it is assumed to have been checked out in isolation and the parent is resolved from the repository. relativePath is just a development convience, not a strict part of the build. Perhaps we can improve the reporting of it, though. > If /project/parent/relativePath fails to resolve, no error is reported. > ----------------------------------------------------------------------- > > Key: MNG-2294 > URL: http://jira.codehaus.org/browse/MNG-2294 > Project: Maven 2 > Issue Type: Bug > Affects Versions: 2.0.4 > Reporter: David Smiley > Fix For: 2.0.5 > > > If I have a bad /project/parent/relativePath specified, maven does not tell > me. Instead the build proceeds as if there is no parent. The build should > fail if the parent can't be resolved. -- 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
