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

mlDeploy with multiple environments #197

Closed
alan-johnson opened this issue May 20, 2017 · 2 comments
Closed

mlDeploy with multiple environments #197

alan-johnson opened this issue May 20, 2017 · 2 comments
Milestone

Comments

@alan-johnson
Copy link

Question about using ml-gradle along with the properties plugin to support different gradle<-environment>.properties . I downloaded the example properties-project which functions fine when setting the -PenvironmentName= setting. However, when using -PenvironmentName=dev along with mlDeploy, the mlHost property doesn't seem to get replaced with the new value in my "gradle-dev.properties" file.

Is this an issue or am I just using -PenvironmentName incorrectly?

@rjrudin
Copy link
Contributor

rjrudin commented May 20, 2017

Ack. Just realized I put the plugins in the wrong order. The properties plugin has to be applied first, then ml-gradle.

I just fixed the proeprties-project example project. I'll get a release of 2.7.1 out over this weekend that fixes the "mlNewProject" task so that it puts the plugins in the right order.

@rjrudin rjrudin modified the milestones: 2.7, 2.7.1 May 20, 2017
@alan-johnson
Copy link
Author

Thanks Rob! I didn't realize from reading the properties plugin README that order was important.

@rjrudin rjrudin closed this as completed May 21, 2017
rjrudin added a commit that referenced this issue Aug 23, 2024
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

No branches or pull requests

2 participants