odo-devfiles / registry Goto Github PK

We should have a README.md (something super short) in each devfile folder so that we can reference it from examples on how to use them, etc.

Seems that each push downloads the full dependencies and does not use the m2 volume.
I noticed that other devfile (quarkus, springboot) needs to set the Maven repository path on each mvn command

Spring Boot is shortened to spring-boot in Spring's own projects, the Maven plugin, etc. Elsewhere we use spring-boot too, but the devfile name is java-springboot. We should rename the devfile to java-spring-boot for consistency.

To avoid failure on odo master test code We are going to add CI validation (travis and prow) CI for this repo. Travis is for running registry test on 3.11 and prow will be responsible for running the same test on the latest OCP version.

• Configure travis
• Configure prow
• Test flow (As described in redhat-developer/odo#3378 (comment))