[Dspace-tech] Mirage 2
591 views
Skip to first unread message
Massimiliano Cilurzo
Aug 26, 2015, 1:57:59 PM8/26/15
to dspace-tech
Dear All,
We have just installed DSPACE 5.0 on our test environment, and we would like to use the Mirage 2 theme.
But after installing it we have this problem:
Syntax error: File to import not found or unreadable: ../vendor/bootstrap-sass-official/assets/stylesheets/bootstrap.
Load paths:
Compass::SpriteImporter
/usr/local/src/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/themes/Mirage2/styles
/usr/local/src/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/rubygems/gems/compass-core-1.0.3/stylesheets
on line 16 of styles/main.scss
Could someone help us?
Thanks
Best regards
Massimiliano Cilurzo
Andrea Schweer
Aug 26, 2015, 1:58:06 PM8/26/15
to Massimiliano Cilurzo, dspace-tech
Hi,
On 30/01/15 01:19, Massimiliano Cilurzo
wrote:
We have just installed DSPACE 5.0 on our test environment, and we would like to use the Mirage 2 theme.But after installing it we have this problem:
Syntax error: File to import not found or unreadable: ../vendor/bootstrap-sass-official/assets/stylesheets/bootstrap.
Load paths:
Compass::SpriteImporter
/usr/local/src/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/themes/Mirage2/styles
/usr/local/src/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/rubygems/gems/compass-core-1.0.3/stylesheets
on line 16 of styles/main.scss
I just had this problem a couple of days ago. For me, maven said
that the build had been successful, but in reality it had failed to
download some files. This is because the server I was running the
build on has restricted access to the outside world. For me,
configuring git to use the https protocol rather than the git
protocol did the trick. You do also need to have git installed on
the machine where you're running maven. Have a look here for common
Mirage 2 build issues:
https://wiki.duraspace.org/display/DSDOC5x/Mirage+2+Configuration+and+Customization#Mirage2ConfigurationandCustomization-CommonBuildIssues
cheers,
Andrea
cheers,
Andrea
-- Dr Andrea Schweer IRR Technical Specialist, ITS Information Systems The University of Waikato, Hamilton, New Zealand
Massimiliano Cilurzo
Aug 26, 2015, 1:58:10 PM8/26/15
to Andrea Schweer, dspace-tech
Hi Andrea,
We have installed git on our machine and we have configured git to use https (git config --global url."https://github.com/".insteadOf git://github.com/).
Then we have used the mvn command: mvn clean package -P \!dspace-jspui,\!dspace-lni,\!dspace-rest,\!dspace-swordv2,\!dspace-sword,\!dspace-oai,\!dspace-rdf -Dmirage2.on=true
And at the end the ant update command.
But the problem wasn’t solved. Have you some tips?
Thanks
Best regards
Massimiliano
Da: Andrea Schweer [mailto:schweer@waikato.ac.nz]
Inviato: giovedì 29 gennaio 2015 20:38
A: Massimiliano Cilurzo; 'dspace-tech'
Oggetto: Re: [Dspace-tech] Mirage 2
sn...@buntblock.de
Aug 26, 2015, 1:58:12 PM8/26/15
to dspac...@lists.sourceforge.net
Hi there,
are you running as root user ?
Try running the 'mvn' command as non root user. The bower component is
not working with root permissions, resulting in webcomponents beeing
installed by bower are missing.
Zitat von Massimiliano Cilurzo <mcil...@unisa.it>:
> Hi Andrea,
>
> We have installed git on our machine and we have configured git to use
> https (git config --global url." <https://github.com/>
> https://github.com/".insteadOf git://github.com/).
>
> Then we have used the mvn command: mvn clean package -P
> \!dspace-jspui,\!dspace-lni,\!dspace-rest,\!dspace-swordv2,\!dspace-sword,\!
> dspace-oai,\!dspace-rdf -Dmirage2.on=true
>
> And at the end the ant update command.
>
> But the problem wasn’t solved. Have you some tips?
>
> Thanks
>
> Best regards
>
> Massimiliano
>
>
>
>
>
> Da: Andrea Schweer [mailto:sch...@waikato.ac.nz]
are you running as root user ?
Try running the 'mvn' command as non root user. The bower component is
not working with root permissions, resulting in webcomponents beeing
installed by bower are missing.
Zitat von Massimiliano Cilurzo <mcil...@unisa.it>:
> Hi Andrea,
>
> We have installed git on our machine and we have configured git to use
> https (git config --global url." <https://github.com/>
> https://github.com/".insteadOf git://github.com/).
>
> Then we have used the mvn command: mvn clean package -P
> \!dspace-jspui,\!dspace-lni,\!dspace-rest,\!dspace-swordv2,\!dspace-sword,\!
> dspace-oai,\!dspace-rdf -Dmirage2.on=true
>
> And at the end the ant update command.
>
> But the problem wasn’t solved. Have you some tips?
>
> Thanks
>
> Best regards
>
> Massimiliano
>
>
>
>
>
Massimiliano Cilurzo
Aug 26, 2015, 1:58:14 PM8/26/15
to sn...@buntblock.de, dspac...@lists.sourceforge.net
Hi,
Yes we are running as root user.
We tried to run as dspace but we had some errors.
So we choosed to use root user.
I will try with another user.
Thanks
Best regards
Massimiliano
-----Messaggio originale-----
>Da: sn...@buntblock.de [mailto:sn...@buntblock.de]
>Inviato: venerdì 30 gennaio 2015 11:08
>A: dspac...@lists.sourceforge.net
>Oggetto: Re: [Dspace-tech] R: Mirage 2
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
DSpace-tech mailing list
DSpac...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Yes we are running as root user.
We tried to run as dspace but we had some errors.
So we choosed to use root user.
I will try with another user.
Thanks
Best regards
Massimiliano
-----Messaggio originale-----
>Da: sn...@buntblock.de [mailto:sn...@buntblock.de]
>Inviato: venerdì 30 gennaio 2015 11:08
>A: dspac...@lists.sourceforge.net
>Oggetto: Re: [Dspace-tech] R: Mirage 2
Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
DSpace-tech mailing list
DSpac...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Sean Carte
Aug 26, 2015, 1:58:15 PM8/26/15
to Massimiliano Cilurzo, dspace-tech
For what it's worth, I've got the same error and I'm running mvn as the dspace user.
I suspect the problem is due to the firewall here. Following Andrea's suggestion of changing git to use https did allow maven to download more things, but still not enough.
Sean
I suspect the problem is due to the firewall here. Following Andrea's suggestion of changing git to use https did allow maven to download more things, but still not enough.
Sean
--
Hilton Gibson
Aug 26, 2015, 1:58:17 PM8/26/15
to Sean Carte, dspace-tech
Same problem with me.
Hilton Gibson
Ubuntu Linux Systems Administrator
JS Gericke Library
Room 1025C
Stellenbosch University
Private Bag X5036
Stellenbosch
7599
South Africa
Tel: +27 21 808 4100 | Cell: +27 84 646 4758
Andrea Schweer
Aug 26, 2015, 1:58:39 PM8/26/15
to Sean Carte, Massimiliano Cilurzo, dspace-tech
Hi,
On 31/01/15 00:19, Sean Carte wrote:
> For what it's worth, I've got the same error and I'm running mvn as
> the dspace user.
>
> I suspect the problem is due to the firewall here. Following Andrea's
> suggestion of changing git to use https did allow maven to download
> more things, but still not enough.
Are you getting any error messages during the maven build step? If not,
is there a way you might be able to get a list of denied outgoing access
attempts from your firewall? I'm assuming you're allowing outgoing https
access to github and maven central / wherever else you're getting your
maven artifacts from.
On 31/01/15 00:19, Sean Carte wrote:
> For what it's worth, I've got the same error and I'm running mvn as
> the dspace user.
>
> I suspect the problem is due to the firewall here. Following Andrea's
> suggestion of changing git to use https did allow maven to download
> more things, but still not enough.
is there a way you might be able to get a list of denied outgoing access
attempts from your firewall? I'm assuming you're allowing outgoing https
access to github and maven central / wherever else you're getting your
maven artifacts from.
Sean Carte
Aug 26, 2015, 1:58:39 PM8/26/15
to Andrea Schweer, dspace-tech
On 2 February 2015 at 06:31, Andrea Schweer <sch...@waikato.ac.nz> wrote:
On 31/01/15 00:19, Sean Carte wrote:
For what it's worth, I've got the same error and I'm running mvn as the dspace user.
I suspect the problem is due to the firewall here. Following Andrea's suggestion of changing git to use https did allow maven to download more things, but still not enough.
Are you getting any error messages during the maven build step? If not, is there a way you might be able to get a list of denied outgoing access attempts from your firewall? I'm assuming you're allowing outgoing https access to github and maven central / wherever else you're getting your maven artifacts from.
Unfortunately it's the institutional firewall and I don't have access to those logs. The other themes work, just not Mirage 2.
Rerunning mvn with a close eye on the output, this doesn't look too healthy:
[INFO] bower datatables#1.10.3 ECMDERR Failed to execute "git ls-remote --tags --heads git://github.com/DataTables/DataTables.git", exit code of #128
[INFO]
[INFO] Additional error details:
[INFO] fatal: unable to connect to github.com:
[INFO] github.com[0: 192.30.252.130]: errno=Connection timed out
[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 Linux 3.13.0-44-generic
[INFO] npm ERR! command "/home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node/node" "/home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node/npm/bin/npm-cli.js" "install" "--color=false"
[INFO] npm ERR! cwd /home/dspace/dspace-5.0-src-release/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 ERR!
[INFO] npm ERR! Additional logging details can be found in:
[INFO] npm ERR! /home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/themes/Mirage2/npm-debug.log
[INFO] npm ERR! not ok code 0
[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:101)
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:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
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:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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
...
[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] /home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/themes/Mirage2/styles
[INFO] /home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/rubygems/gems/compass-core-1.0.3/stylesheets)
[INFO] Compilation failed in 1 files.
[WARNING]
[INFO]
[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:110)
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:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
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:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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: Java returned: 1
at org.apache.tools.ant.taskdefs.Java.execute(Java.java:87)
at de.saumya.mojo.ruby.script.AntLauncher.doExecute(AntLauncher.java:107)
at de.saumya.mojo.ruby.script.AntLauncher.executeIn(AntLauncher.java:141)
at de.saumya.mojo.ruby.script.Script.executeIn(Script.java:108)
at de.saumya.mojo.gem.ExecMojo.executeWithGems(ExecMojo.java:106)
at de.saumya.mojo.gem.AbstractGemMojo.executeJRuby(AbstractGemMojo.java:469)
at de.saumya.mojo.jruby.AbstractJRubyMojo.execute(AbstractJRubyMojo.java:298)
at de.saumya.mojo.gem.AbstractGemMojo.execute(AbstractGemMojo.java:222)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 23 more
[INFO]
[INFO] --- maven-war-plugin:2.4:war (default-war) @ xmlui-mirage2 ---
[INFO] Packaging webapp
[INFO] Assembling webapp [xmlui-mirage2] in [/home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/xmlui-mirage2-5.0]
[INFO] Processing war project
[INFO] Copying webapp webResources [/home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/src/main/webapp] to [/home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/xmlui-mirage2-5.0]
[INFO] Copying webapp webResources [/home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/themes] to [/home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/xmlui-mirage2-5.0]
[INFO] Copying webapp resources [/home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/src/main/webapp]
[INFO] Processing overlay [ id org.dspace:dspace-xmlui-mirage2]
[INFO] Webapp assembled in [3220 msecs]
[INFO] Building war: /home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/xmlui-mirage2-5.0.war
[INFO]
[INFO] Additional error details:
[INFO] fatal: unable to connect to github.com:
[INFO] github.com[0: 192.30.252.130]: errno=Connection timed out
[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 Linux 3.13.0-44-generic
[INFO] npm ERR! command "/home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node/node" "/home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node/npm/bin/npm-cli.js" "install" "--color=false"
[INFO] npm ERR! cwd /home/dspace/dspace-5.0-src-release/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 ERR!
[INFO] npm ERR! Additional logging details can be found in:
[INFO] npm ERR! /home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/themes/Mirage2/npm-debug.log
[INFO] npm ERR! not ok code 0
[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:101)
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:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
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:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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
...
[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] /home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/themes/Mirage2/styles
[INFO] /home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/rubygems/gems/compass-core-1.0.3/stylesheets)
[INFO] Compilation failed in 1 files.
[WARNING]
[INFO]
[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:110)
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:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
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:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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: Java returned: 1
at org.apache.tools.ant.taskdefs.Java.execute(Java.java:87)
at de.saumya.mojo.ruby.script.AntLauncher.doExecute(AntLauncher.java:107)
at de.saumya.mojo.ruby.script.AntLauncher.executeIn(AntLauncher.java:141)
at de.saumya.mojo.ruby.script.Script.executeIn(Script.java:108)
at de.saumya.mojo.gem.ExecMojo.executeWithGems(ExecMojo.java:106)
at de.saumya.mojo.gem.AbstractGemMojo.executeJRuby(AbstractGemMojo.java:469)
at de.saumya.mojo.jruby.AbstractJRubyMojo.execute(AbstractJRubyMojo.java:298)
at de.saumya.mojo.gem.AbstractGemMojo.execute(AbstractGemMojo.java:222)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 23 more
[INFO]
[INFO] --- maven-war-plugin:2.4:war (default-war) @ xmlui-mirage2 ---
[INFO] Packaging webapp
[INFO] Assembling webapp [xmlui-mirage2] in [/home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/xmlui-mirage2-5.0]
[INFO] Processing war project
[INFO] Copying webapp webResources [/home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/src/main/webapp] to [/home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/xmlui-mirage2-5.0]
[INFO] Copying webapp webResources [/home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/themes] to [/home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/xmlui-mirage2-5.0]
[INFO] Copying webapp resources [/home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/src/main/webapp]
[INFO] Processing overlay [ id org.dspace:dspace-xmlui-mirage2]
[INFO] Webapp assembled in [3220 msecs]
[INFO] Building war: /home/dspace/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/xmlui-mirage2-5.0.war
Nothing else is jumping out at me and the build concludes with:
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 16:35.193s
[INFO] Finished at: Mon Feb 02 08:07:44 SAST 2015
[INFO] Final Memory: 81M/240M
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 16:35.193s
[INFO] Finished at: Mon Feb 02 08:07:44 SAST 2015
[INFO] Final Memory: 81M/240M
[INFO] ------------------------------------------------------------------------
(This is on Ubuntu 14.04, with OpenJDK 7, PostgreSQL 9 and Tomcat 7.)
Sean
--
--
Hilton Gibson
Aug 26, 2015, 1:58:40 PM8/26/15
to Sean Carte, dspace-tech
Hi All
I have tested again and it seems DSpace 5.X with Mirage 2 only works on Ubuntu 14.04 LTS.
Cheers
hg
Hilton Gibson
Ubuntu Linux Systems Administrator
JS Gericke Library
Room 1025C
Stellenbosch University
Private Bag X5036
Stellenbosch
7599
South Africa
Tel: +27 21 808 4100 | Cell: +27 84 646 4758
Andrea Schweer
Aug 26, 2015, 1:58:44 PM8/26/15
to Hilton Gibson, dspace-tech
Hi Hilton,
On 02/02/15 20:47, Hilton Gibson wrote:
> I have tested again and it seems DSpace 5.X with Mirage 2 only works
> on Ubuntu 14.04 LTS.
I've compiled it successfully on RHEL6.6, so this is very definitely not
true.
cheers,
Andrea
--
Dr Andrea Schweer
IRR Technical Specialist, ITS Information Systems
The University of Waikato, Hamilton, New Zealand
+64-7-838 4466 ext. 6972
On 02/02/15 20:47, Hilton Gibson wrote:
> I have tested again and it seems DSpace 5.X with Mirage 2 only works
> on Ubuntu 14.04 LTS.
true.
cheers,
Andrea
--
Dr Andrea Schweer
IRR Technical Specialist, ITS Information Systems
The University of Waikato, Hamilton, New Zealand
Andrea Schweer
Aug 26, 2015, 1:58:45 PM8/26/15
to Sean Carte, dspace-tech
Hi Sean,
On 02/02/15 19:19, Sean Carte wrote:
On 2 February 2015 at 06:31, Andrea Schweer <sch...@waikato.ac.nz> wrote:
On 31/01/15 00:19, Sean Carte wrote:
For what it's worth, I've got the same error and I'm running mvn as the dspace user.
I suspect the problem is due to the firewall here. Following Andrea's suggestion of changing git to use https did allow maven to download more things, but still not enough.
Are you getting any error messages during the maven build step? If not, is there a way you might be able to get a list of denied outgoing access attempts from your firewall? I'm assuming you're allowing outgoing https access to github and maven central / wherever else you're getting your maven artifacts from.
Unfortunately it's the institutional firewall and I don't have access to those logs. The other themes work, just not Mirage 2.
Rerunning mvn with a close eye on the output, this doesn't look too healthy:
[INFO] bower datatables#1.10.3 ECMDERR Failed to execute "git ls-remote --tags --heads git://github.com/DataTables/DataTables.git", exit code of #128
Did you run the git config change that I put on the wiki? This is
the exact error message I got, and forcing git to use https rather
than the git protocol fixed the problem for me (also a firewall
issue).
git config --global url."https://github.com/".insteadOf git://github.com/
see https://wiki.duraspace.org/display/DSDOC5x/Mirage+2+Configuration+and+Customization#Mirage2ConfigurationandCustomization-CommonBuildIssues
git config --global url."https://github.com/".insteadOf git://github.com/
see https://wiki.duraspace.org/display/DSDOC5x/Mirage+2+Configuration+and+Customization#Mirage2ConfigurationandCustomization-CommonBuildIssues
Hilton Gibson
Aug 26, 2015, 1:58:46 PM8/26/15
to Andrea Schweer, dspace-tech
Hi Andrea
Thats great to hear.
I am strictly an Ubuntu/Debian person.
I hope you do, as I do, believe in freedom of choice in the very important matter of preserving the digital scholarly record.
The more open the system used, the better I feel.
Therefore my reply was in the context of using Ubuntu, for which I feel qualified.
If I had also tested on Redhat, I would have said the same, if the results demanded it.
Hopefully in the future, the community will endorse a reference architecture for each release of DSpace.
Cheers
hg
Hilton Gibson
Ubuntu Linux Systems Administrator
JS Gericke Library
Room 1025C
Stellenbosch University
Private Bag X5036
Stellenbosch
7599
South Africa
Tel: +27 21 808 4100 | Cell: +27 84 646 4758
Sean Carte
Aug 26, 2015, 1:58:48 PM8/26/15
to Andrea Schweer, dspace-tech
On 2 February 2015 at 22:40, Andrea Schweer <sch...@waikato.ac.nz> wrote:
On 2 February 2015 at 06:31, Andrea Schweer <sch...@waikato.ac.nz> wrote:
On 31/01/15 00:19, Sean Carte wrote:
For what it's worth, I've got the same error and I'm running mvn as the dspace user.
I suspect the problem is due to the firewall here. Following Andrea's suggestion of changing git to use https did allow maven to download more things, but still not enough.
Are you getting any error messages during the maven build step? If not, is there a way you might be able to get a list of denied outgoing access attempts from your firewall? I'm assuming you're allowing outgoing https access to github and maven central / wherever else you're getting your maven artifacts from.
Unfortunately it's the institutional firewall and I don't have access to those logs. The other themes work, just not Mirage 2.
Rerunning mvn with a close eye on the output, this doesn't look too healthy:
[INFO] bower datatables#1.10.3 ECMDERR Failed to execute "git ls-remote --tags --heads git://github.com/DataTables/DataTables.git", exit code of #128
Did you run the git config change that I put on the wiki? This is the exact error message I got, and forcing git to use https rather than the git protocol fixed the problem for me (also a firewall issue).
git config --global url."https://github.com/".insteadOf git://github.com/
see https://wiki.duraspace.org/display/DSDOC5x/Mirage+2+Configuration+and+Customization#Mirage2ConfigurationandCustomization-CommonBuildIssues
Hi Andrea
Yes, I did (see above). I'll try again with a fresh download and see if that makes any difference.
Meanwhile, someone replied to me off-list and sent me the missing files: the
/dspace-xmlui-mirage2/src/main/webapp/vendor directory. Dropping that into dspace-src did resolve the issue.
/dspace-xmlui-mirage2/src/main/webapp/vendor directory. Dropping that into dspace-src did resolve the issue.
Sean
--
--
Sean Carte
Aug 26, 2015, 1:58:48 PM8/26/15
to Andrea Schweer, dspace-tech
On 3 February 2015 at 07:23, Sean Carte <sean....@gmail.com> wrote:
Yes, I did (see above). I'll try again with a fresh download and see if that makes any difference.
Well, it seems the problem is me. (Was there ever any doubt?) I had changed the git config, but I did it as root instead of dspace, so that had no effect on the mvn build process. I ran the git config command as the dspace user and was able to build Mirage 2 without errors.
Thank you, Andrea and all who tried to help me. And sorry to Massimiliano for hijacking your thread. I hope you were able to resolve your problem!
Sean
--
--
Andrea Schweer
Aug 26, 2015, 1:58:55 PM8/26/15
to Sean Carte, dspace-tech
Hi Sean,
On 03/02/15 20:38, Sean Carte wrote:
On 3 February 2015 at 07:23, Sean Carte <sean....@gmail.com> wrote:
Yes, I did (see above). I'll try again with a fresh download and see if that makes any difference.
Well, it seems the problem is me. (Was there ever any doubt?) I had changed the git config, but I did it as root instead of dspace, so that had no effect on the mvn build process. I ran the git config command as the dspace user and was able to build Mirage 2 without errors.
Perfect, glad to hear you got it working and thanks for letting us
know what the problem was. I've updated the official DSpace
documentation to clarify that it needs to be the same user account
as used for the maven step.
Massimiliano Cilurzo
Aug 26, 2015, 1:59:19 PM8/26/15
to Sean Carte, Andrea Schweer, dspace-tech
Dear Sean,
There is no problem for the “ hijacking”.
We tried to do mvn with not root user as DSPACE but we have the same problem.
We have changed the git too but for now we haven’t solved the problem.
Thanks
Best regards
Massimiliano
Da: Sean Carte [mailto:sean....@gmail.com]
Inviato: martedì 3 febbraio 2015 08:39
A: Andrea Schweer
Cc: Massimiliano Cilurzo; dspace-tech
Oggetto: Re: [Dspace-tech] R: R: Mirage 2
Andrea Schweer
Aug 26, 2015, 1:59:23 PM8/26/15
to Massimiliano Cilurzo, dspace-tech
Hi Massimiliano,
We tried to do mvn with not root user as DSPACE but we have the same problem.We have changed the git too but for now we haven’t solved the problem.
What error messages are you getting -- anything useful from the maven step?
cheers,
Andrea
Massimiliano Cilurzo
Aug 26, 2015, 1:59:32 PM8/26/15
to Andrea Schweer, dspace-tech
Dear Andrea,
We have used this command mvn clean package -P \!dspace-jspui,\!dspace-lni,\!dspace-rest,\!dspace-swordv2,\!dspace-sword,\!dspace-oai,\!dspace-rdf -Dmirage2.on=true
as dspace user and before this we have changed always as dspace user the git config : git config --global url."https://github.com/".insteadOf git://github.com/.
We have an error:
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 Linux 2.6.32-279.19.1.el6.x86_64
[INFO] npm ERR! command "/usr/local/src/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node/node" "/usr/local/src/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/themes/Mirage2/node/npm/bin/npm-cli.js" "install" "--color=false"
[INFO] npm ERR! cwd /usr/local/src/dspace-5.0-src-release/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 ERR!
[INFO] npm ERR! Additional logging details can be found in:
[INFO] npm ERR! /usr/local/src/dspace-5.0-src-release/dspace/modules/xmlui-mirage2/target/themes/Mirage2/npm-debug.log
[INFO] npm ERR! not ok code 0
[ERROR] MojoFailureException:
In the attachment you will find the errors in detail.
Thanks
Best regards
Massimiliano
Da: Andrea Schweer [mailto:sch...@waikato.ac.nz]
Inviato: giovedì 5 febbraio 2015 10:18
A: Massimiliano Cilurzo
Cc: dspace-tech
Oggetto: Re: [Dspace-tech] R: R: Mirage 2
>Hi Massimiliano,
>cheers,
>Andrea
Andrea Schweer
Aug 26, 2015, 1:59:54 PM8/26/15
to Massimiliano Cilurzo, dspace-tech
Hi,
in your attachment, I see this just before it starts to complain:
That looks like a permissions problem to me. Ensure that the dspace user has permission to write to /tmp/dspace and try again, does it work then?
in your attachment, I see this just before it starts to complain:
EACCES EACCES, mkdir '/tmp/dspace/bower'
[INFO]
[INFO] Stack trace:
[INFO] Error: EACCES, mkdir '/tmp/dspace/bower'
[INFO]
That looks like a permissions problem to me. Ensure that the dspace user has permission to write to /tmp/dspace and try again, does it work then?
Massimiliano Cilurzo
Aug 26, 2015, 2:00:30 PM8/26/15
to Andrea Schweer, dspace-tech
Hi Andrea,
We have seen that there wasn’t the directory /tmp/dspace/bower.
So we have done it and then launched the mvn and now it works
Thanks
Best regards
Massimiliano
Da: Andrea Schweer [mailto:sch...@waikato.ac.nz]
Inviato: martedì 10 febbraio 2015 01:17
A: Massimiliano Cilurzo
Cc: 'dspace-tech'
Oggetto: Re: R: [Dspace-tech] R: R: Mirage 2
Keith Jones
Aug 26, 2015, 2:22:07 PM8/26/15
to dspac...@lists.sourceforge.net
Hi All,
I'm in the process of upgrading a test instance of DSPACE from 3.2 to 5.1. I have it up and running with Mirage but when I re-compiled to use the Mirage 2 theme the system is up but does not display properly.
Here is the error I'm seeing in the tomcat logs:
Mar 26, 2015 11:39:27 AM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring root WebApplicationContext
Mar 26, 2015 11:39:28 AM org.apache.catalina.core.ApplicationContext log
INFO: Apache Cocoon Spring Configurator v1.0.2 is running in mode 'prod'.
Mar 26, 2015 11:39:28 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class org.springframework.web.context.Conte
xtLoaderListener
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dspace.eventService' defined in
ServletContext resource [/WEB-INF/spring/applicationContext.xml]: Instantiation of bean failed; nested exception is or
g.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public org.dspace.services.EventService o
rg.dspace.utils.DSpace.getEventService()] threw exception; nested exception is java.lang.IllegalStateException: DSpace
kernel cannot be null
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResol
ver.java:581)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(A
bstractAutowireCapableBeanFactory.java:1015)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAuto
wireCapableBeanFactory.java:911)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCa
pableBeanFactory.java:485)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapa
bleBeanFactory.java:456)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegi
stry.java:225)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListabl
eBeanFactory.java:585)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractAppli
cationContext.java:913)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:464)
at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:38
5)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:284)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4791)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1114)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1673)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public org.dspace.services.E
ventService org.dspace.utils.DSpace.getEventService()] threw exception; nested exception is java.lang.IllegalStateExcep
tion: DSpace kernel cannot be null
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrateg
y.java:169)
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResol
ver.java:570)
... 28 more
Caused by: java.lang.IllegalStateException: DSpace kernel cannot be null
at org.dspace.utils.DSpace.getServiceManager(DSpace.java:63)
at org.dspace.utils.DSpace.getEventService(DSpace.java:75)
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:601)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrateg
y.java:149)
... 29 more
Mar 26, 2015 11:39:28 AM org.apache.catalina.core.ApplicationContext log
INFO: Closing Spring root WebApplicationContext
I'm able to get data pulls and click on links, but the interface is incomplete, like a CSS style sheet is missing. Any help would be appreciated.
Thanks
Keith
Bram Luyten
Aug 26, 2015, 2:22:08 PM8/26/15
to Keith Jones, dspac...@lists.sourceforge.net
Hi Keith,
could you post the entire output of your maven build (preferably as a pastebin.com link)?
The snippet "DSpace kernel cannot be null" shows some google results with upgrade related issues from the past, including the discussion at
So at the moment I'm not 100% convinced that the problem is Mirage 2 related and not upgrade related (more broadly).
cheers,
Bram
--
 | Bram Luyten 2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010 Esperantolaan 4, Heverlee 3001, Belgium www.atmire.com |
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
Reply all
Reply to author
Forward
0 new messages