[ https://issues.apache.org/jira/browse/MRM-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Stockhammer closed MRM-1756. ----------------------------------- Resolution: Won't Fix Review of JS will be done for 3.0 and after that we will see, what will be changed. > Split js file and organize into folder to prepare > -------------------------------------------------- > > Key: MRM-1756 > URL: https://issues.apache.org/jira/browse/MRM-1756 > Project: Archiva > Issue Type: Task > Components: Web Interface > Affects Versions: ui-rewrite > Reporter: Eric Barboni > Priority: Minor > > This is early reflection to reorganise js file into folder and smaller js to > have possibility of extension. > "Rough organization for extension point artifact infos" > artifactsinfo/ > standard/ js to add ( Dependencies > Dependency Tree > Artifacts > Used By > Mailing Lists > Metadata ) > graphicalview / js to add (graph visualization ). > "Rough organization for extension point :repository" > repository > maven2 / js to add ( Repository Groups / Repositories / Proxy Connectors > / ProxyConnector Rules) > legacy / js to add ( Legacy Support ) > > > Basic idea: > if legacy folder is present legacy support is shown > if legacy folder is deleted legacy support is hidden. > First step: > Make archiva js ui compatible with this organisation. > Second step: > Position this folder in archiva plugins. > Propose mechanism to add / remove plugins. > I'm not very experienced in J2EE so maybe there are more standardised way to > handle that. > Any comments welcome. -- This message was sent by Atlassian JIRA (v7.6.3#76005)