On 11/11/2010 2:07 PM, Mark Diggory wrote: > I'm researching if I can get the artifact properly registered in the > maven reactor. Alternatives are... > > 1.) move the dspace-ui-share dependencies out of dspace-jspui-webapp > and dspace-xmlui-webapp and only build at [dspace-source] with > -Paddons > 2.) move dspace-ui-share into "modules" and release it asynchronously. > 3.) copy the contents of dspace-ui-shared into both > dspace-xmlui-webapp and dspace-jspui-webapp and get rid of it, only > test from [dspace-source] with -Paddons. > > Given my past opinion on the contents of dspace-ui-shared not just > being copied into the two other webapps, I prefer (3) and tolerate > (1). I feel we are not quite ready for (2)
I'd vote for #3 -- personally, I've never really liked having 5 javascript files be their own "dspace-ui-share" module. Each interface should use it's own javascript as it needs to -- and not be reliant on using the same version of scriptaculous JS as the other UIs. - Tim ------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
