Good Day all,
I did some checks on my Mirage2 pre-requisites, and ran the following
command:
sudo mvn -U clean package -Dmirage2.on=true -Dmirage2.deps.included=false
and received three messages which I have included below.
- The 1st one looks like a warning I can ignore if not accessing DSpace
Mirage2 with IE6.
- The 2nd looks like I might need to respond intelligently.
- The 3rd looks like it is probably connected to the 2nd.
I expect a bit of a learning curve, but a search of the DSpace tech Support
forum yields nothing for "Exit value: 6".
I have doubts concerning just adding mvn -fn to the build command, as I am
worried what unexpectedly might not function later.
So i think I am close to solving my Mirage2 build issues, once I get over
this " "Exit value: 6" issue.
Any advice from the Mirage2 scheme users is welcome, along with anybody who
understands the pre-requisite software well enough to add insight.
--------->
Messages 1 and 2.
DEPRECATION WARNING on line 92 of
/usr/share/compass/frameworks/compass/stylesheets/compass/css3/_deprecated-support.scss:
#{} interpolation near operators will be simplified
in a future version of Sass. To preserve the current behavior, use quotes:
unquote('"$ie6-"#{$legacy-support-for-ie6}
"$ie7-"#{$legacy-support-for-ie7} "$ie8-"#{$legacy-support-for-ie8}')
You can use the sass-convert command to automatically fix most cases.
error styles/main.scss (Line 16: File to import not found or
unreadable: ../vendor/bootstrap-sass-official/assets/stylesheets/bootstrap.
Load paths:
Compass::SpriteImporter
/build/dspace-6.3-release/dspace/modules/xmlui-mirage2/target/themes/Mirage2/styles
/usr/share/compass/frameworks/compass/stylesheets)
Compilation failed in 1 files.
Warning: ↑ Use --force to continue.
--------->
Message 3.
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 01:24 min
[INFO] Finished at: 2020-02-11T15:32:47-04:00
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
com.soebes.maven.plugins:iterator-maven-plugin:0.3:iterator (default) on
project xmlui-mirage2: Command execution failed.: Process exited with an
error: 6 (Exit value: 6) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
On Thu, Feb 6, 2020 at 3:17 AM Paul Münch <muen...@staff.uni-marburg.de>
wrote:
> Hello,
>
> > .....were those of you running DSpace's Mirage2 theme, able to
> successfully implement the theme in-spite > of these warnings?
>
> Yes. These are only warnings.
>
> > Hence, I am interpreting your hint to mean I should look to see if I
> missed any important steps, or didn't
> > read and understand the provided instructions properly.
>
> It is important for the Mirage2-installation that your environment can
> solve the command 'npm'. When you have installed the 'nvm', you have to add
> the path to the script '/home/systemuser/.nvm/nvm.sh' to your environment.
> You can test it with open a terminal and run the command 'npm'.
>
> At the Ruby topic: We do not use JRuby but the standard Debian ruby
> package. Also Sass and Compass we install via standard packages
> 'ruby-compass' and 'ruby-sass'. These are available on Ubuntu, too.
>
> I hope this helps and kind regards,
>
> Paul Münch
>
> Am 04.02.20 um 15:53 schrieb Yerodin P:
>
> Good day all,
>
> Okay,
>
> Can those of you running the Mirage2 responsive theme assist with the
> answer to this question?
>
> In-spite of the following warnings:
>
> 1. Bower
>
> $ npm install -g bower
> npm WARN deprecated bower@1.8.8: We don't recommend using Bower for new
> projects. Please consider Yarn and Webpack or Parcel.
>
>
> 2. Ruby SASS
>
> $ gem install sass -v 3.3.14
> Ruby Sass Has Reached End-of-Life
> Ruby Sass should no longer be used, and will no longer be receiving any
> updates. See the Sass blog, and consider switching to the sassc gem
>
> .....were those of you running DSpace's Mirage2 theme, able to
> successfully implement the theme in-spite of these warnings?
>
> Yerodin P
> DSpace newbie.
>
> On Tue, Feb 4, 2020 at 9:40 AM Yerodin P <yerod...@gmail.com> wrote:
>
>> Thank you for the hint Paul,
>> Forgive me if you get this twice as I did a "reply all" from my Gmail
>> account.
>> I will try just the dspace-tech@googlegroups.com in my next post.
>>
>> Anyway......
>>
>> Close inspection indicates that your counsel is part of the steps
>> described here:
>>
>> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-xmlui-mirage2/readme.md#compass
>>
>> .... for loading Mirage2 prerequisites.
>>
>> I did encounter this suggestion after running the command:
>> $ curl -o-
>> https://raw.githubusercontent.com/creationix/nvm/v0.31.7/install.sh
>> | bash
>>
>>
>> => Close and reopen your terminal to start using nvm or run the following to
>> use it now:
>> $ export NVM_DIR="/home/yerodinp/.nvm"
>> $ [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
>>
>>
>> Hence, I am interpreting your hint to mean I should look to see if I
>> missed any important steps, or didn't read and understand the provided
>> instructions properly.
>>
>> According to the DSpace literature, once Mirage2 prerequisites are
>> successfully loaded, the build and implementation of Mirage2 should be easy
>> peasy.
>>
>> Will report my findings regardless of outcome and post solution if I find
>> out what I was doing wrong.
>>
>> Yerodin P
>> DSpace newbie.
>>
>>
>> On Mon, Feb 3, 2020 at 10:58 AM Paul Münch <muen...@staff.uni-marburg.de>
>> wrote:
>>
>>> Hello,
>>>
>>> during Node installation there is a hint:
>>>
>>> export NVM_DIR="$HOME/.nvm"[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"
>>>
>>>
>>> Use this in a script before the maven run. Or add it to your environment
>>> in a different way.
>>>
>>> I hope this helps and kind regards,
>>>
>>> Paul Münch
>>>
>>> Am 31.01.20 um 21:29 schrieb Yerodin P:
>>>
>>>
>>> Good Day all,
>>>
>>> Before I post for help with my problem, here are the system specifics on
>>> which I am running DSpace v6.3:
>>>
>>> - Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz, 2 cores, 4GB RAM
>>> - Ubuntu Server 18.04.2 LTS
>>> - PostgreSQL v10.10
>>> - OpenSSH_7.6
>>> - Tomcat7 in one instance and Tomcat8 in another.
>>> - javac 1.8.0_242
>>> - openjdk version "1.8.0_242"
>>> OpenJDK Runtime Environment (build
>>> 1.8.0_242-8u242-b08-0ubuntu3~18.04-b08)
>>> OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode)
>>>
>>> - Apache Maven 3.6.0
>>> Maven home: /usr/share/maven
>>> Java version: 1.8.0_242, vendor: Private Build, runtime:
>>> /usr/lib/jvm/java-8-openjdk-amd64/jre
>>> Default locale: en_US, platform encoding: UTF-8
>>> OS name: "linux", version: "4.15.0-76-generic", arch: "amd64", family:
>>> "unix"
>>>
>>>
>>> - Git version 2.17.1
>>> - $ rvm requirements
>>> Checking requirements for ubuntu.
>>> Requirements installation successful.
>>>
>>> - Compass successfully installed
>>> - Ruby-2.6.3 installed.
>>> - home/useraccount/.nvm/versions/node/v6.5.0/lib
>>> ├── bower@1.8.8
>>> ├── grunt@1.0.4
>>> ├── grunt-cli@1.3.2
>>>
>>> Please note:
>>> The standard Mirage XMLUI theme works fine for me.
>>> I have been able as a DSpace Admin, to do such things as batch upload of
>>> files and execute search statistics.
>>>
>>>
>>> *MY DSPACE PROBLEM*
>>>
>>> I was able to successfully:
>>>
>>> - load the pre-requisites for Mirage2
>>> - edit [dspace-source]/dspace/config/xmlui.xconf to uncomment the
>>> regular Mirage theme and add:
>>> <theme name="Mirage 2" regex=".*" path="Mirage2/" />
>>>
>>> - make adjustments to the file
>>> [dspace-source]/dspace-6.3-release/dspace/modules/xmlui-mirage2//pom.xml
>>> where I changed the version of the dependencies to reflect what was
>>> actually loaded.
>>>
>>> However, when I eventually ran:
>>> $ mvn -Dmirage2.on=true -Dmirage2.deps.included=false clean package
>>>
>>> Even though the directory
>>>
>>> /build/dspace-6.3-release/dspace/modules/xmlui-mirage2/target/themes/
>>>
>>> ..does exist, I got the following error message and am temporarily stuck
>>> at this part of the Mirage2 installation:
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Reactor Summary for DSpace Parent Project 6.3:
>>> [INFO]
>>> [INFO] DSpace Parent Project .............................. SUCCESS [
>>> 29.677 s]
>>> [INFO] DSpace Addon Modules ............................... SUCCESS [
>>> 0.019 s]
>>> [INFO] DSpace Kernel :: Additions and Local Customizations SUCCESS
>>> [01:42 min]
>>> [INFO] DSpace XML-UI Mirage2 Theme :: Local Customisations FAILURE [
>>> 49.864 s]
>>> [INFO] DSpace XML-UI (Manakin) :: Local Customizations .... SKIPPED
>>> [INFO] DSpace JSP-UI :: Local Customizations .............. SKIPPED
>>> [INFO] DSpace RDF :: Local Customizations ................. SKIPPED
>>> [INFO] DSpace REST :: Local Customizations ................ SKIPPED
>>> [INFO] DSpace SWORD :: Local Customizations ............... SKIPPED
>>> [INFO] DSpace SWORD v2 :: Local Customizations ............ SKIPPED
>>> [INFO] DSpace SOLR :: Local Customizations ................ SKIPPED
>>> [INFO] DSpace OAI-PMH :: Local Customizations ............. SKIPPED
>>> [INFO] DSpace Assembly and Configuration .................. SKIPPED
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Total time: 03:02 min
>>> [INFO] Finished at: 2020-01-30T16:05:17-04:00
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] Failed to execute goal
>>> com.soebes.maven.plugins:iterator-maven-plugin:0.3:iterator (default) on
>>> project xmlui-mirage2: Command execution failed.: Cannot run program "npm"
>>> (in directory
>>> "/build/dspace-6.3-release/dspace/modules/xmlui-mirage2/target/themes/Mirage2"):
>>> error=2, No such file or directory -> [Help 1]
>>>
>>> Your suggestions on moving forward are welcome.
>>>
>>> Yerodin P
>>> DSpace newbie.
>>>
>>> --
>>> 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 dspace-tech+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/dspace-tech/feb2a656-28c6-4753-bc9f-0338ab7f7c73%40googlegroups.com
>>> <https://groups.google.com/d/msgid/dspace-tech/feb2a656-28c6-4753-bc9f-0338ab7f7c73%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>>
>>> --
>>> 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 a topic in the
>>> Google Groups "DSpace Technical Support" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/dspace-tech/hiVC3XU09U4/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> dspace-tech+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/dspace-tech/b3ed16dc-4a21-9fe3-d7f6-4ce5a3b51b75%40staff.uni-marburg.de
>>> <https://groups.google.com/d/msgid/dspace-tech/b3ed16dc-4a21-9fe3-d7f6-4ce5a3b51b75%40staff.uni-marburg.de?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
> 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 dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/CACtoqqBrA1fX0AegJzS2%3DoRwRpuJ5_k9EafOLvEEHf75%2BM%2BJhw%40mail.gmail.com
> <https://groups.google.com/d/msgid/dspace-tech/CACtoqqBrA1fX0AegJzS2%3DoRwRpuJ5_k9EafOLvEEHf75%2BM%2BJhw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
>
> --
> 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 a topic in the
> Google Groups "DSpace Technical Support" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/dspace-tech/hiVC3XU09U4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/78412133-a7ea-0ec7-8f6a-46a4efe03952%40staff.uni-marburg.de
> <https://groups.google.com/d/msgid/dspace-tech/78412133-a7ea-0ec7-8f6a-46a4efe03952%40staff.uni-marburg.de?utm_medium=email&utm_source=footer>
> .
>
--
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 dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/dspace-tech/CACtoqqA%3DhCspRDhQE8LX0uig-fzuq1KgPKb%2BHzBQpgMb6a6ncw%40mail.gmail.com.
