[
http://jira.codehaus.org/browse/MRM-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126798
]
Maria Odea Ching commented on MRM-216:
--------------------------------------
Applied the patch in archiva-trunk -r635836.
I commented out some parts in the UploadAction class which need to be modified
due to the changes in the Archiva components used.
I made an initial list of what I think still needs to be done and can be
improved:
- modify the commented parts to adapt to the changes in the components (like
the repository layout)
- add 'Upload/Deploy Artifact' in the navigation menu
- form validation
- maybe we could have a drop-down box for the repository ids
- include this feature in the documentation
> Upload (deploy) artifacts to a repository - via a web form (not using wagon)
> ----------------------------------------------------------------------------
>
> Key: MRM-216
> URL: http://jira.codehaus.org/browse/MRM-216
> Project: Archiva
> Issue Type: New Feature
> Components: web application
> Reporter: Oliver Fink
> Assignee: John Tolentino
> Fix For: 1.1
>
> Attachments: MRM-216-20070818-1935.patch
>
>
> The web interface should allow to upload artifacts to the repository. For M1
> one could just ftp the artifacts as neededm but with M2 having to go through
> the file:deploy plugin is a pain. Archiva could help a lot here
--
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
