I am starting with micronaut framework and intellj idea
In other proyects when i save a chance in the source Code, the debugging app auto update.
But when i do It in micronaut project i need stop and restart for achieve get the Code
It s very slow cicle, any solución?
Related
I have written a subclass of Jetty's WebAppClassLoader. I wrote a context XML file to configure the web app context with my classloader, enabled the ext module, and added my classloaders to $JETTY_BASE/lib/ext. This all works when I run my program outside of IntelliJ.
What I need to do though is run my program within IntelliJ. I have it working with the Jetty maven plugin, but this is not ideal because it forces the maven build to run each time I want to start the program which is quite slow.
As far as I can tell the only thing preventing this from working is that I can see no way to tell Jetty about my context XML file when I run it through the IntelliJ Jetty Run/Debug configuration.
Is there a way around this problem?
I just set up JRebel to use with my Spring web app in IntelliJ, and was very surprised to learn that I have to manually rebuild the project/recompile every time I want my changes to be reflected. Doesn't this defeat the whole purpose of JRebel? Is there something I'm missing here? With Eclipse it was nearly instant, make changes anywhere, save, instantly reflected in running app. With IntelliJ the process seems very clunky. Am I missing something here?
Running with JRebel in IntelliJ involves starting your application using Run > Run with JRebel and when you change your application code you have to build the project in order for IntelliJ to compile classes and update your application.
You can do this by running SHIFT + F9 or Build > Build Project
From the JRebel docs:
JRebel relies upon your IDE to do the compiling. JRebel reloads your compiled .class files and not your .java files. When you change code, JRebel pushes the changed classes and resources to the server without redeploying.
Regardless of what IDE you use, JRebel still needs the IDE to compile the classes before it can update the running application. IntelliJ is no different to Eclipse in this regard. Perhaps Eclipse was just auto building the project without you being aware of it. You can also instruct IntelliJ to auto build from Preferences > Build, Execution, Deployment > Compiler > Build project automatically.
Here's a screenshot showing that configuration setting:
I have created a Spring Boot Microservice using IntelliJ-Idea and Gradle as the build engine. I have made no changes to the initial Spring Boot configuration. I also have made no modifications to the build.gradle file provided. I built the application using starter.spring.io through IntelliJ-Idea and have the following dependencies:
compile('org.springframework.boot:spring-boot-starter-data-jpa')
compile('org.springframework.boot:spring-boot-devtools')
compile('org.springframework.boot:spring-boot-starter-web')
runtime('org.postgresql:postgresql')
testCompile('org.springframework.boot:spring-boot-starter-test')
The application currently contains 12 classes and 2 interfaces and is a Web Service provider. It runs fine on my system but when I build with Gradle, the Manifest.MF contains no Main-Class entry.
I created a very simple Hello World app and tried several combinations of IDE’s and build tools(Gradle and Maven)
and got the following results:
Interestingly, I was able to produce executable jars in Eclipse which has a separate Runnable JAR Export process.
I'm fairly new to IntelliJ and Gradle. Has anyone see this behavior before? Any ideas what I might be doing wrong in IntelliJ? I have my Hello World project zipped up if anyone needs it.
I took the advise of M. Denium and I did the Gradle build from the Command Line. The jars created were formatted correctly to be executable. Everything worked like a charm. In fact the Main-Class is a Spring Boot class called org.springframework.boot.loader.JarLauncher and the main class for my app was in a property called Start-Class. The IDE totally misses this.
Looks like you will need to include spring boot plugin for gradle - org.springframework.boot:spring-boot-gradle-plugin
More details in the gradle section of the getting started guide
I use JProfiler 8.1.4 and I have it integrated with IntelliJ IDEA 14.1.3.
I have a JProfiler session for profiling JBoss using the standalone_jprofiler.bat script like this:
Now, when I want to go to the source code for some method, JProfiler uses a (minimal) internal file viewer instead of using IntelliJ.
I would assume that the source code linking works fine when the profiling is initiated by the IntelliJ plugin, but in my case I don't know what run configuration to create in IntelliJ for standalone_jprofiler.bat.
So finally, my question is: Is it possible to see the code in IntelliJ when the profiling is initiated from the standalone JProfiler application?
One more piece of information: In this case I want the profiling to be activated immediately on startup.
I apologize in advance if this is too simple or silly. I've used JProfiler for just one day and googling didn't yield any relevant answers.
Is it possible to see the code in IntelliJ when the profiling is initiated from the standalone JProfiler application
No, that is not possible, you have to start the profiling session from IDEA to get source code navigation in the IDE.
Another possibility is to save a snapshot in JProfiler and open that snapshot in IDEA (via File->Open File). If the JProfiler plugin is installed in IDEA, the snapshot will then be opened with source code navigation in the IDE.
I am currently unable to debug an application that uses gradle + dropwizard from IntelliJ IDEA
I imported the project using the JetGradle plugin and I am launching the "run" task in debug mode from the plugin itself.
I am using this sample project:
https://github.com/quad/dropwizard-gradle
The project actually runs but the breakpoints are never hit.
Anything I may be missing that prevents me from debugging this simple app from IntelliJ ?
There could be many reasons why the debugger isn't stopping at a breakpoint, and from your description it's unclear if the problem is related to (Jet)Gradle. That said, the JetGradle plugin in IDEA 12 is very limited, and I recommend to use Gradle's idea plugin instead. Alternatively, try an early access preview of IDEA 13, which has a much improved Gradle integration.