Re: [dspace-tech] Workflow email notices rejected

[Mark H. Wood]

On Monday, February 3, 2020 at 3:54:22 PM UTC-5, Mark H. Wood wrote:
>
> The admin. email address and the workflow address are different.  My 
> only guess is that the authentication rules for ksu.edu are different 
> from those for k-state.edu even though they are MXed to the same place. 
>
>
No, that's not right -- DSpace should be using the same mail.host for all 
mail.  Sorry for the noise.

-- 
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/2f5f1e8d-db21-447c-be1e-d725797f4735%40googlegroups.com.

Re: [dspace-tech] Workflow email notices rejected

[Mark H. Wood]

On Mon, Feb 03, 2020 at 05:23:31PM +, Jeffrey Sheldon wrote:
> I recently upgraded to DSpace 6 and have noticed different behavior with 
> respect to email configuration as seen in DSpace 5.
> 
> I'm using a trusted and open SMTP relay which doesn't require authentication. 
>  Therefore, I have mail.server populated and mail.server.username and 
> mail.server.password commented out (in DSpace 5, these could simply be left 
> blank).
> 
> When I test the email configuration, the response is positive and the email 
> appears in my inbox: 
> 
> ./dspace test-email
> 
> About to send test email:
>  - To: jshel...@ksu.edu
>  - Subject: DSpace test email
>  - Server: (my SMTP server address)
> 
> Email sent successfully!
> 
> However, workflow tasks will not deliver email, but log errors akin to the 
> following:
> 
> 2020-02-03 09:11:49,354 WARN  
> org.dspace.workflowbasic.BasicWorkflowServiceImpl @ 
> jshel...@k-state.edu:session_id=AF8FE128AE418F4C52CA462EF2BCE798:ip_addr=(address
>  removed):notify_of_reject:cannot email user eperson_id=(eperson UUID 
> removed) eperson_email=jshel...@k-state.edu workflow_item_id=20928\colon;  
> Send failure (javax.mail.AuthenticationFailedException\colon; null)
> 
> Any suggestions?  I have tried a number of combinations (including 
> mail.server = localhost for Postfix to handle) and would expect this to work 
> without issue as it did in the past.  Always the same error.

The admin. email address and the workflow address are different.  My
only guess is that the authentication rules for ksu.edu are different
from those for k-state.edu even though they are MXed to the same place.

-- 
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu

-- 
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/20200203205417.GA14627%40IUPUI.Edu.


signature.asc
Description: PGP signature

Re: [dspace-tech] Show statistics button

[Lucas Silveira]

Colleagues, I found the solution.

community-home.jsp and collection-home.jsp files it is necessary to insert
the following line in the header:

<% @ page import = "org.dspace.eperson.EPerson"%>

then you can use the function that validates the logged in user:

  // Is anyone logged in?
 EPerson user = (EPerson) request.getAttribute ("dspace.current.user");



That way, you can manipulate any html attribute to be shown to the user.

So, I do to manipulates statistics. In community-home.jps,  I added the
following rule:
  <%
if(user!=null)
{
  %>
   
  <%
}
  %>

and collection-home.jsp, I added the following rule:
<%
if(user!=null)
{
  %>
 
  <%
}
  %>


Em seg., 3 de fev. de 2020 às 15:44, Lucas Silveira <
lucasangelosilveira2...@gmail.com> escreveu:

> Dear colleagues, I need to remove the statistics button from pages where
> the user is not logged in.
> However, dspace only allows you to enable and disable access, but the
> button is visible to everyone.
> Does anyone know how to do?
>
> Thanks in advance
>
> --
> 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/1fef345c-ca08-4e85-8993-05287fc64a0f%40googlegroups.com
> 
> .
>

-- 
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/CAHHcpFziESaa3C5BYC0FkzLLPZfKKN%2Bb%3DmxdJbSOZfDmMu9L6A%40mail.gmail.com.

[dspace-tech] Re: Workflow email notices rejected

[Jeffrey Sheldon]

Thanks, Tim.

That's what make this so curious: That the test-email command will result in a 
successfully delivered email and the lack of any discernible notifications in 
any logs which reveal problems or association with this issue (including no 
other WARN or ERROR entries).

I haven't head any issues with email between DSpace 1.x - 5.x.  Only 6.

-Jeff



From: Tim Donohue 
Sent: Monday, February 3, 2020 1:38 PM
To: Jeffrey Sheldon; dspace-tech@googlegroups.com
Subject: Re: Workflow email notices rejected

Hi Jeffrey,

You might want to look more closely at the log lines *around* that WARN message 
you noted below. They may provide more information about what the problem is 
with regards to sending the emails -- especially if you see an ERROR just 
before or after the WARN.

The error "AuthenticationFailedException" implies that either the configuration 
is incorrect (in some way) *or* maybe there's an SSL Handshake failure (if your 
mail server requires SSL and the cert cannot be verified by Java on the server 
running DSpace).  But, it's hard to say for certain.  Since the `test-email` 
works though, that would imply the configuration should hopefully be correct.

Not sure if that helps any, but maybe you'll find something else in the logs 
(either DSpace logs or maybe even Tomcat logs) that provides more info.

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Jeffrey Sheldon 
Sent: Monday, February 3, 2020 11:23 AM
To: dspace-tech@googlegroups.com 
Subject: [dspace-tech] Workflow email notices rejected

All,

I recently upgraded to DSpace 6 and have noticed different behavior with 
respect to email configuration as seen in DSpace 5.

I'm using a trusted and open SMTP relay which doesn't require authentication.  
Therefore, I have mail.server populated and mail.server.username and 
mail.server.password commented out (in DSpace 5, these could simply be left 
blank).

When I test the email configuration, the response is positive and the email 
appears in my inbox:

./dspace test-email

About to send test email:
 - To: jshel...@ksu.edu
 - Subject: DSpace test email
 - Server: (my SMTP server address)

Email sent successfully!

However, workflow tasks will not deliver email, but log errors akin to the 
following:

2020-02-03 09:11:49,354 WARN  org.dspace.workflowbasic.BasicWorkflowServiceImpl 
@ 
jshel...@k-state.edu:session_id=AF8FE128AE418F4C52CA462EF2BCE798:ip_addr=(address
 removed):notify_of_reject:cannot email user eperson_id=(eperson UUID removed) 
eperson_email=jshel...@k-state.edu workflow_item_id=20928\colon;  Send failure 
(javax.mail.AuthenticationFailedException\colon; null)

Any suggestions?  I have tried a number of combinations (including mail.server 
= localhost for Postfix to handle) and would expect this to work without issue 
as it did in the past.  Always the same error.


-Jeff

--
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/BN8PR05MB662FC0843498B5D2F25DD%40BN8PR05MB6644.namprd05.prod.outlook.com.

-- 
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/BN8PR05MB664425D0A27381F706D624E0D%40BN8PR05MB6644.namprd05.prod.outlook.com.

[dspace-tech] Re: Workflow email notices rejected

[Tim Donohue]

Hi Jeffrey,

You might want to look more closely at the log lines *around* that WARN message 
you noted below. They may provide more information about what the problem is 
with regards to sending the emails -- especially if you see an ERROR just 
before or after the WARN.

The error "AuthenticationFailedException" implies that either the configuration 
is incorrect (in some way) *or* maybe there's an SSL Handshake failure (if your 
mail server requires SSL and the cert cannot be verified by Java on the server 
running DSpace).  But, it's hard to say for certain.  Since the `test-email` 
works though, that would imply the configuration should hopefully be correct.

Not sure if that helps any, but maybe you'll find something else in the logs 
(either DSpace logs or maybe even Tomcat logs) that provides more info.

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Jeffrey Sheldon 
Sent: Monday, February 3, 2020 11:23 AM
To: dspace-tech@googlegroups.com 
Subject: [dspace-tech] Workflow email notices rejected

All,

I recently upgraded to DSpace 6 and have noticed different behavior with 
respect to email configuration as seen in DSpace 5.

I'm using a trusted and open SMTP relay which doesn't require authentication.  
Therefore, I have mail.server populated and mail.server.username and 
mail.server.password commented out (in DSpace 5, these could simply be left 
blank).

When I test the email configuration, the response is positive and the email 
appears in my inbox:

./dspace test-email

About to send test email:
 - To: jshel...@ksu.edu
 - Subject: DSpace test email
 - Server: (my SMTP server address)

Email sent successfully!

However, workflow tasks will not deliver email, but log errors akin to the 
following:

2020-02-03 09:11:49,354 WARN  org.dspace.workflowbasic.BasicWorkflowServiceImpl 
@ 
jshel...@k-state.edu:session_id=AF8FE128AE418F4C52CA462EF2BCE798:ip_addr=(address
 removed):notify_of_reject:cannot email user eperson_id=(eperson UUID removed) 
eperson_email=jshel...@k-state.edu workflow_item_id=20928\colon;  Send failure 
(javax.mail.AuthenticationFailedException\colon; null)

Any suggestions?  I have tried a number of combinations (including mail.server 
= localhost for Postfix to handle) and would expect this to work without issue 
as it did in the past.  Always the same error.


-Jeff

--
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/BN8PR05MB662FC0843498B5D2F25DD%40BN8PR05MB6644.namprd05.prod.outlook.com.

-- 
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/DM5PR2201MB114852187BC63D08BF7E8116ED000%40DM5PR2201MB1148.namprd22.prod.outlook.com.

[dspace-tech] Show statistics button

[Lucas Silveira]

Dear colleagues, I need to remove the statistics button from pages where 
the user is not logged in. 
However, dspace only allows you to enable and disable access, but the 
button is visible to everyone. 
Does anyone know how to do?

Thanks in advance

-- 
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/1fef345c-ca08-4e85-8993-05287fc64a0f%40googlegroups.com.

[dspace-tech] Workflow email notices rejected

[Jeffrey Sheldon]

All,

I recently upgraded to DSpace 6 and have noticed different behavior with 
respect to email configuration as seen in DSpace 5.

I'm using a trusted and open SMTP relay which doesn't require authentication.  
Therefore, I have mail.server populated and mail.server.username and 
mail.server.password commented out (in DSpace 5, these could simply be left 
blank).

When I test the email configuration, the response is positive and the email 
appears in my inbox: 

./dspace test-email

About to send test email:
 - To: jshel...@ksu.edu
 - Subject: DSpace test email
 - Server: (my SMTP server address)

Email sent successfully!

However, workflow tasks will not deliver email, but log errors akin to the 
following:

2020-02-03 09:11:49,354 WARN  org.dspace.workflowbasic.BasicWorkflowServiceImpl 
@ 
jshel...@k-state.edu:session_id=AF8FE128AE418F4C52CA462EF2BCE798:ip_addr=(address
 removed):notify_of_reject:cannot email user eperson_id=(eperson UUID removed) 
eperson_email=jshel...@k-state.edu workflow_item_id=20928\colon;  Send failure 
(javax.mail.AuthenticationFailedException\colon; null)

Any suggestions?  I have tried a number of combinations (including mail.server 
= localhost for Postfix to handle) and would expect this to work without issue 
as it did in the past.  Always the same error.


-Jeff

-- 
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/BN8PR05MB662FC0843498B5D2F25DD%40BN8PR05MB6644.namprd05.prod.outlook.com.

Re: [dspace-tech] Re: [Dspace-tech] Browse by Issue Date wont give any results

[Tim Donohue]

Hello,

I'm sorry, but you haven't provided enough information here to allow us to help 
you out.  If upgrading to 5.10 hasn't helped your situation, then it's possible 
that the bug at https://jira.lyrasis.org/browse/DS-2602 was not the cause of 
the behavior you are seeing.

I'd recommend checking your logs for any errors that may be occurring (both 
when you run a date search *and* when you reindex content).  It's possible 
there's an error there that is causing unexpected behavior.  Here's a guide for 
finding errors in logs: 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error

Keep in mind that all support on these mailing lists is provided by volunteers. 
So, the most information you can provide, the easier it may be for someone here 
to diagnose the problem (especially if it is an error they have seen before).

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Arunendra M. Biswas 
Sent: Saturday, February 1, 2020 2:27 PM
To: DSpace Technical Support 
Subject: [dspace-tech] Re: [Dspace-tech] Browse by Issue Date wont give any 
results

Dear Tim,
I am using DSpace 5.10 xmlui on Windows 2007 and the date search doesn't yield 
correct results.Any immediate fix would be of great help

On Thursday, August 27, 2015 at 12:19:12 AM UTC+5:30, sn...@buntblock.de wrote:

Hi,

i am using dspace-5.2 and most things work fine, beside some Browsing Issues:


When i Browse by Issue Date it shows me all items.
After (Choose year) or type in a year i get always zero results.
/xmlui/browse?type=dateissued

In opposite when i click on the sidebar Date Issued: I get the correct result.
/xmlui/discover?filtertype=dateIssued_relational_operator=equals=2012


In all types of "Browse by" i get weird behaviours:

When i enter first letters for Authors, Titles, Subjects it gives me
results i cannot understand and totally wrong.



I searched the logs and cannot find errors, debug is enabled.

I tried:

dspace index-discovery -b
dspace index-discovery -o

Everythings seems fine.

When i rebuild dspace, all indexes "Looks good!"


As i am using xmlui-mirage2 i tested this in jspui and the same wrong
results and missing functionality showed up.

"discover" seems to work
"browse" not


How is the way to get into it and find the problem ?


Best regards


SNEMI





--
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/198b729e-d12e-4fde-9c3b-aff181015532%40googlegroups.com.

-- 
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/DM5PR2201MB1148C369D09D427F8C1B4418ED000%40DM5PR2201MB1148.namprd22.prod.outlook.com.

Re: [dspace-tech] CORS - Cross Origin Request Blocked

[Tim Donohue]

I would recommend looking at the DSpace logs when your site starts up to look 
for errors reported there. It sounds (to me) like the /server webapp (which 
includes the REST API) is not starting/initializing properly.  The result you 
see should be similar to our DSpace 7 Demo REST API at 
https://dspace7.4science.cloud/server/

Without the errors you are receiving, it's very hard to debug this.  Also, you 
might want to simply try running the Docker images on "localhost" (instead of a 
custom URL) *first*, just to verify you can get things working *without 
modifying any configurations at all*.  Once it works on "localhost" you can 
work on customizing the URLs to match what you want to see.

Tim

From: Julien Cochennec 
Sent: Monday, February 3, 2020 1:51 AM
To: Tim Donohue 
Cc: DSpace Technical Support 
Subject: Re: [dspace-tech] CORS - Cross Origin Request Blocked

I got a response from 
http://snp-dev-exd001.snump.in.cloe.education.gouv.fr:8080/server/?endpointMap#/server/api
 but all the links it mention give 404.
All the links 
http://snp-dev-exd001.snump.in.cloe.education.gouv.fr:8080/api/core/ give 404 
errors


Le lun. 3 févr. 2020 à 08:24, Julien Cochennec 
mailto:trb...@gmail.com>> a écrit :
When I follow the step by step instructions, from fresh git clone, just 
modified the angular conf :

more ../../add-ons/angular-tools/environment.dev.js
module.exports = {
  rest: {
ssl: false,
host: 
'snp-dev-exd001.snump.in.cloe.education.gouv.fr',
port: 8080,
// NOTE: Space is capitalized because 'namespace' is a reserved string in 
TypeScript
nameSpace: '/server/api'
  }
};

I did this command :

export BASEROOT=http://snp-dev-exd001.snump.in.cloe.education.gouv.fr:8080


Then runned :
docker-compose -p d7 -f docker-compose.yml -f d7.override.yml -f 
load.entities.yml pull
docker-compose -p d7 -f docker-compose.yml -f d7.override.yml -f 
load.entities.yml up -d


I get this error message, with an infinite Loading gif, in Google Chrome 
developer tools console, on 
http://snp-dev-exd001.snump.in.cloe.education.gouv.fr:3000/ :

Access to XMLHttpRequest at 
'http://snp-dev-exd001.snump.in.cloe.education.gouv.fr:8080/api/core/sites' 
from origin 'http://snp-dev-exd001.snump.in.cloe.education.gouv.fr:3000' has 
been blocked by CORS policy: Response to preflight request doesn't pass access 
control check: No 'Access-Control-Allow-Origin' header is present on the 
requested resource.


On http://snp-dev-exd001.snump.in.cloe.education.gouv.fr:8080/ I get the tomcat 
welcome page.

On http://snp-dev-exd001.snump.in.cloe.education.gouv.fr:8080/rest I get the 
REST API doc.

On http://snp-dev-exd001.snump.in.cloe.education.gouv.fr:8080/spring-rest I get 
a 404.

On http://snp-dev-exd001.snump.in.cloe.education.gouv.fr:8080/server/api I get 
a 500 Error.


Le lun. 3 févr. 2020 à 08:13, Julien Cochennec 
mailto:trb...@gmail.com>> a écrit :
The part I need is this one :
Ingest the Entities Test Dataset and Start DSpace 7 (Server Setup)
I'm not sure what  mean, is this the FQDN?

Le lun. 3 févr. 2020 à 07:53, Julien Cochennec 
mailto:trb...@gmail.com>> a écrit :
Ok, thank you, it seems that the CORS message only occurs when an endpoint is 
missing, so maybe it has nothing to do with CORS.
I found the modules/rest.conf and CORS is allowed.
So my second guess is that something is wrong between my angular conf and my 
dspace backend conf local.cfg.
Here are the two files.
Everything else seems to be working perfectly.

Angular conf in add-ons/angular-tools/environment.dev.js
[root@snp-dev-exd001 /opt/DSpace-Docker-Images]# more 
add-ons/angular-tools/environment.dev.js
module.exports = {
  rest: {
ssl: false,
host: 
'snp-dev-exd001.snump.in.cloe.education.gouv.fr',
port: 8080,
// NOTE: Space is capitalized because 'namespace' is a reserved string in 
TypeScript
nameSpace: '/rest'
  }
};

DSpace backend conf :
root@57f0be4df5e7:/dspace/config# more local.cfg
# 
# This file contains the localized properties for published DSpace images.
# See https://github.com/DSpace-Labs/DSpace-Docker-Images for usage information.
# 
dspace.dir = /dspace
db.url = jdbc:postgresql://dspacedb:5432/dspace
dspace.hostname = localhost
dspace.baseUrl = http://localhost:8080/server
solr.server=http://dspacesolr:8983/solr
root@57f0be4df5e7:/dspace/config#

Modified section of docker-compose.yml (should I modify the override.yml?) :
  dspace:
image: "${DOCKER_OWNER:-dspace}/dspace:${DSPACE_VER:-dspace-6_x-jdk8-test}"
container_name: dspace
environment:
  # - JAVA_OPTS=
  # The following memory allocation will be appended to any JAVA_OPTS 
settings
  # - JAVA_MEM=-Xmx2500m
  - SCRIPTVER=6
  - 

Re: [dspace-tech] Build failure for installing Mirage 2 in Dspace...Cannot run program "npm"

[Paul Münch]

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:
> 
>
> - 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
> .

-- 
All messages to this mailing list should adhere to 

[dspace-tech] Re: DSpace Mirage2 Errors

[Anis]

Seems like the newest ffi (1.12.2) is causing some problems, downgrading to 
1.12.1 seems to work.

so adding the following lines to dspace/modules/xmlui-mirage2/pom.xml


rubygems
ffi
1.12.1
gem


- Anis

On Monday, February 3, 2020 at 8:41:47 AM UTC, Anis wrote:
>
> Hi, I'm trying to compile DSpace 5 with the following command mvn package 
> -Dmirage2.on=true
>
> The error I get is the following,
> ERROR:  Error installing 
> ../.m2/repository/rubygems/ffi/1.12.2/ffi-1.12.2.gem:
>  ERROR: Failed to build gem native extension.
>
>  current directory: 
> /source-dspace/dspace/modules/xmlui-mirage2/target/rubygems/gems/ffi-1.12.2/ext/ffi_c
>  /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -cp 
> :/source-dspace/dspace/modules/xmlui-mirage2/target/test-classes:/source-dspace/dspace/modules/xmlui-mirage2/target/classes
>  
> org.jruby.Main -r ./siteconf20200203-5637-783ftr.rb extconf.rb
>  Error: Could not find or load main class org.jruby.Main
>
>  extconf failed, exit code 1
>
> this is crippling our deployment right now, so I'd be grateful of any help.
>

-- 
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/b1b0a682-8118-4827-9f47-dc3ac518fdc0%40googlegroups.com.

[dspace-tech] DSpace Mirage2 Errors

[Anis]

Hi, I'm trying to compile DSpace 5 with the following command mvn package 
-Dmirage2.on=true

The error I get is the following,
ERROR:  Error installing 
../.m2/repository/rubygems/ffi/1.12.2/ffi-1.12.2.gem:
 ERROR: Failed to build gem native extension.

 current directory: 
/source-dspace/dspace/modules/xmlui-mirage2/target/rubygems/gems/ffi-1.12.2/ext/ffi_c
 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -cp 
:/source-dspace/dspace/modules/xmlui-mirage2/target/test-classes:/source-dspace/dspace/modules/xmlui-mirage2/target/classes
 
org.jruby.Main -r ./siteconf20200203-5637-783ftr.rb extconf.rb
 Error: Could not find or load main class org.jruby.Main

 extconf failed, exit code 1

this is crippling our deployment right now, so I'd be grateful of any help.

-- 
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/e163ba91-110d-4b28-9262-092d2348758b%40googlegroups.com.