Some more detail: When you build with minification/concatenation turned on, all the css files, including cspace.css, get concatenated into a few larger files (of which index.css and myCollectionSpace.css are two), and those larger files are deployed into the server. HTML files are also modified during the process to load those concatenated files, instead of the individual source files. That's why you end up having to edit multiple files in the server, and editing cspace.css in the server has no effect. The advantage of this is that there are fewer css files to download, so pages should load faster. The downside is that they're hard to edit. Ray On Mon, Jul 1, 2013 at 4:33 PM, Ray Lee <rhlee@berkeley.edu> wrote: > Oh, I also missed that. > > Al, it looks like at some point you built the UI layer with > minification/concatenation turned on, using mvn -Pminimize,tomcat clean > install. That means that if you make changes to cspace.css in the source > tree, you can't copy it by hand into the server. You have to do a mvn > build. > > To make things simpler, I would not use minification at this point. It's > really only meant for production servers. If you now do mvn clean install > (without the (-Pminimize,tomcat) from the UI source tree, and clear your > browser's offline application cache, you should get back to an unminified > state. > > Ray > > > > > On Mon, Jul 1, 2013 at 4:24 PM, Aron Roberts <aron@socrates.berkeley.edu>wrote: > >> Hi Al, >> >> Having written that, I'm now a bit confused ... I don't see files in >> the UI source code folder or in the deployed UI folder in the Tomcat >> server folder named index.css, myCollectionSpace.css, etc. in my stock >> 3.2.3/3.3 distribution. I've also had the experience that changing >> only cspace.css - a stylesheet which is referenced from most/all HTML >> pages - should be sufficient to make that logo change universally. >> (Perhaps someone else on this list might wish to comment further ...) >> >> No matter for your demo - if it works, it's absolutely all good :-) - >> but as/when you get around to doing a more substantial configuration, >> we can revisit this, as you see fit. >> >> Aron >> >> On Mon, Jul 1, 2013 at 4:16 PM, Aron Roberts <aron@socrates.berkeley.edu> >> wrote: >> > Excellent - glad to hear of this success, Al! >> > Aron >> > >> > On Mon, Jul 1, 2013 at 3:56 PM, Al Bersch <abersch@museumca.org> wrote: >> >> Hi Aron, all, >> >> >> >> So, I didn't realize that I also needed to make also make changes to >> the >> >> index.css, myCollectionSpace.css, etc, for the logo to change on all >> pages. >> >> Once I made those changes, the new logo appears. >> >> >> >> thanks again for your time, >> >> >> >> Al >> >> >> >> Al Bersch >> >> Digital Project Coordinator >> >> Oakland Museum of California >> >> 1000 Oak Street, Oakland, CA 94607 >> >> abersch@museumca.org >> >> 510-318-8468 >> >> ________________________________ >> >> From: "Aron Roberts" <aron@socrates.berkeley.edu> >> >> To: "Al Bersch" <abersch@museumca.org> >> >> Cc: "talk" <talk@lists.collectionspace.org>, "Chris Hoffman" >> >> <chris_h@berkeley.edu>, "Ray Lee" <rhlee@berkeley.edu>, "Becky >> Escamilla" >> >> <rescamilla@museumca.org> >> >> Sent: Monday, July 1, 2013 3:16:33 PM >> >> >> >> Subject: Re: error when running mvn deploy >> >> >> >> Thanks, Al. Based on that directory path, it seems likely you may >> >> have been doing 'scenario A' - editing configuration files (and adding >> >> a custom logo) directly in place, in the Tomcat server folder. >> >> >> >> In scenario b, you will have these two folders: >> >> >> >> A source code folder where you can customize the 'core' tenant >> >> * {the location of some folder where you downloaded the UI source >> >> code}/ui/src/main/webapp/tenants/core/ >> >> (which can have 'css' and 'images' sub-folders, which you can also >> >> create if not already present); and >> >> A corresponding target folder within the Tomcat server folder to which >> >> your changes will be copied (deployed); e.g.: >> >> * ~/tomcat/webapps/cspace-ui/tenants/core >> >> >> >> To deploy (copy) any changes you might make in that source code >> >> folder, to one or more relevant folders within the Tomcat server >> >> folder, making those changes 'live,' you'd go into the top level of >> >> that source code folder: >> >> * {some folder where you downloaded the UI source code}/ui >> >> >> >> and run: >> >> >> >> ant deploy -DskipTests >> >> (note: not "mvn deploy -DskipTests" - I'd missed noticing that earlier) >> >> >> >> This would then copy those files into the Tomcat server folder. >> >> >> >> Aron >> >> >> >> On Mon, Jul 1, 2013 at 3:01 PM, Al Bersch <abersch@museumca.org> >> wrote: >> >>> Hi Aron, >> >>> >> >>> Thanks, that makes sense. It was scenario B we were doing, and I must >> have >> >>> run mvn deploy -DskipTests in the wrong folder. However, I'm not sure >> what >> >>> the "top level of our folder containing source code for the relevant >> >>> CollectionSpace layer" is, because the code we were working with was >> in >> >>> the >> >>> tomcat folder (the path looks like >> >>> ~/tomcat/webapps/cspace-ui/tenants/core/css). Any suggestions? >> >>> >> >>> thanks again, >> >>> >> >>> Al >> >>> >> >>> Al Bersch >> >>> Digital Project Coordinator >> >>> Oakland Museum of California >> >>> 1000 Oak Street, Oakland, CA 94607 >> >>> abersch@museumca.org >> >>> 510-318-8468 >> >>> ________________________________ >> >>> From: "Aron Roberts" <aron@socrates.berkeley.edu> >> >>> To: "Al Bersch" <abersch@museumca.org> >> >>> Cc: "talk" <talk@lists.collectionspace.org>, "Chris Hoffman" >> >>> <chris_h@berkeley.edu>, "Ray Lee" <rhlee@berkeley.edu>, "Becky >> Escamilla" >> >>> <rescamilla@museumca.org> >> >>> Sent: Monday, July 1, 2013 2:53:14 PM >> >>> Subject: Re: error when running mvn deploy >> >>> >> >>> >> >>> Hi Al, >> >>> >> >>> It looks like the relevant document on the wiki on 'branding' a >> >>> CollectionSpace system with your own logo >> >>> (http://wiki.collectionspace.org/display/DOC/How+to+add+branding) >> >>> suggests that you: >> >>> >> >>> a) make changes directly within the Tomcat server folder; >> >>> as contrasted with >> >>> b) making them within your source code directory, then copying >> >>> (deploying) them to the server. >> >>> >> >>> (The first method, a), is quick and easy, while the second method, b), >> >>> allows you to document your changes, retain successive versions if you >> >>> need to roll back from mistakes, and reliably deploy those changes in >> >>> the future.) >> >>> >> >>> If you've used method a), directly modifying files in place in the >> >>> server folder, you don't need to run the deploy command at all. You >> >>> should be able to see your changes right away, after you clear your >> >>> browser's caches. (If you don't, you could try also restarting the >> >>> CollectionSpace server.) >> >>> >> >>> If you've used the latter method, b), following my example here >> >>> >> >>> ( >> https://github.com/aronr/ui/commit/eb5749db997dc2bdae7510d987140d9f316395d2 >> ) >> >>> then you'll want to run the 'mvn deploy -DskipTests' command from the >> >>> top level of your folder containing source code for the relevant >> >>> CollectionSpace layer, rather than from a folder inside the Tomcat >> >>> folder. That'll deploy (copy) your changes from that source code >> >>> folder, into the Tomcat server folder. >> >>> >> >>> (The error message "there is no POM in this directory >> >>> >> >>> >> (/usr/local/share/apache-tomcat-6.0.33/webapps/cspace-ui/tenants/core/images" >> >>> suggests the latter scenario.) >> >>> >> >>> Hope this helps! >> >>> Aron >> >>> >> >>> On Mon, Jul 1, 2013 at 1:41 PM, Al Bersch <abersch@museumca.org> >> wrote: >> >>>> Hello talk, and Aron, >> >>>> >> >>>> Regarding the customization instructions Aron sent us on how to >> change >> >>>> the >> >>>> logo in cspace, I ran into the following error when running mvn >> deploy >> >>>> -DskipTests. Do you have any ideas as to why this would happen? >> Thanks so >> >>>> much! >> >>>> >> >>>> [INFO] Scanning for projects... >> >>>> [INFO] >> >>>> >> ------------------------------------------------------------------------ >> >>>> [INFO] BUILD FAILURE >> >>>> [INFO] >> >>>> >> ------------------------------------------------------------------------ >> >>>> [INFO] Total time: 0.230s >> >>>> [INFO] Finished at: Mon Jul 01 13:33:24 PDT 2013 >> >>>> [INFO] Final Memory: 3M/30M >> >>>> [INFO] >> >>>> >> ------------------------------------------------------------------------ >> >>>> [ERROR] The goal you specified requires a project to execute but >> there is >> >>>> no >> >>>> POM in this directory >> >>>> >> >>>> >> >>>> >> (/usr/local/share/apache-tomcat-6.0.33/webapps/cspace-ui/tenants/core/images). >> >>>> Please verify you invoked Maven from the correct directory. -> [Help >> 1] >> >>>> [ERROR] >> >>>> [ERROR] To see the full stack trace of the errors, re-run Maven with >> the >> >>>> -e >> >>>> switch. >> >>>> [ERROR] Re-run Maven using the -X switch to enable full debug >> logging. >> >>>> [ERROR] >> >>>> [ERROR] For more information about the errors and possible solutions, >> >>>> please >> >>>> read the following articles: >> >>>> [ERROR] [Help 1] >> >>>> >> http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException >> >>>> >> >>>> Al Bersch >> >>>> Digital Project Coordinator >> >>>> Oakland Museum of California >> >>>> 1000 Oak Street, Oakland, CA 94607 >> >>>> abersch@museumca.org >> >>>> 510-318-8468 >> >>>> ________________________________ >> >>>> From: "Aron Roberts" <aron@socrates.berkeley.edu> >> >>>> To: "Al Bersch" <abersch@museumca.org>, "Becky Escamilla" >> >>>> <rescamilla@museumca.org> >> >>>> Cc: "Chris Hoffman" <chris_h@berkeley.edu>, "Ray Lee" >> >>>> <rhlee@berkeley.edu> >> >>>> Sent: Monday, June 10, 2013 9:03:36 PM >> >>>> Subject: A couple of starting-out CollectionSpace customizations >> >>>> >> >>>> Hi Becky and Al, >> >>>> >> >>>> A few notes, below, on making a couple of 'starting-out' >> >>>> customizations. For simplicity, you might make these in the >> >>>> already-created, demonstration 'core' tenant. >> >>>> >> >>>> FYI, >> >>>> Aron >> >>>> >> >>>> -- >> >>>> >> >>>> (Recommendation: start the CollectionSpace server before making the >> >>>> following changes. This will help ensure those changes are made >> >>>> 'live.') >> >>>> >> >>>> * An example of how to replace the default CollectionSpace logo with >> >>>> the OMCA logo: >> >>>> >> >>>> Documentation: >> >>>> >> >>>> >> >>>> >> http://wiki.collectionspace.org/display/DOC/How+to+add+branding#Howtoaddbranding-howtologo >> >>>> >> >>>> Actual change(s) made, within the source code tree for >> >>>> CollectionSpace's user interface (UI) layer: >> >>>> >> >>>> >> >>>> >> https://github.com/aronr/ui/commit/da1cbdacf364beef1b4821cd2a3dbcbffba9a04d >> >>>> >> >>>> (Specifically, this change involved copying the file 'cspace.css', >> >>>> from the 'defaults' directory into a newly-created 'css' folder for >> >>>> your 'core' tenant, then changing lines 389-391 and 402-404, as per >> >>>> the documentation above, to specify the filename for your image, and >> >>>> its height and width dimensions. And the image file itself was >> copied >> >>>> into a newly-created 'images' folder for your 'core' tenant, >> alongside >> >>>> that new 'css' folder.) >> >>>> >> >>>> >> >>>> >> https://github.com/aronr/ui/commit/da1cbdacf364beef1b4821cd2a3dbcbffba9a04d#L0R389 >> >>>> >> >>>> To copy (deploy) these changes to the server folder, enter the >> >>>> following at a command prompt, from within the top-level folder of >> the >> >>>> UI source code tree: >> >>>> mvn deploy -DskipTests >> >>>> >> >>>> * An example of how to rename the Collection field in the Cataloging >> >>>> record to "OMCA Collection": >> >>>> >> >>>> Documentation: >> >>>> http://wiki.collectionspace.org/display/DOC/How+to+rename+a+field >> >>>> >> >>>> Actual change made - again, within the source code tree for >> >>>> CollectionSpace's user interface (UI) layer: >> >>>> >> >>>> >> >>>> >> https://github.com/aronr/ui/commit/eb5749db997dc2bdae7510d987140d9f316395d2 >> >>>> >> >>>> To copy (deploy) this change to the server, enter the following (i.e. >> >>>> a second time - or you can first make both changes described here and >> >>>> enter this command just once) at a command prompt, from within the >> >>>> top-level folder of the UI source code tree: >> >>>> mvn deploy -DskipTests >> >>>> >> >>>> To see the changes: >> >>>> >> >>>> * Clear your browser's cache(s) >> >>>> * Visit your login page; e.g. >> >>>> http://localhost:8180/collectionspace/core/ui/html >> >>>> (The new OMCA logo should appear on that page.) >> >>>> >> >>>> * Log in using the default administrator's username and password, >> >>>> shown on the login screen >> >>>> * Select "Create New" >> >>>> * Select "Cataloging" >> >>>> * Click the "Create" button >> >>>> (Look for the "OMCA Cataloging" field label on the left side of the >> >>>> Cataloging record screen, about five fields down.) >> >>>> >> >>>> A screenshot is attached. >> >>>> >> >>>> Aron >> >>>> >> >>>> P.S. Tomorrow, I'm expecting to also send an example of how to change >> >>>> the values in the drop-down menus for the Collection and Responsible >> >>>> Department fields, in Cataloging. >> >>>> >> >>> >> >> >> >> >> >> _______________________________________________ >> >> Talk mailing list >> >> Talk@lists.collectionspace.org >> >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> >> >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> > >

Hi Ray, Thank you for this explanation. I had no idea we had minification turned on. I will try running the clean install as you say. Thanks again, Al Al Bersch Digital Project Coordinator Oakland Museum of California 1000 Oak Street, Oakland, CA 94607 abersch@museumca.org 510-318-8468 ----- Original Message ----- From: "Ray Lee" <rhlee@berkeley.edu> To: "Aron Roberts" <aron@socrates.berkeley.edu> Cc: "Al Bersch" <abersch@museumca.org>, "talk" <talk@lists.collectionspace.org>, "Becky Escamilla" <rescamilla@museumca.org> Sent: Monday, July 1, 2013 4:43:19 PM Subject: Re: [Talk] error when running mvn deploy Some more detail: When you build with minification/concatenation turned on, all the css files, including cspace.css, get concatenated into a few larger files (of which index.css and myCollectionSpace.css are two), and those larger files are deployed into the server. HTML files are also modified during the process to load those concatenated files, instead of the individual source files. That's why you end up having to edit multiple files in the server, and editing cspace.css in the server has no effect. The advantage of this is that there are fewer css files to download, so pages should load faster. The downside is that they're hard to edit. Ray On Mon, Jul 1, 2013 at 4:33 PM, Ray Lee < rhlee@berkeley.edu > wrote: Oh, I also missed that. Al, it looks like at some point you built the UI layer with minification/concatenation turned on, using mvn -Pminimize,tomcat clean install. That means that if you make changes to cspace.css in the source tree, you can't copy it by hand into the server. You have to do a mvn build. To make things simpler, I would not use minification at this point. It's really only meant for production servers. If you now do mvn clean install (without the (-Pminimize,tomcat) from the UI source tree, and clear your browser's offline application cache, you should get back to an unminified state. Ray On Mon, Jul 1, 2013 at 4:24 PM, Aron Roberts < aron@socrates.berkeley.edu > wrote: <blockquote> Hi Al, Having written that, I'm now a bit confused ... I don't see files in the UI source code folder or in the deployed UI folder in the Tomcat server folder named index.css, myCollectionSpace.css, etc. in my stock 3.2.3/3.3 distribution. I've also had the experience that changing only cspace.css - a stylesheet which is referenced from most/all HTML pages - should be sufficient to make that logo change universally. (Perhaps someone else on this list might wish to comment further ...) No matter for your demo - if it works, it's absolutely all good :-) - but as/when you get around to doing a more substantial configuration, we can revisit this, as you see fit. Aron On Mon, Jul 1, 2013 at 4:16 PM, Aron Roberts < aron@socrates.berkeley.edu > wrote: > Excellent - glad to hear of this success, Al! > Aron > > On Mon, Jul 1, 2013 at 3:56 PM, Al Bersch < abersch@museumca.org > wrote: >> Hi Aron, all, >> >> So, I didn't realize that I also needed to make also make changes to the >> index.css, myCollectionSpace.css, etc, for the logo to change on all pages. >> Once I made those changes, the new logo appears. >> >> thanks again for your time, >> >> Al >> >> Al Bersch >> Digital Project Coordinator >> Oakland Museum of California >> 1000 Oak Street, Oakland, CA 94607 >> abersch@museumca.org >> 510-318-8468 >> ________________________________ >> From: "Aron Roberts" < aron@socrates.berkeley.edu > >> To: "Al Bersch" < abersch@museumca.org > >> Cc: "talk" < talk@lists.collectionspace.org >, "Chris Hoffman" >> < chris_h@berkeley.edu >, "Ray Lee" < rhlee@berkeley.edu >, "Becky Escamilla" >> < rescamilla@museumca.org > >> Sent: Monday, July 1, 2013 3:16:33 PM >> >> Subject: Re: error when running mvn deploy >> >> Thanks, Al. Based on that directory path, it seems likely you may >> have been doing 'scenario A' - editing configuration files (and adding >> a custom logo) directly in place, in the Tomcat server folder. >> >> In scenario b, you will have these two folders: >> >> A source code folder where you can customize the 'core' tenant >> * {the location of some folder where you downloaded the UI source >> code}/ui/src/main/webapp/tenants/core/ >> (which can have 'css' and 'images' sub-folders, which you can also >> create if not already present); and >> A corresponding target folder within the Tomcat server folder to which >> your changes will be copied (deployed); e.g.: >> * ~/tomcat/webapps/cspace-ui/tenants/core >> >> To deploy (copy) any changes you might make in that source code >> folder, to one or more relevant folders within the Tomcat server >> folder, making those changes 'live,' you'd go into the top level of >> that source code folder: >> * {some folder where you downloaded the UI source code}/ui >> >> and run: >> >> ant deploy -DskipTests >> (note: not "mvn deploy -DskipTests" - I'd missed noticing that earlier) >> >> This would then copy those files into the Tomcat server folder. >> >> Aron >> >> On Mon, Jul 1, 2013 at 3:01 PM, Al Bersch < abersch@museumca.org > wrote: >>> Hi Aron, >>> >>> Thanks, that makes sense. It was scenario B we were doing, and I must have >>> run mvn deploy -DskipTests in the wrong folder. However, I'm not sure what >>> the "top level of our folder containing source code for the relevant >>> CollectionSpace layer" is, because the code we were working with was in >>> the >>> tomcat folder (the path looks like >>> ~/tomcat/webapps/cspace-ui/tenants/core/css). Any suggestions? >>> >>> thanks again, >>> >>> Al >>> >>> Al Bersch >>> Digital Project Coordinator >>> Oakland Museum of California >>> 1000 Oak Street, Oakland, CA 94607 >>> abersch@museumca.org >>> 510-318-8468 >>> ________________________________ >>> From: "Aron Roberts" < aron@socrates.berkeley.edu > >>> To: "Al Bersch" < abersch@museumca.org > >>> Cc: "talk" < talk@lists.collectionspace.org >, "Chris Hoffman" >>> < chris_h@berkeley.edu >, "Ray Lee" < rhlee@berkeley.edu >, "Becky Escamilla" >>> < rescamilla@museumca.org > >>> Sent: Monday, July 1, 2013 2:53:14 PM >>> Subject: Re: error when running mvn deploy >>> >>> >>> Hi Al, >>> >>> It looks like the relevant document on the wiki on 'branding' a >>> CollectionSpace system with your own logo >>> ( http://wiki.collectionspace.org/display/DOC/How+to+add+branding ) >>> suggests that you: >>> >>> a) make changes directly within the Tomcat server folder; >>> as contrasted with >>> b) making them within your source code directory, then copying >>> (deploying) them to the server. >>> >>> (The first method, a), is quick and easy, while the second method, b), >>> allows you to document your changes, retain successive versions if you >>> need to roll back from mistakes, and reliably deploy those changes in >>> the future.) >>> >>> If you've used method a), directly modifying files in place in the >>> server folder, you don't need to run the deploy command at all. You >>> should be able to see your changes right away, after you clear your >>> browser's caches. (If you don't, you could try also restarting the >>> CollectionSpace server.) >>> >>> If you've used the latter method, b), following my example here >>> >>> ( https://github.com/aronr/ui/commit/eb5749db997dc2bdae7510d987140d9f316395d2 ) >>> then you'll want to run the 'mvn deploy -DskipTests' command from the >>> top level of your folder containing source code for the relevant >>> CollectionSpace layer, rather than from a folder inside the Tomcat >>> folder. That'll deploy (copy) your changes from that source code >>> folder, into the Tomcat server folder. >>> >>> (The error message "there is no POM in this directory >>> >>> (/usr/local/share/apache-tomcat-6.0.33/webapps/cspace-ui/tenants/core/images" >>> suggests the latter scenario.) >>> >>> Hope this helps! >>> Aron >>> >>> On Mon, Jul 1, 2013 at 1:41 PM, Al Bersch < abersch@museumca.org > wrote: >>>> Hello talk, and Aron, >>>> >>>> Regarding the customization instructions Aron sent us on how to change >>>> the >>>> logo in cspace, I ran into the following error when running mvn deploy >>>> -DskipTests. Do you have any ideas as to why this would happen? Thanks so >>>> much! >>>> >>>> [INFO] Scanning for projects... >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] BUILD FAILURE >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Total time: 0.230s >>>> [INFO] Finished at: Mon Jul 01 13:33:24 PDT 2013 >>>> [INFO] Final Memory: 3M/30M >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [ERROR] The goal you specified requires a project to execute but there is >>>> no >>>> POM in this directory >>>> >>>> >>>> (/usr/local/share/apache-tomcat-6.0.33/webapps/cspace-ui/tenants/core/images). >>>> Please verify you invoked Maven from the correct directory. -> [Help 1] >>>> [ERROR] >>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the >>>> -e >>>> switch. >>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >>>> [ERROR] >>>> [ERROR] For more information about the errors and possible solutions, >>>> please >>>> read the following articles: >>>> [ERROR] [Help 1] >>>> http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException >>>> >>>> Al Bersch >>>> Digital Project Coordinator >>>> Oakland Museum of California >>>> 1000 Oak Street, Oakland, CA 94607 >>>> abersch@museumca.org >>>> 510-318-8468 >>>> ________________________________ >>>> From: "Aron Roberts" < aron@socrates.berkeley.edu > >>>> To: "Al Bersch" < abersch@museumca.org >, "Becky Escamilla" >>>> < rescamilla@museumca.org > >>>> Cc: "Chris Hoffman" < chris_h@berkeley.edu >, "Ray Lee" >>>> < rhlee@berkeley.edu > >>>> Sent: Monday, June 10, 2013 9:03:36 PM >>>> Subject: A couple of starting-out CollectionSpace customizations >>>> >>>> Hi Becky and Al, >>>> >>>> A few notes, below, on making a couple of 'starting-out' >>>> customizations. For simplicity, you might make these in the >>>> already-created, demonstration 'core' tenant. >>>> >>>> FYI, >>>> Aron >>>> >>>> -- >>>> >>>> (Recommendation: start the CollectionSpace server before making the >>>> following changes. This will help ensure those changes are made >>>> 'live.') >>>> >>>> * An example of how to replace the default CollectionSpace logo with >>>> the OMCA logo: >>>> >>>> Documentation: >>>> >>>> >>>> http://wiki.collectionspace.org/display/DOC/How+to+add+branding#Howtoaddbranding-howtologo >>>> >>>> Actual change(s) made, within the source code tree for >>>> CollectionSpace's user interface (UI) layer: >>>> >>>> >>>> https://github.com/aronr/ui/commit/da1cbdacf364beef1b4821cd2a3dbcbffba9a04d >>>> >>>> (Specifically, this change involved copying the file 'cspace.css', >>>> from the 'defaults' directory into a newly-created 'css' folder for >>>> your 'core' tenant, then changing lines 389-391 and 402-404, as per >>>> the documentation above, to specify the filename for your image, and >>>> its height and width dimensions. And the image file itself was copied >>>> into a newly-created 'images' folder for your 'core' tenant, alongside >>>> that new 'css' folder.) >>>> >>>> >>>> https://github.com/aronr/ui/commit/da1cbdacf364beef1b4821cd2a3dbcbffba9a04d#L0R389 >>>> >>>> To copy (deploy) these changes to the server folder, enter the >>>> following at a command prompt, from within the top-level folder of the >>>> UI source code tree: >>>> mvn deploy -DskipTests >>>> >>>> * An example of how to rename the Collection field in the Cataloging >>>> record to "OMCA Collection": >>>> >>>> Documentation: >>>> http://wiki.collectionspace.org/display/DOC/How+to+rename+a+field >>>> >>>> Actual change made - again, within the source code tree for >>>> CollectionSpace's user interface (UI) layer: >>>> >>>> >>>> https://github.com/aronr/ui/commit/eb5749db997dc2bdae7510d987140d9f316395d2 >>>> >>>> To copy (deploy) this change to the server, enter the following (i.e. >>>> a second time - or you can first make both changes described here and >>>> enter this command just once) at a command prompt, from within the >>>> top-level folder of the UI source code tree: >>>> mvn deploy -DskipTests >>>> >>>> To see the changes: >>>> >>>> * Clear your browser's cache(s) >>>> * Visit your login page; e.g. >>>> http://localhost:8180/collectionspace/core/ui/html >>>> (The new OMCA logo should appear on that page.) >>>> >>>> * Log in using the default administrator's username and password, >>>> shown on the login screen >>>> * Select "Create New" >>>> * Select "Cataloging" >>>> * Click the "Create" button >>>> (Look for the "OMCA Cataloging" field label on the left side of the >>>> Cataloging record screen, about five fields down.) >>>> >>>> A screenshot is attached. >>>> >>>> Aron >>>> >>>> P.S. Tomorrow, I'm expecting to also send an example of how to change >>>> the values in the drop-down menus for the Collection and Responsible >>>> Department fields, in Cataloging. >>>> >>> >> >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> _______________________________________________ Talk mailing list Talk@lists.collectionspace.org http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org </blockquote>

Uh oh, this might be my fault! It looks like in the VM I'm distributing, the UI is already built with minification/concatenation on. Ray On Mon, Jul 1, 2013 at 4:48 PM, Al Bersch <abersch@museumca.org> wrote: > Hi Ray, > > Thank you for this explanation. I had no idea we had minification turned > on. I will try running the clean install as you say. > > Thanks again, > > Al > Al Bersch > Digital Project Coordinator > Oakland Museum of California > 1000 Oak Street, Oakland, CA 94607 > abersch@museumca.org > 510-318-8468 > ------------------------------ > *From: *"Ray Lee" <rhlee@berkeley.edu> > *To: *"Aron Roberts" <aron@socrates.berkeley.edu> > *Cc: *"Al Bersch" <abersch@museumca.org>, "talk" < > talk@lists.collectionspace.org>, "Becky Escamilla" < > rescamilla@museumca.org> > *Sent: *Monday, July 1, 2013 4:43:19 PM > *Subject: *Re: [Talk] error when running mvn deploy > > > Some more detail: > > When you build with minification/concatenation turned on, all the css > files, including cspace.css, get concatenated into a few larger files (of > which index.css and myCollectionSpace.css are two), and those larger files > are deployed into the server. HTML files are also modified during the > process to load those concatenated files, instead of the individual source > files. That's why you end up having to edit multiple files in the server, > and editing cspace.css in the server has no effect. The advantage of this > is that there are fewer css files to download, so pages should load faster. > The downside is that they're hard to edit. > > Ray > > > > On Mon, Jul 1, 2013 at 4:33 PM, Ray Lee <rhlee@berkeley.edu> wrote: > >> Oh, I also missed that. >> >> Al, it looks like at some point you built the UI layer with >> minification/concatenation turned on, using mvn -Pminimize,tomcat clean >> install. That means that if you make changes to cspace.css in the source >> tree, you can't copy it by hand into the server. You have to do a mvn >> build. >> >> To make things simpler, I would not use minification at this point. It's >> really only meant for production servers. If you now do mvn clean install >> (without the (-Pminimize,tomcat) from the UI source tree, and clear your >> browser's offline application cache, you should get back to an unminified >> state. >> >> Ray >> >> >> >> >> On Mon, Jul 1, 2013 at 4:24 PM, Aron Roberts <aron@socrates.berkeley.edu>wrote: >> >>> Hi Al, >>> >>> Having written that, I'm now a bit confused ... I don't see files in >>> the UI source code folder or in the deployed UI folder in the Tomcat >>> server folder named index.css, myCollectionSpace.css, etc. in my stock >>> 3.2.3/3.3 distribution. I've also had the experience that changing >>> only cspace.css - a stylesheet which is referenced from most/all HTML >>> pages - should be sufficient to make that logo change universally. >>> (Perhaps someone else on this list might wish to comment further ...) >>> >>> No matter for your demo - if it works, it's absolutely all good :-) - >>> but as/when you get around to doing a more substantial configuration, >>> we can revisit this, as you see fit. >>> >>> Aron >>> >>> On Mon, Jul 1, 2013 at 4:16 PM, Aron Roberts <aron@socrates.berkeley.edu> >>> wrote: >>> > Excellent - glad to hear of this success, Al! >>> > Aron >>> > >>> > On Mon, Jul 1, 2013 at 3:56 PM, Al Bersch <abersch@museumca.org> >>> wrote: >>> >> Hi Aron, all, >>> >> >>> >> So, I didn't realize that I also needed to make also make changes to >>> the >>> >> index.css, myCollectionSpace.css, etc, for the logo to change on all >>> pages. >>> >> Once I made those changes, the new logo appears. >>> >> >>> >> thanks again for your time, >>> >> >>> >> Al >>> >> >>> >> Al Bersch >>> >> Digital Project Coordinator >>> >> Oakland Museum of California >>> >> 1000 Oak Street, Oakland, CA 94607 >>> >> abersch@museumca.org >>> >> 510-318-8468 >>> >> ________________________________ >>> >> From: "Aron Roberts" <aron@socrates.berkeley.edu> >>> >> To: "Al Bersch" <abersch@museumca.org> >>> >> Cc: "talk" <talk@lists.collectionspace.org>, "Chris Hoffman" >>> >> <chris_h@berkeley.edu>, "Ray Lee" <rhlee@berkeley.edu>, "Becky >>> Escamilla" >>> >> <rescamilla@museumca.org> >>> >> Sent: Monday, July 1, 2013 3:16:33 PM >>> >> >>> >> Subject: Re: error when running mvn deploy >>> >> >>> >> Thanks, Al. Based on that directory path, it seems likely you may >>> >> have been doing 'scenario A' - editing configuration files (and adding >>> >> a custom logo) directly in place, in the Tomcat server folder. >>> >> >>> >> In scenario b, you will have these two folders: >>> >> >>> >> A source code folder where you can customize the 'core' tenant >>> >> * {the location of some folder where you downloaded the UI source >>> >> code}/ui/src/main/webapp/tenants/core/ >>> >> (which can have 'css' and 'images' sub-folders, which you can also >>> >> create if not already present); and >>> >> A corresponding target folder within the Tomcat server folder to which >>> >> your changes will be copied (deployed); e.g.: >>> >> * ~/tomcat/webapps/cspace-ui/tenants/core >>> >> >>> >> To deploy (copy) any changes you might make in that source code >>> >> folder, to one or more relevant folders within the Tomcat server >>> >> folder, making those changes 'live,' you'd go into the top level of >>> >> that source code folder: >>> >> * {some folder where you downloaded the UI source code}/ui >>> >> >>> >> and run: >>> >> >>> >> ant deploy -DskipTests >>> >> (note: not "mvn deploy -DskipTests" - I'd missed noticing that >>> earlier) >>> >> >>> >> This would then copy those files into the Tomcat server folder. >>> >> >>> >> Aron >>> >> >>> >> On Mon, Jul 1, 2013 at 3:01 PM, Al Bersch <abersch@museumca.org> >>> wrote: >>> >>> Hi Aron, >>> >>> >>> >>> Thanks, that makes sense. It was scenario B we were doing, and I >>> must have >>> >>> run mvn deploy -DskipTests in the wrong folder. However, I'm not >>> sure what >>> >>> the "top level of our folder containing source code for the relevant >>> >>> CollectionSpace layer" is, because the code we were working with was >>> in >>> >>> the >>> >>> tomcat folder (the path looks like >>> >>> ~/tomcat/webapps/cspace-ui/tenants/core/css). Any suggestions? >>> >>> >>> >>> thanks again, >>> >>> >>> >>> Al >>> >>> >>> >>> Al Bersch >>> >>> Digital Project Coordinator >>> >>> Oakland Museum of California >>> >>> 1000 Oak Street, Oakland, CA 94607 >>> >>> abersch@museumca.org >>> >>> 510-318-8468 >>> >>> ________________________________ >>> >>> From: "Aron Roberts" <aron@socrates.berkeley.edu> >>> >>> To: "Al Bersch" <abersch@museumca.org> >>> >>> Cc: "talk" <talk@lists.collectionspace.org>, "Chris Hoffman" >>> >>> <chris_h@berkeley.edu>, "Ray Lee" <rhlee@berkeley.edu>, "Becky >>> Escamilla" >>> >>> <rescamilla@museumca.org> >>> >>> Sent: Monday, July 1, 2013 2:53:14 PM >>> >>> Subject: Re: error when running mvn deploy >>> >>> >>> >>> >>> >>> Hi Al, >>> >>> >>> >>> It looks like the relevant document on the wiki on 'branding' a >>> >>> CollectionSpace system with your own logo >>> >>> (http://wiki.collectionspace.org/display/DOC/How+to+add+branding) >>> >>> suggests that you: >>> >>> >>> >>> a) make changes directly within the Tomcat server folder; >>> >>> as contrasted with >>> >>> b) making them within your source code directory, then copying >>> >>> (deploying) them to the server. >>> >>> >>> >>> (The first method, a), is quick and easy, while the second method, >>> b), >>> >>> allows you to document your changes, retain successive versions if >>> you >>> >>> need to roll back from mistakes, and reliably deploy those changes in >>> >>> the future.) >>> >>> >>> >>> If you've used method a), directly modifying files in place in the >>> >>> server folder, you don't need to run the deploy command at all. You >>> >>> should be able to see your changes right away, after you clear your >>> >>> browser's caches. (If you don't, you could try also restarting the >>> >>> CollectionSpace server.) >>> >>> >>> >>> If you've used the latter method, b), following my example here >>> >>> >>> >>> ( >>> https://github.com/aronr/ui/commit/eb5749db997dc2bdae7510d987140d9f316395d2 >>> ) >>> >>> then you'll want to run the 'mvn deploy -DskipTests' command from the >>> >>> top level of your folder containing source code for the relevant >>> >>> CollectionSpace layer, rather than from a folder inside the Tomcat >>> >>> folder. That'll deploy (copy) your changes from that source code >>> >>> folder, into the Tomcat server folder. >>> >>> >>> >>> (The error message "there is no POM in this directory >>> >>> >>> >>> >>> (/usr/local/share/apache-tomcat-6.0.33/webapps/cspace-ui/tenants/core/images" >>> >>> suggests the latter scenario.) >>> >>> >>> >>> Hope this helps! >>> >>> Aron >>> >>> >>> >>> On Mon, Jul 1, 2013 at 1:41 PM, Al Bersch <abersch@museumca.org> >>> wrote: >>> >>>> Hello talk, and Aron, >>> >>>> >>> >>>> Regarding the customization instructions Aron sent us on how to >>> change >>> >>>> the >>> >>>> logo in cspace, I ran into the following error when running mvn >>> deploy >>> >>>> -DskipTests. Do you have any ideas as to why this would happen? >>> Thanks so >>> >>>> much! >>> >>>> >>> >>>> [INFO] Scanning for projects... >>> >>>> [INFO] >>> >>>> >>> ------------------------------------------------------------------------ >>> >>>> [INFO] BUILD FAILURE >>> >>>> [INFO] >>> >>>> >>> ------------------------------------------------------------------------ >>> >>>> [INFO] Total time: 0.230s >>> >>>> [INFO] Finished at: Mon Jul 01 13:33:24 PDT 2013 >>> >>>> [INFO] Final Memory: 3M/30M >>> >>>> [INFO] >>> >>>> >>> ------------------------------------------------------------------------ >>> >>>> [ERROR] The goal you specified requires a project to execute but >>> there is >>> >>>> no >>> >>>> POM in this directory >>> >>>> >>> >>>> >>> >>>> >>> (/usr/local/share/apache-tomcat-6.0.33/webapps/cspace-ui/tenants/core/images). >>> >>>> Please verify you invoked Maven from the correct directory. -> >>> [Help 1] >>> >>>> [ERROR] >>> >>>> [ERROR] To see the full stack trace of the errors, re-run Maven >>> with the >>> >>>> -e >>> >>>> switch. >>> >>>> [ERROR] Re-run Maven using the -X switch to enable full debug >>> logging. >>> >>>> [ERROR] >>> >>>> [ERROR] For more information about the errors and possible >>> solutions, >>> >>>> please >>> >>>> read the following articles: >>> >>>> [ERROR] [Help 1] >>> >>>> >>> http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException >>> >>>> >>> >>>> Al Bersch >>> >>>> Digital Project Coordinator >>> >>>> Oakland Museum of California >>> >>>> 1000 Oak Street, Oakland, CA 94607 >>> >>>> abersch@museumca.org >>> >>>> 510-318-8468 >>> >>>> ________________________________ >>> >>>> From: "Aron Roberts" <aron@socrates.berkeley.edu> >>> >>>> To: "Al Bersch" <abersch@museumca.org>, "Becky Escamilla" >>> >>>> <rescamilla@museumca.org> >>> >>>> Cc: "Chris Hoffman" <chris_h@berkeley.edu>, "Ray Lee" >>> >>>> <rhlee@berkeley.edu> >>> >>>> Sent: Monday, June 10, 2013 9:03:36 PM >>> >>>> Subject: A couple of starting-out CollectionSpace customizations >>> >>>> >>> >>>> Hi Becky and Al, >>> >>>> >>> >>>> A few notes, below, on making a couple of 'starting-out' >>> >>>> customizations. For simplicity, you might make these in the >>> >>>> already-created, demonstration 'core' tenant. >>> >>>> >>> >>>> FYI, >>> >>>> Aron >>> >>>> >>> >>>> -- >>> >>>> >>> >>>> (Recommendation: start the CollectionSpace server before making the >>> >>>> following changes. This will help ensure those changes are made >>> >>>> 'live.') >>> >>>> >>> >>>> * An example of how to replace the default CollectionSpace logo with >>> >>>> the OMCA logo: >>> >>>> >>> >>>> Documentation: >>> >>>> >>> >>>> >>> >>>> >>> http://wiki.collectionspace.org/display/DOC/How+to+add+branding#Howtoaddbranding-howtologo >>> >>>> >>> >>>> Actual change(s) made, within the source code tree for >>> >>>> CollectionSpace's user interface (UI) layer: >>> >>>> >>> >>>> >>> >>>> >>> https://github.com/aronr/ui/commit/da1cbdacf364beef1b4821cd2a3dbcbffba9a04d >>> >>>> >>> >>>> (Specifically, this change involved copying the file 'cspace.css', >>> >>>> from the 'defaults' directory into a newly-created 'css' folder for >>> >>>> your 'core' tenant, then changing lines 389-391 and 402-404, as per >>> >>>> the documentation above, to specify the filename for your image, and >>> >>>> its height and width dimensions. And the image file itself was >>> copied >>> >>>> into a newly-created 'images' folder for your 'core' tenant, >>> alongside >>> >>>> that new 'css' folder.) >>> >>>> >>> >>>> >>> >>>> >>> https://github.com/aronr/ui/commit/da1cbdacf364beef1b4821cd2a3dbcbffba9a04d#L0R389 >>> >>>> >>> >>>> To copy (deploy) these changes to the server folder, enter the >>> >>>> following at a command prompt, from within the top-level folder of >>> the >>> >>>> UI source code tree: >>> >>>> mvn deploy -DskipTests >>> >>>> >>> >>>> * An example of how to rename the Collection field in the Cataloging >>> >>>> record to "OMCA Collection": >>> >>>> >>> >>>> Documentation: >>> >>>> http://wiki.collectionspace.org/display/DOC/How+to+rename+a+field >>> >>>> >>> >>>> Actual change made - again, within the source code tree for >>> >>>> CollectionSpace's user interface (UI) layer: >>> >>>> >>> >>>> >>> >>>> >>> https://github.com/aronr/ui/commit/eb5749db997dc2bdae7510d987140d9f316395d2 >>> >>>> >>> >>>> To copy (deploy) this change to the server, enter the following >>> (i.e. >>> >>>> a second time - or you can first make both changes described here >>> and >>> >>>> enter this command just once) at a command prompt, from within the >>> >>>> top-level folder of the UI source code tree: >>> >>>> mvn deploy -DskipTests >>> >>>> >>> >>>> To see the changes: >>> >>>> >>> >>>> * Clear your browser's cache(s) >>> >>>> * Visit your login page; e.g. >>> >>>> http://localhost:8180/collectionspace/core/ui/html >>> >>>> (The new OMCA logo should appear on that page.) >>> >>>> >>> >>>> * Log in using the default administrator's username and password, >>> >>>> shown on the login screen >>> >>>> * Select "Create New" >>> >>>> * Select "Cataloging" >>> >>>> * Click the "Create" button >>> >>>> (Look for the "OMCA Cataloging" field label on the left side of the >>> >>>> Cataloging record screen, about five fields down.) >>> >>>> >>> >>>> A screenshot is attached. >>> >>>> >>> >>>> Aron >>> >>>> >>> >>>> P.S. Tomorrow, I'm expecting to also send an example of how to >>> change >>> >>>> the values in the drop-down menus for the Collection and Responsible >>> >>>> Department fields, in Cataloging. >>> >>>> >>> >>> >>> >> >>> >> >>> >> _______________________________________________ >>> >> Talk mailing list >>> >> Talk@lists.collectionspace.org >>> >> >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>> >> >>> >>> _______________________________________________ >>> Talk mailing list >>> Talk@lists.collectionspace.org >>> >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>> >> >> > >

Ok, it's not anything I did. The cspace tarball comes with the ui layer minified. I forget, is that intentional? So that means that if you want it unminified for development, you should first do a mvn clean install from the ui source tree, and clear the offline application cache in your browser. At that point, you'll have files deployed in the server that look a lot more like the files in the source tree, and copying individual files from the source tree into the server will work. Ray On Mon, Jul 1, 2013 at 4:59 PM, Ray Lee <rhlee@berkeley.edu> wrote: > Uh oh, this might be my fault! It looks like in the VM I'm distributing, > the UI is already built with minification/concatenation on. > > Ray > > > On Mon, Jul 1, 2013 at 4:48 PM, Al Bersch <abersch@museumca.org> wrote: > >> Hi Ray, >> >> Thank you for this explanation. I had no idea we had minification turned >> on. I will try running the clean install as you say. >> >> Thanks again, >> >> Al >> Al Bersch >> Digital Project Coordinator >> Oakland Museum of California >> 1000 Oak Street, Oakland, CA 94607 >> abersch@museumca.org >> 510-318-8468 >> ------------------------------ >> *From: *"Ray Lee" <rhlee@berkeley.edu> >> *To: *"Aron Roberts" <aron@socrates.berkeley.edu> >> *Cc: *"Al Bersch" <abersch@museumca.org>, "talk" < >> talk@lists.collectionspace.org>, "Becky Escamilla" < >> rescamilla@museumca.org> >> *Sent: *Monday, July 1, 2013 4:43:19 PM >> *Subject: *Re: [Talk] error when running mvn deploy >> >> >> Some more detail: >> >> When you build with minification/concatenation turned on, all the css >> files, including cspace.css, get concatenated into a few larger files (of >> which index.css and myCollectionSpace.css are two), and those larger files >> are deployed into the server. HTML files are also modified during the >> process to load those concatenated files, instead of the individual source >> files. That's why you end up having to edit multiple files in the server, >> and editing cspace.css in the server has no effect. The advantage of this >> is that there are fewer css files to download, so pages should load faster. >> The downside is that they're hard to edit. >> >> Ray >> >> >> >> On Mon, Jul 1, 2013 at 4:33 PM, Ray Lee <rhlee@berkeley.edu> wrote: >> >>> Oh, I also missed that. >>> >>> Al, it looks like at some point you built the UI layer with >>> minification/concatenation turned on, using mvn -Pminimize,tomcat clean >>> install. That means that if you make changes to cspace.css in the source >>> tree, you can't copy it by hand into the server. You have to do a mvn >>> build. >>> >>> To make things simpler, I would not use minification at this point. It's >>> really only meant for production servers. If you now do mvn clean install >>> (without the (-Pminimize,tomcat) from the UI source tree, and clear your >>> browser's offline application cache, you should get back to an unminified >>> state. >>> >>> Ray >>> >>> >>> >>> >>> On Mon, Jul 1, 2013 at 4:24 PM, Aron Roberts <aron@socrates.berkeley.edu >>> > wrote: >>> >>>> Hi Al, >>>> >>>> Having written that, I'm now a bit confused ... I don't see files in >>>> the UI source code folder or in the deployed UI folder in the Tomcat >>>> server folder named index.css, myCollectionSpace.css, etc. in my stock >>>> 3.2.3/3.3 distribution. I've also had the experience that changing >>>> only cspace.css - a stylesheet which is referenced from most/all HTML >>>> pages - should be sufficient to make that logo change universally. >>>> (Perhaps someone else on this list might wish to comment further ...) >>>> >>>> No matter for your demo - if it works, it's absolutely all good :-) - >>>> but as/when you get around to doing a more substantial configuration, >>>> we can revisit this, as you see fit. >>>> >>>> Aron >>>> >>>> On Mon, Jul 1, 2013 at 4:16 PM, Aron Roberts < >>>> aron@socrates.berkeley.edu> wrote: >>>> > Excellent - glad to hear of this success, Al! >>>> > Aron >>>> > >>>> > On Mon, Jul 1, 2013 at 3:56 PM, Al Bersch <abersch@museumca.org> >>>> wrote: >>>> >> Hi Aron, all, >>>> >> >>>> >> So, I didn't realize that I also needed to make also make changes to >>>> the >>>> >> index.css, myCollectionSpace.css, etc, for the logo to change on all >>>> pages. >>>> >> Once I made those changes, the new logo appears. >>>> >> >>>> >> thanks again for your time, >>>> >> >>>> >> Al >>>> >> >>>> >> Al Bersch >>>> >> Digital Project Coordinator >>>> >> Oakland Museum of California >>>> >> 1000 Oak Street, Oakland, CA 94607 >>>> >> abersch@museumca.org >>>> >> 510-318-8468 >>>> >> ________________________________ >>>> >> From: "Aron Roberts" <aron@socrates.berkeley.edu> >>>> >> To: "Al Bersch" <abersch@museumca.org> >>>> >> Cc: "talk" <talk@lists.collectionspace.org>, "Chris Hoffman" >>>> >> <chris_h@berkeley.edu>, "Ray Lee" <rhlee@berkeley.edu>, "Becky >>>> Escamilla" >>>> >> <rescamilla@museumca.org> >>>> >> Sent: Monday, July 1, 2013 3:16:33 PM >>>> >> >>>> >> Subject: Re: error when running mvn deploy >>>> >> >>>> >> Thanks, Al. Based on that directory path, it seems likely you may >>>> >> have been doing 'scenario A' - editing configuration files (and >>>> adding >>>> >> a custom logo) directly in place, in the Tomcat server folder. >>>> >> >>>> >> In scenario b, you will have these two folders: >>>> >> >>>> >> A source code folder where you can customize the 'core' tenant >>>> >> * {the location of some folder where you downloaded the UI source >>>> >> code}/ui/src/main/webapp/tenants/core/ >>>> >> (which can have 'css' and 'images' sub-folders, which you can also >>>> >> create if not already present); and >>>> >> A corresponding target folder within the Tomcat server folder to >>>> which >>>> >> your changes will be copied (deployed); e.g.: >>>> >> * ~/tomcat/webapps/cspace-ui/tenants/core >>>> >> >>>> >> To deploy (copy) any changes you might make in that source code >>>> >> folder, to one or more relevant folders within the Tomcat server >>>> >> folder, making those changes 'live,' you'd go into the top level of >>>> >> that source code folder: >>>> >> * {some folder where you downloaded the UI source code}/ui >>>> >> >>>> >> and run: >>>> >> >>>> >> ant deploy -DskipTests >>>> >> (note: not "mvn deploy -DskipTests" - I'd missed noticing that >>>> earlier) >>>> >> >>>> >> This would then copy those files into the Tomcat server folder. >>>> >> >>>> >> Aron >>>> >> >>>> >> On Mon, Jul 1, 2013 at 3:01 PM, Al Bersch <abersch@museumca.org> >>>> wrote: >>>> >>> Hi Aron, >>>> >>> >>>> >>> Thanks, that makes sense. It was scenario B we were doing, and I >>>> must have >>>> >>> run mvn deploy -DskipTests in the wrong folder. However, I'm not >>>> sure what >>>> >>> the "top level of our folder containing source code for the relevant >>>> >>> CollectionSpace layer" is, because the code we were working with >>>> was in >>>> >>> the >>>> >>> tomcat folder (the path looks like >>>> >>> ~/tomcat/webapps/cspace-ui/tenants/core/css). Any suggestions? >>>> >>> >>>> >>> thanks again, >>>> >>> >>>> >>> Al >>>> >>> >>>> >>> Al Bersch >>>> >>> Digital Project Coordinator >>>> >>> Oakland Museum of California >>>> >>> 1000 Oak Street, Oakland, CA 94607 >>>> >>> abersch@museumca.org >>>> >>> 510-318-8468 >>>> >>> ________________________________ >>>> >>> From: "Aron Roberts" <aron@socrates.berkeley.edu> >>>> >>> To: "Al Bersch" <abersch@museumca.org> >>>> >>> Cc: "talk" <talk@lists.collectionspace.org>, "Chris Hoffman" >>>> >>> <chris_h@berkeley.edu>, "Ray Lee" <rhlee@berkeley.edu>, "Becky >>>> Escamilla" >>>> >>> <rescamilla@museumca.org> >>>> >>> Sent: Monday, July 1, 2013 2:53:14 PM >>>> >>> Subject: Re: error when running mvn deploy >>>> >>> >>>> >>> >>>> >>> Hi Al, >>>> >>> >>>> >>> It looks like the relevant document on the wiki on 'branding' a >>>> >>> CollectionSpace system with your own logo >>>> >>> (http://wiki.collectionspace.org/display/DOC/How+to+add+branding) >>>> >>> suggests that you: >>>> >>> >>>> >>> a) make changes directly within the Tomcat server folder; >>>> >>> as contrasted with >>>> >>> b) making them within your source code directory, then copying >>>> >>> (deploying) them to the server. >>>> >>> >>>> >>> (The first method, a), is quick and easy, while the second method, >>>> b), >>>> >>> allows you to document your changes, retain successive versions if >>>> you >>>> >>> need to roll back from mistakes, and reliably deploy those changes >>>> in >>>> >>> the future.) >>>> >>> >>>> >>> If you've used method a), directly modifying files in place in the >>>> >>> server folder, you don't need to run the deploy command at all. You >>>> >>> should be able to see your changes right away, after you clear your >>>> >>> browser's caches. (If you don't, you could try also restarting the >>>> >>> CollectionSpace server.) >>>> >>> >>>> >>> If you've used the latter method, b), following my example here >>>> >>> >>>> >>> ( >>>> https://github.com/aronr/ui/commit/eb5749db997dc2bdae7510d987140d9f316395d2 >>>> ) >>>> >>> then you'll want to run the 'mvn deploy -DskipTests' command from >>>> the >>>> >>> top level of your folder containing source code for the relevant >>>> >>> CollectionSpace layer, rather than from a folder inside the Tomcat >>>> >>> folder. That'll deploy (copy) your changes from that source code >>>> >>> folder, into the Tomcat server folder. >>>> >>> >>>> >>> (The error message "there is no POM in this directory >>>> >>> >>>> >>> >>>> (/usr/local/share/apache-tomcat-6.0.33/webapps/cspace-ui/tenants/core/images" >>>> >>> suggests the latter scenario.) >>>> >>> >>>> >>> Hope this helps! >>>> >>> Aron >>>> >>> >>>> >>> On Mon, Jul 1, 2013 at 1:41 PM, Al Bersch <abersch@museumca.org> >>>> wrote: >>>> >>>> Hello talk, and Aron, >>>> >>>> >>>> >>>> Regarding the customization instructions Aron sent us on how to >>>> change >>>> >>>> the >>>> >>>> logo in cspace, I ran into the following error when running mvn >>>> deploy >>>> >>>> -DskipTests. Do you have any ideas as to why this would happen? >>>> Thanks so >>>> >>>> much! >>>> >>>> >>>> >>>> [INFO] Scanning for projects... >>>> >>>> [INFO] >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> [INFO] BUILD FAILURE >>>> >>>> [INFO] >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> [INFO] Total time: 0.230s >>>> >>>> [INFO] Finished at: Mon Jul 01 13:33:24 PDT 2013 >>>> >>>> [INFO] Final Memory: 3M/30M >>>> >>>> [INFO] >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> [ERROR] The goal you specified requires a project to execute but >>>> there is >>>> >>>> no >>>> >>>> POM in this directory >>>> >>>> >>>> >>>> >>>> >>>> >>>> (/usr/local/share/apache-tomcat-6.0.33/webapps/cspace-ui/tenants/core/images). >>>> >>>> Please verify you invoked Maven from the correct directory. -> >>>> [Help 1] >>>> >>>> [ERROR] >>>> >>>> [ERROR] To see the full stack trace of the errors, re-run Maven >>>> with the >>>> >>>> -e >>>> >>>> switch. >>>> >>>> [ERROR] Re-run Maven using the -X switch to enable full debug >>>> logging. >>>> >>>> [ERROR] >>>> >>>> [ERROR] For more information about the errors and possible >>>> solutions, >>>> >>>> please >>>> >>>> read the following articles: >>>> >>>> [ERROR] [Help 1] >>>> >>>> >>>> http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException >>>> >>>> >>>> >>>> Al Bersch >>>> >>>> Digital Project Coordinator >>>> >>>> Oakland Museum of California >>>> >>>> 1000 Oak Street, Oakland, CA 94607 >>>> >>>> abersch@museumca.org >>>> >>>> 510-318-8468 >>>> >>>> ________________________________ >>>> >>>> From: "Aron Roberts" <aron@socrates.berkeley.edu> >>>> >>>> To: "Al Bersch" <abersch@museumca.org>, "Becky Escamilla" >>>> >>>> <rescamilla@museumca.org> >>>> >>>> Cc: "Chris Hoffman" <chris_h@berkeley.edu>, "Ray Lee" >>>> >>>> <rhlee@berkeley.edu> >>>> >>>> Sent: Monday, June 10, 2013 9:03:36 PM >>>> >>>> Subject: A couple of starting-out CollectionSpace customizations >>>> >>>> >>>> >>>> Hi Becky and Al, >>>> >>>> >>>> >>>> A few notes, below, on making a couple of 'starting-out' >>>> >>>> customizations. For simplicity, you might make these in the >>>> >>>> already-created, demonstration 'core' tenant. >>>> >>>> >>>> >>>> FYI, >>>> >>>> Aron >>>> >>>> >>>> >>>> -- >>>> >>>> >>>> >>>> (Recommendation: start the CollectionSpace server before making the >>>> >>>> following changes. This will help ensure those changes are made >>>> >>>> 'live.') >>>> >>>> >>>> >>>> * An example of how to replace the default CollectionSpace logo >>>> with >>>> >>>> the OMCA logo: >>>> >>>> >>>> >>>> Documentation: >>>> >>>> >>>> >>>> >>>> >>>> >>>> http://wiki.collectionspace.org/display/DOC/How+to+add+branding#Howtoaddbranding-howtologo >>>> >>>> >>>> >>>> Actual change(s) made, within the source code tree for >>>> >>>> CollectionSpace's user interface (UI) layer: >>>> >>>> >>>> >>>> >>>> >>>> >>>> https://github.com/aronr/ui/commit/da1cbdacf364beef1b4821cd2a3dbcbffba9a04d >>>> >>>> >>>> >>>> (Specifically, this change involved copying the file 'cspace.css', >>>> >>>> from the 'defaults' directory into a newly-created 'css' folder for >>>> >>>> your 'core' tenant, then changing lines 389-391 and 402-404, as per >>>> >>>> the documentation above, to specify the filename for your image, >>>> and >>>> >>>> its height and width dimensions. And the image file itself was >>>> copied >>>> >>>> into a newly-created 'images' folder for your 'core' tenant, >>>> alongside >>>> >>>> that new 'css' folder.) >>>> >>>> >>>> >>>> >>>> >>>> >>>> https://github.com/aronr/ui/commit/da1cbdacf364beef1b4821cd2a3dbcbffba9a04d#L0R389 >>>> >>>> >>>> >>>> To copy (deploy) these changes to the server folder, enter the >>>> >>>> following at a command prompt, from within the top-level folder of >>>> the >>>> >>>> UI source code tree: >>>> >>>> mvn deploy -DskipTests >>>> >>>> >>>> >>>> * An example of how to rename the Collection field in the >>>> Cataloging >>>> >>>> record to "OMCA Collection": >>>> >>>> >>>> >>>> Documentation: >>>> >>>> http://wiki.collectionspace.org/display/DOC/How+to+rename+a+field >>>> >>>> >>>> >>>> Actual change made - again, within the source code tree for >>>> >>>> CollectionSpace's user interface (UI) layer: >>>> >>>> >>>> >>>> >>>> >>>> >>>> https://github.com/aronr/ui/commit/eb5749db997dc2bdae7510d987140d9f316395d2 >>>> >>>> >>>> >>>> To copy (deploy) this change to the server, enter the following >>>> (i.e. >>>> >>>> a second time - or you can first make both changes described here >>>> and >>>> >>>> enter this command just once) at a command prompt, from within the >>>> >>>> top-level folder of the UI source code tree: >>>> >>>> mvn deploy -DskipTests >>>> >>>> >>>> >>>> To see the changes: >>>> >>>> >>>> >>>> * Clear your browser's cache(s) >>>> >>>> * Visit your login page; e.g. >>>> >>>> http://localhost:8180/collectionspace/core/ui/html >>>> >>>> (The new OMCA logo should appear on that page.) >>>> >>>> >>>> >>>> * Log in using the default administrator's username and password, >>>> >>>> shown on the login screen >>>> >>>> * Select "Create New" >>>> >>>> * Select "Cataloging" >>>> >>>> * Click the "Create" button >>>> >>>> (Look for the "OMCA Cataloging" field label on the left side of the >>>> >>>> Cataloging record screen, about five fields down.) >>>> >>>> >>>> >>>> A screenshot is attached. >>>> >>>> >>>> >>>> Aron >>>> >>>> >>>> >>>> P.S. Tomorrow, I'm expecting to also send an example of how to >>>> change >>>> >>>> the values in the drop-down menus for the Collection and >>>> Responsible >>>> >>>> Department fields, in Cataloging. >>>> >>>> >>>> >>> >>>> >> >>>> >> >>>> >> _______________________________________________ >>>> >> Talk mailing list >>>> >> Talk@lists.collectionspace.org >>>> >> >>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>>> >> >>>> >>>> _______________________________________________ >>>> Talk mailing list >>>> Talk@lists.collectionspace.org >>>> >>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>>> >>> >>> >> >> >

On Mon, Jul 1, 2013 at 5:20 PM, Ray Lee <rhlee@berkeley.edu> wrote: > So that means that if you want it unminified for development, you should > first do a mvn clean install from the ui source tree, and clear the offline > application cache in your browser. At that point, you'll have files deployed > in the server that look a lot more like the files in the source tree, and > copying individual files from the source tree into the server will work. Becky and Al: to follow-up on what Ray noted here: >When you build with minification/concatenation turned on, all the css files, including cspace.css, get concatenated into a few larger files (of which index.css and myCollectionSpace.css are two), and those larger files are deployed into the server. HTML files are also modified during the process to load those concatenated files, instead of the individual source files. That's why you end up having to edit multiple files in the server, and editing cspace.css in the server has no effect. The advantage of this is that there are fewer css files to download, so pages should load faster. The downside is that they're hard to edit. There's also a wiki page that discusses this option: http://wiki.collectionspace.org/display/collectionspace/UI+layer+deployment+with+minified+and+concatenated+source+code. Note: doing this is strictly optional. As Ray noted, if you choose this option, you may get modestly faster page loading, but with the tradeoff that the deployed files - not the ones you can edit within your UI source code tree, but the ones deployed (copied) to their corresponding folders within the Tomcat server folder - are more difficult to read and edit. > Ok, it's not anything I did. The cspace tarball comes with the ui layer > minified. I forget, is that intentional? Ray: We're building the tarball from the Tomcat folder on our QA server. When building the UI layer on QA, in turn, it appears we have minification/concatenation enabled - I'm not sure of the history behind that. Have set up an alternate build plan that builds the UI without that option, and will use that before generating the v3.3 tarball; will also update the tarball-building instructions accordingly. Aron > > Ray > > > On Mon, Jul 1, 2013 at 4:59 PM, Ray Lee <rhlee@berkeley.edu> wrote: >> >> Uh oh, this might be my fault! It looks like in the VM I'm distributing, >> the UI is already built with minification/concatenation on. >> >> Ray >> >> >> On Mon, Jul 1, 2013 at 4:48 PM, Al Bersch <abersch@museumca.org> wrote: >>> >>> Hi Ray, >>> >>> Thank you for this explanation. I had no idea we had minification turned >>> on. I will try running the clean install as you say. >>> >>> Thanks again, >>> >>> Al >>> Al Bersch >>> Digital Project Coordinator >>> Oakland Museum of California >>> 1000 Oak Street, Oakland, CA 94607 >>> abersch@museumca.org >>> 510-318-8468 >>> ________________________________ >>> From: "Ray Lee" <rhlee@berkeley.edu> >>> To: "Aron Roberts" <aron@socrates.berkeley.edu> >>> Cc: "Al Bersch" <abersch@museumca.org>, "talk" >>> <talk@lists.collectionspace.org>, "Becky Escamilla" >>> <rescamilla@museumca.org> >>> Sent: Monday, July 1, 2013 4:43:19 PM >>> Subject: Re: [Talk] error when running mvn deploy >>> >>> >>> Some more detail: >>> >>> When you build with minification/concatenation turned on, all the css >>> files, including cspace.css, get concatenated into a few larger files (of >>> which index.css and myCollectionSpace.css are two), and those larger files >>> are deployed into the server. HTML files are also modified during the >>> process to load those concatenated files, instead of the individual source >>> files. That's why you end up having to edit multiple files in the server, >>> and editing cspace.css in the server has no effect. The advantage of this is >>> that there are fewer css files to download, so pages should load faster. The >>> downside is that they're hard to edit. >>> >>> Ray >>> >>> >>> >>> On Mon, Jul 1, 2013 at 4:33 PM, Ray Lee <rhlee@berkeley.edu> wrote: >>>> >>>> Oh, I also missed that. >>>> >>>> Al, it looks like at some point you built the UI layer with >>>> minification/concatenation turned on, using mvn -Pminimize,tomcat clean >>>> install. That means that if you make changes to cspace.css in the source >>>> tree, you can't copy it by hand into the server. You have to do a mvn build. >>>> >>>> To make things simpler, I would not use minification at this point. It's >>>> really only meant for production servers. If you now do mvn clean install >>>> (without the (-Pminimize,tomcat) from the UI source tree, and clear your >>>> browser's offline application cache, you should get back to an unminified >>>> state. >>>> >>>> Ray >>>> >>>> >>>> >>>> >>>> On Mon, Jul 1, 2013 at 4:24 PM, Aron Roberts >>>> <aron@socrates.berkeley.edu> wrote: >>>>> >>>>> Hi Al, >>>>> >>>>> Having written that, I'm now a bit confused ... I don't see files in >>>>> the UI source code folder or in the deployed UI folder in the Tomcat >>>>> server folder named index.css, myCollectionSpace.css, etc. in my stock >>>>> 3.2.3/3.3 distribution. I've also had the experience that changing >>>>> only cspace.css - a stylesheet which is referenced from most/all HTML >>>>> pages - should be sufficient to make that logo change universally. >>>>> (Perhaps someone else on this list might wish to comment further ...) >>>>> >>>>> No matter for your demo - if it works, it's absolutely all good :-) - >>>>> but as/when you get around to doing a more substantial configuration, >>>>> we can revisit this, as you see fit. >>>>> >>>>> Aron >>>>> >>>>> On Mon, Jul 1, 2013 at 4:16 PM, Aron Roberts >>>>> <aron@socrates.berkeley.edu> wrote: >>>>> > Excellent - glad to hear of this success, Al! >>>>> > Aron >>>>> > >>>>> > On Mon, Jul 1, 2013 at 3:56 PM, Al Bersch <abersch@museumca.org> >>>>> > wrote: >>>>> >> Hi Aron, all, >>>>> >> >>>>> >> So, I didn't realize that I also needed to make also make changes to >>>>> >> the >>>>> >> index.css, myCollectionSpace.css, etc, for the logo to change on all >>>>> >> pages. >>>>> >> Once I made those changes, the new logo appears. >>>>> >> >>>>> >> thanks again for your time, >>>>> >> >>>>> >> Al >>>>> >> >>>>> >> Al Bersch >>>>> >> Digital Project Coordinator >>>>> >> Oakland Museum of California >>>>> >> 1000 Oak Street, Oakland, CA 94607 >>>>> >> abersch@museumca.org >>>>> >> 510-318-8468 >>>>> >> ________________________________ >>>>> >> From: "Aron Roberts" <aron@socrates.berkeley.edu> >>>>> >> To: "Al Bersch" <abersch@museumca.org> >>>>> >> Cc: "talk" <talk@lists.collectionspace.org>, "Chris Hoffman" >>>>> >> <chris_h@berkeley.edu>, "Ray Lee" <rhlee@berkeley.edu>, "Becky >>>>> >> Escamilla" >>>>> >> <rescamilla@museumca.org> >>>>> >> Sent: Monday, July 1, 2013 3:16:33 PM >>>>> >> >>>>> >> Subject: Re: error when running mvn deploy >>>>> >> >>>>> >> Thanks, Al. Based on that directory path, it seems likely you may >>>>> >> have been doing 'scenario A' - editing configuration files (and >>>>> >> adding >>>>> >> a custom logo) directly in place, in the Tomcat server folder. >>>>> >> >>>>> >> In scenario b, you will have these two folders: >>>>> >> >>>>> >> A source code folder where you can customize the 'core' tenant >>>>> >> * {the location of some folder where you downloaded the UI source >>>>> >> code}/ui/src/main/webapp/tenants/core/ >>>>> >> (which can have 'css' and 'images' sub-folders, which you can also >>>>> >> create if not already present); and >>>>> >> A corresponding target folder within the Tomcat server folder to >>>>> >> which >>>>> >> your changes will be copied (deployed); e.g.: >>>>> >> * ~/tomcat/webapps/cspace-ui/tenants/core >>>>> >> >>>>> >> To deploy (copy) any changes you might make in that source code >>>>> >> folder, to one or more relevant folders within the Tomcat server >>>>> >> folder, making those changes 'live,' you'd go into the top level of >>>>> >> that source code folder: >>>>> >> * {some folder where you downloaded the UI source code}/ui >>>>> >> >>>>> >> and run: >>>>> >> >>>>> >> ant deploy -DskipTests >>>>> >> (note: not "mvn deploy -DskipTests" - I'd missed noticing that >>>>> >> earlier) >>>>> >> >>>>> >> This would then copy those files into the Tomcat server folder. >>>>> >> >>>>> >> Aron >>>>> >> >>>>> >> On Mon, Jul 1, 2013 at 3:01 PM, Al Bersch <abersch@museumca.org> >>>>> >> wrote: >>>>> >>> Hi Aron, >>>>> >>> >>>>> >>> Thanks, that makes sense. It was scenario B we were doing, and I >>>>> >>> must have >>>>> >>> run mvn deploy -DskipTests in the wrong folder. However, I'm not >>>>> >>> sure what >>>>> >>> the "top level of our folder containing source code for the >>>>> >>> relevant >>>>> >>> CollectionSpace layer" is, because the code we were working with >>>>> >>> was in >>>>> >>> the >>>>> >>> tomcat folder (the path looks like >>>>> >>> ~/tomcat/webapps/cspace-ui/tenants/core/css). Any suggestions? >>>>> >>> >>>>> >>> thanks again, >>>>> >>> >>>>> >>> Al >>>>> >>> >>>>> >>> Al Bersch >>>>> >>> Digital Project Coordinator >>>>> >>> Oakland Museum of California >>>>> >>> 1000 Oak Street, Oakland, CA 94607 >>>>> >>> abersch@museumca.org >>>>> >>> 510-318-8468 >>>>> >>> ________________________________ >>>>> >>> From: "Aron Roberts" <aron@socrates.berkeley.edu> >>>>> >>> To: "Al Bersch" <abersch@museumca.org> >>>>> >>> Cc: "talk" <talk@lists.collectionspace.org>, "Chris Hoffman" >>>>> >>> <chris_h@berkeley.edu>, "Ray Lee" <rhlee@berkeley.edu>, "Becky >>>>> >>> Escamilla" >>>>> >>> <rescamilla@museumca.org> >>>>> >>> Sent: Monday, July 1, 2013 2:53:14 PM >>>>> >>> Subject: Re: error when running mvn deploy >>>>> >>> >>>>> >>> >>>>> >>> Hi Al, >>>>> >>> >>>>> >>> It looks like the relevant document on the wiki on 'branding' a >>>>> >>> CollectionSpace system with your own logo >>>>> >>> (http://wiki.collectionspace.org/display/DOC/How+to+add+branding) >>>>> >>> suggests that you: >>>>> >>> >>>>> >>> a) make changes directly within the Tomcat server folder; >>>>> >>> as contrasted with >>>>> >>> b) making them within your source code directory, then copying >>>>> >>> (deploying) them to the server. >>>>> >>> >>>>> >>> (The first method, a), is quick and easy, while the second method, >>>>> >>> b), >>>>> >>> allows you to document your changes, retain successive versions if >>>>> >>> you >>>>> >>> need to roll back from mistakes, and reliably deploy those changes >>>>> >>> in >>>>> >>> the future.) >>>>> >>> >>>>> >>> If you've used method a), directly modifying files in place in >>>>> >>> the >>>>> >>> server folder, you don't need to run the deploy command at all. >>>>> >>> You >>>>> >>> should be able to see your changes right away, after you clear your >>>>> >>> browser's caches. (If you don't, you could try also restarting the >>>>> >>> CollectionSpace server.) >>>>> >>> >>>>> >>> If you've used the latter method, b), following my example here >>>>> >>> >>>>> >>> >>>>> >>> (https://github.com/aronr/ui/commit/eb5749db997dc2bdae7510d987140d9f316395d2) >>>>> >>> then you'll want to run the 'mvn deploy -DskipTests' command from >>>>> >>> the >>>>> >>> top level of your folder containing source code for the relevant >>>>> >>> CollectionSpace layer, rather than from a folder inside the Tomcat >>>>> >>> folder. That'll deploy (copy) your changes from that source code >>>>> >>> folder, into the Tomcat server folder. >>>>> >>> >>>>> >>> (The error message "there is no POM in this directory >>>>> >>> >>>>> >>> >>>>> >>> (/usr/local/share/apache-tomcat-6.0.33/webapps/cspace-ui/tenants/core/images" >>>>> >>> suggests the latter scenario.) >>>>> >>> >>>>> >>> Hope this helps! >>>>> >>> Aron >>>>> >>> >>>>> >>> On Mon, Jul 1, 2013 at 1:41 PM, Al Bersch <abersch@museumca.org> >>>>> >>> wrote: >>>>> >>>> Hello talk, and Aron, >>>>> >>>> >>>>> >>>> Regarding the customization instructions Aron sent us on how to >>>>> >>>> change >>>>> >>>> the >>>>> >>>> logo in cspace, I ran into the following error when running mvn >>>>> >>>> deploy >>>>> >>>> -DskipTests. Do you have any ideas as to why this would happen? >>>>> >>>> Thanks so >>>>> >>>> much! >>>>> >>>> >>>>> >>>> [INFO] Scanning for projects... >>>>> >>>> [INFO] >>>>> >>>> >>>>> >>>> ------------------------------------------------------------------------ >>>>> >>>> [INFO] BUILD FAILURE >>>>> >>>> [INFO] >>>>> >>>> >>>>> >>>> ------------------------------------------------------------------------ >>>>> >>>> [INFO] Total time: 0.230s >>>>> >>>> [INFO] Finished at: Mon Jul 01 13:33:24 PDT 2013 >>>>> >>>> [INFO] Final Memory: 3M/30M >>>>> >>>> [INFO] >>>>> >>>> >>>>> >>>> ------------------------------------------------------------------------ >>>>> >>>> [ERROR] The goal you specified requires a project to execute but >>>>> >>>> there is >>>>> >>>> no >>>>> >>>> POM in this directory >>>>> >>>> >>>>> >>>> >>>>> >>>> >>>>> >>>> (/usr/local/share/apache-tomcat-6.0.33/webapps/cspace-ui/tenants/core/images). >>>>> >>>> Please verify you invoked Maven from the correct directory. -> >>>>> >>>> [Help 1] >>>>> >>>> [ERROR] >>>>> >>>> [ERROR] To see the full stack trace of the errors, re-run Maven >>>>> >>>> with the >>>>> >>>> -e >>>>> >>>> switch. >>>>> >>>> [ERROR] Re-run Maven using the -X switch to enable full debug >>>>> >>>> logging. >>>>> >>>> [ERROR] >>>>> >>>> [ERROR] For more information about the errors and possible >>>>> >>>> solutions, >>>>> >>>> please >>>>> >>>> read the following articles: >>>>> >>>> [ERROR] [Help 1] >>>>> >>>> >>>>> >>>> http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException >>>>> >>>> >>>>> >>>> Al Bersch >>>>> >>>> Digital Project Coordinator >>>>> >>>> Oakland Museum of California >>>>> >>>> 1000 Oak Street, Oakland, CA 94607 >>>>> >>>> abersch@museumca.org >>>>> >>>> 510-318-8468 >>>>> >>>> ________________________________ >>>>> >>>> From: "Aron Roberts" <aron@socrates.berkeley.edu> >>>>> >>>> To: "Al Bersch" <abersch@museumca.org>, "Becky Escamilla" >>>>> >>>> <rescamilla@museumca.org> >>>>> >>>> Cc: "Chris Hoffman" <chris_h@berkeley.edu>, "Ray Lee" >>>>> >>>> <rhlee@berkeley.edu> >>>>> >>>> Sent: Monday, June 10, 2013 9:03:36 PM >>>>> >>>> Subject: A couple of starting-out CollectionSpace customizations >>>>> >>>> >>>>> >>>> Hi Becky and Al, >>>>> >>>> >>>>> >>>> A few notes, below, on making a couple of 'starting-out' >>>>> >>>> customizations. For simplicity, you might make these in the >>>>> >>>> already-created, demonstration 'core' tenant. >>>>> >>>> >>>>> >>>> FYI, >>>>> >>>> Aron >>>>> >>>> >>>>> >>>> -- >>>>> >>>> >>>>> >>>> (Recommendation: start the CollectionSpace server before making >>>>> >>>> the >>>>> >>>> following changes. This will help ensure those changes are made >>>>> >>>> 'live.') >>>>> >>>> >>>>> >>>> * An example of how to replace the default CollectionSpace logo >>>>> >>>> with >>>>> >>>> the OMCA logo: >>>>> >>>> >>>>> >>>> Documentation: >>>>> >>>> >>>>> >>>> >>>>> >>>> >>>>> >>>> http://wiki.collectionspace.org/display/DOC/How+to+add+branding#Howtoaddbranding-howtologo >>>>> >>>> >>>>> >>>> Actual change(s) made, within the source code tree for >>>>> >>>> CollectionSpace's user interface (UI) layer: >>>>> >>>> >>>>> >>>> >>>>> >>>> >>>>> >>>> https://github.com/aronr/ui/commit/da1cbdacf364beef1b4821cd2a3dbcbffba9a04d >>>>> >>>> >>>>> >>>> (Specifically, this change involved copying the file 'cspace.css', >>>>> >>>> from the 'defaults' directory into a newly-created 'css' folder >>>>> >>>> for >>>>> >>>> your 'core' tenant, then changing lines 389-391 and 402-404, as >>>>> >>>> per >>>>> >>>> the documentation above, to specify the filename for your image, >>>>> >>>> and >>>>> >>>> its height and width dimensions. And the image file itself was >>>>> >>>> copied >>>>> >>>> into a newly-created 'images' folder for your 'core' tenant, >>>>> >>>> alongside >>>>> >>>> that new 'css' folder.) >>>>> >>>> >>>>> >>>> >>>>> >>>> >>>>> >>>> https://github.com/aronr/ui/commit/da1cbdacf364beef1b4821cd2a3dbcbffba9a04d#L0R389 >>>>> >>>> >>>>> >>>> To copy (deploy) these changes to the server folder, enter the >>>>> >>>> following at a command prompt, from within the top-level folder of >>>>> >>>> the >>>>> >>>> UI source code tree: >>>>> >>>> mvn deploy -DskipTests >>>>> >>>> >>>>> >>>> * An example of how to rename the Collection field in the >>>>> >>>> Cataloging >>>>> >>>> record to "OMCA Collection": >>>>> >>>> >>>>> >>>> Documentation: >>>>> >>>> http://wiki.collectionspace.org/display/DOC/How+to+rename+a+field >>>>> >>>> >>>>> >>>> Actual change made - again, within the source code tree for >>>>> >>>> CollectionSpace's user interface (UI) layer: >>>>> >>>> >>>>> >>>> >>>>> >>>> >>>>> >>>> https://github.com/aronr/ui/commit/eb5749db997dc2bdae7510d987140d9f316395d2 >>>>> >>>> >>>>> >>>> To copy (deploy) this change to the server, enter the following >>>>> >>>> (i.e. >>>>> >>>> a second time - or you can first make both changes described here >>>>> >>>> and >>>>> >>>> enter this command just once) at a command prompt, from within the >>>>> >>>> top-level folder of the UI source code tree: >>>>> >>>> mvn deploy -DskipTests >>>>> >>>> >>>>> >>>> To see the changes: >>>>> >>>> >>>>> >>>> * Clear your browser's cache(s) >>>>> >>>> * Visit your login page; e.g. >>>>> >>>> http://localhost:8180/collectionspace/core/ui/html >>>>> >>>> (The new OMCA logo should appear on that page.) >>>>> >>>> >>>>> >>>> * Log in using the default administrator's username and password, >>>>> >>>> shown on the login screen >>>>> >>>> * Select "Create New" >>>>> >>>> * Select "Cataloging" >>>>> >>>> * Click the "Create" button >>>>> >>>> (Look for the "OMCA Cataloging" field label on the left side of >>>>> >>>> the >>>>> >>>> Cataloging record screen, about five fields down.) >>>>> >>>> >>>>> >>>> A screenshot is attached. >>>>> >>>> >>>>> >>>> Aron >>>>> >>>> >>>>> >>>> P.S. Tomorrow, I'm expecting to also send an example of how to >>>>> >>>> change >>>>> >>>> the values in the drop-down menus for the Collection and >>>>> >>>> Responsible >>>>> >>>> Department fields, in Cataloging. >>>>> >>>> >>>>> >>> >>>>> >> >>>>> >> >>>>> >> _______________________________________________ >>>>> >> Talk mailing list >>>>> >> Talk@lists.collectionspace.org >>>>> >> >>>>> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>>>> >> >>>>> >>>>> _______________________________________________ >>>>> Talk mailing list >>>>> Talk@lists.collectionspace.org >>>>> >>>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>>> >>>> >>> >>> >> > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >