Skip to content

Commit

Permalink
Remove antisamy-markup-formatter version, it is now part of BOM.
Browse files Browse the repository at this point in the history
  • Loading branch information
@uhafner
uhafner committed Feb 13, 2022
1 parent e19f6f4 commit 0ce8853
Showing 1 changed file with 0 additions and 2 deletions.
2 changes: 0 additions & 2 deletions pom.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,6 @@
<plugin-util-api.version>2.13.0</plugin-util-api.version>
<bootstrap5-api.version>5.1.3-4</bootstrap5-api.version>
<font-awesome-api.version>5.15.4-5</font-awesome-api.version>
<antisamy-markup-formatter.version>136.v94fb_413c7721</antisamy-markup-formatter.version>
<jsoup.version>1.14.3</jsoup.version>
</properties>

Expand Down Expand Up @@ -64,7 +63,6 @@
<dependency>
<groupId>org.jenkins-ci.plugins</groupId>
<artifactId>antisamy-markup-formatter</artifactId>
<version>${antisamy-markup-formatter.version}</version>
</dependency>
<dependency>
<groupId>org.jsoup</groupId>
Expand Down

2 comments on commit 0ce8853

@woscostametaxa
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I couldnt find something to report bugs to, but appearently this breaks loading the prism API because OWASP Markup Formatter plugin is too old ):
Failed to load: Prism API Plugin (1.26.0-1)

  • Update required: OWASP Markup Formatter Plugin (2.7) to be updated to 136.v94fb_413c7721 or higher

From the log Some plugins could not be loaded due to unsatisfied dependencies. Fix these issues and restart Jenkins to re-enable these plugins.

Dependency errors:

Prism API Plugin (1.26.0-1)
Update required: OWASP Markup Formatter Plugin (2.7) to be updated to 136.v94fb_413c7721 or higher
Some of the above failures also result in additional indirectly dependent plugins not being able to load.

Indirectly dependent plugins:

Warnings Next Generation Plugin (9.11.0)
Failed to load: Prism API Plugin (1.26.0-1)

(we use only jenkins lts in hope of not breaking the server. [Jenkins 2.319.3] and I presume removal of this somewhat thinks the OWASP is in the Jenkins core?

Again - without the ability to add issues I thought I paste it here.

@uhafner
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I already fixed that with the commit that you are commenting: 1.26.0-2 is the latest version.

Please sign in to comment.