archiva-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olivier Lamy <ol...@apache.org>
Subject Re: Reorganizing js into folders to prepare "plugin mechanism"
Date Thu, 16 May 2013 12:55:33 GMT
2013/5/13 Eric Barboni <Eric.Barboni@irit.fr>:
> Hi,
>  I do lots of file  move and renaming.
>  Archiva admin seems to work.
>    -New Services to list plugins.
>    -New folder layout
> Comments welcome (I use a pure arbiratry grouping of features)
>
>  I have an issue with svn because move are considered as add and delete an
> history is not kept.
>  I must rewrite modification using git I think. What do you think?
we use svn :-)

>
> Regards
>
> -----Message d'origine-----
> De : Eric Barboni [mailto:Eric.Barboni@irit.fr]
> Envoyé : jeudi 2 mai 2013 15:50
> À : dev@archiva.apache.org
> Objet : RE: Reorganizing js into folders to prepare "plugin mechanism"
>
> Seems possible to do.
>  Js may be stored in other jar.
>
> -----Message d'origine-----
> De : Eric Barboni [mailto:Eric.Barboni@irit.fr] Envoyé : lundi 29 avril 2013
> 11:55 À : dev@archiva.apache.org Objet : RE: Reorganizing js into folders to
> prepare "plugin mechanism"
>
> Well, I'm slow :).
> I will commit on the branch as soon as possible.
>
> -----Message d'origine-----
> De : Olivier Lamy [mailto:olamy@apache.org] Envoyé : dimanche 28 avril 2013
> 11:48 À : dev@archiva.apache.org Objet : Re: Reorganizing js into folders to
> prepare "plugin mechanism"
>
> Sounds good to reorganize js paths. I agree it's really flat currently :-)
> I'm just curious to see how you will get that working with requirejs ?
> (if path not here revert to something else).
> Feel free to do a POC in the branch you created.
>
> 2013/4/25 Eric Barboni <skygo@apache.org>:
>> Hi all,
>>
>>
>>
>> Copy pasting the issue  <https://jira.codehaus.org/browse/MRM-1756>
>> https://jira.codehaus.org/browse/MRM-1756 to the list to make it easy
>> for discussion.
>>
>>
>>
>> This is early reflection to reorganize file of j sui  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 organization.
>>
>>  (css, js for lib)
>>
>>
>>
>> Second step:
>>
>> Position this folders in archiva plugins.
>>
>> Propose mechanism to add / remove plugins.
>>
>>
>>
>>
>>
>>
>>
>> I'm not very experienced in J2EE so maybe there are more standardized
>> way to handle that.
>>
>>
>>
>> Any comments welcome.
>>
>>
>>
>> Best regards
>>
>>
>>
>> Eric
>>
>>
>>
>
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
>
>



--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy

Mime
View raw message