You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@isis.apache.org by Dan Haywood <da...@haywood-associates.co.uk> on 2019/04/03 10:18:59 UTC
Re: Migrating to IntelliJ 2018.3 from IntelliJ 2017.1.4
Not sure. I've been using intellij 2018 all year without any problems, so
the issue is somewhere in your setup I suppose.
I use mvn to enhance, and also run using org.apache.isis.Webserver. The
enhance.txt script looks fine, but in the launch.txt I see that there's a
groovy hotswap agent of some sort, perhaps this is the issue?
I also notice that you are running using a different WebServer (
com.sprobe.iaoy.boot.webapp.WebServer). Is this just your own subclass of
o.a.i.WebServer?
On Fri, 22 Mar 2019, 03:53 Paul Benedict Jabines, <ja...@sprobe.com>
wrote:
> Hi everyone,
>
>
>
> An IllegalStateException is thrown saying ‘*Non-enhanced
> @PersistenceCapable classes found’*. However, this was ran in IntelliJ
> 2018.3. In IntelliJ 2017.1.4, there is *no problem* like this.
>
>
>
> Attached herewith is the gradle enhance classes and the exception
> stacktrace when launching web server using the IntelliJ 2018.3.
>
>
>
> My hypothesis is:
>
> 1. When running the Application in IntelliJ 2018.3, there is a *shorten
> command line *field. I wonder this has something to do with the
> exception.
>
>
>
> Hoping someone will help with my problem.
>
>
>
> Thanks,
>
> Paul
>
>
>