[JIRA] (JENKINS-61094) Reformatting Jenkins plugin source code

sbuhary@veracode.com (JIRA)

unread,

Feb 14, 2020, 5:45:03 AM2/14/20

to jenkinsc...@googlegroups.com

Shihaaz Buhary started work on

Change By:	Shihaaz Buhary
Status:	Open In Progress

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

sbuhary@veracode.com (JIRA)

unread,

Feb 14, 2020, 5:45:03 AM2/14/20

to jenkinsc...@googlegroups.com

Shihaaz Buhary created an issue

Jenkins /

JENKINS-61094

Reformatting Jenkins plugin source code

Issue Type:	Improvement
Assignee:	Shihaaz Buhary
Components:	veracode-scan-plugin
Created:	2020-02-14 10:44
Priority:	Minor
Reporter:	Shihaaz Buhary

Our existing Jenkins plugin source code does not follow proper formatting. We need to properly format the code.

Add Comment

mark.earl.waite@gmail.com (JIRA)

unread,

Feb 16, 2020, 8:28:05 PM2/16/20

to jenkinsc...@googlegroups.com

Mark Waite commented on

JENKINS-61094

Re: Reformatting Jenkins plugin source code

I've found that the maven fmt plugin will enforce formatting of Java source code if you prefer rigorously maintained source code formatting. See the platformlabeler-plugin for an example pom file that enforce formatting of Java source files and the pom file.

Enforced formatting involves compromises that may not be acceptable to your team. It takes some work to make it operate reasonably with IDE's. It may cause anguish and complaining from team members that disagree with the formatting choices of the automatic formatter.