You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ace.apache.org by "Marcel Offermans (JIRA)" <ji...@apache.org> on 2013/11/13 15:55:22 UTC

[jira] [Resolved] (ACE-428) Make uploading to a bundle store more robust and configurable

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

Marcel Offermans resolved ACE-428.
----------------------------------

    Resolution: Fixed

Committed code.

> Make uploading to a bundle store more robust and configurable
> -------------------------------------------------------------
>
>                 Key: ACE-428
>                 URL: https://issues.apache.org/jira/browse/ACE-428
>             Project: ACE
>          Issue Type: Improvement
>          Components: OBR
>            Reporter: Marcel Offermans
>            Assignee: Marcel Offermans
>
> There are a couple of issues with the current bundle store:
> 1. The interface extends ManagedService, which is wrong as there is no fundamental reason why every implementation should be configurable.
> 2. If you currently upload the exact same artifact again, the implementation signals this as an error. It would be better if it only did that if the artifact was different (but its metadata the same).
> 3. You cannot currently "forcefully" replace an existing artifact. In 99% of the cases, that is a good thing, but there are a few corner cases where you might want to be able to replace an artifact, so it would be good to add that as an option. One example is the Velocity based artifact preprocessor. It uploads filled out templates which normally have unique names. However, in a specific corner case, if a client commit fails, you might end up with a few artifacts that need to be replaced the next time you commit.



--
This message was sent by Atlassian JIRA
(v6.1#6144)