fastest way to execute server development cycle?
Hi all,
I'd like to make some code contributions to Subsonic, particularly the server component. Prior to getting started, I was wondering what the fastest way is to execute the classical code/compile/test cycle. Packaging everything up to an installable after every change isn't an option as it pretty much contradicts the notion of fast turnaround times.
So I've already checked out the code and set things up within Eclipse. To my understanding, a Maven install run leads to a WAR file. Am I correct in assuming that in order to see how code changes behave, one would need an application server like Jetty and deploy that WAR file within? As of now, I've been dealing with standalone Java applications only that didn't need any third-party bootstrapping component like Jetty, so the development approach is not perfectly clear to me yet. I am particularly curious whether there's a way to take advantage of Eclipse's debugging capabilities (e.g., breaking at certain locations) in a most productive way when testing a new piece of Subsonic backend code.
Thanks in advance!
I'd like to make some code contributions to Subsonic, particularly the server component. Prior to getting started, I was wondering what the fastest way is to execute the classical code/compile/test cycle. Packaging everything up to an installable after every change isn't an option as it pretty much contradicts the notion of fast turnaround times.
So I've already checked out the code and set things up within Eclipse. To my understanding, a Maven install run leads to a WAR file. Am I correct in assuming that in order to see how code changes behave, one would need an application server like Jetty and deploy that WAR file within? As of now, I've been dealing with standalone Java applications only that didn't need any third-party bootstrapping component like Jetty, so the development approach is not perfectly clear to me yet. I am particularly curious whether there's a way to take advantage of Eclipse's debugging capabilities (e.g., breaking at certain locations) in a most productive way when testing a new piece of Subsonic backend code.
Thanks in advance!