Andrey Hihlovskiy
Andrey Hihlovskiy
The problem is solved by using additional package in ComponentScan annotation: ``` java @Configuration @ComponentScan(basePackages = {"rs.in.staleksit.foo.web.controller", "rs.in.staleksit.foo.service"}) @EnableWebMvc public class FooWebMvcConfig extends WebMvcConfigurerAdapter { // ... } ```
There was concrete bug: "org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'userController' defined in file...", which is spring-specific, not gradle-specific.
So yes, fix is for both plugins in a sense, that the problem is not related to gradle plugins.
Uhm... Sorry, it was more workaround, not an issue. Explanation: Adding package to the ComponentScan just forces spring "scan this, scan that". The real problem was with Profile annotation, not...
Yes, you are right. Sorry for too quick, too wrong first answer :smile_cat:
I opened new issue: https://github.com/akhikhl/gretty/issues/99
CLA signed and sent to [email protected] and [email protected].
Are you trying to run examples from sources? In order to do so, you need to install Gretty artifacts into some repository - like maven local or your own artifactory....
@Paul-Shaw , @AlekseyMko , @dparish , @isk0001y , @sergey-morenets : I will see to fixing it in Gretty 1.4.2, scheduled for release on 1 of March, 2017.
@jnaalisv , @nikolauskrismer , @sander-adhese , @m4rt , the problem is fixed on "develop" branch of Gretty. I plan to do official release of Gretty 1.4.1 (with the fix) tomorrow,...