Skip to content

Avoid using MAVEN_OPTS as a command line argument #5986

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Dec 6, 2019
Merged

Avoid using MAVEN_OPTS as a command line argument #5986

merged 1 commit into from
Dec 6, 2019
+1 −1

Conversation

gastaldi
Copy link
Contributor

@gastaldi gastaldi commented Dec 6, 2019

No description provided.

@gastaldi gastaldi requested a review from gsmet December 6, 2019 13:58
@gsmet gsmet added the triage/waiting-for-ci Ready to merge when CI successfully finishes label Dec 6, 2019
@gastaldi gastaldi added this to the 1.1.0 milestone Dec 6, 2019
@gastaldi gastaldi changed the title Do not use MAVEN_OPTS while building the gradle project Avoid using MAVEN_OPTS as a command line argument Dec 6, 2019
@gastaldi gastaldi merged commit 91ca4ad into quarkusio:master Dec 6, 2019
@gastaldi gastaldi deleted the gradle branch December 6, 2019 21:55
@gastaldi
Copy link
Contributor Author

gastaldi commented Dec 6, 2019

@gsmet now it works. Don't forget to add -Dmaven.repo.local=... to your local MAVEN_OPTS if you want to use a different local repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@gsmet gsmet gsmet approved these changes

Assignees

No one assigned

Labels

triage/waiting-for-ci Ready to merge when CI successfully finishes

Projects

None yet

Milestone

1.1.0.CR1

Development

Successfully merging this pull request may close these issues.

2 participants

@gastaldi @gsmet