ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <>
Subject [jira] [Commented] (ACE-367) Deleting artifacts, features, distributions or targets leave orphaned association records
Date Fri, 05 Jul 2013 11:05:49 GMT


Marcel Offermans commented on ACE-367:

I think we need to separate two different use cases here:

1. You're directly using the low-level Java client API. In this case, I think it is your responsibility
to delete the appropriate associations when you delete objects. In the general case it is
impossible to automatically do this correctly: When I delete an artifact, and there was a
feature that matched, I might want to keep the feature because my next step is to upload/add
a new matching artifact (or something similar).

2. You're working with the Web UI, which always creates 1:1 associations. It could, after
a delete, scan associations to see if there are orphans, and delete them. Even this would
require some care, as you might be manipulating a workspace with multiple different clients
(UI, shell, REST) so probably we should then take care only to delete associations created
by the Web UI in the first place. That in turn would require us to start tagging them somehow
so we know how they were created.

Alternatively we could probably provide convenience methods or commands that list all associations
that match nothing (left- or right-hand side). That would at least allow you to create a script
to remove all of those, if you want to clean up at some point.
> Deleting artifacts, features, distributions or targets leave orphaned association records
> -----------------------------------------------------------------------------------------
>                 Key: ACE-367
>                 URL:
>             Project: ACE
>          Issue Type: Bug
>          Components: Client Repository
>    Affects Versions: 1.0.0
>            Reporter: Wilfried Sibla
> When a  artifact, feature, distribution or target is deleted, associations referencing
the deleted object is left orphaned within the association repository.
> A strategy to handle these orphaned associations should be developed.
> 1:1 associations referencing only a certain artifact/feature/distribution/target which
is deleted could easily be deleted. Associations containing wildcards, e.g. referencing to
targets with a certain attribute value could be kept and will become automatically effective,
if a new target with a corresponding attribute value is added.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message