[
https://jira.codehaus.org/browse/MRM-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=324251#comment-324251
]
Olivier Lamy commented on MRM-1756:
-----------------------------------
maybe start a discussion on dev@ that will be more easy to discuss than here
BTW you can try a POC in a branch.
> Split js file and organize into folder to prepare
> --------------------------------------------------
>
> Key: MRM-1756
> URL: https://jira.codehaus.org/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 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
