StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>The eclipse builder uses simpler logic than maven, so sometimes the things m2eclipse does are just not enough. I usually keep a shell open to issue simple commands before I run unit tests. depending on your setup, here are some commands that might be helpful.</p> <pre><code>mvn process-resources # This is usually enough when you have # changed something in src/main/resources </code></pre> <p>If you know that the only resource processing needed is maven resource filtering, just call the goal:</p> <pre><code>mvn resources:resources </code></pre> <p>Same for tests:</p> <pre><code>mvn processs-test-resources </code></pre> <p>or</p> <pre><code>mvn resources:test-resources </code></pre> <p>If you need a fuller solution, because perhaps some new code has to be generated etc, then use</p> <pre><code>mvn test-compile # This will through recursion process the following phases: validate initialize generate-sources process-sources generate-resources process-resources compile process-classes generate-test-sources process-test-sources generate-test-resources process-test-resources test-compile </code></pre> <p>So you're getting pretty much everything except the actual unit test execution. Most plugins are smart enough to detect changes and leave unchanged files alone, so mvn <code>test-compile</code> is usually fast enough.</p> <p>If you prefer not to use a shell, you can of course bind any of the above phases / goals to m2eclipse <code>Run as... maven build</code> targets.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload