Hi John,
On 12/20/06, John Casey <[EMAIL PROTECTED]> wrote:
I switched to using a testing version of the plugin (which BTW is only
resolvable ever in the repo created during the integration testing phase) so
the ITs themselves wouldn't have to:
a. adjust to new plugin versions in order to run
b. rely on metadata resolution for the plugin version, which can lead to
using an incorrect version of the plugin
The previous tests that were done using the embedded didn't had to
specify a plugin version at all, and they just loaded the current
version directly from the target folder without using the installed
jar... isn't that better? I am wrong or there is actually support to
run unpacked plugins in embedder?
The only drawback was that the version of the embedder I was using
didn't support multiproject builds, but this should be fixed in the
refactoring by jason-not sure if it can be used in a plugin that
depends on maven 2.0)
I guess I don't understand why everyone's nervous about this?
not sure what went wrong, but look at these:
http://www.nabble.com/Maven-eclipse-plugin-error-tf2692962.html#a7509615
http://jira.codehaus.org/browse/MECLIPSE-192
(and btw, I also had problem in running the eclipse plugin on my
enviroment after running tests once... looks like the -test version is
not really circumvented to the test repo)
fabrizio
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
