[
https://issues.apache.org/jira/browse/KARAF-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14047642#comment-14047642
]
Jean-Baptiste Onofré commented on KARAF-1056:
---------------------------------------------
Fixed on cave-2.x:
https://git-wip-us.apache.org/repos/asf?p=karaf-cave.git;a=commitdiff;h=d245aafa70d71efffe49cc355a0f065ebff8235a
> 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-2.3.0
> Reporter: Glen Mazza
> Assignee: Jean-Baptiste Onofré
> Fix For: cave-2.3.1, cave-3.0.0
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)
