[
https://issues.apache.org/jira/browse/ACE-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700609#comment-13700609
]
Wilfried Sibla commented on ACE-367:
------------------------------------
That's what I learned since creating this issue. Such a task couldn't be
performed automatically in the ACE client layer, where there repos are
manipulated.
It also depends how ACE is used and how the workflow in and around a certain
client implementation are implemented or defined.
I would propose to close this issue.
> Deleting artifacts, features, distributions or targets leave orphaned
> association records
> -----------------------------------------------------------------------------------------
>
> Key: ACE-367
> URL: https://issues.apache.org/jira/browse/ACE-367
> 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: http://www.atlassian.com/software/jira
