-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
che-developer-workflow
This is a issue that could be splitted into several subtasks:
- choose short names for profiles or properties
CHE-234 - rethink what should be built by default or not according to what developers usually need
- create a 'CI' profile which is not the default (default is the developer environment)
- do not co and rebuild a new che by default. use nexus if not found locally
CHE-223 - be able to skip build components
CHE-241 - avoid the usage of the invoker (maven in maven)
CHE-247 - if using invoker, be able to have custom maven build option without modifying git managed files
- do not make overkill checking (for instance branch name of che-base needs to be specify if not using openshift-connector branch)
- SCM and build should be decoupled as much as possible
- use a maven bom
- how to generate a docker image for the developer to be used in minishift
- use classifier for different assembly flavour
- do not duplicate nor patch code from upstream: try to reuse code