Debugging 调试模式不适用于STS Eclipse中的jhipster

Debugging 调试模式不适用于STS Eclipse中的jhipster,debugging,spring-boot,breakpoints,jhipster,spring-tool-suite,Debugging,Spring Boot,Breakpoints,Jhipster,Spring Tool Suite,我正在使用JHipster 4.9.0和STS Eclipse 3.9.0(Spring Boot 1.5.7) 问题是我无法调试,因为出现了错误 当我尝试单击“调试为”-->“Spring Boot App”时,我得到以下结果: The Class-Path manifest attribute in C:\Users\user1\.gradle\caches\modules-2\files-2.1\org.liquibase\liquibase-core\3.5.3\f346404c3876

我正在使用JHipster 4.9.0和STS Eclipse 3.9.0(Spring Boot 1.5.7)

问题是我无法调试,因为出现了错误

当我尝试单击“调试为”-->“Spring Boot App”时,我得到以下结果:

The Class-Path manifest attribute in C:\Users\user1\.gradle\caches\modules-2\files-2.1\org.liquibase\liquibase-core\3.5.3\f346404c3876c5bd0e07a7e10b7565bdcd35dbab\liquibase-core-3.5.3.jar referenced one or more files that do not exist: C:\Users\user1\.gradle\caches\modules-2\files-2.1\org.liquibase\liquibase-core\3.5.3\f346404c3876c5bd0e07a7e10b7565bdcd35dbab\lib\snakeyaml-1.13.jar

        ??? ???   ??? ????????? ????????   ??????? ????????? ????????? ????????
        ??? ???   ??? ????????? ????????? ???????? ????????? ????????? ?????????
        ??? ?????????    ???    ????????? ???????     ???    ???????   ?????????
  ???   ??? ?????????    ???    ????????   ???????    ???    ???????   ????????
  ????????? ???   ??? ????????? ???       ????????    ???    ????????? ???  ????
   ???????  ???   ??? ????????? ???       ???????     ???    ????????? ???   ???

:: JHipster ?  :: Running Spring Boot 1.5.7.RELEASE ::
:: http://www.jhipster.tech ::

2017-10-06 15:39:16.338  WARN 8540 --- [  restartedMain] c.c.c.ConfigServicePropertySourceLocator : Could not locate PropertySource: I/O error on GET request for "http://localhost:8761/config/prosopografia/dev/master": Connection refused: connect; nested exception is java.net.ConnectException: Connection refused: connect
2017-10-06 15:39:16.366  INFO 8540 --- [  restartedMain] a.g.i.prosopografia.ProsopografiaApp     : The following profiles are active: swagger,dev
2017-10-06 15:39:22.246  INFO 8540 --- [  restartedMain] a.g.i.p.config.WebConfigurer             : Web application configuration, using profiles: swagger
2017-10-06 15:39:22.251  INFO 8540 --- [  restartedMain] a.g.i.p.config.WebConfigurer             : Web application fully configured
2017-10-06 15:39:22.492  WARN 8540 --- [afia-Executor-1] i.g.j.c.liquibase.AsyncSpringLiquibase   : Starting Liquibase asynchronously, your database might not be ready at startup!
2017-10-06 15:39:37.682  WARN 8540 --- [  restartedMain] ationConfigEmbeddedWebApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'ambitoServiceImpl' defined in file [D:\Desarrollo\prosopografia\bin\a\g\i\prosopografia\service\impl\AmbitoServiceImpl.class]: Unsatisfied dependency expressed through constructor parameter 1; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'a.g.i.prosopografia.service.mapper.AmbitoMapper' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {}
2017-10-06 15:39:37.995 ERROR 8540 --- [  restartedMain] o.s.b.d.LoggingFailureAnalysisReporter   :

***************************
APPLICATION FAILED TO START
***************************

Description:

Parameter 1 of constructor in a.g.i.prosopografia.service.impl.AmbitoServiceImpl required a bean of type 'a.g.i.prosopografia.service.mapper.AmbitoMapper' that could not be found.


Action:

Consider defining a bean of type 'a.g.i.prosopografia.service.mapper.AmbitoMapper' in your configuration.
如果我运行命令“gradlew”或“gradletasks”中的任务“bootRun”,它工作得很好,但是我不能调试,因为我不能使用断点


有什么问题吗?

我不使用Eclipse,所以无法使用它,但您可以调试,或者运行应用程序的
main()
作为启动目标,或者使用
gradle bootRun--debug jvm
“有什么问题?”很难说。也许jhipster会为事物的运行方式添加一些渐变魔法,自然STS/eclipse不会意识到在渐变运行中添加了任何额外的魔法。另一种可能的解释是,添加到运行时类路径的测试依赖项会把事情搞砸。这是gradle eclipse集成的一个长期问题,直到最近BuildShip的人员才开始解决这个问题。请看:谢谢Gaël Marziou,这很好用。我不使用Eclipse,所以无法使用它,但您可以调试,或者运行应用程序的
main()
,作为启动目标,或者使用
gradle bootRun--debug jvm
“会有什么问题?”很难说。也许jhipster会为事物的运行方式添加一些渐变魔法,自然STS/eclipse不会意识到在渐变运行中添加了任何额外的魔法。另一种可能的解释是,添加到运行时类路径的测试依赖项会把事情搞砸。这是gradle eclipse集成的一个长期问题,直到最近BuildShip的人员才开始解决这个问题。看:谢谢Gaël Marziou,这很好用