[ 
https://issues.apache.org/jira/browse/MDEPLOY-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965539#comment-17965539
 ] 

Olivier Lamy commented on MDEPLOY-3:
------------------------------------

This project has moved from Jira to GitHub Issues. This issue was migrated to 
[apache/maven-deploy-plugin#126|https://github.com/apache/maven-deploy-plugin/issues/126].
 

> inconsistencies to correct in deploy file goal
> ----------------------------------------------
>
>                 Key: MDEPLOY-3
>                 URL: https://issues.apache.org/jira/browse/MDEPLOY-3
>             Project: Maven Deploy Plugin (Moved to GitHub Issues)
>          Issue Type: Bug
>            Reporter: Brett Porter
>            Assignee: Allan Q. Ramirez
>            Priority: Blocker
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> considered a blocker for the next deploy plugin release (not necessarily 
> 2.0.1 itself) because we can't change var names after it has been released.
> In deploy-file, there are some mojo parameters where the command line 
> arguments differ (deployFile vs file - should be file, repositoryId vs 
> serverId - should be repositoryId)
> In addition, note the old syntax for component expressions.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to