Branch: refs/heads/master

  Home:   https://github.com/jenkinsci/jobConfigHistory-plugin

  Commit: cb04858217f63b3fba4b51d8bf83820ee43553b1

      
https://github.com/jenkinsci/jobConfigHistory-plugin/commit/cb04858217f63b3fba4b51d8bf83820ee43553b1

  Author: René Scheibe <[email protected]>

  Date:   2019-05-02 (Thu, 02 May 2019)



  Changed paths:

    M pom.xml

    M src/main/java/hudson/plugins/jobConfigHistory/ComputerHistoryListener.java

    M src/main/java/hudson/plugins/jobConfigHistory/JobConfigBadgeAction.java

    M src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistory.java

    M src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistoryPurger.java

    M 
src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistorySaveableListener.java

    M 
src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistoryStrategy.java

    M src/main/java/hudson/plugins/jobConfigHistory/PluginUtils.java

    M 
src/test/java/hudson/plugins/jobConfigHistory/JobConfigHistoryBaseActionIT.java

    M 
src/test/java/hudson/plugins/jobConfigHistory/JobConfigHistoryProjectActionTest.java

    M 
src/test/java/hudson/plugins/jobConfigHistory/JobConfigHistoryRootActionIT.java

    M src/test/java/hudson/plugins/jobConfigHistory/PluginIT.java

    R src/test/resources/plugins/maven-plugin.hpi



  Log Message:

  -----------

  Modernize (parent pom and Jenkins) (#87)



Upgrading parent pom to be up-to-date.



Upgrading Jenkins as JCasC requires at least 2.60.3.



Fixing jdepend-maven-plugin version. There is no version 2.9.1. It looks

like this was a copy'n'paste error from maven-javadoc-plugin version.



Setting upper bound version for plugins via <dependencyManagement>

to be compliant with Maven enforcer rules.



Upgrading maven-plugin so that `mvn hpi:run` runs without errors.



Use SpotBugs instead of FindBugs in reporting (see change in parent pom).



Jenkins::getInstance is now annotated with @Nonnull. Therefore removing

the unnecessary null checks that have been detected by SpotBugs.



HtmlUnit removed/changed some methods, adapting tests to compile again.



Plugin "maven-plugin" is not required to be loaded explicitly in a test.

It is loaded automatically because it is defined as dependency in pom.xml.

Therefore just verifying that it is loaded is enough.





-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to