Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move /lib/test taglib here from core #473

Open
jglick opened this issue Dec 21, 2022 · 2 comments
Open

Move /lib/test taglib here from core #473

jglick opened this issue Dec 21, 2022 · 2 comments

Comments

@jglick
Copy link
Member

jglick commented Dec 21, 2022

I noticed a taglib in core sources https://github.com/jenkinsci/jenkins/blob/e7b46e917cef7273638a4c00cbfa88911c305a19/core/src/main/resources/lib/test/bar.jelly#L26 apparently forgotten during the junit plugin split. https://github.com/search?q=org%3Ajenkinsci+%22%2Flib%2Ftest%22&type=code shows it being used here from core

<j:jelly xmlns:j="jelly:core" xmlns:st="jelly:stapler" xmlns:d="jelly:define" xmlns:l="/lib/layout" xmlns:t="/lib/hudson" xmlns:f="/lib/form" xmlns:test="/lib/test">
<l:layout title="${it.run} ${it.displayName}">
<st:include page="sidepanel.jelly" />
<l:main-panel>
<h1><st:out value="${it.title}" /></h1>
<j:set var="prev" value="${it.previousResult}" />
<test:bar />
yet it is also used in various other plugins like

as well as some taglib imports not apparently used like

Not to be confused with https://github.com/jenkinsci/junit-plugin/blob/000693f1f36ea33a48a974d330f718cebf7044d3/src/main/resources/lib/hudson/test which was moved during the split.

@uhafner
Copy link
Member

uhafner commented Dec 22, 2022

Yes, I noticed this as well while reviewing the styling changes in jenkinsci/jenkins#6728.

Rather than moving the tag I would suggest to restyle/rewrite the whole widget so that it would also reuse the current theme colors (green vs. blue).

@jglick
Copy link
Member Author

jglick commented Dec 22, 2022

restyle/rewrite the whole widget

Sounds fine as a later step. I was just hoping it would be possible to physically move sources to this plugin, where they seem to belong, without breaking compatibility for this or other plugins—at least assuming that the user accepts a junit update prior to accepting a core update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants