Maybe we can create some roadmap entry like it was done for ui-rewrite just to maybe not bind to a numerical version.
Was thinking on one for (repository API stuff + runtime plugin) . Another one for grouping thinks on auth (because of potential rewrite). -----Message d'origine----- De : Brett Porter [mailto:br...@porterclan.net] De la part de Brett Porter Envoyé : lundi 24 septembre 2012 06:34 À : dev@archiva.apache.org Objet : Re: Future plans for archiva ? Sorry for the delayed response, just picked up on this. Aside from the roadmap-level things Olivier and JB mentioned, in JIRA I think we did reasonably well of keeping things targeted to a good version. And anything not in a version should be responded to and put into one if appropriate. Triage is always a valuable thing to do... On 03/09/2012, at 9:59 PM, Eric Barboni <eric.barb...@irit.fr> wrote: > As I am quite new to Archiva and as there are a lots of opened issues > in Jira, I have not a clear opinion of what should be done. > > > > Seems that in a near future 1.4-M3 will be released for new UI rewrite. > > > > It seems that there will be a plugin way of supporting different > repository type (more or less new Repository API ) (sounds great) > > AFAIK That the new big rewrite plan. > > > > Why not: > > doing also plugin mechanism for authentication provider (i.e. ldap) + > configuration parameters in UI instead of in xml files ? > > > > Best Regards > > > > Eric > > PS: I keep playing with jdk 7 tests. > > > > > > > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter http://twitter.com/brettporter
