It fails for me
Here is the output I get.
2005-12-16 11:15:35,361 [Thread-1] INFO ContinuumScm
- Checking out project: 'MDS WMS Merger', id: '1' to
'D:\apache\continuum-1.0.2\bin\..\apps\continuum\working-directory\1'.
Working dir:
D:\apache\continuum-1.0.2\bin\..\apps\continuum\working-director
better yet, you can patch and test it, since it seems you have a need for
this.
But putting -o into scm:update will be slow the update process.
-Dan
On 12/15/05, Mordo, Aviran (EXP N-NANNATEK) <[EMAIL PROTECTED]> wrote:
>
> Thank you
>
> -Original Message-
> From: dan tran [mailto:[EMA
Emmanuel Venisse schrieb:
Not yet, it wil be supported in 1.1.
http://jira.codehaus.org/browse/CONTINUUM-44
Emmanuel
Thanks.
--
Christian
no, you can't define the working directory. File an issue.
Emmanuel
Doug Johnson a écrit :
Emmanuel,
No I don't have that file in my working directory. When i moved it to the recommended
directory it does not fail on the build properties but fails to run "ant". The
following files are unde
Thank you
-Original Message-
From: dan tran [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 15, 2005 3:14 PM
To: continuum-users@maven.apache.org
Subject: Re: How to tell continuum to force checkout
in this case, most likely
- user add a file,
- continuum does the build
- us
Emmanuel,
No I don't have that file in my working directory. When i moved it to the
recommended directory it does not fail on the build properties but fails to run
"ant". The following files are under version control and are all located in
the directory below. All paths for build.sh, and set
Hi Mike,
Hurray! It works fine with the new provider. I didn't have any trailing
slashes so I cannot comment on that. I'll be testing it more and let you
know of any failures.
Thanks a lot for your quick response and your effort is greatly
appreciated (hey it makes me look good :)
Regards,
Ro
Damned if you do, damned if you don't! :-) Glad to at least hear the
overall build is now working for someone.
Obviously I need to add some canonicalization to the repo path handling.
Please enter a JIRA issue in the Maven SCM project.
mike
-Original Message-
From: Neil Padgen [mailto:
Yes, that is correct. I will check for changes in the future. Thank you for
your help.
Michael
-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 15, 2005 9:19 AM
To: continuum-users@maven.apache.org
Subject: Re: FW: Continuum 1.0.2
I'd gue
Actually, no. I will change it to 'READ_UNCOMMITTED' in both places. It
currently is:
...
...
org.codehaus.plexus.jdo.JdoFactory
org.codehaus.plexus.jdo.DefaultJdoFactory
...
org.jpox.transactionIsolation
READ_COMMITTED
You can join to maven-scm developers list (scm-dev@maven.apache.org)
You need to checkout the whole maven-scm project and run mvn install in root directory, or if you
don't want to build all :
in root directory : mvn -N install
in maven-scm-api : mvn install
in maven-scm-providers : mvn -N ins
Ok,
I located the checkout command to the file
PerforceCheckOutCommand.java in
(org.maven.apache.scm.provider.perforce.command.checkout)
The dirty fix I would like to do is probably make the function
public static String createClientspec( String specname, String workDir,
String repoPath )
retur
It seems that it's a problem with your script. I don't know it, so i can't help
you.
Are you sure this command works from command line in this working directory
(/export/home/cruise/workspace/working-directory/6/vmu/build/build.sh cruise clean package_web_ear)?
Emmanuel
Doug Johnson a écrit
13 matches
Mail list logo
