Can be a dumb question But too curious to know a way or a plugin to do this.
I am triggering a mavenized project build through eclipse as
Run As -> Maven build
So once i done it can it be aborted before it is getting completed ? Like Some times i forgot to change some config so I want to redo . I know how to do it if it is triggered via cmd. But if there is way for this then it would be great ..
The Maven build run should be displayed in the Console view. There should be a toolbar action (red square) in the Console view to terminate the run:
Related
In my current project we have 30+ Maven run configurations.
Are any of you aware of a plugin that contributes a view for Eclipse where I can see all/a selected set of Maven run configurations and run them with a single click?
It is a bit cumbersome to always go to Run -> Run configurations... -> scroll a year and search the required configuration and run it.
Run faviourites are not an options since 1) I have tons of important configurations there already and 2) spamming it with all the required maven configurations would eat all the screen up :-)
Thanks in advance!
One of my colleagues suggested trying the Eclipse Runner plug-in (easy to install through the marketplace).
Simple and perfect for the job, here's a screenshot:
Problem:
After starting ratpack application under netbeans IDE there's no way to stop it.
Steps to reproduce
Checkout project: https://github.com/akhikhl/ratpack-helloworld.git
Start netbeans 7.4 (Gradle Support IDE plugin must be installed)
Open project ratpack-helloworld
Invoke menu command "Run/Run Project" - gradle task starts nicely, app waits on port 5050.
Now try to stop it:
There's no task for stopping ratpack app
Ctrl+Break has no effect
menu command "Run/Stop Buid/Run..." has no effect
when clicking "Cancel Running Task button, IDE asks "Are you sure you want to cancel...", then it reports "Build failure", but run task is still running.
Workaround
Restarting IDE kind of solves the problem, but eliminates fun factor from using ratpack.
Question
Any ideas on how to stop ratpack under netbeans the legitimate way?
You can use the [X] button in the bottom bar to cancel the gradle run task.
Migrating from Worklight Studio 5.0.6 to 6.0
We observe a small, but undesirable, difference in behaviour, or maybe a confiuguration chenge is needed somewhere we failed to find.
In v5.0.6 when one selects an environment and requests Build Environment and Deploy, the project's Builders are first executed. In v6.0 this does not appear to be the case, unless there's a option somewhere ...
The use case is that we have some pre-processing carried out by an ant task installed as a project builder. In v6.0 we now need to rememeber to run a Build Project and then build the environment.
Is there an option to control this behaviour?
this is how to run ant task in worklight 5.0.x - 6.x:
create the Ant file (build.xml):
Navigate to project->properties->Builders->new->Ant Builder. press ok
in "Main" tab set the name for the builder and choose your Ant file (build.xml):
in "Targets" tab choose when to run the Ant file (in this exemple in Auto Build):
press OK
press OK
run "Build All and Deploy":
Success:
This is an open defect in Worklight 6.0.0.x and 6.1.0.x.
There is currently no workaround for it.
Thanks to those info http://www.ralfebert.de/blog/wicket/wicket_eclipse_setup/ and How can I begin using Wicket? now I am able to edit Java code and html files with Eclipse, and run it to get Jetty started.
However there are still two problems which do not allow me to repeatedly run the project:
I have to stop previous run in order to run it again
unlike regular Java project, where I could simply choose "run", now I have to go into "Run Configuration", select Maven Build type, and below select my project to run, and then finally click "run"
ad.1. How to make Eclipse stop the previous run on next run -- i.e. I would like to just run project, and Eclipse should either run it, or stop previous one and run it again
ad.2. how to "bind" Run/Run to running my configuration (Maven Build / my project)?
Thank you in advance for help.
Another simply option is to use a Start class with a main that runs and embedded jetty. Then you will be able to run and debug your application as a normal desktop java application with your IDE.
Check the example start file that comes with the wicket quickstart here:
https://github.com/jordeu/wicket/blob/master/archetypes/quickstart/src/main/resources/archetype-resources/src/test/java/Start.java
I have a set of dependent projects in Eclipse, each with its own Ant build script. If I make a change in multiple projects, then select "Build All" (Ctrl+B), each Ant build is invoked in the correct order. But if there is an error in one project, Eclipse still tries to build the other projects also, and in the process clobbers the Ant console so that the build errors are no longer visible. This wouldn't be quite so annoying if I could open up the offending project and select "Build Project", but Eclipse out-smarts me: it won't rebuild until I open some file in the project, edit it, and save (typically I add and remove a space character wherever my cursor happens to be). An answer to any of the following questions would be welcome.
How can I configure Eclipse to (in preference order):
terminate a "Build All" as soon as any project's Ant build fails?
save all console output for "Build All" instead of resetting the console for each project?
spawn a separate console for each new instance of Ant?
allow me to force a "Build Project" even if it doesn't think anything has changed?
[UPDATE] Bonus Question:
How can I configure Eclipse so that fixing any build errors in a depended-on project counts as a "change" for the purposes of "Build Project"?
Have you tried redirecting standard out to file via a run configuration? A few screen shots to help if not... (you may try 'append' this is not in my screen shot :) )
One alternative is to have each Ant build log itself, e.g., using the following in build.xml
<record name="build.log"
loglevel="verbose"
append="false" />
Oddly, Eclipse seems to disable this logging somehow when running an Ant build.
I am not too big on ant, but can't you make the builds dependent on one another?