Prototype, Scriptaculous, DWR and YUI are all listed in the system-webresources-plugin.xml. I believe this should make them all avaliable via the "resources". Do you mean that a plugin author would like to only include e.g. effects.js without e.g. dragdrop.js?

If so, isn't there some dependency between these files? I am afraid that if we split them up we will then have to remember to include the dependencies each time. Also, what are we winning by splitting them up? Once they are cached on the browser side, they should never be redownloaded?

At the moment we are too chicken to ship with *-min, as all of development and testing gets done with the regular files. What is your experience with switching over to min files?

Cheers,
Anton

1. There is usually no dependency between including the various files of the javascript libraries – you are encouraged to just include the specific files you need. Based on what you try to do with the library, a particular effect may require multiple sub-files (say effects.js & dragdrop.js, but that's something to work out in development).

2. As for remembering, there is no reason why we shouldn't have several web-resource entries: one that includes everything from the library, one for each bundle of files we need for a particular effect, and then one for each individual file, so that plugin developers can request just the additional ones they need. For example, in the labels plugin I needed YUI, and someone was already including it on the page. However, they weren't using the connection.js, which I needed, and it wasn't even in the webresources xml. So that meant I had to bundle my own copy of YUI and reference that.

3. I've used *-min versions of scriptaculous and YUI in my personal projects and it has worked flawlessly, with a huge savings in download time,

In JIRA 3.11 we will ship the min versions of the files.

I will see if we can split up the dependencies for JIRA 3.12. I think Scott was looking into this.

Cheers,
Anton