-
Notifications
You must be signed in to change notification settings - Fork 41
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
jrubyPrepare fails to resolve dependencies like 1.5.0.alpha.8 #325
Comments
@smartg00se you are right the gradle version resolution or the underlying mapping from rubygems to maven is not 100% compatible. for example it will not pick prereleased versions of gems from a range of versions, otherwise we would default to the maven repository excludes these prerelease version from the version range BUT they can be cherrypicked. so the only workaround for you is to add a gem dependency |
I've tried to cherrypick |
@xlijun This issue does show a defect, but before I address the potential solution to this, I would to say that if you use a GEM that has dependencies {
gems 'rubygems:asciidoctor-pdf-cjk-kai_gen_gothic:0.1.1', {
exclude module : 'asciidoctor-pdf'
}
} |
Now as to the fix for the most general case, I now have a solution that will go into 2.0.0 when it is released. The idea with the fix is that specific configurations or just modules can use Gradle's standard Ivy resolution rules rather the GEM version (bundler-like) resolution rules. gemResolverStrategy {
excludeModule ~/^asciidoctor-pdf$/, ~/.+(alpha|beta).*/
}
dependencies {
gems 'rubygems:asciidoctor-pdf-cjk-kai_gen_gothic:0.1.1'
gems 'rubygems:asciidoctor-pdf:1.5.0.alpha.8'
} In |
…ruby-gradle#325) For specific cases it might be better to use the standard Gradle resolution strategies rather than the bundler-like atrategy suppleid vua GemVersionResolver. To accomplish this a script author may configure specific configurations and modules (or modules+revisions) to be excluded.
PR #377 addresses this. |
…ruby-gradle#325) For specific cases it might be better to use the standard Gradle resolution strategies rather than the bundler-like atrategy suppleid vua GemVersionResolver. To accomplish this a script author may configure specific configurations and modules (or modules+revisions) to be excluded.
…ruby-gradle#325) For specific cases it might be better to use the standard Gradle resolution strategies rather than the bundler-like atrategy suppleid vua GemVersionResolver. To accomplish this a script author may configure specific configurations and modules (or modules+revisions) to be excluded.
…ruby-gradle#325) For specific cases it might be better to use the standard Gradle resolution strategies rather than the bundler-like atrategy suppleid vua GemVersionResolver. To accomplish this a script author may configure specific configurations and modules (or modules+revisions) to be excluded.
…ruby-gradle#325) For specific cases it might be better to use the standard Gradle resolution strategies rather than the bundler-like strategy supplied via GemVersionResolver. To accomplish this a script author may configure specific configurations and modules (or modules+revisions) to be excluded.
…ruby-gradle#325) For specific cases it might be better to use the standard Gradle resolution strategies rather than the bundler-like strategy supplied via GemVersionResolver. To accomplish this a script author may configure specific configurations and modules (or modules+revisions) to be excluded.
Backgroud:
I am trying to requires asciidoctor-pdf-cjk-kai_gen_gothic into asciidoc gradle plugin.
Error Message (from jrubyPrepare):
Could not find any matches for rubygems:asciidoctor-pdf:[1.5.0.alpha.8-SNAPSHOT,1.5.99999] as no versions of rubygems:asciidoctor-pdf are available.
Configuration:
It seems like the version resolution algorithm used by jrubyPrepare is not fully compatible with native ruby.
The text was updated successfully, but these errors were encountered: