Thanks. Deleting the project would cause the history to be lost. Is
there another solution for this? Thanks.
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 07, 2007 8:58 PM
To: continuum-users@maven.apache.org
Subject: Re: Adding a Maven 2 Project
On 6/7/07, Morgovsky, Alexander (US - Glen Mills)
<[EMAIL PROTECTED]> wrote:
If I add a new Maven 2 project to Continuum 1.0.3 using the SVN POM
location, and the POM for the project is changed in SVN, will Continuum
1.0.3 check out the latest POM?
Try it and see... I doubt it. Even with 1.1
If I add a new Maven 2 project to Continuum 1.0.3 using the SVN POM
location, and the POM for the project is changed in SVN, will Continuum
1.0.3 check out the latest POM? Also, what is the latest stable version
of Continuum? Thank you.
This message (including any attachments) contains confide
Ok, it's weird but, for a project, I can't stop the build process if failure
appears and generate systematically reports even if failure appears
It seems there is no solution for this case except generating 2 pom files with
differents groupId/artifactID !!!
__
Having two projects won't change anything. If it's the same
groupId/artifactId it's considered as the same project by continuum.
I find that a bit weird btw.
Stéphane
On 6/7/07, VILA Jean-Louis <[EMAIL PROTECTED]> wrote:
Thanks for your answer,
But it's not exactly the same case because I've 2
Thanks for your answer,
But it's not exactly the same case because I've 2 different projects with 2
goals. The objective was to avoid the case that you mentioned!!!
Jean-Louis
__
Jean-Louis VILA
SWORD
[EMAIL PROTECTED]
-Message d'origine-
De
Hi all,
I've 2 projects (maven2) with the same configuration except "goals and
profile" : One is for the test (build stops if some failures appear in
test phase), the second is for the report (build not stops even if some
failure appear).
The first is scheduled at 00:00AM and the second at 04:
