I exported Eclipse product without generate p2 repository for windows. When I run it for the first time it was starting very slow about a minute or more.
I removed all unused dependencies.
The product includes native launcher artifacts.
I don't use any arguments when i started application.
What should I do to reduce start-up time?
Related
Recently I've moved to Java Enterprise world. I use Netbeans IDE with Tomcat to develop my webapp. I faced a problem that it takes long time to deploy the webapp. When I change some code, netbeans requires re-deployment to make changes applied.
I did search around this problem and I found JRebel (which helps us apply code change quickly), but it is not free.
Can you tell me how to apply code changes quickly (freely)? And how to reduce deployment time in Netbeans?
Thank you very much,
Khuong Dao.
When IDE compiles gradle project there is java process in memory ( about 250MB).
However launching gradle buld --daemon other daemon java process is launched (about 150MB)
http://i.stack.imgur.com/9SUBd.png
Is there way to connect to Gradle daemon launched by Gradle Tooling APIs from command line.
More info from http://www.nodeclipse.org/projects/gradle
Design differences
Pivotal Gradle IDE uses Gradle Tooling API, see Chapter 62 of User Guide.
This is recommended integration by GradleWare.
In contrast Enide Gradle launches gradle executable similar how you do from command line. (And similar to Enide Maven)
The API is simpler, just as what you see from gradle -h, but of course it will not give access to underlying model as with Tooling API.
Since 0.15 --daemon option is enabled by default see Chapter 19. The Gradle Daemon.
And as Tooling API also uses Gradle Deamon, the performance is similar: i.e. a bit longer first run, second run is faster and optimized.
Read also about incremental builds.
It is possible to reuse the same Gradle daemon process when requesting build from IDE and/or command line. If you see new process created then it is most likely because one of the situations described in http://www.gradle.org/docs/current/userguide/gradle_daemon.html#reusing_daemons happened. You can try to look into daemon log files to see how they were invoked (Java home, args, distribution, ...) and to see why it is not reused. In your image it looks that one daemon uses Gradle 1.10 and the 2nd 1.10.
I am currently writing a site in Spring, Thymeleaf, JBoss and I am using Spring Tool Suite. The turnaround time is horrible. I have to recompile and package the app, every time I make a change and then push it out to the server. How to make my turnaround time quicker?
Try JRebel. You can get it free if you spread some social media love for them.
http://zeroturnaround.com/software/jrebel/
Consider using a tool which supports continuous integration, and which supports working on an exploded war file.
For example, sbt supports that mode. It integrates jetty, and the webapp is restarted, if a source file changes (resources like .html, .css and .jsp do not restart the container).
As for details look here: Eclipse + Tomcat - Serve webapp directly from workspace. This question shows other possibilities as well.
If you use EJB features like session beans, you can split your project. If the EJB and pressentation is kept separate, the turn around times for redeploying EJB ears are acceptable.
Maven is a great addition to Eclipse but why does it take almost 10x as long to debug a Mavenized web service project compared to a similar one not managed with Maven?
For example, I have two Apache CXF projects. One is a Maven project and the other is just a plain Dynamic Web project. Debugging the former via Debug As -> Maven Build using goals: clean package tomcat:run-war or even just clean tomcat:run-war takes about 160 seconds from when I initiate the debug action till when the webservice is ready for invocation. However, debugging the latter via Debug As -> Debug On Server takes only 12 seconds. This is killing any productivity I gained by managing my dependencies using Maven.
I see what Maven is doing each time, but it sure looks like some optimizations can be done to expedite the process, especially if this project has already been built before.
For someone trying, so far in vain, to sell Maven to my superiors, this is a serious impediment. Any suggestions or ideas?
TIA.
I need to run the eclipse FeaturesAndBundlesPublisher application on a linux server. The clumsy way is to download eclipse and put it on the server but since I only need the FeaturesAndBundlesPublisher is there someway of getting that application as a standalone application?
Eclipse itself is a standalone application, though it contains many applications based on different arguments.
If you're unhappy with the big size or base, you can create a .product definition, then export the p2.publisher and its dependencies as a standalone application.