jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
Signup
GRECLIPSE
  • GRECLIPSE
  • GRECLIPSE-426

Install size

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.0alpha
  • Fix Version/s: 2.0.0RC1
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

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

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Andrew Eisenberg added a comment - 02/Oct/09 11:20 AM

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.

Show
Andrew Eisenberg added a comment - 02/Oct/09 11:20 AM 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.
Hide
Permalink
Andy Clement added a comment - 13/Oct/09 9:53 PM

we've made a dent, can look to do more for M2. So far:

  • including the sources so we've removed the javadoc jars
  • splitting the compiler levels out into separate features so you don't have to download what you don't want

further work:

  • look at why we have all and not all jars, seems a waste (although I know they currently have different uses).
  • reduce the jdt core patch to be a proper patch and not a replacement if possible.
Show
Andy Clement added a comment - 13/Oct/09 9:53 PM we've made a dent, can look to do more for M2. So far: including the sources so we've removed the javadoc jars splitting the compiler levels out into separate features so you don't have to download what you don't want further work: look at why we have all and not all jars, seems a waste (although I know they currently have different uses). reduce the jdt core patch to be a proper patch and not a replacement if possible.
Hide
Permalink
Andy Clement added a comment - 17/Dec/09 11:52 PM

nothing more planned imminently

Show
Andy Clement added a comment - 17/Dec/09 11:52 PM nothing more planned imminently

People

  • Assignee:
    Andy Clement
    Reporter:
    Andy Clement
Vote (0)
Watch (0)

Dates

  • Created:
    02/Oct/09 10:42 AM
    Updated:
    17/Dec/09 11:52 PM
    Resolved:
    17/Dec/09 11:52 PM
  • Atlassian JIRA (v5.2.7#850-sha1:b2af0c8)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.