GRECLIPSE

Create a separate feature / plug-in that just contains the parser

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Duplicate
  • Affects Version/s: 2.0.1Release
  • Fix Version/s: 2.0.2Release
  • Component/s: Build and distribution
  • Labels:
    None
  • Number of attachments :
    0

Description

I have a project for which I'd like to include Groovy support. Not the whole workbench, but just a copy of the language parser. I would like to have a split like that become part of the org. codehaus.groovy pair? e.g. org.codehaus.groovy (a) and org.codehaus.groovy.core (b) where a depends on b?

As a way of an example, I can use JDT as a plug-in without the workbench

Issue Links

is superceded by

Wish - General wishlist item GRECLIPSE-716 Provide headless Groovy-Eclipse feature

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrew Eisenberg added a comment -

Robert,

I am reluctant to package the groovy compiler in a way that is not one of the standard packages that you can download from the groovy distro site. However, there is talk about modularizing the groovy-all jar as described here:

http://docs.codehaus.org/display/GROOVY/Groovy+1.8+modularization

This will be one of the features of Groovy 1.8. Is this breakdown of modules the kind of thing that would solve your problem?

I would definitely consider providing different bundles for each of the modules provided.

Show
Andrew Eisenberg added a comment - Robert, I am reluctant to package the groovy compiler in a way that is not one of the standard packages that you can download from the groovy distro site. However, there is talk about modularizing the groovy-all jar as described here: http://docs.codehaus.org/display/GROOVY/Groovy+1.8+modularization This will be one of the features of Groovy 1.8. Is this breakdown of modules the kind of thing that would solve your problem? I would definitely consider providing different bundles for each of the modules provided.
Hide
Permalink
Robert Konigsberg added a comment -

Yes, I see this comment:

Since we've made Groovy's deliverables be proper OSGi bundles, we need to persue our efforts, and make sure the core modules are also valid OSGi bundles, also marking dependencies between core modules, and external dependencies.

I'm not necessarily interested in some very specific discrete subcompnent, I would be satisfied with a non-UI version of the Groovy plug-in to which I can reference, as long as there's an update site. Anyway, you get the idea, and it sounds like there's already work to move in that direction.

Show
Robert Konigsberg added a comment - Yes, I see this comment: Since we've made Groovy's deliverables be proper OSGi bundles, we need to persue our efforts, and make sure the core modules are also valid OSGi bundles, also marking dependencies between core modules, and external dependencies. I'm not necessarily interested in some very specific discrete subcompnent, I would be satisfied with a non-UI version of the Groovy plug-in to which I can reference, as long as there's an update site. Anyway, you get the idea, and it sounds like there's already work to move in that direction.
Hide
Permalink
Andrew Eisenberg added a comment -

Will work on this once the module system becomes more formalized.

Show
Andrew Eisenberg added a comment - Will work on this once the module system becomes more formalized.
Hide
Permalink
Andrew Eisenberg added a comment -

Will not release a separate feature for the parser only, but I will likely create a headless feature that contains only the non-ui plugins of groovy-eclipse.

Show
Andrew Eisenberg added a comment - Will not release a separate feature for the parser only, but I will likely create a headless feature that contains only the non-ui plugins of groovy-eclipse.

People

  • Assignee:
    Andrew Eisenberg
    Reporter:
    Robert Konigsberg
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: