You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Michael McGrady <mi...@michaelmcgrady.com> on 2004/07/05 21:06:42 UTC
[OT] Re: Opening Salvo 'n CVS: step one
I am somewhat surprised that there is not a standard procedure for doing
this sort of thing. Accordingly, I guess I will just have to take my time
and eventually get there, since I have other things to do than work on
struts open source. I am going to keep track of what I do so that
hopefully others will be able to use the process in the future, sort of
like code reuse. Not complaining! It is just that I love to code and am
not crazy about learning new administrative nuances.
Please let me know if I am screwing up. So far, this is what I have done.
1. Downloaded and installed Python 2.3.4 from http://www.python.org/.
(APPARENTLY REQUIRED BY WinCVS)
2. Downloaded and installed WinCVS13b18 from http://www.wincvs.org/.
3. Rooted around in
http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1
4. Got a reference to a WinCVS manual at
http://cvsgui.sourceforge.net/howto/index.html.
5. Downloaded PuTTY from
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html.
6. Jettisoned PuTTY
7. Went to SecureCRT at http://www.vandyke.com/products/securecrt/.
8. Completely screwed up setting up WinCVS following the outdated
instructions at jakarta and decided to get back to this tomorrow.
At 07:52 AM 7/5/2004, you wrote:
>I probably wouldn't start with jcvs. For Windows, a good place to start is
>with PuTTY and WinCVS or TortoiseCVS. (I haven't used TortoiseCVS myself
>but TortoiseSVN is excellent.) For Unix, the standard command line version
>might be simplest.
>
>A good place to get "your feet wet" is with a SourceForge project, since
>the procedure there is so well documented.
>
>http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1
>
>You might try getting an anonymous checkout of, say, struts.sf.net first,
>to confirm that you have a working infrastructure, and then give Apache
>Struts another try.
>
>-Ted.
>
>On Mon, 05 Jul 2004 06:18:19 -0700, Michael McGrady wrote:
> > I am attempting to download struts cvs with jcvs ii. I am a new
> > user of CVS. I am essentially a coder and have not master the
> > finer arts of administrating these jobbers. Guess it is time I
> > learned, so here goes.
> >
> > I am getting the following error:
> >
> >
> > The CVS Request failed.
> > Failed to open socket to connect to cvs server
> > '2401@cvs.apache.org/home/cvspublic'.
> > could not create INETD connection for
> > '2401@cvs.apache.org:/home/cvspublic' -->
> > cvs.apache.org:/home/cvspublic could not create INETD connection for
> > '2401@cvs.apache.org:/home/cvspublic' -->
> > cvs.apache.org:/home/cvspublic
> >
> >
> > ** The command completed with an error status
> >
> >
> > I have used the PServer option and have the username as anoncvs.
> > My CVS Modules is "checkout". My CVS Server is
> > "cvs.apache.org:/home/cvspublic". My CVS Repository is
> > "/home/cvspublic". My Checkout Directory is "jakarta-struts". And
> > my arguments is "-d".
> >
> > Then I click "Checkout Module" and get the error. Any ideas?
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org For
> > additional commands, e-mail: dev-help@struts.apache.org
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>For additional commands, e-mail: dev-help@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [OT] Re: Opening Salvo 'n CVS: step two: build time
Posted by Martin Cooper <ma...@apache.org>.
On Mon, 5 Jul 2004, Craig McClanahan wrote:
> Michael McGrady wrote:
>
>> I have successfully, and without too much difficulty, now uploaded the
>> struts src code into the wincvs as follows:
>>
>> 1. Downloaded and installed Python 2.3.4 from http://www.python.org/.
>> 2. Downloaded and installed WinCVS13b18 from http://www.wincvs.org/.
>> 3. Rooted around in
>> http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1
>> 4. Got a reference to a WinCVS manual at
>> http://cvsgui.sourceforge.net/howto/index.html.
>> 5. Downloaded PuTTY from
>> http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html.
>> 6. Jettisoned PuTTY and went to SecureCRT at
>> http://www.vandyke.com/products/securecrt/.
>> 7. Got the jakarta cvs info source from Ted Husted:
>> http://jakarta.apache.org/site/cvsindex.html.
>> 8. Uploaded jakarta-struts with:
>> Module name and path on the server = "jakarta-struts"
>> Local folder to checkout to = "C:\Program Files\GNU\WinCvs 1.3\"
>> CVSROOT = ":pwerver:anoncvs@cvs.apache.org:/home/cvspublic"
>>
>> I presume that I will want to do this all over and to find a more suitable
>> place to put the code, once I decide how to go about building the code. I
>> know there is a split of preferences between Maven and Ant going on.
>> Could the adherents of each train of thought please give me what they
>> would do to build? All the gory details are encouraged. Thanks. Who
>> knows? Maybe in a week or so I might become useful. ??
>>
>> Michael
>>
> I'm only familiar with the command line compilation environments (once you've
> got the source code checked out). In either the Ant or Maven case, you'll
> want to install CYGWIN (http://www.cygwin.com) to give yourself a set of
> command line tools that is like those available on Unix and Linux systems.
Just wanted to point out that cygwin (or other Unix-like tool set) is not
actually required, for either the Ant or Maven approaches. If you're more
comfortable with Windows tools, you can skip this step.
--
Martin Cooper
> Then:
>
> For either type of build:
> - I recommend using J2SE 1.4.2 (the latest production JDK)
> from (http://java.sun.com/j2se). That's what the nightly builds
> are created with, and in general it has better performance than
> 1.3 (or earlier) JDKs.
>
> For an Ant-based build:
> - Download and install Ant (http://ant.apache.org) 1.5.4 or later
> per website instructions.
> - Examine the documentation on the Struts website for all the
> dependent libraries you'll need (basically all available from
> <http://jakarta.apache.org>).
> - Configure a "build.properties" file in the top-level directory of your
> "jakarta-struts" source tree to point at where you have downloaded
> all the dependencies. The simplest way to create this is to copy
> "build.properties.sample" to "build.properties" and edit the paths.
> - Open a command line window and navigate to the top-level
> "jakarta-struts" directory.
> - Execute "ant clean dist".
>
> For a Maven-based build:
> - Download and install Maven (http://maven.apache.org)
> 1.0-rc4 or later per website instructions.
> - Open a command line window and navigate to the top-level
> "jakarta-struts" directory.
> - Execute "maven clean dist".
> - (I'm sure that there's a Maven option that does enough to
> create just the JAR files needed to test, instead of all the
> extra reports that Maven likes; I don't use Maven regularly,
> so you'll need to ask someone else about that.)
>
> Note that, while easier to set up, the Maven build is still experimental.
> The Ant build is the official one.
>
> Craig McClanahan
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [OT] Re: Opening Salvo 'n CVS: step two: build time
Posted by Craig McClanahan <cr...@apache.org>.
Michael McGrady wrote:
> I have successfully, and without too much difficulty, now uploaded the
> struts src code into the wincvs as follows:
>
> 1. Downloaded and installed Python 2.3.4 from http://www.python.org/.
> 2. Downloaded and installed WinCVS13b18 from http://www.wincvs.org/.
> 3. Rooted around in
> http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1
> 4. Got a reference to a WinCVS manual at
> http://cvsgui.sourceforge.net/howto/index.html.
> 5. Downloaded PuTTY from
> http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html.
> 6. Jettisoned PuTTY and went to SecureCRT at
> http://www.vandyke.com/products/securecrt/.
> 7. Got the jakarta cvs info source from Ted Husted:
> http://jakarta.apache.org/site/cvsindex.html.
> 8. Uploaded jakarta-struts with:
> Module name and path on the server = "jakarta-struts"
> Local folder to checkout to = "C:\Program Files\GNU\WinCvs 1.3\"
> CVSROOT = ":pwerver:anoncvs@cvs.apache.org:/home/cvspublic"
>
> I presume that I will want to do this all over and to find a more
> suitable place to put the code, once I decide how to go about building
> the code. I know there is a split of preferences between Maven and
> Ant going on. Could the adherents of each train of thought please
> give me what they would do to build? All the gory details are
> encouraged. Thanks. Who knows? Maybe in a week or so I might become
> useful. ??
>
> Michael
>
I'm only familiar with the command line compilation environments (once
you've got the source code checked out). In either the Ant or Maven
case, you'll want to install CYGWIN (http://www.cygwin.com) to give
yourself a set of command line tools that is like those available on
Unix and Linux systems. Then:
For either type of build:
- I recommend using J2SE 1.4.2 (the latest production JDK)
from (http://java.sun.com/j2se). That's what the nightly builds
are created with, and in general it has better performance than
1.3 (or earlier) JDKs.
For an Ant-based build:
- Download and install Ant (http://ant.apache.org) 1.5.4 or later
per website instructions.
- Examine the documentation on the Struts website for all the
dependent libraries you'll need (basically all available from
<http://jakarta.apache.org>).
- Configure a "build.properties" file in the top-level directory of your
"jakarta-struts" source tree to point at where you have downloaded
all the dependencies. The simplest way to create this is to copy
"build.properties.sample" to "build.properties" and edit the paths.
- Open a command line window and navigate to the top-level
"jakarta-struts" directory.
- Execute "ant clean dist".
For a Maven-based build:
- Download and install Maven (http://maven.apache.org)
1.0-rc4 or later per website instructions.
- Open a command line window and navigate to the top-level
"jakarta-struts" directory.
- Execute "maven clean dist".
- (I'm sure that there's a Maven option that does enough to
create just the JAR files needed to test, instead of all the
extra reports that Maven likes; I don't use Maven regularly,
so you'll need to ask someone else about that.)
Note that, while easier to set up, the Maven build is still
experimental. The Ant build is the official one.
Craig McClanahan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [OT] Re: Opening Salvo 'n CVS: step two: build time
Posted by Michael McGrady <mi...@michaelmcgrady.com>.
I have successfully, and without too much difficulty, now uploaded the
struts src code into the wincvs as follows:
1. Downloaded and installed Python 2.3.4 from http://www.python.org/.
2. Downloaded and installed WinCVS13b18 from http://www.wincvs.org/.
3. Rooted around in
http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1
4. Got a reference to a WinCVS manual at
http://cvsgui.sourceforge.net/howto/index.html.
5. Downloaded PuTTY from
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html.
6. Jettisoned PuTTY and went to SecureCRT at
http://www.vandyke.com/products/securecrt/.
7. Got the jakarta cvs info source from Ted Husted:
http://jakarta.apache.org/site/cvsindex.html.
8. Uploaded jakarta-struts with:
Module name and path on the server = "jakarta-struts"
Local folder to checkout to = "C:\Program Files\GNU\WinCvs 1.3\"
CVSROOT = ":pwerver:anoncvs@cvs.apache.org:/home/cvspublic"
I presume that I will want to do this all over and to find a more suitable
place to put the code, once I decide how to go about building the code. I
know there is a split of preferences between Maven and Ant going on. Could
the adherents of each train of thought please give me what they would do to
build? All the gory details are encouraged. Thanks. Who knows? Maybe in
a week or so I might become useful. ??
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [OT] Re: Opening Salvo 'n CVS: step one
Posted by Michael McGrady <mi...@michaelmcgrady.com>.
Many thanks!
At 12:22 PM 7/5/2004, Ted Husted wrote:
>If you mean Apache projects don't require a uniform set of tools, that's
>correct. Many people want to use the same CVS client or IDE to work on ASF
>code as they do at work, so we don't prescribe which to use. Developers
>are invited to use whatever client software they like, so long as it can
>hook up to our CVS (or SVN), web, and mail servers. The standard procedure
>for accessing our CVS with the client of your choice are here:
>
>http://jakarta.apache.org/site/cvsindex.html
>
>At the bottom are links with instructions for various Unix and Windows
>clients.
>
>-Ted.
>
>On Mon, 05 Jul 2004 12:06:42 -0700, Michael McGrady wrote:
> > I am somewhat surprised that there is not a standard procedure for
> > doing this sort of thing. Accordingly, I guess I will just have to
> > take my time and eventually get there, since I have other things to
> > do than work on struts open source. I am going to keep track of
> > what I do so that hopefully others will be able to use the process
> > in the future, sort of like code reuse. Not complaining! It is
> > just that I love to code and am not crazy about learning new
> > administrative nuances.
> >
> > Please let me know if I am screwing up. So far, this is what I
> > have done.
> >
> >
> > 1. Downloaded and installed Python 2.3.4 from
> > http://www.python.org/. (APPARENTLY REQUIRED BY WinCVS)
> > 2. Downloaded and installed WinCVS13b18 from
> > http://www.wincvs.org/. 3. Rooted around in
> > http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1 4
> > . Got a reference to a WinCVS manual at
> > http://cvsgui.sourceforge.net/howto/index.html. 5. Downloaded
> > PuTTY from
> > http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html. 6.
> > Jettisoned PuTTY
> > 7. Went to SecureCRT at
> > http://www.vandyke.com/products/securecrt/. 8. Completely screwed
> > up setting up WinCVS following the outdated instructions at jakarta
> > and decided to get back to this tomorrow.
> >
> >
> > At 07:52 AM 7/5/2004, you wrote:
> >> I probably wouldn't start with jcvs. For Windows, a good place to
> >> start is with PuTTY and WinCVS or TortoiseCVS. (I haven't used
> >> TortoiseCVS myself but TortoiseSVN is excellent.) For Unix, the
> >> standard command line version might be simplest.
> >>
> >> A good place to get "your feet wet" is with a SourceForge
> >> project, since the procedure there is so well documented.
> >>
> >> http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1
> >>
> >>
> >> You might try getting an anonymous checkout of, say,
> >> struts.sf.net first, to confirm that you have a working
> >> infrastructure, and then give Apache Struts another try.
> >>
> >> -Ted.
> >>
> >>
> >> On Mon, 05 Jul 2004 06:18:19 -0700, Michael McGrady wrote:
> >>
> >>> I am attempting to download struts cvs with jcvs ii. I am a
> >>> new user of CVS. I am essentially a coder and have not master
> >>> the finer arts of administrating these jobbers. Guess it is
> >>> time I learned, so here goes.
> >>>
> >>> I am getting the following error:
> >>>
> >>>
> >>> The CVS Request failed.
> >>> Failed to open socket to connect to cvs server
> >>> '2401@cvs.apache.org/home/cvspublic'.
> >>> could not create INETD connection for
> >>> '2401@cvs.apache.org:/home/cvspublic' -->
> >>> cvs.apache.org:/home/cvspublic could not create INETD
> >>> connection for '2401@cvs.apache.org:/home/cvspublic' -->
> >>> cvs.apache.org:/home/cvspublic
> >>>
> >>>
> >>> ** The command completed with an error status
> >>>
> >>>
> >>> I have used the PServer option and have the username as
> >>> anoncvs. My CVS Modules is "checkout". My CVS Server is
> >>> "cvs.apache.org:/home/cvspublic". My CVS Repository is
> >>> "/home/cvspublic". My Checkout Directory is "jakarta-struts".
> >>> And my arguments is "-d".
> >>>
> >>> Then I click "Checkout Module" and get the error. Any ideas?
> >>>
> >>>
> >>> ----------------------------------------------------------------
> >>> ---- - To unsubscribe, e-mail: dev-
> >>> unsubscribe@struts.apache.org For additional commands, e-mail:
> >>> dev-help@struts.apache.org
> >>
> >>
> >> ------------------------------------------------------------------
> >> --- To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org For
> >> additional commands, e-mail: dev-help@struts.apache.org
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org For
> > additional commands, e-mail: dev-help@struts.apache.org
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>For additional commands, e-mail: dev-help@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [OT] Re: Opening Salvo 'n CVS: step one
Posted by Ted Husted <hu...@apache.org>.
If you mean Apache projects don't require a uniform set of tools, that's correct. Many people want to use the same CVS client or IDE to work on ASF code as they do at work, so we don't prescribe which to use. Developers are invited to use whatever client software they like, so long as it can hook up to our CVS (or SVN), web, and mail servers. The standard procedure for accessing our CVS with the client of your choice are here:
http://jakarta.apache.org/site/cvsindex.html
At the bottom are links with instructions for various Unix and Windows clients.
-Ted.
On Mon, 05 Jul 2004 12:06:42 -0700, Michael McGrady wrote:
> I am somewhat surprised that there is not a standard procedure for
> doing this sort of thing. Accordingly, I guess I will just have to
> take my time and eventually get there, since I have other things to
> do than work on struts open source. I am going to keep track of
> what I do so that hopefully others will be able to use the process
> in the future, sort of like code reuse. Not complaining! It is
> just that I love to code and am not crazy about learning new
> administrative nuances.
>
> Please let me know if I am screwing up. So far, this is what I
> have done.
>
>
> 1. Downloaded and installed Python 2.3.4 from
> http://www.python.org/. (APPARENTLY REQUIRED BY WinCVS)
> 2. Downloaded and installed WinCVS13b18 from
> http://www.wincvs.org/. 3. Rooted around in
> http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1 4
> . Got a reference to a WinCVS manual at
> http://cvsgui.sourceforge.net/howto/index.html. 5. Downloaded
> PuTTY from
> http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html. 6.
> Jettisoned PuTTY
> 7. Went to SecureCRT at
> http://www.vandyke.com/products/securecrt/. 8. Completely screwed
> up setting up WinCVS following the outdated instructions at jakarta
> and decided to get back to this tomorrow.
>
>
> At 07:52 AM 7/5/2004, you wrote:
>> I probably wouldn't start with jcvs. For Windows, a good place to
>> start is with PuTTY and WinCVS or TortoiseCVS. (I haven't used
>> TortoiseCVS myself but TortoiseSVN is excellent.) For Unix, the
>> standard command line version might be simplest.
>>
>> A good place to get "your feet wet" is with a SourceForge
>> project, since the procedure there is so well documented.
>>
>> http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1
>>
>>
>> You might try getting an anonymous checkout of, say,
>> struts.sf.net first, to confirm that you have a working
>> infrastructure, and then give Apache Struts another try.
>>
>> -Ted.
>>
>>
>> On Mon, 05 Jul 2004 06:18:19 -0700, Michael McGrady wrote:
>>
>>> I am attempting to download struts cvs with jcvs ii. I am a
>>> new user of CVS. I am essentially a coder and have not master
>>> the finer arts of administrating these jobbers. Guess it is
>>> time I learned, so here goes.
>>>
>>> I am getting the following error:
>>>
>>>
>>> The CVS Request failed.
>>> Failed to open socket to connect to cvs server
>>> '2401@cvs.apache.org/home/cvspublic'.
>>> could not create INETD connection for
>>> '2401@cvs.apache.org:/home/cvspublic' -->
>>> cvs.apache.org:/home/cvspublic could not create INETD
>>> connection for '2401@cvs.apache.org:/home/cvspublic' -->
>>> cvs.apache.org:/home/cvspublic
>>>
>>>
>>> ** The command completed with an error status
>>>
>>>
>>> I have used the PServer option and have the username as
>>> anoncvs. My CVS Modules is "checkout". My CVS Server is
>>> "cvs.apache.org:/home/cvspublic". My CVS Repository is
>>> "/home/cvspublic". My Checkout Directory is "jakarta-struts".
>>> And my arguments is "-d".
>>>
>>> Then I click "Checkout Module" and get the error. Any ideas?
>>>
>>>
>>> ----------------------------------------------------------------
>>> ---- - To unsubscribe, e-mail: dev-
>>> unsubscribe@struts.apache.org For additional commands, e-mail:
>>> dev-help@struts.apache.org
>>
>>
>> ------------------------------------------------------------------
>> --- To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org For
>> additional commands, e-mail: dev-help@struts.apache.org
>
>
> --------------------------------------------------------------------
> - To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org For
> additional commands, e-mail: dev-help@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org