Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependency erros #11

Open
mbaquir opened this issue Sep 1, 2015 · 11 comments
Open

Dependency erros #11

mbaquir opened this issue Sep 1, 2015 · 11 comments

Comments

@mbaquir
Copy link

mbaquir commented Sep 1, 2015

Hi!
Thanks for sharing this library. I cloned the repository on NetBeans and now Im having issues with dependencies. The error I get when I try to run it is:
Failed to execute goal on project folioxml-commandline: Could not resolve dependencies for project folioxml:folioxml-commandline:jar:0.0.1-SNAPSHOT: Could not find artifact folioxml:folioxml-lucene:jar:0.0.1-SNAPSHOT -> [Help 1]

Any idea on how to fix this problem?

Thanks

@lilith
Copy link
Member

lilith commented Sep 1, 2015

You need to switch to the develop branch and run maven.

https://github.com/imazen/folioxml/tree/develop#running-the-command-line-app

I would also suggest IntelliJ over Netbeans, but you don't need either to build/run this app.

@DonnyLi
Copy link

DonnyLi commented Sep 2, 2015

Hey Mr.Jones,

When running the command line app using these commands:

  • mvn clean compile assembly:single -U -B -fae
  • java -jar commandline/target/folioxml-commandline-jar-with-dependencies.jar -config core/folioxml/resources/test.yaml -export folio_help

I receive a file not found exception error where it's looking for FolioHlp.FFF. I'm not sure if this is a test case or you were originally testing your app on this file. How can I remedy this problem or what commands would I have to use to convert a file in a specific folder. Furthermore, where would the converted file be?

@lilith
Copy link
Member

lilith commented Sep 2, 2015

This issue is related to: #9

If we can find/create a public domain test infobase we can replaces FolioHlp.FFF. Given that different versions of the JVM can have different regex behaviors, these tests are important.

@DonnyLi
Copy link

DonnyLi commented Sep 2, 2015

If I needed to conduct my own test on my own .FFF file (say it's named test.FFF) what would my steps be?

@lilith
Copy link
Member

lilith commented Sep 2, 2015

I would need to help set this up. Would you be able to collaborate me on #9 ? I'm using Folio Views 4.7.1. Created repo here: https://github.com/imazen/folio-test-infobases

@DonnyLi
Copy link

DonnyLi commented Sep 2, 2015

As much as I would love to collaborate with you on the issue, I am in the same boat as you are. I do not own the rights to distribute the file and cannot push it into your repo. Is there a way for me to set it up so that I could test on my own accord?

@lilith
Copy link
Member

lilith commented Sep 2, 2015

I'm afraid not, unless you have a licensed copy of the Folio Help Manual. My suggestion was that we create new public domain content in a new infobase to exercise all of the features.

@DonnyLi
Copy link

DonnyLi commented Sep 2, 2015

I actually do have a licensed copy of the Folio Help Manual. I have a .fff file that I need to convert into either xhtml or xml. How can I use your tool to allow me to do this?

@lilith
Copy link
Member

lilith commented Sep 2, 2015

If you export the manual to FFF, then you can place those files in the /files/folio-help directory (within the project), and it should build & test. I suggest the develop branch.

@DonnyLi
Copy link

DonnyLi commented Sep 2, 2015

I tried using your tool on my FolioHlp.FFF file and was able to get a folder with a few .txt, .css, .html files where the html file contained readable content displayed in a fairly aesthetically pleasing manner. However, while the tool was running it ran into an error that gave an exception in the main thread:

  • at folioxml.export.html.LinkMapper.process(LinkMapper.java:45)
  • at folioxml.export.html.MultiRunner.process(MultiRunner.java:36)
  • at folioxml.export.plugins.ApplyProcessor.onRecordComplete(ApplyProcessor.java:61)
  • at folioxml.export.InfobaseSetVisitor.complete(InfobaseSetVisitor.java:127)
  • at folioxml.export.ExportRunner.Export(ExportRunner.java:113)
  • at folioxml.command.Main.run(Main.java:70)
  • at folioxml.command.Main.main(Main.java:40)

Also, would it be possible to use this tool on a file other than the FolioHlp file given that I already have my own help manual?

@lilith
Copy link
Member

lilith commented Sep 2, 2015

LinkMapper is a new feature I just added yesterday; it may be a bit buggy. You could roll back a commit or comment it out. I also offer a paid service to put the content though conversion and resolve any issues that crop up around esoteric flat file codes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants