Details

    • Type: New Feature New Feature
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Complete
    • Affects Version/s: None
    • Fix Version/s: 2.7.0.M1
    • Component/s: None
    • Labels:
      None

      Activity

      Hide
      Davide Cavestro added a comment - - edited

      @Kris
      Finally I had some time to prepare a test case for wtp integration.
      The attached archive migrationtest.zip contains one library and two wtp projects.
      My goals was providing examples for:

      • gradle support for development of a web application (coreapp)
      • customizing the former web application through a new one (customapp)
      • being able to develop customapp without the need to have the coreapp sources (hence using the dependency manager)
      • providing the developer the possibility to install on its local maven cache its refactorings

      I noticed some issues, but they may be my fault:

      • I had to provide a settings.gradle configuration file cause it is needed to resolve deps between projects at the gradle side, but in certain phases its entries have to be commented cause it makes the ide throw tantrum (now I really don't remember in which case, but I can try to reproduce it)
      • I had to add the dependency to a server runtime cause adding provided deps to servlet and jsp api, eclipse publishes them into the webapp hence leading to problems with jstl (see http://forum.springsource.org/showthread.php?87691-Petclinic-Unable-to-read-TLD-quot-META-INF-c.tld-quot&p=314641#post314641) while without the deps, the validation of tags complains "HttpServletRequest cannot be resolved to a type".
      • I had to introduce into customapp a linked folder that points to coreapp and map it as a depoyment assembly, cause I've not found other ways to let STS merge coreapp war contents with customapp ones (and make them available even for code completion and validation)

      So in order to use the example you should

      Further discussions:

      Hope it could be a good starting point. Please give it a look and ask me for every missing detail.

      Show
      Davide Cavestro added a comment - - edited @Kris Finally I had some time to prepare a test case for wtp integration. The attached archive migrationtest.zip contains one library and two wtp projects. My goals was providing examples for: gradle support for development of a web application ( coreapp ) customizing the former web application through a new one ( customapp ) being able to develop customapp without the need to have the coreapp sources (hence using the dependency manager) providing the developer the possibility to install on its local maven cache its refactorings I noticed some issues, but they may be my fault: I had to provide a settings.gradle configuration file cause it is needed to resolve deps between projects at the gradle side, but in certain phases its entries have to be commented cause it makes the ide throw tantrum (now I really don't remember in which case, but I can try to reproduce it) I had to add the dependency to a server runtime cause adding provided deps to servlet and jsp api, eclipse publishes them into the webapp hence leading to problems with jstl (see http://forum.springsource.org/showthread.php?87691-Petclinic-Unable-to-read-TLD-quot-META-INF-c.tld-quot&p=314641#post314641 ) while without the deps, the validation of tags complains "HttpServletRequest cannot be resolved to a type". I had to introduce into customapp a linked folder that points to coreapp and map it as a depoyment assembly, cause I've not found other ways to let STS merge coreapp war contents with customapp ones (and make them available even for code completion and validation) So in order to use the example you should decompress the archive import the projects run gradle install to cache the assembled artifacts run the coreapp and customapp projects on a local server. Their contents should be available respectively at http://localhost:8080/coreapp/core/ and http://localhost:8080/customapp/custom/ . Further discussions: About electing a local gradle project to satisfy other projects deps Project deps without multiproject Hope it could be a good starting point. Please give it a look and ask me for every missing detail.
      Hide
      Kris De Volder (c) added a comment -

      Hi Davide, that sounds great. Could you do me a favor and make this into a separate and focussed Jira?

      This Jira is too vague and open ended, and its already closed. I think your test project and the requirements it entails deserves to be an issue of its own.

      Thanks,

      Kris

      Show
      Kris De Volder (c) added a comment - Hi Davide, that sounds great. Could you do me a favor and make this into a separate and focussed Jira? This Jira is too vague and open ended, and its already closed. I think your test project and the requirements it entails deserves to be an issue of its own. Thanks, Kris
      Hide
      Davide Cavestro added a comment -

      Hi Kris,
      I've just created STS-2065 with a naive cut-and-paste (sorry).

      Talk to you soon
      Davide

      Show
      Davide Cavestro added a comment - Hi Kris, I've just created STS-2065 with a naive cut-and-paste (sorry). Talk to you soon Davide
      Hide
      Suminda Dharmasena added a comment -

      Is it possible to make gradle builds non blocking on the IDE. There are a lot of other operation/tasks that can be done without the need to wait for the build to finish

      Show
      Suminda Dharmasena added a comment - Is it possible to make gradle builds non blocking on the IDE. There are a lot of other operation/tasks that can be done without the need to wait for the build to finish
      Hide
      Mauro Molinari added a comment -

      Suminda, please see (and vote for) issue STS-2284.

      Show
      Mauro Molinari added a comment - Suminda, please see (and vote for) issue STS-2284 .

        People

        • Assignee:
          Kris De Volder (c)
          Reporter:
          Christian Dupuis
        • Votes:
          88 Vote for this issue
          Watchers:
          47 Start watching this issue

          Dates

          • Created:
            Updated:
            Resolved:
            First Response Date: