-
Notifications
You must be signed in to change notification settings - Fork 18
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
Fix Maven release issues #545
Conversation
…ications, bump version to 0.2.0-SNAPSHOT
…r, fixes jgo import issues
@skalarproduktraum is this expected to fix the missing JAWT issue? I still get that after doing a gradle clean, manually emptying sciview from
|
Yes, this is supposed to fix this error and actually does it for me 😅 Did you purge scenery as well? The jawt-related fix is actually in scenery. |
And yeah, this looks like it. The scenery version in your log (055400) is older than the one used in this PR (de3897c) |
Ok, got it. Repeating what I said in zulip for posterity: i found the issue. i'm using jgo from a conda environment, which puts the jgo path in the conda environment (this is good but i kept looking at the .jgo dir in my home directory). since i was using a snapshot versions of sciview it needed to be manually be removed before the deployment to local maven would overwrite |
This PR fixes some issues related to versions not declared correctly in Maven publications. Furthermore:
gradle.properties
, thecustomVersion
property can be defined. If set togit
, this will lead to jitpack-like behaviour, where the first seven characters of the current git hash are used as version.Command
s discovered by the annotation processor being logged, as well as pom-scijava-managed dependencies