Closed gabrielbodard closed 2 years ago
Dear all,
I do not get EFES to work on my Mac (OS 10.15.7). I followed the instructions on GitHub, also downloaded the Java SE Development Kit 8, but a few seconds after I entered “sh build.sh” it crashes and there is a long error list (see attachment) and I cannot enter EFES. First I used Java 8.281, then I also tried 8.271, but without success.
Does anybody have a solution for this?
All the best, Alex
Dear all, I have the same problem. I followed the instructions on GitHub and downloaded Java8.281 and it happened the same. after I entered sh build.sh” it crashes in the same way:
AppContext@1a75e76a{/,file:/Users/beatricepestarino/Desktop/EFES/webapps/ROOT/,STARTING}{/ROOT}: java.lang.ExceptionInInitializerError java.lang.ExceptionInInitializerError at org.apache.cocoon.util.log.ExtensiblePatternFormatter.addTextRun(ExtensiblePatternFormatter.java:185)
I guess the problem is Java. Does anyone can help? Many thanks Beatrice
This appears to be https://issues.apache.org/jira/browse/LANG-624. Thankfully that is long fixed, but it does require installing updated JAR files; I'm in the process of doing this.
Thank you for your reply! So do I need do install updated JAR files? How can do this? Many thanks Beatrice
Sadly it's not as simple (currently, at least) as just installing some files - replacing the commons-* JAR files and rebuilding Cocoon fails, so there are incompatibilities between the JAR that fixes the problem you're experiencing and the other (working) parts of the system. I'm still investigating.
By the way, as far as I know the only part of EFES that does not currently work with a version of Java later than 1.8 is some of the image handling (such as automatically creating thumbnails). You might want to try using a later version of Java, which with luck wouldn't trigger the bug you're seeing now. No guarantees though.
Thank you very much!! I will try tomorrow to download and try a later version. I will let you know if it works or not. Hopefully fingers crossed Many thanks Beatrice
Thank you very much!
It seems that it has also to do with the OS version (or any changes that come with it). On my iMac with OS 10.13.6 EFES works with Java 7.80 as well as 8.281, but on my MacBook with OS 10.15.7 it does not work regardless of the Java version …
I've tried with a later version of Java, and the problem continues!
Me to I have problems in getting EFES work on MAC (10.15.7). In the Terminal I get the following: 021-04-12 10:38:15.206:WARN:oejuc.AbstractLifeCycle:main: FAILED o.e.j.a.AntWebAppContext@5032714f{/,file:/Users/danielacolomo/Desktop/EFES-master/webapps/ROOT/,STARTING}{/ROOT}: java.lang.ExceptionInInitializerError java.lang.ExceptionInInitializerError at org.apache.cocoon.util.log.ExtensiblePatternFormatter.addTextRun(ExtensiblePatternFormatter.java:185) at org.apache.cocoon.util.log.ExtensiblePatternFormatter.parse(ExtensiblePatternFormatter.java:400) at org.apache.cocoon.util.log.ExtensiblePatternFormatter.setFormat(ExtensiblePatternFormatter.java:417) at org.apache.cocoon.servlet.CocoonServlet.initLogger(CocoonServlet.java:798) at org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:356) at org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:542) at org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:351) at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:800) at …
Total time: 5 seconds Danielas-MBP-2:EFES-master danielacolomo$ Any suggestions? Thank you in advance!
A quick (non-representative) check-in with my colleagues showed that the two with OS 10.15.7 have problems, the one with 11.2.3 does not. Maybe the update solves it …
Curiously, as mentioned above, it also works with a previous OS version (10.13.6).
Many thanks. I have 10.15.7 too and I still have problems!
Update to 11.2.3 didn't solve the problem for me, alas.
Unfortunately I don't have any good news regarding this issue yet. While the bug that appears to be causing the issue was fixed years ago (2011!), the fixed version is not being used, and other changes in the fixed version cause different, equally fatal, problems.
I've written to those who make and use Cocoon (a major part of the software underlying EFES) to see what options there are to fix or work around the problem, but there is little I can do other than that for now. Sorry! I have never encountered this problem myself, nor has it been reported before now (including at numerous EFES workshops), and suddenly lots of people are encountering it.
@ajenhl Thanks for this update, Jamie. This is indeed an odd problem—perhaps caused by Java updates and support in various versions of OSX? Anyway as you can say we can't really fix it overnight (although I would like to make a push at making EFES more robust in the long term—including getting the latest versions of Java baked in at all levels), so we'll have to work around.
Apologies to everyone else who hasn't managed to get EFES working; we'll try to find guidance for you to set up a transformation scenario in Oxygen for the time being.
Goodmorning everyone
My problem with EFES is a different one.
A few days ago I was able to enter EFES without problems, but after updating my mac (now it is BigSur version 11.2.3) it doesn't work anymore. I thought the problem might be the Java version, so I updated this too (which is now Java 8 update 281).
When I open the terminal a message appears saying:
"The default interactive shell is now zsh.
To update your account to use zsh, please run chsh -s / bin / zsh
.
For more details, please visit https://support.apple.com/kb/HT208050.
MacBook-Air-by-Giordana: ~ giordanafranceschini $ "
If I run chsh -s / bin / zsh
, nothing happens.
Entering the commands "cd Desktop / EFES /" and then "sh build.sh" the total result is:
"The default interactive shell is now zsh.
To update your account to use zsh, please run chsh -s / bin / zsh
.
For more details, please visit https://support.apple.com/kb/HT208050.
MacBook-Air-by-Giordana: ~ giordanafranceschini $ cd Desktop / EFES /
MacBook-Air-di-Giordana: EFES giordanafranceschini $ sh build.sh
/ bin / sh: sw / ant / bin / ant: Operation not permitted
MacBook-Air-di-Giordana: EFES giordanafranceschini $ ".
Anyone know what the problem might be?
Thank you
Giordana
In this case I think it is a permission issue, to be solved with the "chmod" command. Try this:
chmod 777 build.sh
chmod 777 sw/ant/bin/ant
Unfortunately this appears
Ah, yes, you have to enter the EFES folder with cd Desktop/EFES
before trying this
mmm... try this:
sudo chmod 777 build.sh
sudo chmod 777 sw/ant/bin/ant
(with sudo
you will be asked to insert the password of your computer account in order to allow you to act as administrator, granting you all the permissions)
The image of a small key appears in fact, but it does not allow me to write the password (nor do you open other spaces in which to enter the password)
When the Terminal requests a password, it usually allows you to type it and press enter, but does not display anything on the Terminal screen (neither the password itself nor dots for hiding it): does it allow you to type it and press enter?
No, it doesn't allow me to type anything else after entering the command "sudo chmod 777 build.sh sudo chmod 777 sw/ant/bin/ant".
It is ok if nothing happens on the screen: just after the 'Password' message appears, you should type the password (and nothing will happen on the screen at all) and then press Enter. Doesn't this work?
Yes, in fact even if nothing appears, typing the password and pressing enter seems to have entered the password. But it tells me it's wrong. it is strange that it tells me that it is wrong, because it is the one I use to download and update programs. I tried to change the password and by entering that there, the pc confirms that it is the password currently in use.
@GiordanaFranceschini : the only thing I can think is that the user you are logged into your computer as has enough access rights to update software, but not administrator (or Root) access to the system itself. Was your computer's system set up by someone else? Do you know who would have the administrator password?
(Alternatively you are inadvertently pressing a space or some other invisible character when entering the password in Terminal, but it's hard to imagine you would be doing that over and over again.)
Sorry not to be more help.
My computer's system was set up by myself. The password is the same one I use to download and update programs and to change some settings on my pc. I'm sorry, because until now I have always been able to use EFES and now there is this strange problem. I will continue to look for other solutions. Thanks for now!
Dear all, last week I could open EFES without any problems, but today isn't going an I see this message Last login: Tue Apr 13 16:35:59 on ttys000
The default interactive shell is now zsh.
To update your account to use zsh, please run chsh -s /bin/zsh
.
For more details, please visit https://support.apple.com/kb/HT208050.
Camillas-Air:~ camillacampedelli$ cd Dekstop/EFES-master
-bash: cd: Dekstop/EFES-master: No such file or directory
Camillas-Air:~ camillacampedelli$
Have you moved or renamed your EFES folder?
Watch out, there is a typo. It's cd Desktop/EFES-master not cd Dekstop/EFES-master
@GiordanaFranceschini : sorry for the basic questions! I was grasping at straws, because otherwise I don't know why that would be happening. Sorry you're now having trouble with EFES. I will try to post instructions for the alternative (using stylesheets in Oxygen) in this forum later today.
It would have been entirely possible that this was a minor issue that I hadn't been paying attention to, so thank you!
epidoc
.Quickrefs
you will find a file named Running_Epidoc_Stylesheets.pdf
which should give you instructions on how to load the Oxygen project, and run the transformation scenario that will transform one EpiDoc XML file on your computer into one HTML file that you can open in a web browser.Hi there! I am experiencing a new issue with EFES when displaying my xml files. In some cases, instead of the title I have in the XML file, EFES displays what seems to be a standard heading (picture attached).
Thanks!
@fra-anthos It surprises me that you say this only sometimes happens. Can you see any difference in the way you have marked up the title in the EpiDoc file between those that display the standard title vs your title?
In any case, as we're really only using EFES as a way to quickly check your encoding exercises this week, I'd ask you to be tolerant of these idiosyncrasies, and if you really want to learn how to fix EFES, come back in September! :)
It is again a glitch in the XSLT stylesheets, which expect to have at least some text (or space) directly inside <title>
, and in the example that you posted there isn't because all the text is inside the three <persName>
s. If you add a space among the three <persName>
s (which should have been added in any case!) you should see the heading
Dear All, I tried the new lib folder but still it does not work. I attach here what it appears
Last login: Wed Apr 14 13:53:22 on console
beatricepestarino@MacBook-Air-di-Beatrice ~ % cd Desktop/EFES
beatricepestarino@MacBook-Air-di-Beatrice EFES % sh build.sh
Java HotSpot(TM) 64-Bit Server VM warning: Ignoring option PermSize; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0
Buildfile: /Users/beatricepestarino/Desktop/EFES/local.build.xml
Development server is running at http://127.0.0.1:9999
Quit the server with CONTROL-C.
2021-04-14 14:39:18.013:WARN:oejuc.AbstractLifeCycle:main: FAILED o.e.j.a.AntWebAppContext@402c4085{/,file:/Users/beatricepestarino/Desktop/EFES/webapps/ROOT/,STARTING}{/ROOT}: java.lang.ExceptionInInitializerError
java.lang.ExceptionInInitializerError
at org.apache.cocoon.util.log.ExtensiblePatternFormatter.addTextRun(ExtensiblePatternFormatter.java:185)
at org.apache.cocoon.util.log.ExtensiblePatternFormatter.parse(ExtensiblePatternFormatter.java:400)
at org.apache.cocoon.util.log.ExtensiblePatternFormatter.setFormat(ExtensiblePatternFormatter.java:417)
at org.apache.cocoon.servlet.CocoonServlet.initLogger(CocoonServlet.java:806)
at org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:356)
at org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:542)
at org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:351)
at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:800)
at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:288)
at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1322)
at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:731)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:490)
at org.eclipse.jetty.ant.AntWebAppContext.doStart(AntWebAppContext.java:664)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:108)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:90)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:58)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:175)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:108)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:90)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:58)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:108)
at org.eclipse.jetty.server.Server.start(Server.java:342)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:90)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:58)
at org.eclipse.jetty.server.Server.doStart(Server.java:290)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.ant.ServerProxyImpl.start(ServerProxyImpl.java:253)
at org.eclipse.jetty.ant.JettyRunTask.execute(JettyRunTask.java:262)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:435)
at org.apache.tools.ant.Target.performTasks(Target.java:456)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
at org.apache.tools.ant.Main.runBuild(Main.java:851)
at org.apache.tools.ant.Main.startAnt(Main.java:235)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
Caused by:
java.lang.StringIndexOutOfBoundsException: begin 0, end 3, length 2
at java.base/java.lang.String.checkBoundsBeginEnd(String.java:3751)
at java.base/java.lang.String.substring(String.java:1907)
at org.apache.commons.lang.SystemUtils.getJavaVersionAsFloat(SystemUtils.java:1133)
at org.apache.commons.lang.SystemUtils.
BUILD FAILED
/Users/beatricepestarino/Desktop/EFES/buildfiles/jetty-build.xml:30: java.lang.ExceptionInInitializerError
at org.apache.cocoon.util.log.ExtensiblePatternFormatter.addTextRun(ExtensiblePatternFormatter.java:185)
at org.apache.cocoon.util.log.ExtensiblePatternFormatter.parse(ExtensiblePatternFormatter.java:400)
at org.apache.cocoon.util.log.ExtensiblePatternFormatter.setFormat(ExtensiblePatternFormatter.java:417)
at org.apache.cocoon.servlet.CocoonServlet.initLogger(CocoonServlet.java:806)
at org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:356)
at org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:542)
at org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:351)
at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:800)
at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:288)
at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1322)
at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:731)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:490)
at org.eclipse.jetty.ant.AntWebAppContext.doStart(AntWebAppContext.java:664)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:108)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:90)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:58)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:175)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:108)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:90)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:58)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:108)
at org.eclipse.jetty.server.Server.start(Server.java:342)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:90)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:58)
at org.eclipse.jetty.server.Server.doStart(Server.java:290)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.ant.ServerProxyImpl.start(ServerProxyImpl.java:253)
at org.eclipse.jetty.ant.JettyRunTask.execute(JettyRunTask.java:262)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:435)
at org.apache.tools.ant.Target.performTasks(Target.java:456)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
at org.apache.tools.ant.Main.runBuild(Main.java:851)
at org.apache.tools.ant.Main.startAnt(Main.java:235)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
Caused by: java.lang.StringIndexOutOfBoundsException: begin 0, end 3, length 2
at java.base/java.lang.String.checkBoundsBeginEnd(String.java:3751)
at java.base/java.lang.String.substring(String.java:1907)
at org.apache.commons.lang.SystemUtils.getJavaVersionAsFloat(SystemUtils.java:1133)
at org.apache.commons.lang.SystemUtils.
Total time: 8 seconds beatricepestarino@MacBook-Air-di-Beatrice EFES %
It is different from the other. It stays 6/7 seconds more or less without showing anything more after CONTROL-C... so I had good hopes but after ten seconde the list with Error and then apache started again. Thank you for trying! Beatrice
I'm trying too, but I don't understand the steps: I downloaded the "lib" folder from the dropbox and put it on the desktop. What should I do next? Thank you
unzip it and put all its contents inside webapps/ROOT/WEB-INF/lib, replacing the existing content of that folder
As far as I understood you should replace the old lib folder with the new lib folder that is in webapps/Root/WEB-INF/lib inside of EFES folder. Then try to open EFES through the terminal... and you will see.
Thanks to both of you! I did as you said but sadly the error looks the same.
Last login: Wed Apr 14 16:08:37 on ttys000
The default interactive shell is now zsh.
To update your account to use zsh, please run chsh -s /bin/zsh
.
For more details, please visit https://support.apple.com/kb/HT208050.
DGTELA-140:~ giordanafranceschini$ cd Desktop/EFES/
DGTELA-140:EFES giordanafranceschini$ sh build.sh
/bin/sh: sw/ant/bin/ant: Operation not permitted
DGTELA-140:EFES giordanafranceschini$
Hi! Sorry today I had an emergency and I could not attend the Q and A session. Sorry, could you please send again the instructions about how to display the inscriptions by Oxygen (not by EFES)? I have no idea why I cannot see the email anymore. Many thanks. Beatrice
Here you can find the instructions: https://github.com/EpiDoc/Tutorials/issues/4#issuecomment-818848559
Grazie!!
@ajenhl @gabrielbodard Thank you very for the new "lib" folder. It works on my computer now!!! The messages in the terminal (see attachment) differ from that on my other computer with the original "lib", though.
Yes!!! It works for me too now!! Thank you!!! Thank you @ajenhl !!
I'm glad that the new files with the backported fix are at least somewhat working. @alexgangoly, that's another error I've never seen before; I'll try to figure out what's happening, but if the main part of EFES is still running you should be able to see the rendering of your documents. Working with authority files and associated aspects will not work, though, since they depend on the part that is throwing that error.
Working with authority files and associated aspects will not work, though, since they depend on the part that is throwing that error.
Ah, so this fix is not ready for prime time yet, then. This is increasingly urgent. Let's talk about this on the EFES-users list soon.
Thanks so much for this fix, Jamie!
Ah, so this fix is not ready for prime time yet, then. This is increasingly urgent. Let's talk about this on the EFES-users list soon.
That only applies for the error @alexgangoly is having, which is unrelated (as far as I can tell) to the other problem.
Alex, can you try changing the build.sh file that you use to run EFES, to replace the line starting "export ANT_OPTS" with the following:
export ANT_OPTS='-XX:PermSize=64m -XX:MaxPermSize=128m -Xmx512m -Dinfo.aduna.platform.appdata.basedir=./webapps/openrdf-sesame/app_dir/ -Dorg.eclipse.jetty.LEVEL=WARN --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.reflect=ALL-UNNAMED'
That should all be one line, and there should be no spaces after any "-" character (the word wrapping in this comment may have inserted such).
If you have any technical problems installing, indexing, or viewing your EpiDoc files in EFES, that you are not able to answer by consulting the User Guide, please report them here, with as much information/screenshots of error messages etc. as possible, and we (or fellow participants) will help you if we can.
Interim workaround for people who can't use EFES this week