[
http://jira.codehaus.org/browse/MRM-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wendy Smoak updated MRM-774:
----------------------------
Assignee: Wendy Smoak
Fix Version/s: (was: 1.x)
1.1
Initial work done in r653190.
* Upload of filenames ending in .pom is not working (no content type found.)
I'll try defaulting to application/xml for the pomFile Content-Type.
* No success message displays after a successful upload [I don't think this
was working before my changes...]
* filename.replaceAll( packaging, "pom" ) is dangerous; if 'jar' or 'war'
appears elsewhere in the path it's going to get replaced.
* The groupId/artifactId/version/packaging fields are still required even if a
pom file is supplied. (This differs from deploy:deploy-file which can read
them from the pom.)
* No validation that the uploaded POM file matches the supplied
groupId/artifactId/etc.
* Documentation still needs to be updated
* Should checksums be created for the uploaded files? We currently only do it
for the metadata file. (Archiva can be configured to "fix checksums".)
* Automated tests?
> Support inclusion of pom file when deploying an artifact via the web upload
> form
> --------------------------------------------------------------------------------
>
> Key: MRM-774
> URL: http://jira.codehaus.org/browse/MRM-774
> Project: Archiva
> Issue Type: New Feature
> Components: web application
> Affects Versions: 1.1
> Reporter: Maria Odea Ching
> Assignee: Wendy Smoak
> Fix For: 1.1
>
>
> Currently the web upload form only supports pom generation when uploading M2
> artifacts.
--
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
