Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: 3.0.0.GA
    • Fix Version/s: 3.3.0.M4
    • Component/s: build
    • Labels:
      None

      Description

      After JBIDE-3873 it is about time we find time to set:

      Bundle-Require-Execution-Environment

      minimum versions boundaries for dependencies

      (add more if needed)

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            dgolovin Denis Golovin added a comment -

            patch applied with open OSGi version range 3.7.0

            Show
            dgolovin Denis Golovin added a comment - patch applied with open OSGi version range 3.7.0
            Hide
            vpakan Vlado Pakan added a comment -

            Please, how can I get list of plugins which has to have updated MANIFEST.MF

            Show
            vpakan Vlado Pakan added a comment - Please, how can I get list of plugins which has to have updated MANIFEST.MF
            Hide
            dgolovin Denis Golovin added a comment -

            They are the same plugins that has dependency to org.jboss.tools.usage.
            Something like command below should do the trick

            find jbosstools-src/jmx -name *.MF -exec grep -l 'usage' {} \;
            

            Show
            dgolovin Denis Golovin added a comment - They are the same plugins that has dependency to org.jboss.tools.usage. Something like command below should do the trick find jbosstools-src/jmx -name *.MF -exec grep -l 'usage' {} \;
            Hide
            vpakan Vlado Pakan added a comment -

            These plugins have dependency on org.jboss.tools.usage plugin and doesn't have version restriction for org.eclipse.core.runtime plugin:

            org.jboss.tools.modeshape.rest_1.1.0.v20111022-0835-H25-M4
            org.jboss.ide.eclipse.freemarker_1.2.0.v20111022-0834-H30-M4

            org.mozilla.xpcom_1.9.2.16 - is dependent on 'usage' plugin but is not dependent on 'runtime' plugin so probably manifest file is correct?

            Show
            vpakan Vlado Pakan added a comment - These plugins have dependency on org.jboss.tools.usage plugin and doesn't have version restriction for org.eclipse.core.runtime plugin: org.jboss.tools.modeshape.rest_1.1.0.v20111022-0835-H25-M4 org.jboss.ide.eclipse.freemarker_1.2.0.v20111022-0834-H30-M4 org.mozilla.xpcom_1.9.2.16 - is dependent on 'usage' plugin but is not dependent on 'runtime' plugin so probably manifest file is correct?
            Hide
            dgolovin Denis Golovin added a comment -

            org.mozilla.xpcom is fine without this dependency, because it just pure java libraries for JavaXPCOM bridge.
            I've fixed fremarker in trunk.

            modeshape shouldn't have one because this fix is for JBoss Tools Indigo installation from Eclipse Marketplace where modeshape is not present.

            Missing version range in freemarker is not a blocker for M4.
            Resolving.

            Show
            dgolovin Denis Golovin added a comment - org.mozilla.xpcom is fine without this dependency, because it just pure java libraries for JavaXPCOM bridge. I've fixed fremarker in trunk. modeshape shouldn't have one because this fix is for JBoss Tools Indigo installation from Eclipse Marketplace where modeshape is not present. Missing version range in freemarker is not a blocker for M4. Resolving.
            Hide
            dgolovin Denis Golovin added a comment - - edited

            I've added open version range (3.7.0) or org.eclipse.core.runtime in modeshape plugin as well to make it work the same way for normal installation from update site.

            Show
            dgolovin Denis Golovin added a comment - - edited I've added open version range (3.7.0) or org.eclipse.core.runtime in modeshape plugin as well to make it work the same way for normal installation from update site.
            Hide
            vpakan Vlado Pakan added a comment -

            Fix for freemarker plugin is not reason to respin 3.3.0.M4. Verified that fix is commited in trunk so it will be fixed in next version.

            Show
            vpakan Vlado Pakan added a comment - Fix for freemarker plugin is not reason to respin 3.3.0.M4. Verified that fix is commited in trunk so it will be fixed in next version.

              People

              • Assignee:
                dgolovin Denis Golovin
                Reporter:
                maxandersen Max Rydahl Andersen
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development