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

[error] -Dsbt.log.noformat=true - expected ';' #4006

Closed
Synesso opened this issue Oct 11, 2019 · 10 comments
Closed

[error] -Dsbt.log.noformat=true - expected ';' #4006

Synesso opened this issue Oct 11, 2019 · 10 comments
Labels

Comments

@Synesso
Copy link

Synesso commented Oct 11, 2019

Please provide:

https://jitpack.io/com/github/synesso/scala-stellar-sdk_2.12/0.10.0/build.log

  • Does the project build on your machine with the same commands (e.g. ./gradlew install) ?

No

  • What error are you seeing?
[error] -Dsbt.log.noformat=true
[error]                        ^

The command issued sbt ++2.12.0 -Dsbt.log.noformat=true clean publishM2

should instead be

sbt -Dsbt.log.noformat=true ++2.12.0 clean publishM2

@nightscape
Copy link

Same issue here. @jitpack-io any known workarounds, e.g. is it possible to provide a custom jitpack.yml that is still able to cross-publish?

@nightscape
Copy link

nightscape commented Jan 1, 2020

Temporary (ugly) workaround:

# .jitpack.yml
install:
- sbt `echo $ARTIFACT | sed 's/.*2.11$/++2.11.12/;s/.*2.12$/++2.12.12/;s/.*2.13$/++2.13.4/;/^++[0-9.]\+/! s/.*/++2.13.4/'` publishM2

Note that when you request a module in a multi-module build, the $ARTIFACT will be the name of the module without any version number, and there also isn't any other available environment variable that would let us find out what Scala version was requested (I checked with env), so in that case the last part of the sed expression replaces the entire module name with the version specified at the end of the sed expression.

@derek9gag
Copy link

This is fixed in newer sbt-launcher. It works with 1.3.8. @jitpack-io can we have the sbt launcher package upgraded please?

See: sbt/sbt#3921

@milin-k
Copy link

milin-k commented Jun 23, 2020

Temporary (ugly) workaround:

# jitpack.yml
install:
   - sbt `echo $ARTIFACT | sed 's/.*2.11$/++2.11.12/;s/.*2.12$/++2.12.11/;s/.*2.13$/++2.13.1/'` publishM2

Does this solution work for private repo- I was getting permision issue in jitpack build log

@nightscape
Copy link

@milin-k I don't have any experience with private repos, but imo this should be unrelated.

@nightscape
Copy link

@jitpack-io any chance to fix this?
It's probably a one-line change and currently requires forking every single Scala SBT project I want to use with JitPack...

@nightscape
Copy link

@zt1983811 I think your issue is completely unrelated to this issue.
As far as I can tell, the issue here has been fixed silently 😉

@github-actions
Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Aug 27, 2022
@github-actions
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

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

No branches or pull requests

5 participants