Announcement Announcement Module
Collapse
No announcement yet.
STS & GGTS 3.6.0.M1 released Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • STS & GGTS 3.6.0.M1 released

    Dear Spring Community,

    I am happy to announce the first milestone release 3.6.0.M1 of the Spring Tool Suite (STS) and the Groovy/Grails Tool Suite (GGTS).

    Highlights from this milestone build include:
    • based on Eclipse Luna 4.4
    • support for Groovy 2.3
    • updated to Grails 2.4
    • updated to tc Server 2.9.6
    • minor improvements to the Gradle tooling
    • bugfixes, including fixes for endless build loops and memory leaks
    To download the distributions, please go visit:Detailed new and noteworthy notes can be found here: STS/GGTS 3.6.0.M1 New & Noteworthy

    NOTE:
    Both tool suites ship on top of the latest Eclipse Luna 4.4 release candidates as 64bit based zip files ONLY.
    We plan to no longer ship installers and 32bit distributions anymore. Update sites will be available for use with
    older Eclipse versions and 32bit installations.

    We are very keen to hear any feedback on this change.

    The 3.6.0 release is scheduled early July 2014 - shortly after the Eclipse Luna release.

    Enjoy!!!
    The tooling team

  • #2
    Thanks for that new version.
    I got it work with my workspace that would do endless builds in 3.5.1!

    Comment


    • #3
      Hey!

      That is great to hear, thanks for letting us know!

      Cheers,
      -Martin

      Comment


      • #4
        Originally posted by Martin Lippert View Post
        Hey!

        That is great to hear, thanks for letting us know!

        Cheers,
        -Martin
        No problem,

        just to let you know the last update of m2e looks broken on 3.6M1.

        m2e - Maven Integration for Eclipse (includes Incubating components) 1.5.0.20140605-0047
        m2e - slf4j over logback logging (Optional) 1.5.0.20140605-0047
        m2e-wtp - Maven Integration for WTP 1.1.0.20140528-2051

        Error

        Errors occurred during the build.
        Error instantiating builder 'org.eclipse.m2e.core.maven2Builder'.
        Plug-in org.eclipse.m2e.core was unable to load class org.eclipse.m2e.core.internal.builder.MavenBuilder .
        An error occurred while automatically activating bundle org.eclipse.m2e.core (1059).
        Plug-in org.eclipse.m2e.core was unable to load class org.eclipse.m2e.core.internal.builder.MavenBuilder .
        An error occurred while automatically activating bundle org.eclipse.m2e.core (1059).
        Error instantiating builder 'org.eclipse.m2e.core.maven2Builder'.
        Plug-in org.eclipse.m2e.core was unable to load class org.eclipse.m2e.core.internal.builder.MavenBuilder .
        An error occurred while automatically activating bundle org.eclipse.m2e.core (1059).
        Plug-in org.eclipse.m2e.core was unable to load class org.eclipse.m2e.core.internal.builder.MavenBuilder .
        An error occurred while automatically activating bundle org.eclipse.m2e.core (1059).
        Error instantiating builder 'org.eclipse.m2e.core.maven2Builder'.
        Plug-in org.eclipse.m2e.core was unable to load class org.eclipse.m2e.core.internal.builder.MavenBuilder .
        An error occurred while automatically activating bundle org.eclipse.m2e.core (1059).
        Plug-in org.eclipse.m2e.core was unable to load class org.eclipse.m2e.core.internal.builder.MavenBuilder .
        An error occurred while automatically activating bundle org.eclipse.m2e.core (1059).
        Error instantiating builder 'org.eclipse.m2e.core.maven2Builder'.
        Plug-in org.eclipse.m2e.core was unable to load class org.eclipse.m2e.core.internal.builder.MavenBuilder .
        An error occurred while automatically activating bundle org.eclipse.m2e.core (1059).
        Plug-in org.eclipse.m2e.core was unable to load class org.eclipse.m2e.core.internal.builder.MavenBuilder .
        An error occurred while automatically activating bundle org.eclipse.m2e.core (1059).
        Error instantiating builder 'org.eclipse.m2e.core.maven2Builder'.
        Plug-in org.eclipse.m2e.core was unable to load class org.eclipse.m2e.core.internal.builder.MavenBuilder .
        An error occurred while automatically activating bundle org.eclipse.m2e.core (1059).
        Plug-in org.eclipse.m2e.core was unable to load class org.eclipse.m2e.core.internal.builder.MavenBuilder .
        An error occurred while automatically activating bundle org.eclipse.m2e.core (1059).
        Error instantiating builder 'org.eclipse.m2e.core.maven2Builder'.
        Plug-in org.eclipse.m2e.core was unable to load class org.eclipse.m2e.core.internal.builder.MavenBuilder .
        An error occurred while automatically activating bundle org.eclipse.m2e.core (1059).
        Plug-in org.eclipse.m2e.core was unable to load class org.eclipse.m2e.core.internal.builder.MavenBuilder .
        An error occurred while automatically activating bundle org.eclipse.m2e.core (1059).
        Error instantiating builder 'org.eclipse.m2e.core.maven2Builder'.
        Plug-in org.eclipse.m2e.core was unable to load class org.eclipse.m2e.core.internal.builder.MavenBuilder .
        An error occurred while automatically activating bundle org.eclipse.m2e.core (1059).
        Plug-in org.eclipse.m2e.core was unable to load class org.eclipse.m2e.core.internal.builder.MavenBuilder .
        An error occurred while automatically activating bundle org.eclipse.m2e.core (1059).

        I tried to revert to previous install but it didn't work for some reason. Had to go back to a fresh install of STS. I didn't have time to look what is the cause...

        Note, I'm running on Windows 8.1, jdk 1.7.0_60

        Nico

        Comment


        • #5
          Hey!

          That looks like a conflict with the underlying Maven runtime packages, maybe there was a conflict with the update. Would be interesting to analyze the broken installation. Do you still have that around?

          Thanks a lot for your help!
          -Martin

          Comment


          • #6
            Originally posted by Martin Lippert View Post
            Hey!

            That looks like a conflict with the underlying Maven runtime packages, maybe there was a conflict with the update. Would be interesting to analyze the broken installation. Do you still have that around?

            Thanks a lot for your help!
            -Martin
            Amazingly, yes I still have the installation.
            Where do you want me to look at?

            Comment


            • #7
              Hey!

              It would be interesting to do the following:
              - open a console view
              - switch it to the OSGi Host Console (in the drop-down menu inside the Console view)
              - type in "ss" and look for a bundle with the name "org.eclipse.m2e.core"
              - what is its status? (INSTALLED, ACTIVE, etc.)
              - and is there a bundle in the state "INSTALLED"? If so, which one?
              - if there is a "INSTALLED" bundle, type "diag " and post the output

              Maybe we can find out what is going wrong here.

              Thanks a lot for your help!
              -Martin

              Comment


              • #8
                hmmm here is the log

                1082 RESOLVED org.eclipse.m2e.archetype.common_1.5.0.20140604-2045
                1083 RESOLVED org.eclipse.m2e.core_1.5.0.20140605-0047
                1084 STARTING org.eclipse.m2e.core.ui_1.5.0.20140605-0047
                1085 INSTALLED org.eclipse.m2e.discovery_1.5.0.20140605-0047
                1086 INSTALLED org.eclipse.m2e.editor_1.5.0.20140605-0047
                1087 INSTALLED org.eclipse.m2e.editor.xml_1.5.0.20140605-0047
                1088 INSTALLED org.eclipse.m2e.jdt_1.5.0.20140605-0047
                1089 INSTALLED org.eclipse.m2e.jdt.ui_1.5.0.20140605-0047
                1090 INSTALLED org.eclipse.m2e.launching_1.5.0.20140605-0047
                1091 INSTALLED org.eclipse.m2e.lifecyclemapping.defaults_1.5.0.20 140605-0047
                1092 RESOLVED org.eclipse.m2e.logback.appender_1.5.0.20140605-0047
                Master=5
                1093 INSTALLED org.eclipse.m2e.logback.configuration_1.5.0.201406 05-0047
                1094 RESOLVED org.eclipse.m2e.maven.indexer_1.5.0.20140604-2045
                1095 RESOLVED org.eclipse.m2e.maven.runtime_1.5.0.20140604-2045
                1096 RESOLVED org.eclipse.m2e.maven.runtime.slf4j.simple_1.5.0.2 0140604-2045
                1097 STARTING org.eclipse.m2e.model.edit_1.5.0.20140605-0047
                1098 STARTING org.eclipse.m2e.profiles.core_1.5.0.20140605-0047
                1099 INSTALLED org.eclipse.m2e.profiles.ui_1.5.0.20140605-0047
                1100 INSTALLED org.eclipse.m2e.refactoring_1.5.0.20140605-0047
                1101 INSTALLED org.eclipse.m2e.scm_1.5.0.20140605-0047
                1102 INSTALLED org.eclipse.m2e.wtp_1.1.0.20140528-2051
                1103 INSTALLED org.eclipse.m2e.wtp.overlay_1.1.0.20140528-2051
                1104 INSTALLED org.eclipse.m2e.wtp.overlay.ui_1.1.0.20140528-2051

                So m2e core is RESOLVED

                In the diag I see that related to m2e

                org.maven.ide.eclipse.ajdt [878]
                Unresolved requirement: Require-Bundle: org.eclipse.m2e.jdt
                -> Bundle-SymbolicName: org.eclipse.m2e.jdt; bundle-version="1.5.0.20140605-0047"; singleton:="true"
                org.eclipse.m2e.jdt [1088]
                Bundle was not resolved because of a uses contraint violation.
                org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.m2e.jdt [osgi.identity; osgi.identity="org.eclipse.m2e.jdt"; type="osgi.bundle"; version:Version="1.5.0.20140605-0047"; singleton:="true"] because it is exposed to package 'org.slf4j.helpers' from resources org.slf4j.api [osgi.identity; osgi.identity="org.slf4j.api"; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"] and slf4j.api [osgi.identity; osgi.identity="slf4j.api"; type="osgi.bundle"; version:Version="1.7.2"] via two dependency chains.

                ...

                Chain 2:
                org.maven.ide.eclipse.ajdt [osgi.identity; osgi.identity="org.maven.ide.eclipse.ajdt"; type="osgi.bundle"; version:Version="0.13.0.201107281640"; singleton:="true"]
                require: (&(osgi.wiring.bundle=org.slf4j.api)(bundle-version>=1.6.1))
                |
                provide: osgi.wiring.bundle; osgi.wiring.bundle="org.slf4j.api"; bundle-version:Version="1.7.2.v20121108-1250"
                org.slf4j.api [osgi.identity; osgi.identity="org.slf4j.api"; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"]
                require: (&(osgi.wiring.bundle=ch.qos.logback.classic)(&(bu ndle-version>=1.0.7)(!(bundle-version>=1.0.8))))
                |
                provide: osgi.wiring.bundle; osgi.wiring.bundle="ch.qos.logback.classic"; bundle-version:Version="1.0.7.v20121108-1250"
                ch.qos.logback.classic [osgi.identity; osgi.identity="ch.qos.logback.classic"; type="osgi.bundle"; version:Version="1.0.7.v20121108-1250"]
                import: (&(osgi.wiring.package=org.slf4j.helpers)(version> =1.7.0))
                |
                export: osgi.wiring.package: org.slf4j.helpers
                slf4j.api [osgi.identity; osgi.identity="slf4j.api"; type="osgi.bundle"; version:Version="1.7.2"]
                org.sonatype.m2e.buildhelper [885]
                Unresolved requirement: Require-Bundle: org.eclipse.m2e.jdt; bundle-version="[1.1.0,2.0.0)"
                -> Bundle-SymbolicName: org.eclipse.m2e.jdt; bundle-version="1.5.0.20140605-0047"; singleton:="true"
                org.eclipse.m2e.jdt [1088]
                Bundle was not resolved because of a uses contraint violation.
                org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.m2e.jdt [osgi.identity; osgi.identity="org.eclipse.m2e.jdt"; type="osgi.bundle"; version:Version="1.5.0.20140605-0047"; singleton:="true"] because it is exposed to package 'org.slf4j.helpers' from resources org.slf4j.api [osgi.identity; osgi.identity="org.slf4j.api"; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"] and slf4j.api [osgi.identity; osgi.identity="slf4j.api"; type="osgi.bundle"; version:Version="1.7.2"] via two dependency chains.

                ...

                Chain 2:
                org.eclipse.m2e.refactoring [osgi.identity; osgi.identity="org.eclipse.m2e.refactoring"; type="osgi.bundle"; version:Version="1.5.0.20140605-0047"; singleton:="true"]
                require: (&(osgi.wiring.bundle=org.slf4j.api)(bundle-version>=1.6.2))
                |
                provide: osgi.wiring.bundle; osgi.wiring.bundle="org.slf4j.api"; bundle-version:Version="1.7.2.v20121108-1250"
                org.slf4j.api [osgi.identity; osgi.identity="org.slf4j.api"; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"]
                require: (&(osgi.wiring.bundle=ch.qos.logback.classic)(&(bu ndle-version>=1.0.7)(!(bundle-version>=1.0.8))))
                |
                provide: osgi.wiring.bundle; osgi.wiring.bundle="ch.qos.logback.classic"; bundle-version:Version="1.0.7.v20121108-1250"
                ch.qos.logback.classic [osgi.identity; osgi.identity="ch.qos.logback.classic"; type="osgi.bundle"; version:Version="1.0.7.v20121108-1250"]
                import: (&(osgi.wiring.package=org.slf4j.helpers)(version> =1.7.0))
                |
                export: osgi.wiring.package: org.slf4j.helpers
                slf4j.api [osgi.identity; osgi.identity="slf4j.api"; type="osgi.bundle"; version:Version="1.7.2"]
                org.eclipse.m2e.scm [1101]
                Bundle was not resolved because of a uses contraint violation.
                org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.m2e.scm [osgi.identity; osgi.identity="org.eclipse.m2e.scm"; type="osgi.bundle"; version:Version="1.5.0.20140605-0047"; singleton:="true"] because it is exposed to package 'org.slf4j.helpers' from resources org.slf4j.api [osgi.identity; osgi.identity="org.slf4j.api"; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"] and slf4j.api [osgi.identity; osgi.identity="slf4j.api"; type="osgi.bundle"; version:Version="1.7.2"] via two dependency chains.


                Is it slf4j conflicts? Not too sure how to read that...


                Thanks!
                Nico

                Comment


                • #9
                  Hey!

                  It looks like there is a bundle called "slf4j.api" installed in your STS (that is causing confusion and conflicts) and I wonder where that one is coming from. As far as I can see there is no such bundle/plugin in the default STS distribution. Did you install additional plugins?

                  -Martin

                  Comment


                  • #10
                    The only one I installed is Subclipse and then the update for m2e.
                    And basically, it's OK till the m2e update.
                    Last edited by NicoTexas; Jun 10th, 2014, 04:59 PM.

                    Comment


                    • #11
                      Hey!

                      I tried to reproduce this problem, but I am not able to get into this situation. I downloaded a fresh copy of STS 3.6.0.M1 on Eclipse 4.4, installed Subclipse from the dashboard, then did the m2e update. But I am not ending up with an installation that contains the "slf4j.api" bundle in addition to the "org.slf4j.api" bundle. There must be another way that this bundle ended up being in your STS. Do you have any idea?

                      -Martin

                      Comment


                      • #12
                        Originally posted by Martin Lippert View Post
                        Hey!

                        I tried to reproduce this problem, but I am not able to get into this situation. I downloaded a fresh copy of STS 3.6.0.M1 on Eclipse 4.4, installed Subclipse from the dashboard, then did the m2e update. But I am not ending up with an installation that contains the "slf4j.api" bundle in addition to the "org.slf4j.api" bundle. There must be another way that this bundle ended up being in your STS. Do you have any idea?

                        -Martin
                        Yes, and I feel bad that I forgot that... I installed SonarQube plugins.
                        I can't believe I missed it . Anyway, strange behavior of Eclispe, or OSGI, there...
                        I guess SonarQube is loading slf4j.api rather than org.slf4j.api, I will report it to them.
                        Thanks again for looking into it.

                        Comment


                        • #13
                          Hey!

                          Yes, it would be good to report this to them and let them know that they should use the version from the Eclipse Orbit project. That should help to avoid this situation. In the end it might not be their fault, but they might be the guys with the easiest solution to this.

                          Thanks!
                          -Martin

                          Comment

                          Working...
                          X