Spring Tool Suite
  1. Spring Tool Suite
  2. STS-2347

Using Grails 2.0.0, external jar files are not included in build path

    Details

    • Type: Bug Bug
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.8.1.RELEASE
    • Fix Version/s: 2.9.0.M2
    • Component/s: GRAILS
    • Environment:

      Grails 2.0.0, Groovy 1.8.4, STS v2.8.1 Release
      Windows 7 64-bi

      Description

      After starting a new grails 2.0.0 project (not upgrading my old one) there seems to be no way for any external jars to be added to the project. I have added my jars on the build path (tried adding them as external jars, as native jars and as a part of a user defined library), placed them inside the lib folder and then tried refreshing dependencies. Despite all that, I keep getting compile time errors from missing imports, as it seems that the compiler does not know where to look for the imported packages.

      I face the above issue with Grails v2.0.0 + Groovy v1.8.4 + sts 2.8.1 release.

      Let me add that while using Grails v1.3.7 + Groovy v1.7.10 + sts 2.8.1, I faced no problems with imported jars whatsoever.

        Activity

        Hide
        Kris De Volder (c) added a comment -

        BTW: I closed this as 'won't fix'. I don't think it right to close as 'Works as Designed'. Cache corruption is obviously not a good thing and shouldn't occur. But it would be very hard to figure out what caused the corruption... so 'won't fix'. Unless we see more problems like this...

        Show
        Kris De Volder (c) added a comment - BTW: I closed this as 'won't fix'. I don't think it right to close as 'Works as Designed'. Cache corruption is obviously not a good thing and shouldn't occur. But it would be very hard to figure out what caused the corruption... so 'won't fix'. Unless we see more problems like this...
        Hide
        Christopher Varakliotis added a comment -

        Well, it seems more like a grails issue that has nothing to do with the ide, so there's nothing to fix really... The only thing an ide could do would be to perform some cache cleaning silently every now and then. I did not have the patience to create a project from command line and see what happens though. And since I haven't seen many people complaining about it maybe it's not such big an issue (or maybe grails 2.0 has not undergone enough testing yet)

        Show
        Christopher Varakliotis added a comment - Well, it seems more like a grails issue that has nothing to do with the ide, so there's nothing to fix really... The only thing an ide could do would be to perform some cache cleaning silently every now and then. I did not have the patience to create a project from command line and see what happens though. And since I haven't seen many people complaining about it maybe it's not such big an issue (or maybe grails 2.0 has not undergone enough testing yet)
        Hide
        Kris De Volder (c) added a comment -

        > so there's nothing to fix really.

        Well, there is, if it is a Grails issue, which is what it looks like, we could consider raising a Jira ticket on Grails itself. But... I wouldn't pursue this further at this point. Though I'd reconsider if we see more problems like this.

        Show
        Kris De Volder (c) added a comment - > so there's nothing to fix really. Well, there is, if it is a Grails issue, which is what it looks like, we could consider raising a Jira ticket on Grails itself. But... I wouldn't pursue this further at this point. Though I'd reconsider if we see more problems like this.
        Hide
        Neil Grover added a comment -

        Just a heads up that I've experienced the need to "grails clean" twice under 2.1.0 in order to get my jars on the classpath. I've only added jars twice so in my case it's safe to say that "grails clean" is probably a requirement after adding jars to the project lib folder.

        Show
        Neil Grover added a comment - Just a heads up that I've experienced the need to "grails clean" twice under 2.1.0 in order to get my jars on the classpath. I've only added jars twice so in my case it's safe to say that "grails clean" is probably a requirement after adding jars to the project lib folder.
        Hide
        Christopher Varakliotis added a comment -

        Thanks for the heads up Neil.
        Running a 'clean' prior to building my projects has become a part of my routine now (even under 2.1.0) and everything works like a charm.

        Show
        Christopher Varakliotis added a comment - Thanks for the heads up Neil. Running a 'clean' prior to building my projects has become a part of my routine now (even under 2.1.0) and everything works like a charm.

          People

          • Assignee:
            Kris De Volder (c)
            Reporter:
            Christopher Varakliotis
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              First Response Date: