On 16 September 2015 at 12:07, Johan Corveleyn <jcor...@gmail.com> wrote: > On Wed, Sep 16, 2015 at 11:59 AM, Ivan Zhakov <i...@visualsvn.com> wrote: >> On 16 September 2015 at 11:32, Stefan Hett <ste...@egosoft.com> wrote: >>> Hi, >>>>> >>>>> Speaking about Ivan's suggested monospace-renderer-plugin and the concern >>>>> that it might break with a future version of JIRA: My experience with >>>>> JIRA >>>>> (which dates back to around 2005 I guess) is that Atlassian is quite >>>>> reluctant with introducing changes which break plugins. So it's quite >>>>> rare >>>>> that that a plugin which works in 6.0 breaks during the 6.x releases. >>>>> Things >>>>> are slightly different when the major version numbers change, but then >>>>> this >>>>> only happens every 2 years or so. Hence the maintenance work for such a >>>>> plugin should be considered quite low in the general case. >>>>> On the other side Atlassian requires plugin developers to maintain and >>>>> test >>>>> their plugins on a regular basis (so they are still ensured to be >>>>> compatible >>>>> with later versions). >>>>> If that's some concern and there is some help wanted/needed, I'd be >>>>> willing >>>>> to offer Ivan a hand with the maintenance work on his plugin (if that >>>>> would >>>>> help). As a test environment I'd provide my own JIRA instance, so that >>>>> would >>>>> not add much workload to me. >>>>> >>>> Thanks for offering help, but I already have test JIRA instance at my >>>> office that I used for Serf project issues migration. >>>> >>>> Btw do you have any experience in writing JIRA plugins? Writing >>>> monospaced (preformated) text render would be big help. >>> >>> Unfortunately not at all, otherwise I would have offered to do so. >>> While I do have some decent knowledge of Java due to my studies, I haven't >>> been coding in Java for several years now and don't even have a development >>> environment set-up for that. >>> >> I also don't have Java environment, while I developed several plugins >> more then 10 years ago. >> Link to the Atlassian tutorial if ever want to learn it: >> https://developer.atlassian.com/docs/getting-started/set-up-the-atlassian-plugin-sdk-and-build-a-project >> > > I think we're almost there: I don't think we need a custom renderer or > plugin. Apparently, we can get what we want by enclosing everything > coming from bugzilla within: {noformat:nopanel=true} > > That way, we still have the option of using the normal rendering for > new issues (or even editing old issues to move "nicer parts" out of > the noformat block), and only put inside a noformat block the things > which really need to be monospaced. > > See here for an example: > https://issues.apache.org/jira/browse/TST-210?focusedCommentId=14747248&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14747248 > > That's great! I'll update my conversion script to use "{noformat:nopanel=true}" instead of "{noformat}" and ask INFRA team use it for test conversion.
-- Ivan Zhakov
