I can ssh to minotaur with no problems using my ssh key. Just for kicks, I tried it from my linux box, and it worked. So, I guess there's an issue with using cygwin's ssh?
-----Original Message----- From: Phil Steitz [mailto:[EMAIL PROTECTED] Sent: Sunday, August 28, 2005 1:52 AM To: Jakarta Commons Developers List Subject: Re: [proxy] Site Generation Issues... This could be an ssh authentication problem. Do you an ssh key set up on minotaur? IIRC, there is a problem getting challenge-response to work on windows. Phil On 8/27/05, James Carman <[EMAIL PROTECTED]> wrote: > > Well, there's only one problem. I did what you instructed me to do. > However, when I run site:sshdeploy on the commons-build project, it hangs > on > the step where it tries to create the directory: > > [gzip] Building: C:\Documents and > Settings\jcarman\IdeaProjects\commons-build\target\commons-1.0-site.tar.gz > [delete] Deleting: C:\Documents and > Settings\jcarman\IdeaProjects\commons-build\target\commons-1.0-site.tar > [exec] [VERBOSE] Current OS is Windows XP > [exec] [VERBOSE] Executing 'ssh' with arguments: > '-l' > 'jcarman' > 'people.apache.org <http://people.apache.org>' > 'mkdir -p /www/jakarta.apache.org/commons' > > The ' characters around the executable and arguments are not part of the > command. > > [exec] [DEBUG] Execute:Java13CommandLauncher: Executing 'ssh' with > arguments: > '-l' > 'jcarman' > 'people.apache.org <http://people.apache.org>' > 'mkdir -p /www/jakarta.apache.org/commons' > > The ' characters around the executable and arguments are > not part of the command. > > > It just sits there doing nothing at this point. Is it a file permissions > problem? If so, you'd think it'd fail pretty quickly on that. > > > -----Original Message----- > From: Phil Steitz [mailto:[EMAIL PROTECTED] > Sent: Saturday, August 27, 2005 10:23 PM > To: Jakarta Commons Developers List > Subject: Re: [proxy] Site Generation Issues... > > You need to add an entry to commons-build/menus/sandbox-items.ent. You > should also add an entry to commons-build/parts/sandbox-table.ent so it > shows up in the sandbox components table. Then do site:generate from > commons-build, make sure it looks OK, check in changes and then maven > site:sshdeploy. > > If you want the commons l&f, you should also add > maven.xdoc.jsl=../commons-build/commons-site.jsl > to your project.properties > > Phil > > > On 8/27/05, James Carman <[EMAIL PROTECTED]> wrote: > > > > How do I get Commons Proxy listed on the main Jakarta Commons page as a > > link > > in the sandbox section? > > > > -----Original Message----- > > From: James Carman [mailto:[EMAIL PROTECTED] > > Sent: Saturday, August 27, 2005 8:40 PM > > To: 'Jakarta Commons Developers List'; [EMAIL PROTECTED] > > Subject: RE: [proxy] Site Generation Issues... > > > > It's generated using the standard Maven build project.xml file. For some > > reason, the "style" directory on the filesystem was created without read > > permissions for "all" when I did sshdeploy (or maybe it happened when I > > manually uploaded stuff). That's weird. Hopefully doing a chmod on it > will > > fix the problem. > > > > > > -----Original Message----- > > From: Simon Kitching [mailto:[EMAIL PROTECTED] > > Sent: Saturday, August 27, 2005 8:04 PM > > To: Jakarta Commons Developers List > > Subject: Re: [proxy] Site Generation Issues... > > > > On Sat, 2005-08-27 at 19:57 -0400, James Carman wrote: > > > I finally got everything working and the site on my local machine > looks > > > pretty good. But, it looks horrible on the web! Is there something > > special > > > I have to do to get it looking correct? > > > > I would guess that the problem is a missing stylesheet. The site may > > reference the stylesheet through some path that isn't valid once the > > site is deployed to its final destination... > > > > Regards, > > > > Simon > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
