[ http://jira.codehaus.org/browse/MDEPLOY-22?page=comments#action_56846 ]
Matthew Beermann commented on MDEPLOY-22: ----------------------------------------- I've got site:site and site:deploy attached to the deploy phase, which seems like a reasonable sort of thing to do. As such, my <distributionManagement> section has a <site/> entry but no <repository/>. > distributionManagement/repository shouldn't be required > ------------------------------------------------------- > > Key: MDEPLOY-22 > URL: http://jira.codehaus.org/browse/MDEPLOY-22 > Project: Maven 2.x Deploy Plugin > Type: Bug > Versions: 2.1 > Reporter: Matthew Beermann > Fix For: 2.2 > > > Currently, the deploy plugin will blow up if there isn't a nonempty > <repository/> defined inside of <distrubutionManagement>. This is silly; > there are situations where you might not need or want to deploy your files to > a remote repository. Right now, for eample, I'm trying to set up a > documentation-only build - I'm only interested in the reports. I don't see > any real reason to require this element. -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
