This repository has been archived by the owner on Jun 19, 2024. It is now read-only.
until we have S2I + ImageStreams working with multi-namespaces, Jenkins pipelines & Arquillian - lets default to kubernetes mode for now - then switch back later #240
Labels
status/stale
Issue/PR considered to be stale
Comments
jstrachan
changed the title
jstrachan
added a commit
to jstrachan/fabric8-maven-plugin
that referenced
this issue
Aug 9, 2016
chirino
added a commit
to chirino/fabric8-maven-plugin
that referenced
this issue
Oct 5, 2016
… auto detection.
chirino
added a commit
to chirino/fabric8-maven-plugin
that referenced
this issue
Oct 5, 2016
apupier
pushed a commit
to apupier/fabric8-maven-plugin
that referenced
this issue
Feb 20, 2018
This works nicely if you don't want to write out a property file with port and host values. Otherwise you need to use the old syntax since when using ${..} the variable name is not preserved because when the property is set then it gets interpolated by maven itself before the plugin gets it. Only when its empty, the property name is injected in which case the plugin can fill it with the dynamically assigned port.
tl;dr : Use ${...} if you don't need to write out port properties in a file.
In a future version we will provide a property mode with writes out all properties with a calculated name so that there is no need to preserve property names.
See also fabric8io#240 for a lengthy discussion on that.
|
This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
then we can switch back to
automode once we can use openshift mode with fabric8-arquillan and the jenkins pipeline libraryso lets set to
kubernetesas a short term measure until we get Arquillian and Jenkins pipelines working withopenshiftmode - then we can switch back toautoas the defaultThe text was updated successfully, but these errors were encountered: