karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (Assigned) (JIRA) <j...@apache.org>
Subject [jira] [Assigned] (KARAF-1056) Enhancements to cave:upload-artifact command
Date Tue, 29 Nov 2011 07:01:40 GMT

     [ https://issues.apache.org/jira/browse/KARAF-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jean-Baptiste Onofré reassigned KARAF-1056:

    Assignee: Jean-Baptiste Onofré
> Enhancements to cave:upload-artifact command
> --------------------------------------------
>                 Key: KARAF-1056
>                 URL: https://issues.apache.org/jira/browse/KARAF-1056
>             Project: Karaf
>          Issue Type: Improvement
>          Components: cave-repository
>    Affects Versions: cave-3.0.0
>            Reporter: Glen Mazza
>            Assignee: Jean-Baptiste Onofré
>         Attachments: uploadArtifact.patch
> Attached patch makes these changes:
> 1.) If you upload an already existing bundle to the cave repo using upload-artifact you'll
get an "destination file exists" error message -- I switched it to a more user-friendly message
that the bundle already exists.  Also added an similar error message where you're trying to
upload a non-bundle.  Added test cases for both.
> 2.) In #1 above, if you get this duplicate bundle error Cave erroneously leaves a temp
file called "archive--{date}.zip" or similar in the Cave repo, patch will delete that temp
file if a duplicate file error occurs.
> 3.) I removed the -nu command OBR registration capabilities from this command, as I wasn't
sure if it's needed (this portion of the patch can be ignored if it is useful).  (Unless the
goal is to alert the OBR server of additional bundles present in the cave repo, I wasn't sure
what the relation was between adding an artifact to a cave repo and needing to re-register
the cave repo with the external OBR server.)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message