We have some integration tests and prefer to use an embedded Tomcat
instance vs deploying to an external, running server (avoid external dep
problem). The tests are in a separate module than the war module. The
need is to retrieve the built war from the local repo and explode it into
the working
Hi,
If I understood correctly, what I'd do is make a dummy pom with a
maven-dependency-plugin:unpack goal with output directory as the working
directory, then just build that dummy project whenever you want.
Another thing you can do is overlay the .war when building the test
module, or vice versa
Thanks for the suggestions.
I tried the dependency plugin. Works great as a Maven goal. I have not
found a m2e lifecycle mapping for unpack yet; finding some info, so hope to
make it work within the IDE.
Tried this [0] with but only removed the warning of no lifecycle
mapped. Will continue tryi
Fixed.
We also use Spring STS, and, whatever its "Spring STS Maven Support" is, it
was preventing m2e from executing it.
Uninstalling just the STS Maven Support feature magically made it work.
For future googlers, this is the page to read:
http://wiki.eclipse.org/M2E_plugin_execution_not_covered
Did you have 2 m2e installations?
STS includes m2e.
Ron
On 03/11/2012 10:40 AM, Jeff Jensen wrote:
Fixed.
We also use Spring STS, and, whatever its "Spring STS Maven Support" is, it
was preventing m2e from executing it.
Uninstalling just the STS Maven Support feature magically made it work.
F
Yes, that's what I uninstalled, the STS one. Funny there were no
conflicts noticed prior.
And it's weird behavior still - it works at Eclipse start but not on
clean or incremental builds. Restarting Eclipse causes it to work but
then it stops after one build. If I delete its dir and the dep
plu
We never use anything outside Eclipse/STS and do not have any problems
with Maven.
I don't understand why you have m2e installed with STS.
Ron
On 03/11/2012 2:37 PM, Jeff Jensen wrote:
Yes, that's what I uninstalled, the STS one. Funny there were no
conflicts noticed prior.
And it's weird b
It is the STS plugin for Eclipse, not the STS distro. Because m2e has
updated faster than STS releases.
On Sat, Nov 3, 2012 at 8:07 PM, Ron Wheeler
wrote:
> We never use anything outside Eclipse/STS and do not have any problems with
> Maven.
>
> I don't understand why you have m2e installed with
I guess that one of the downsides of having everything nicely packaged
in a working integrated IDE is that I am dependent on Springsource to
determine what versions I have to use.
Currently STS includes an m2e version 1.2.0-20120903 which would seem
to be pretty current if you want to stick wit
