<!-- Disabled due to integration issues

     <ant antfile="nuxeo-platform-thumbnail/build.xml" target="deploy"

     -->

One other thing, of considerable importance, not only for you and your colleagues at OMCA, Al, but also for the community - and those at other museums and heritage collections who will join it in the future. CollectionSpace right now requires a many-step installation process. It's, frankly speaking, onerous and silly to require this. While I'm sure you're learning a great deal about Ant, Maven, and building Java servers, that might not always be your cup of tea, and takes time away from simply customizing it for your museum. The CollectionSpace project team has explored the option of building an installer tool for the product. And there's already been a prototype Windows installer built not long ago. One issue with that approach, however, is that building an installer that can adroitly handle the many potential variations in a customer's OS environment often requires considerable time, both initially and in maintaining it over time. So does supporting multiple operating systems with variant installers, for Windows, Mac OS X, and one or more major flavors of Linux (each of which often have subtle differences). (Having in the past been a long-time member of a team that built product installers here at UC Berkeley, I have a visceral appreciation for the complexity of building and testing installers on a variety of systems.) My colleague, Richard Millet, has been actively working on an alternative mechanism, taking advantage of newer technologies, where you can just acquire a virtual machine (VM) image or a lightweight Linux 'container': one on which a working instance of CollectionSpace, with all its dependencies, is almost completely installed from the get-go. By filling in a few blanks, you can then rapidly complete the last remaining parts of the installation and be up and running. (Some of the techologies he's exploring for the latter are Vagrant, http://www.vagrantup.com/, and Docker, https://www.docker.io/, although no technology choices have yet been made.) Like your work at OMCA, this likely would initially be based on Ubuntu Linux, although that has yet to be decided as well. We'll keep you and others here informed of developments in this area. They're already promising, but still at a somewhat early stage. Aron On Mon, Sep 9, 2013 at 1:15 PM, Aron Roberts <aronroberts@gmail.com> wrote: > Hi Al, > > A suggestion: would you be willing to try out CollectionSpace 4.0? > This release, likely to become available later this week for community > QA testing, introduces some simplifications when a) getting started in > setting up your tenant and a *great many* simplifications when b) > customizing CollectionSpace for your museum. > > If so, we can follow-up about how you can get that now. There's > already an update to the 'create your new tenant' instructions for > v4.0 here: > > http://wiki.collectionspace.org/display/UNRELEASED/Creating+your+new+tenant > > Glen Jackson of our Museum Informatics team and I walked through the > above instructions and successfully created a new tenant, for the > BAM/PFA CineFiles instance that he and his colleagues are working on, > last Friday. > > As for the problem you're experiencing, in your helpfully detailed > report, it sounds like the Ant buildfile that's asking Maven to build > the 'updateobjectlocationonmove' event handler/listener - the one that > keeps Cataloging records updated with an object's current location > from its related movement records, as those are added or changed - is > reporting a Maven error. > > From within: > > /home/cspace/source/collectionspace-services/3rdparty/nuxeo/nuxeo-platform-listener/updateobjectlocationonmove > > Try: > > mvn clean install -X > > (the -X will spit out verbose log messages) > > That's pretty much what the 'ant install' target is doing here: > > https://github.com/collectionspace/services/blob/v3.3/3rdparty/nuxeo/nuxeo-platform-listener/updateobjectlocationonmove/build.xml#L64 > > And you might note that the 'ant deploy' target is calling 'ant > installl' ("under the hood") here: > > https://github.com/collectionspace/services/blob/v3.3/3rdparty/nuxeo/nuxeo-platform-listener/updateobjectlocationonmove/build.xml#L64 > > Aron > > > > On Mon, Sep 9, 2013 at 12:23 PM, Al Bersch <abersch@museumca.org> wrote: >> Hello again all, >> >> I wasn't able to solve the problem in with our settings.xml file, and >> decided to rebuild our tenant. However, when I ran "ant undeploy deploy" in >> the collectionspace-services directory (as user cpace), and with cspace >> servers shut down, I'm getting this message: >> >> BUILD FAILED >> >> /home/cspace/source/collectionspace-services/build.xml:257: The following >> error occurred while executing this line: >> >> /home/cspace/source/collectionspace-services/3rdparty/build.xml:121: The >> following error occurred while executing this line: >> >> /home/cspace/source/collectionspace-services/3rdparty/nuxeo/build.xml:133: >> The following error occurred while executing this line: >> >> /home/cspace/source/collectionspace-services/3rdparty/nuxeo/nuxeo-platform-listener/build.xml:118: >> The following error occurred while executing this line: >> >> /home/cspace/source/collectionspace-services/3rdparty/nuxeo/nuxeo-platform-listener/updateobjectlocationonmove/build.xml:67: >> exec returned: 1 >> >> >> >> >> the lines in question (copied from the above-referenced build.xml files): >> >> >> in /home/cspace/source/collectionspace-services/build.xml:257: >> >> >> <ant antfile="3rdparty/build.xml" target="deploy" inheritAll="false"/> >> >> >> In /home/cspace/source/collectionspace-services/3rdparty/build.xml:121: >> >> >> <ant antfile="nuxeo/build.xml" target="deploy" inheritall="false"/> >> >> >> In >> /home/cspace/source/collectionspace-services/3rdparty/nuxeo/build.xml:133: >> >> >> <ant antfile="nuxeo-platform-listener/build.xml" target="deploy" >> inheritall="false"/> >> >> <!-- Disabled due to integration issues >> between ImageMagick and Ghostscript on Linux systems >> >> <ant antfile="nuxeo-platform-thumbnail/build.xml" target="deploy" >> inheritall="false"/> >> >> --> >> >> >> In >> /home/cspace/source/collectionspace-services/3rdparty/nuxeo/nuxeo-platform-listener/build.xml:118: >> >> >> <ant antfile="updateobjectlocationonmove/build.xml" target="deploy" >> inheritall="false"/> >> >> >> In >> /home/cspace/source/collectionspace-services/3rdparty/nuxeo/nuxeo-platform-listener/updateobjectlocationonmove/build.xml:67: >> >> >> <exec executable="mvn" failonerror="true"> >> >> >> >> Any ideas you all may have would be much appreciated! >> >> Thanks, >> >> >> Al >> >> >> Al Bersch >> Digital Project Coordinator >> Oakland Museum of California >> 1000 Oak Street, Oakland, CA 94607 >> abersch@museumca.org >> 510-318-8468 >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>