[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [pde-build-dev] Headless build with CVS Fetch
|
Dear
Andrew,
As a follow-up, I have tried to find a way of specifying
something in the .map file that will cause the attribute "passfile=" to be
set nside each cvs command element.
However, if I specify a password and a passfile on a map
entry, I do not get the result I'm looking for. Instead I get an additional
elemnt before the cvs command:
<cvspass
cvsRoot="..." password="..." passfile="..."
/>
When that runs it simply inserts the password in the
passfile that it is already in. When the following "cvs command" runs it still
fails, presumably because it doesn't know where the password file to use
is.
I found that the way to get the cvs exportto work is by
having that passfile attribute in the cvs command element. Can you tell me if
and where I can set some parameter that will cause the result I want or does it
have to be a coding change in the PDE Build? If the latter, if you could give me
a pointer of where to look I can work something out, debug it and give it
back to you..
Best wishes, Ivan
Dear
Andrew,
Thank you very much for the lead. I took the generated
retrieve.xml, renamed it as build.xml and ran it from the command line with
ant.
I got the same problem, but at least I had a file I
could modifiy until I got it to work -- which I eventually did. I added
passfile="/home/ivan/.cvspass" to the two "cvs command="export..." lines and
the files were retrieved from CVS correctly.
Now I have to go back and get the "passfile=" into the
main build, and then make sure that I can also specify it to
pluginbuilder.
So thank you for your help.
Best wishes, Ivan.
I
don't know a lot about cvs passfiles, but, here is some info:
PDE.Build uses the cvs ant task for the
fetch. When the fetch fails, it should leave behind a retrieve.xml
script that was used to try and fetch. You can look there to see the
ant calls.
A cvspass task will be
generated for authentication if password and passfile are specified in the
map file and this task adds the password to the passfile. Ant docs say
the default passfile is ~/.cvspass
Note however that the ant docs
(http://ant.apache.org/manual/CoreTasks/cvspass.html) say that if you are
using CVSNT then your passfile may be ignored, see
http://issues.apache.org/bugzilla/show_bug.cgi?id=21657#c5.
-Andrew
"Ivan Biddles"
<ivanb@xxxxxxxxxxxxxxx>
Sent by: pde-build-dev-bounces@xxxxxxxxxxx
07/19/2007 03:21 PM
|
Please respond
to
"Eclipse PDE Build developers list."
<pde-build-dev@xxxxxxxxxxx> |
|
|
To
| <pde-build-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| [pde-build-dev] Headless build
with CVS Fetch |
|
Hi,
I'm not sure if this is the correct forum,
so, if it isn't, please let know which forum I should use.
I have been
having a problem getting a headless PDE build in which I pull the source
code from CVS to work.
I have followed the instructions as far as I
can tell. I even found and installed the pluginbuilder plug-in (which is
very good by the way) and yet things hang at the same point. When the build
attempts to login to the CVS server I get an error message on the client
side and a login failure at the server. (I see "cvs: login failure (for
/usr/local/cvsroot) in /var/log/messages on the server).
The build
error is reported as:
(eclipse.fetch) Could not retrieve feature.xml and/or
build.properties:
cvs exited with
error code 1
(eclipse.fetch) Command line
was [Executing 'cvs' with arguments:
(eclipse.fetch) '-d:pserver:ivan@lindev09:/usr/local/cvsroot'
(eclipse.fetch) '-q'
(eclipse.fetch) 'export'
(eclipse.fetch) '-r'
(eclipse.fetch) 'HEAD'
(eclipse.fetch) 'org.xxx.xxx/feature.xml'
(eclipse.fetch)
If I take that exact same CVS execute string,
form it into a single command-line and run it from a command prompt, the cvs
checkout works perfectly.
I am running on WinXP with Eclipse 3.3 and my
CVS server is on a linux box.
My CVS password file on the client
was created at "c:\Documents and Settings\ivan\.cvspass" by Eclipse. I also
created a .cvspass in \home\ivan and set the HOME environment variable to
that directory.
Does anyone have any ideas about what the problem is or
what I should try next?
Thanks, Ivan
_______________________________________________
pde-build-dev
mailing
list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
