Versions Compared

Old Version 6

changes.mady.by.user Keong Lim

Saved on

compared with

New Version 7

changes.mady.by.user Keong Lim

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

DurationAgenda ItemRequested byNotes / Links
START RECORDING

Emergency Maintenance Release - Tag: 3.0.2

  • Final list of projects
  • Testing
  • Readthedocs

Former user (Deleted)

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyTSC-120


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

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2198
, two maven plugins were trialled in AAI using an Eclipse Java Formatter 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.:

Code Block
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














...