Hi there,
as you (may) know,
Sonatype Nexus
is an OSS Maven Repository Manager.
As the Proximity developer (that later became Nexus) and lead of Nexus project, I got fed up with Nexus “dull” UI (using ExtJS). So, I felt it was time to play with it, and I came across Vaadin. It is a_w_e_s_o_m_e!
And, here is it, very baby:
http://github.com/cstamas/nexus-peedy/
To avoid the “build hell” (you need modded
Enunciate
too for this, but almost all my patches are already applied to Enunciate trunk), here is a WAR:
http://s3.cservenak.net/maven/nexus-war-1.4.2-SNAPSHOT.war
URLs of interests (if WAR context path is /nexus):
The only (this is a baby, remember?) implemented REST Service using Jersey
http://localhost:8080/nexus/rest/status
Enunciate generated doco and ruby, ObjC and other clients:
http://localhost:8080/nexus/apidocs/
The Vaadin UI:
http://localhost:8080/nexus/ui
And the “old” REST API is there too:
http://localhost:8080/nexus/service/local/status
The “root” will give you broken “old” ExtJS UI, but will not work since ExtJS JS code is removed.
It is SVN Trunk mirrored in Git, and “afloated” some new patches. Also, new modules are added like the Vaadin UI (nexus-vaadin-ui module).
I have to emphasize, that this is just a “technology showcase”, so I blatantly reused the Sample UI (reworked it a bit, and integrated with Plexus IoC container, that is soon gonna be transferred to Guice+Peaberry).
So, hello Vaadin + OSGi!
Looking at Nexus with “sampler-like” UI is such a refreshment, it is simply unbelievable to me!
Is there any concern about Sample codebase? As far as I understand, it is ASL2.0, just like Vaadin UI. Naturally, I would like to modify it, but the initial functional design of Sampler app is just great!
Any interested parties in participating in Vaadinizing Nexus?
Have fun!
~t~