use new UI web framework

I'd prefer that rather than a "big bang" change, we implement this as having an alternative that is not default, and work to pull the logic out of the struts actions / xmlrpc where needed to be in a single place.

When we feel the new UI is "complete enough" we can switch over - but I guess there'll have to be a call about some features we want to drop.

Would you agree?

How about some discussion on the dev list about what features we're looking for and what frameworks people are interested in working with, and then breaking this down into multiple issues with more specific descriptions?

Wendy, we have started some threads on those points in ML ( http://markmail.org/message/4uuenvbpfcsfj2mu and others).

@Brett yup sound reasonnable.

for the record, jobs has started in trunk in an optional module called archiva-webapp-js.
Have a look at README file to test it.

Hello I am trying the new UI and commenting there because dev archiva not want me anymore

Was complicated to understand that I have to create admin account .

If it possible may I edit https://cwiki.apache.org/confluence/display/ARCHIVA/New+UI+framework to adds ideas, user tasks and so on?

test