Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.0alpha
-
Fix Version/s: 2.0.0RC1
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
Christian observed the groovy plugin being a large download. We should not ignore this problem.
I'm going to delete the javadoc from the 1.7 plugin (to save 8meg).
We should look at whether we can ship the JDT patch as a proper small patch - or does it have to be so large because it now applies to 3.5 and 3.5.1?
Shame we have to ship XXX.jar and XXX-all.jar.
Activity
Andy Clement
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 2.0.0m2 [ 15562 ] | |
| Assignee | James E. Ervin [ jervin ] | Andy Clement [ aclement ] |
| Fix Version/s | 2.0.0m1 [ 15311 ] |
Andy Clement
made changes -
| Fix Version/s | 2.0.0RC1 [ 15956 ] | |
| Fix Version/s | 2.0.0m2 [ 15562 ] |
Andy Clement
made changes -
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
Another possibility would be to separate out the jar files like jline, ivy, asm, etc into their own plugin. Both groovy plugins use the same versions of these jars, so we can save a few Mb there (granted, it's only 1 or 2 Mb, but it's something).
The Groovy 16 jar is optional, so not downloading that could save some space.
As for making the JDT patch smaller, this could be tricky because of changes between 3.5.0 and 3.5.1. Also, we would need to set up our workspaces and SVN so that only the patched files are in the jdt.core project.