Skip to content
This repository has been archived by the owner on Jun 2, 2023. It is now read-only.

Select Bluemix as default, and mvn install doesn't deploy to Bluemix #113

Open
hughesj opened this issue Dec 14, 2016 · 2 comments
Open

Comments

@hughesj
Copy link

hughesj commented Dec 14, 2016

By checking the flag I should just have to do:

mvn install -Dcf.org=[your email address] -Dcf.username=[your username] -Dcf.password=[your password]

But I don't get a deployment to Bluemix. To do that I had to add on -P bluemix

@katheris
Copy link
Contributor

This is due to the skipTests profile. When you run mvn install -Dcf.org=[your email address] -Dcf.username=[your username] -Dcf.password=[your password] the build system should have activated the Bluemix profile by default. However, as the skipTests profile is activated due to the skipTests flag not being set the Bluemix profile is deactivated. (As profile activated by default are deactivated as soon as another profile is active.)

So the only way to make it work at the moment is to run mvn install -P bluemix or mvn install -DskipTests. We need to fix this.

@katheris
Copy link
Contributor

This has been partially fixed by pull request #121 however it is not the best outcome. The disadvantage of the current behaviour is having to specify -Pbluemix every time you run a build. To get a a better solution we should consider the following:

  • how do we make sure it is easy to enable and disable deploying to Bluemix
    • unfortunately you can't enable and disable profiles using properties set inside the pom file
  • should we include the maven code for deploying to Bluemix even if you don't choose Bluemix

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

No branches or pull requests

2 participants