-
Notifications
You must be signed in to change notification settings - Fork 38
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
Problems running on Windows #83
Comments
Hi @lask79,
For interest sake, does it actually work if you manually create |
No, this folder exists the whole time. As I mentioned before it is running inside a CMD with Run as Administrator or when I call the JRuby gem install manually. |
@lask79 is this bug really closed? I don't think we've actually fixed anything :P |
Hmm, I wish it could be fixed by just pressing the wrong button ;-) |
For sanity, can you clarify which version of if the jruby-gradle-plugin you were using. |
Sure, I tried several versions from 0.1.2 to 0.1.9. |
I have the same problem building the current AsciidoctorJ on Windows7. |
Interesting, good to know @robertpanzer. I'll try to get a Windows machine up in AWS to reproduce and debug this issue |
Keep in mind that for testing on Windows, you can use the Modern IE virtual machine images. IMO, it's the fastest way to get a Windows box on your non-Windows machine. As for tests, we should definitely get the JRuby plugin running on AppVeyor. Setup is extremely simple. You create a YAML file much like Travis and it handles the rest. You can even use the web-based wizard to create the appveyor.yml file. Here's the config for Asciidoctor for reference: https://github.com/asciidoctor/asciidoctor/blob/master/appveyor.yml |
Appveyor support is in (#92). However, @mojavelinux , do you know if there is a way of using the github organisation account on Appveyor rather than my own account? |
Good (??) news is that I have been able to reproduce the issue that @lask79 was referring to. |
Unlike @lask79, I do not even get it to run
(lines broken for readability) When run with |
Just to add to it, the problem has nothing to do with Asciidoctor, Even a Gradle script as simple as buildscript {
repositories {
jcenter()
}
dependencies {
classpath 'com.github.jruby-gradle:jruby-gradle-plugin:0.1.10'
}
}
apply plugin: 'com.github.jruby-gradle.base'
dependencies {
gems 'rubygems:asciidoctor-diagram:1.2.0'
} reproduces the problem (tested with Gradle 2.0 & 2.2). (Which bugs me, as we are not seeing this problem in the integration tests). |
Actually, it is reproducible in the integration tests on a local 32-bit VM (but not on Appveyor) |
I haven't looked into how to setup an organization on AppVeyor. We can |
The problem is related to the environment, specifically to the way that it is run to install GEMs. See At this point I suspect it might be related to the fact that |
Issue is that neither |
What's strange is that the AsciidoctorJ builds work on AppVeyor using the 0.1.0 release of the JRuby Gradle plugin. We are expecting this build to fail. Any idea why it works and how to break it? https://ci.appveyor.com/project/asciidoctor/asciidoctorj Do I need to unset TMP and TEMP? |
...or is it because it's fixed in JRuby 1.7.17? |
Also, this argument worries me:
Can we force that to be UTF-8? |
The builds passed on Appveyor, even though it failed locally. This being with our Appveyour setup using both 32-bt and 64-bit JDKs. The only thing that I have seen in common is that both @robertpanzer and I had failed builds on Windows 7. I am not sure what OS Appveyor runs on by default. |
AppVeyor is Windows Server 2012 by default. Perhaps we need to unset TMP & TEMP? |
I have noticed that. It seems to be a Gradle default. I'll see if i can use |
Here's a much simpler gradle script to help reproduce the problem https://gist.github.com/ysb33r/31419a20f77edc850e2e. Just fill in the path to a local |
I have to mail that to my account at work because I don't have access to gist there :(
|
I can confirm that the problem occurs on Windows 8.1 32-bit as well. |
Works on my machine as well with AsciidoctorJ build. |
👍 |
Do you mean my fix worked? |
Yes, absolutely!
|
@robertpanzer that's excellent! This will be in the 0.1.11 release which I plan on releasing today provided in-flight wifi allows me to :) |
👍 |
…f an error on windows 'Could not load FFI Provider' see jruby-gradle/jruby-gradle-plugin#83 (latest version is 0.3.0 but seems not to work ootB)
Hi,
I am facing some problems when trying to get this example to run on my Windows machine:
http://mrhaki.blogspot.de/2014/11/awesome-asciidoctor-use-asciidoctor.html
I am getting the following error:
It seems JRuby can not install the gems because the folder "build/vendors" is still empty. But when I try to install them in the command client with the same input it works:
I also found out that I can run the gradle build when I start my console with "Run as Administrator". Most of my collegues do not have admin rights on their machine so this is not an option for us.
Do you have any Ideas how I can run this build without admin rights?
Regards
Lasse
The text was updated successfully, but these errors were encountered: