Re: Keeping up to date with nightly builds

2002-11-18 Thread Martin Cooper 


On Mon, 18 Nov 2002, Wendy Smoak wrote:

>
> Does anyone have a procedure for updating an existing project to use all the
> stuff from a nightly build?
>
> So far, I delete my 'jakarta-struts' directory and unzip both of the nightly
> build files (source & binary) again.  Then I copy all the .jar files, all
> the .tld files and the validator-rules.xml file over from the unzipped
> jakarta-struts/lib into the appropriate places in my own project.
>
> I'm a bit confused about the .dtd files included with the nightly build from
> the 18th.  They don't seem to be used anywhere.  For example, there is a
> validator-rules_1_1.dtd, but the included validator-rules.xml file uses
> http://jakarta.apache.org/commons/dtds/validator_1_0.dtd.

If you check the latest version of validator-rules_1_1.dtd, you'll find
DEPRECATED comments all over it. The Validator is now part of Jakarta
Commons, and so the latest code references the Commons Validator DTD. The
DTD in the Struts tree is maintained for backwards compatibility only.

--
Martin Cooper


>
> Do I need these .dtd files from the nightly build?  Have I missed anything?
> (It compiles, but I've already caused myself problems by using some files
> from one build and some from another!)
>
> Thanks,
>
> --
> Wendy Smoak
> Applications Systems Analyst, Sr.
> Arizona State University PA Information Resources Management
>


--
To unsubscribe, e-mail:   
For additional commands, e-mail:

RE: Keeping up to date with nightly builds

2002-11-18 Thread Kevin . Bedell 



I've been using Eclipse for this and the built-in cvs support works well.
Others may have other preferences.

Also, the easiest way to get all the supporting jar files is to browse
around at:

  http://jakarta.apache.org/builds/

though, you may already know this...






"edgar" <[EMAIL PROTECTED]> on 11/18/2002 05:06:38 PM

Please respond to "Struts Users Mailing List"
   <[EMAIL PROTECTED]>

To:"'Struts Users Mailing List'" <[EMAIL PROTECTED]>
cc: (bcc: Kevin Bedell/Systems/USHO/SunLife)
Subject:RE: Keeping up to date with nightly builds


The best way is to set up cvs with an ant build.

It is a bit of a pain to get going the first time since you need quite a
few jars and both struts and commons (certain parts) and you have to
carefully create your build.properties but once you get it done

Then you can script the whole download rebuild process.

If you are going to make any contributions, this is the only way to go.

Edgar
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 18, 2002 4:31 PM
To: '[EMAIL PROTECTED]'
Subject: Keeping up to date with nightly builds



Does anyone have a procedure for updating an existing project to use all
the stuff from a nightly build?

So far, I delete my 'jakarta-struts' directory and unzip both of the
nightly build files (source & binary) again.  Then I copy all the .jar
files, all the .tld files and the validator-rules.xml file over from the
unzipped jakarta-struts/lib into the appropriate places in my own
project.

I'm a bit confused about the .dtd files included with the nightly build
from the 18th.  They don't seem to be used anywhere.  For example, there
is a validator-rules_1_1.dtd, but the included validator-rules.xml file
uses http://jakarta.apache.org/commons/dtds/validator_1_0.dtd.

Do I need these .dtd files from the nightly build?  Have I missed
anything? (It compiles, but I've already caused myself problems by using
some files from one build and some from another!)

Thanks,

--
Wendy Smoak
Applications Systems Analyst, Sr.
Arizona State University PA Information Resources Management


--
To unsubscribe, e-mail:   <
mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <
mailto:[EMAIL PROTECTED]>







---
This e-mail message (including attachments, if any) is intended for the use
of the individual or entity to which it is addressed and may contain
information that is privileged, proprietary , confidential and exempt from
disclosure.  If you are not the intended recipient, you are notified that
any dissemination, distribution or copying of this communication is
strictly prohibited.  If you have received this communication in error,
please notify the sender and erase this e-mail message immediately.
---



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: Keeping up to date with nightly builds

2002-11-18 Thread edgar 
The best way is to set up cvs with an ant build.

It is a bit of a pain to get going the first time since you need quite a
few jars and both struts and commons (certain parts) and you have to
carefully create your build.properties but once you get it done

Then you can script the whole download rebuild process.

If you are going to make any contributions, this is the only way to go.

Edgar
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]] 
Sent: Monday, November 18, 2002 4:31 PM
To: '[EMAIL PROTECTED]'
Subject: Keeping up to date with nightly builds



Does anyone have a procedure for updating an existing project to use all
the stuff from a nightly build?

So far, I delete my 'jakarta-struts' directory and unzip both of the
nightly build files (source & binary) again.  Then I copy all the .jar
files, all the .tld files and the validator-rules.xml file over from the
unzipped jakarta-struts/lib into the appropriate places in my own
project.

I'm a bit confused about the .dtd files included with the nightly build
from the 18th.  They don't seem to be used anywhere.  For example, there
is a validator-rules_1_1.dtd, but the included validator-rules.xml file
uses http://jakarta.apache.org/commons/dtds/validator_1_0.dtd.

Do I need these .dtd files from the nightly build?  Have I missed
anything? (It compiles, but I've already caused myself problems by using
some files from one build and some from another!)

Thanks,

-- 
Wendy Smoak
Applications Systems Analyst, Sr.
Arizona State University PA Information Resources Management


--
To unsubscribe, e-mail:   
For additional commands, e-mail: