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

add option to set commands #15

Merged
merged 1 commit into from
Nov 30, 2020
Merged

add option to set commands #15

merged 1 commit into from
Nov 30, 2020

Conversation

jburel
Copy link
Member

@jburel jburel commented Nov 26, 2020

@sbesson
Copy link
Member

sbesson commented Nov 30, 2020

From https://github.com/search?l=YAML&q=org%3Aome+gradlew&type=Code, commands seem to be mostly using one of publishToMavenLocal, build, test . Having some flexibility in the template makes sense.

Does gradle_commands handle the scenario where two targets are invoked e.g.publishToMavenLocal and test?

@jburel
Copy link
Member Author

jburel commented Nov 30, 2020

I have opted to use build by default since it will also run the test command
if you pass publishToMavenLocal test both commands will be run.

https://github.com/jburel/omero-model/actions/runs/385672366 ran for example build and publishToMavenLocal

@sbesson sbesson merged commit 0e853f4 into ome:master Nov 30, 2020
@jburel jburel deleted the gradle_command branch March 22, 2022 10:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants