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/06 07:59:33 UTC
Re: [OT] Re: Opening Salvo 'n CVS: step two: build time
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 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