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 2014/04/17 10:54:51 UTC

[jira] [Updated] (ACE-319) Improve the artifact view

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

Marcel Offermans updated ACE-319:
---------------------------------

    Fix Version/s: next

> Improve the artifact view
> -------------------------
>
>                 Key: ACE-319
>                 URL: https://issues.apache.org/jira/browse/ACE-319
>             Project: ACE
>          Issue Type: Improvement
>          Components: UI
>            Reporter: Marcel Offermans
>            Assignee: Marcel Offermans
>             Fix For: next
>
>
> We should model our artifact view more after that of Bndtools and have a tree view that shows BSNs at the top level and versions beneath. This has a couple of benefits:
> a) It creates a better overview of the bundles and their versions than a flat list can ever give.
> b) It allows us to implement a more elegant solution for our dynamic vs static associations.
> That last aspect should probably be explained a bit more. We have either static or dynamic associations between artifacts and features. Static means, you link to exactly the BSN+version that you select. Dynamic means it will always link to the highest version of that BSN. By dragging a feature onto a BSN we can now always create a dynamic link, and by dragging it onto a specific version we can make it static. That not only simplifies the interaction, it also gives better feedback as you can now see what links are dynamic and which ones are not.



--
This message was sent by Atlassian JIRA
(v6.2#6252)