On Dec 12, 2007, at 9:47 PM, Dan Fabulich wrote:
I tweak the test to add a MAVEN_OPTS environment variable,
including the -Xrunjdwp string. (It would be easy to add some
sugar to Verifier and/or Invoker to make this easier; I didn't want
to go fooling around with the Verifier, so I just
John Casey wrote:
On Dec 12, 2007, at 9:47 PM, Dan Fabulich wrote:
I tweak the test to add a MAVEN_OPTS environment variable, including the
-Xrunjdwp string. (It would be easy to add some sugar to Verifier and/or
Invoker to make this easier; I didn't want to go fooling around with the
]
Sent: Tuesday, December 11, 2007 9:07 PM
To: Maven Developers List
Subject: Re: Invoker vs. Verifier?
John Casey wrote:
What you're seeing as overlap is a mixture of concerns in the invoker
plugin. The verifications beanshell really needs to be migrated out to
some sort
Dan Fabulich wrote:
John Casey wrote:
What you're seeing as overlap is a mixture of concerns in the invoker
plugin. The verifications beanshell really needs to be migrated out to
some sort of proper integration-testing plugin (or, even better, a
plugin that unites invoker and verifier under
First things first. maven-invoker and maven-invoker-plugin are not
separate things. The maven-invoker-plugin uses maven-invoker, but
maven-invoker is meant to be a reusable library, not just a plugin.
Aside from this, there is actually a good reason for running
integration tests using
John Casey wrote:
First things first. maven-invoker and maven-invoker-plugin are not
separate things. The maven-invoker-plugin uses maven-invoker, but
maven-invoker is meant to be a reusable library, not just a plugin.
I find this remark quite confusing... if one is a library, and one is a
On Dec 12, 2007, at 4:18 PM, Dan Fabulich wrote:
John Casey wrote:
First things first. maven-invoker and maven-invoker-plugin are not
separate things. The maven-invoker-plugin uses maven-invoker, but
maven-invoker is meant to be a reusable library, not just a plugin.
I find this remark
John Casey wrote:
Not at all; I mean running the test. In order to run one of these tests
(which are orchestrated by something akin to the maven-verifier from a JUnit
or other java-driven test case), you must run JUnit or whatever, so you can
be sure you have the same options enabled,
What you're seeing as overlap is a mixture of concerns in the invoker
plugin. The verifications beanshell really needs to be migrated out
to some sort of proper integration-testing plugin (or, even better, a
plugin that unites invoker and verifier under a common
configuration...then extend
John Casey wrote:
What you're seeing as overlap is a mixture of concerns in the invoker
plugin. The verifications beanshell really needs to be migrated out to
some sort of proper integration-testing plugin (or, even better, a
plugin that unites invoker and verifier under a common
You forgot the maven-plugin-testing-harness ;-)
-Original Message-
From: Dan Fabulich [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 11, 2007 9:07 PM
To: Maven Developers List
Subject: Re: Invoker vs. Verifier?
John Casey wrote:
What you're seeing as overlap is a mixture
PROTECTED]
Sent: Tuesday, December 11, 2007 9:07 PM
To: Maven Developers List
Subject: Re: Invoker vs. Verifier?
John Casey wrote:
What you're seeing as overlap is a mixture of concerns in the invoker
plugin. The verifications beanshell really needs to be migrated out to
some sort of proper
12 matches
Mail list logo
