date:20010329

RE: [JBoss-dev] Sourceforge cvs problem

2001-03-29 Thread Micheal J


Some ideas:
1. Use an RSA key-pair for SSH1. Ensure that the keys have no passphrase (no
pint in going password-less only to be asked for the passphrase instead)
2. Use the "Edit key" feature of the account management page to upload your
*public* key file only to all the relevant SF servers (this requires a 6
hour wait for full propagation)
3. Ensure your machine has the corresponding private+public keyfiles as your
default (or only) SSH1 identity. Actually it may be enough for it to be just
one of many identities but no point in complicating things right?

Good luck,

Micheal

> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> Vladimir Blagojevic
> Sent: 29 March 2001 05:04
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] Sourceforge cvs problem
>
>
> Hey,
>
> I still can not do this on Redhat 7 although I am close.  Used
> ssh-keygen, created both RSA and DSA
> key pairs, added them to running ssh-agent, uploaded pub keys to
> server. Did you use website upload
> or scp command?


___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: contrib/catalina/src/build build.sh

2001-03-29 Thread phox


  User: phox
  Date: 01/03/29 00:27:17

  Modified:catalina/src/build build.sh
  Log:
  Upgrade for ant1.3
  
  Revision  ChangesPath
  1.2   +2 -1  contrib/catalina/src/build/build.sh
  
  Index: build.sh
  ===
  RCS file: /cvsroot/jboss/contrib/catalina/src/build/build.sh,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- build.sh  2001/02/22 14:51:03 1.1
  +++ build.sh  2001/03/29 08:27:17 1.2
  @@ -1,11 +1,12 @@
   #!/bin/bash
   
   ABORT=0
  +
   if [ "X${JBOSS_HOME}" = "X" ] ; then echo "JBOSS_HOME is not set. You need jboss 
2.1+" ; ABORT=1 ; fi
   if [ "X${TOMCAT_HOME}" = "X" ] ; then echo "TOMCAT_HOME is not set. You need tomcat 
4.0-b1+" ; ABORT=1 ; fi
   if [ $ABORT = 1 ] ; then echo "Aborting..." ; exit ; fi
   
  -TARGET_CLASSPATH=${JBOSS_HOME}/lib/ant.jar:\
  +TARGET_CLASSPATH=${JBOSS_HOME}/lib/ant-1.3.jar:\
   ${TOMCAT_HOME}/server/crimson.jar:\
   ${TOMCAT_HOME}/server/jaxp.jar:\
   ${JBOSS_HOME}/lib/javac.jar
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: newsite/documentation jboss1.html jboss_win32_1.html

2001-03-29 Thread starksm

User: starksm
Date: 01/03/29 00:27:53

Modified:documentation jboss1.html jboss_win32_1.html
Log:
Change the obsolete java -jar run.jar to run.bat and run.sh

Revision ChangesPath
1.3 +1 -1 newsite/documentation/jboss1.html

Index: jboss1.html
===
RCS file: /cvsroot/jboss/newsite/documentation/jboss1.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- jboss1.html 2001/02/08 05:31:32 1.2
+++ jboss1.html 2001/03/29 08:27:53 1.3
@@ -40,7 +40,7 @@
rm -f install.zip
You could try running the server now.
Change to the bin directory, and run the program like this:
cd bin
-java -jar run.jar
+run.sh
In a proper installation, the server
should start without any error messages or exceptions being thrown. It will produce
about three pages of output on startup.
The JBoss distribution is supplied with
one test Bean, packaged as bank.jar. This is supplied in the `deploy'
subdirectory, which is where Beans are placed to deploy them. The effect of this is to
deploy the `bank' bean when the server starts up. This is fine the first time, as it
tests that the SQL server is working, but you can usefully move bank.jar
out of the deploy directory when you are sure that everything's OK, and
the server will start up more quickly.

1.3 +1 -1 newsite/documentation/jboss_win32_1.html

Index: jboss_win32_1.html
===
RCS file: /cvsroot/jboss/newsite/documentation/jboss_win32_1.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- jboss_win32_1.html2001/02/08 05:31:33 1.2
+++ jboss_win32_1.html2001/03/29 08:27:53 1.3
@@ -30,7 +30,7 @@
On a Windows NT system, you will not need
Administrator priviledges. JBoss itself will work perfectly well if installed in a user directory and run
as an ordinary user. I will assume in this tutorial that you are installing in
c:\jboss. If you haven't, change the paths as appropriate.
You could try running the server now. Open a Command Prompt
(DOS window), change to the \jboss\bin directory and run
cd c:\jboss\bin
-java -jar run.jar
+run.bat
The server should start without any
error messages or exceptions being thrown. It will produce about three pages of output
on startup.

To deploy your beans, put them in
C:\jboss\deploy\. JBoss' AutoDeploy system will detect a new or revised
.jar file and automatically deploy your beans. If you still have the
JBoss window open, you'll see some messages scroll by as your bean deploys. (Note:
C:\jboss\deploy\ must exist when you start JBoss or you'll need to
restart the server to activate the AutoDeploy mechanism.)

39 matches

Mail list logo