-
Notifications
You must be signed in to change notification settings - Fork 10
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
compileFrege task doesn't execute Frege compiler #38
Comments
A bit more data. I completely removed the entire Gradle cache (at the risk of downloading half the Internet again :-). I did a clean first and it downloaded lots of Frege bits and pieces including the frege jar the plugin uses. When I then asked for a build:
So although the POM for the Frege jar was downloaded, the actual jar was not. I am not sure this is manually hackable? |
More data. Using: dependencies {
compile 'org.frege-lang:frege:3.23.+'
} with JDK8 (but not JDK9 since that is never going to work) works fine. So I suspect that there is a problem with the Frege 3.24 artefact and it's POM. Everything also works if I manually download the Frege 3.24.100.1 artefact: dependencies {
compile files(System.properties['user.home']+ '/lib/JDK/frege.jar')
} |
It could be that the version range "+" does not work nicely with the 100.1 scheme. Dierk sent from:mobile
|
The problem is that the packaging declaration in the pom has changed. In |
Seems like a 3.24.100.2 release should be able to fix everything. |
On Debian Sid, using JDK8 from packages (or JDK9 download), with the build.gradle file:
on the project that looks like:
with the Frege file being:
the result of an execution is:
The text was updated successfully, but these errors were encountered: