hi can you give me the full steps of installing mirag2 on ubuntu 18.04 with dspace 6
On Monday, November 7, 2016 at 9:36:29 PM UTC+3, Pedro Amorim wrote: > > Hello again, > > After realizing my problem had to do with npm and bower folder > permissions, I solved them manually, prior to 'mvn package': > > RUN cd /root && mkdir .cache .config .local .npm > RUN chown -R dspace:dspace /root > > This solved my problem. > Mirage2 was built successfully and everything is working fine. > However, I'm not very happy with this solution as it's clumsly and > shouldn't be necessary to manually create these dirs. > > This bug thread seems to accept this workaround as a final solution: > https://github.com/bower/bower/issues/2262 > > If anyone has successfully built 6.0 with Mirage2 on Debian Jessie without > this, please do let me know and share how they done it. > > Thanks all. > > Regards, > > Pedro Amorim > > segunda-feira, 7 de Novembro de 2016 às 12:48:18 UTC-1, Pedro Amorim > escreveu: >> >> Hello Ari, >> >> I'm using maven 3.3.9 through environment variable and it also outputs >> 3.3.9 from the 'mvn --version' command. >> >> However, I think I made some progress (in finding the cause of the >> problem at least). >> >> Upon closer inspection on that build, I noticed an error on the Mirage2 >> component: >> >> [ERROR] npm ERR! Linux 4.4.0-45-generic [ERROR] npm ERR! argv >> "/usr/src/DSpace-dspace-6.0/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node/node" >> >> "/usr/src/DSpace-dspace-6.0/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node/node_modules/npm/bin/npm-cli.js" >> >> "install" [ERROR] npm ERR! node v6.5.0 [ERROR] npm ERR! npm v3.10.8 [ERROR] >> npm ERR! path /root/.npm/grunt-contrib-compass/1.1.1/package [ERROR] npm >> ERR! code EACCES [ERROR] npm ERR! errno -13 [ERROR] npm ERR! syscall mkdir >> >> User DSpace cannot write in directory /root (didn't have this problem >> before). After manually rebuilding as user DSpace (using gosu), the same >> problem occurs. >> However, running the mvn package command as the 'root' user, it builds >> sucessfully (now the fun part), all files are there >> (themes/Mirage2/styles/main.css and >> themes/Mirage2/vendor/modernizr/modernizr.js) but now there's a new error: >> >> Syntax error: File to import not found or unreadable: >> ../vendor/bootstrap-sass-official/assets/stylesheets/bootstrap. >> >> This error is discussed here >> http://dspace.2283337.n4.nabble.com/Mirage-2-td4676411.html >> >> So, >> I wonder why that permission problem is happening in the first place and >> if I find and solve it's root cause I hope it'll resolve all my issues. >> >> Also, some additional info. >> I went back to my previous build (with maven 3.0.5) and it seems there >> really was a problem: >> >> WARNING: Error injecting: >> com.github.eirslett.maven.plugins.frontend.mojo.InstallNodeAndNpmMojo >> java.lang.NoClassDefFoundError: Lorg/eclipse/aether/RepositorySystemSession; >> >> Which doesn't show anymore, leading me to believe and confirm that 3.3.9 >> maven is indeed the solution for the initial problem, and now my problem >> lies elsewhere (as described above). >> >> Thanks for the help Ari. >> >> Regards, >> >> Pedro Amorim >> >> segunda-feira, 7 de Novembro de 2016 às 12:13:34 UTC-1, Ari escreveu: >>> >>> Hi, >>> my setup is little bit different. I have a separate images for compiling >>> and running. >>> here is the docker file I use for compiling if that helps: >>> >>> FROM centos:7RUN yum -y install tomcat ant curl git wget which >>> java-1.7.0-openjdk java-1.7.0-openjdk-devel ADD maven3/maven.sh >>> /etc/profile.d/RUN cd /opt/ && \ wget >>> http://www.nic.funet.fi/pub/mirrors/apache.org/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.tar.gz >>> && \ tar -zxvf apache-maven-3.3.9-bin.tar.gz && \ mv >>> /opt/apache-maven-3.3.9 /opt/maven && \ ln -s /opt/maven/bin/mvn >>> /usr/bin/mvn && \ chmod +x /etc/profile.d/maven.sh && \ source >>> /etc/profile.d/maven.sh && \mvn -version ADD DSpace /dspace-src/RUN chown >>> -R tomcat /dspace-srcUSER tomcatWORKDIR /dspace-srcRUN mvn package >>> -Dmirage2.on=true -P !dspace-jspuiWORKDIR >>> /dspace-src/dspace/target/dspace-installer >>> >>> >>> >>> ------------------------------ >>> *Lähettäjä:* [email protected] [[email protected]] >>> käyttäjän Pedro Amorim [[email protected]] puolesta >>> *Lähetetty:* 4. marraskuuta 2016 18:30 >>> *Vastaanottaja:* DSpace Technical Support >>> *Aihe:* [dspace-tech] Re: Compiling DSpace 6 with Mirage2 theme does >>> not generate CSS files >>> >>> Hello Ari, >>> >>> Thanks for coming back. >>> Please ignore the last post, as by mistake I ran the mvn package command >>> without the -Dmirage2=true so that error was because the theme was indeed >>> missing from the build process. >>> >>> However, after installing DSpace with maven 3.3.9, I still have the >>> problem (themes/Mirage2/styles/main.css and >>> themes/Mirage2/vendor/modernizr/modernizr.js missing). >>> >>> I am also using Docker and here's the whole build: >>> >>> https://hub.docker.com/r/governoregionalazores/dspace/builds/bjmu5wajuvqhjoxr7ftr2z8/ >>> >>> As far as I can tell, everything went smoothly, including the Mirage2 >>> XMLUI theme section. >>> >>> sexta-feira, 4 de Novembro de 2016 às 05:16:10 UTC-1, Ari escreveu: >>>> >>>> Hello Pedro, >>>> upgrading maven was enough for me. I'm quite certain that I didn't do >>>> anything else. Did you get any errors on compile? >>>> >>>> Ari >>>> >>>> On Thursday, 3 November 2016 17:40:17 UTC+2, Pedro Amorim wrote: >>>>> >>>>> Hello Ari. Im having the exact same problem. So I installed maven >>>>> 3.3.9 and rebuilt DSpace with mvn package. >>>>> However, now XMLUI only shows the error: >>>>> FileNotFoundException: >>>>> dspace/webapps/xmlui/themes/Mirage2/sitemap.xmap >>>>> >>>>> Did you do any other additional procedures ? >>>>> >>>>> Thanks, >>>>> Pedro Amorim >>>>> >>>>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "DSpace Technical Support" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/dspace-tech/2qQvNL2KOB8/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at https://groups.google.com/group/dspace-tech. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
