sorry i meant, it is a new bug
On 4/10/06, dan tran <[EMAIL PROTECTED]> wrote:
>
> If you are using the latest snaphost of release plugin, then it is a bug
>
>
> On 4/10/06, Todd Nine <[EMAIL PROTECTED]> wrote:
> >
> > Sorry, I misspoke in my initial posting, I mean release:perform
> >
> > On 4/10
If you are using the latest snaphost of release plugin, then it is a bug
On 4/10/06, Todd Nine <[EMAIL PROTECTED]> wrote:
>
> Sorry, I misspoke in my initial posting, I mean release:perform
>
> On 4/10/06, dan tran <[EMAIL PROTECTED]> wrote:
> >
> > not sure why release:prepare would trigger a bui
Sorry, I misspoke in my initial posting, I mean release:perform
On 4/10/06, dan tran <[EMAIL PROTECTED]> wrote:
>
> not sure why release:prepare would trigger a build, according to the
> source,
>
> the build only happen in release:perform which has special handling of -
> Dmaven.test.skip.
>
> -D
not sure why release:prepare would trigger a build, according to the source,
the build only happen in release:perform which has special handling of -
Dmaven.test.skip.
-D
On 4/10/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
>
> A quick-n-dirty approach... In your pom.xml, in , add the
> element src
A quick-n-dirty approach... In your pom.xml, in , add the
element src/mytests.
This will override the src/test folder, so no tests will be found, and
thus no tests will be executed.
You should see:
[INFO] [surefire:test]
[INFO] No tests to run.
Make sure you use "mvn clean" first to delete the c
Your solution will definitely do :) but u may need to define a
maven-surefire-plugin inside build/plugins and there you define
true
Thanks & Regards,
A.S.KRISHNAN,
AZTEC, BANGALORE.
-Original Message-
From: Todd Nine [mailto:[EMAIL PROTECTED]
Sent: Monday, April 10, 2006 7:38 PM
To: user
