You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2006/01/25 00:19:06 UTC

[jira] Closed: (MDEPLOY-22) distributionManagement/repository shouldn't be required

     [ http://jira.codehaus.org/browse/MDEPLOY-22?page=all ]
     
Brett Porter closed MDEPLOY-22:
-------------------------------

      Assign To: Brett Porter
     Resolution: Won't Fix
    Fix Version:     (was: 2.2)

will do

> 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
>     Assignee: Brett Porter

>
>
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org