Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

zoom bridge: https://zoom.us/j/283628617

PTL RecordingsZoom Chat Log

Duration 60 minutes

DurationAgenda ItemRequested byNotes / Links
START RECORDING

Emergency Maintenance Release - Tag: 3.0.2

  • Final list of projects
  • Testing
  • Readthedocs

Former user (Deleted)

TSC-120 - Getting issue details... STATUS


M4 Preparation

  • Integration Blockers
  • Risks
  • Projects
  • Requirements
  • oParent Integration
  • Containers Procedure from Inegration/OOM Teams


Please update M4 checklist by April 3rd, 2019 noon - thank you

Former user (Deleted)



Windriver Clean-Up checkpointYang Xu
5minConsistent Java code style using maven plugins

Keong Lim

Regarding instructions under Setting Up Your Development Environment

Instead of starting with Google style and Setting Up Your Development Environment

Suggest using Setting Up Your Development Environment as the ONAP style formatter file is committed to the repo

In AAI-2198 - Getting issue details... STATUS two maven plugins were trialled in AAI using the formatter XML file above, as intended to pass "onap-java-style" checkstyle audit.

Plugins can do batch re-formatting of Java code in the repository and run the audit, e.g.:

mvn formatter:format spotless:apply process-sources

Suggest that the formatter file and plugin config be adopted into oparent for all to share.

Otherwise individual projects can copy the configuration and adopt it for their own local usage as per Setting Up Your Development Environment














  • No labels