Maven Build Failure on Reference/Library w/ JRuby < 1.7.23

[Leonardo Canessa]

All,

On the following system:

• Linux Mint x64 17.3, current
• Maven 3.3.9
• Java JDK 1.8.0u66 & u72
• Git 2.7.0 & 1.9.3

with a clean Maven repository and a freshly pulled repository the following error occurred when attempting to build the reference/library sub-project:

[INFO] --- gem-maven-plugin:1.0.10:exec (default) @ library ---

[INFO] SystemCallError on line ["952"] of org/jruby/RubyFile.java: Unknown error - Unknown Error (0) - /home/elearning/opt/sakai/reference/library/src/morpheus-master/../webapp/skin/morpheus-default/access.css

[INFO] Run with --trace to see the full backtrace

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 6.510 s

[INFO] Finished at: 2016-02-03T15:06:39-05:00

[INFO] Final Memory: 28M/347M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal de.saumya.mojo:gem-maven-plugin:1.0.10:exec (default) on project library: Execution default of goal de.saumya.mojo:gem-maven-plugin:1.0.10:exec failed: Java returned: 1 -> [Help 1]

A debug stacktrace of this project is attached.

After much frustration and digging, I was finally able to resolve this issue by upgrading the jruby version used from 1.7.20 to 1.7.24. This issue was also present in jruby 1.7.21 and 1.7.22. At a minimum we should upgrade to 1.7.23, but as 1.7.24 only has bugfixes I see no reason not to upgraded to the latest stable. As such I have created a ticket (JIRA) and a PR for this change.

The oddest part about this is that the error did not occur on my dev environment (with the same java version & maven version), but did occur as Kyle Wedoff was setting up a fresh Sakai 11 dev environment.

Leonardo Canessa

Web Developer - E-Learning

937-229-2085

[Earle Nietzel]

It would be nice if we can get off the ruby SASS compiler all together there are java versions out there that are much better suited.

https://github.com/vaadin/sass-compiler

http://sass-lang.com/libsass

--
You received this message because you are subscribed to the Google Groups "Sakai Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sakai-dev+...@apereo.org.
To post to this group, send email to saka...@apereo.org.
Visit this group at https://groups.google.com/a/apereo.org/group/sakai-dev/.
<2016-02-03_Reference-library-buildfailure.txt>

[Matthew Buckett]

Having merge this pull request some users may be seeing build failures
of the library module. If you do this may well be because at some
point in the past rubygems-proxy.torquebox.org was serving up a bad
gem which you now have cached in your maven repo. The simplest fix is
to remove all the rubygems from your local repository with:

rm -r ~/.m2/repository/rubygems

and it should re-download them and the build complete. There is
currently a discussion about this on:
https://github.com/sakaiproject/sakai/pull/1669 if you are interested.

Nightly failed because if this error, I'm going to clean out it's
rubygems folder and then run the build, this will cause the trunk
nightly servers to get restarted in about 30 minutes.

On 3 February 2016 at 22:49, Earle Nietzel <ea...@longsight.com> wrote:
> It would be nice if we can get off the ruby SASS compiler all together there
> are java versions out there that are much better suited.
>
> https://github.com/vaadin/sass-compiler
> http://sass-lang.com/libsass
>
>
>
> On Feb 3, 2016, at 3:51 PM, Leonardo Canessa <lcan...@udayton.edu> wrote:
>

> --
> You received this message because you are subscribed to the Google Groups
> "Sakai Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sakai-dev+...@apereo.org.
> To post to this group, send email to saka...@apereo.org.
> Visit this group at https://groups.google.com/a/apereo.org/group/sakai-dev/.
> <2016-02-03_Reference-library-buildfailure.txt>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Sakai Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sakai-dev+...@apereo.org.
> To post to this group, send email to saka...@apereo.org.
> Visit this group at https://groups.google.com/a/apereo.org/group/sakai-dev/.

--
Matthew Buckett, VLE Developer, IT Services, University of Oxford

[Earle Nietzel]

I did a POC on switching to libsass http://sass-lang.com/libsass from using the maven plugin https://github.com/warmuuh/libsass-maven-plugin

The compile time was near instant and ruby was not involved at all so no gems to worry about.

Probably the biggest challenge was removing compass as that is a ruby only project.

I am not sure if there is something similar to compass that we could use in its stead…

But clearly a huge improvement.

[Eduardo Rey Jara]

Hi,

We are using Compass in the core just as a library to support most of the css name-dependant properties, I can migrate it and make a standalone library with that (box-shadow, calc, transition and properties like that). I could be a pain if we had been keeping sprite library but we are not so... if the JRuby compiler is messing everything up maybe it should be replaced.

The only problem I see is that bootstrap needs compass to be compiled, and bootstrap is, for now, inside of morpheus to make a few important tools compatible by default.

https://github.com/sakaiproject/sakai/blob/master/reference/library/src/morpheus-master/sass/base/_bootstrap-defaults.scss (two lasts lines)