How to resolve web-resource version conflict if the resources are batched by the context

[ziohimself]

Let's suppose, I have a web-resource, which is included into the atl.general context:

<web-resource key="foo" name="FooBar">
        <dependency>com.atlassian.auiplugin:jquery</dependency>
        <context>atl.general</context>
 
        <resource type="download" name="baz.js" location="js/baz.js">
            <property key="content-type" value="text/javascript"/>
        </resource>
</web-resource>

when I browse into issue navigator, with the atl.general context, the batch file is composed with the following URL:

http://BASE_URL/s/en_USsqeg33-1988229788/6095/3/0b73ce5185d4ccdb3c6eabaf74df100c/_/download/contextbatch/js/jira.navigator.simple,jira.navigator.advanced,jira.view.issue,jira.navigator.kickass,atl.general,jira.global/batch.js

If I make changes to the baz.js file, the URL for the batch, containing the baz.js would be the same, thus resulting in me, seing the cached version of the batch.

Is there any way to resolve this conflict of the batch versions? (Any way, except manually refreshing the page - I can not ask the customers to do this after each plugin update)

Thanks in advance.

[ziohimself · Accepted solution]

We are including our own resources without any context to all the pages. By calling

...
((com.atlassian.plugin.webresource.WebResourceManager
)webResourceManager).requireResource("foo.bar.baztlassian.qux:foo");
...

From within a Servlet Filter Plugin Module's doFilter method.

If anyone would like me to elaborate, please, ask.

[SerhiyO]

We are including our own resources without any context to all the pages. By calling

...
((com.atlassian.plugin.webresource.WebResourceManager
)webResourceManager).requireResource("foo.bar.baztlassian.qux:foo");
...

From within a Servlet Filter Plugin Module's doFilter method.

If anyone would like me to elaborate, please, ask.

[Mark Lapierre]

Was this ever resolved?

[SerhiyO]

We've implemented a workaround for this one.