[Dspace-tech] Mirage 2 build problem - repost

[Germán Biozzoli]

Sorry, but I've encountered problems again building Mirage2, this time using windows:

------------------------------------------------

[INFO] Found NPM version 1.4.23

[INFO] ------ (Mirage2) com.github.eirslett:frontend-maven-plugin:0.0.16:npm

[INFO] Running 'npm install --color=false' in C:\Devel\DSpace-master\dspace\modules\xmlui-mirage2\target\themes\Mirage2

[INFO] npm WARN package.json Mir...@0.1.1 No description

[INFO] npm WARN package.json Mir...@0.1.1 No repository field.

[INFO] npm WARN package.json Mir...@0.1.1 No README data

[INFO] 

[INFO] > Mir...@0.1.1 postinstall C:\Devel\DSpace-master\dspace\modules\xmlui-mirage2\target\themes\Mirage2

[INFO] > bower install

[INFO] 

[INFO] bower jquery#~1.10.2            ENOGIT git is not installed or not in the PATH

[INFO] 

[INFO] npm ERR! Mir...@0.1.1 postinstall: `bower install`

[INFO] npm ERR! Exit status 1

[INFO] npm ERR! 

[INFO] npm ERR! Failed at the Mir...@0.1.1 postinstall script.

[INFO] npm ERR! This is most likely a problem with the Mirage2 package,

[INFO] npm ERR! not with npm itself.

[INFO] npm ERR! Tell the author that this fails on your system:

[INFO] npm ERR!     bower install

[INFO] npm ERR! You can get their info via:

[INFO] npm ERR!     npm owner ls Mirage2

[INFO] npm ERR! There is likely additional logging output above.

[INFO] npm ERR! System Windows_NT 6.2.9200

[INFO] npm ERR! command "C:\\Devel\\DSpace-master\\dspace\\modules\\xmlui-mirage2\\target\\themes\\Mirage2\\node\\node" "C:\\Devel\\DSpace-master\\dspace\\modules\\xmlui-mirage2\\target\\themes\\Mirage2\\node\\npm\\bin\\npm-cli.js" "install" "--color=false"

[INFO] npm ERR! cwd C:\Devel\DSpace-master\dspace\modules\xmlui-mirage2\target\themes\Mirage2

[INFO] npm ERR! node -v v0.10.31

[INFO] npm ERR! npm -v 1.4.23

[INFO] npm ERR! code ELIFECYCLE

[INFO] npm

[ERROR] MojoFailureException:

org.apache.maven.plugin.MojoFailureException: Failed to run task

at com.github.eirslett.maven.plugins.frontend.mojo.NpmMojo.execute(NpmMojo.java:45)

at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)

at com.soebes.maven.plugins.iterator.ExecutorMojo.executeMojo(ExecutorMojo.java:302)

at com.soebes.maven.plugins.iterator.ExecutorMojo.execute(ExecutorMojo.java:235)

at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)

at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)

at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)

at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)

at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)

at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)

at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)

at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)

at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)

at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Caused by: com.github.eirslett.maven.plugins.frontend.lib.TaskRunnerException: 'npm install --color=false' failed. (error code 1)

at com.github.eirslett.maven.plugins.frontend.lib.NodeTaskExecutor.execute(NodeTaskExecutor.java:38)

at com.github.eirslett.maven.plugins.frontend.mojo.NpmMojo.execute(NpmMojo.java:43)

... 24 more

------------------------------------------------

And some lines after, the reported problem

------------------------------------------------

[INFO] ------ (Mirage2) de.saumya.mojo:gem-maven-plugin:1.0.6:exec

[INFO]     error styles/main.scss (Line 16: File to import not found or unreadable: ../vendor/bootstrap-sass-official/assets/stylesheets/bootstrap.

[INFO] Load paths:

[INFO]   Compass::SpriteImporter

[INFO]   C:/Devel/DSpace-master/dspace/modules/xmlui-mirage2/target/themes/Mirage2/styles

[INFO]   C:/Devel/DSpace-master/dspace/modules/xmlui-mirage2/target/rubygems/gems/compass-core-1.0.1/stylesheets)

[INFO] Compilation failed in 1 files.

[ERROR] PluginManagerException:

org.apache.maven.plugin.PluginExecutionException: Execution null of goal de.saumya.mojo:gem-maven-plugin:1.0.6:exec failed: Java returned: 1

at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:115)

at com.soebes.maven.plugins.iterator.ExecutorMojo.executeMojo(ExecutorMojo.java:302)

at com.soebes.maven.plugins.iterator.ExecutorMojo.execute(ExecutorMojo.java:235)

at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)

Any advice?

Regards & thanks

Germán

PD: It's a fresh install with zip downloaded yesterday from github, maven 3.1.1, Oracle JRE 1.7.0_25

[euler]

Hello Germán,

I have successfully deployed Mirage 2 in my test server using windows 7.
Have you tried running mvn clean -U package -Dmirage2.on=true? Regarding
about your post a few weeks ago about Mirage 2 theme without any styling, I
noticed that this happens when some tasks failed to execute during the
building of DSpace XML-UI Mirage2 Theme :: Local Customisations even though
it will still result in "BUILD SUCCESS". I have installed all the
prerequisite softwares for Mirage 2 but I only use the option
-Dmirage2.deps.included=false after a successful build. That way, I know
that all dependencies for Mirage 2 were downloaded although I'm not sure if
my assumptions were correct. Building and deploying Mirage 2 successfully
for me is just a matter of trial and error but doing mvn clean seemed to do
the trick.

Best regards,
euler



--
View this message in context: http://dspace.2283337.n4.nabble.com/Mirage-2-build-problem-repost-tp4675686p4675687.html
Sent from the DSpace - Tech mailing list archive at Nabble.com.