Bug 291669 - investigate providing swt jnlp and jars for JWS apps
Summary: investigate providing swt jnlp and jars for JWS apps
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.6   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-07 15:23 EDT by Grant Gayed CLA
Modified: 2019-09-06 16:09 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Grant Gayed CLA 2009-10-07 15:23:42 EDT
Issues:

- Should eclipse.org provide these for JWS apps to point at, or just to copy and host themselves?
  -> if the former then approval would likely be needed from eclipse.org, as there could be an increase in bandwidth usage

- How to update these for new releases?
  -> hopefully not manually
Comment 1 Christopher Deckers CLA 2009-10-07 16:11:53 EDT
I don't know what to think about this enhancement. It seems good to have a hosted version of SWT somewhere, but in practice:
- Users may not want the latest SWT. They may want specific versions so all versions have to be provided.
- Sometimes a fix is required for a specific OS and the JAR would have to be of a different version only for that one.

I think a practical hosted approach would be to have all the SWT JARs of all versions made available (including a "latest"). Then users would link to these JARs from their JNLP. Of course, we would need a reliable example in which we would just change the URLs to the JARs that we want.
This could also help desktop apps, because when JARs are not shipped it would be easier to just give a link to the JAR of interest for supported platforms rather than the full archive.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:09:28 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.