TED]>
Sent: Friday, August 27, 2004 1:18 PM
Subject: Re: cvs commit: jakarta-struts project.xml
> I went ahead and updated the downloads page to 1.1.3, what should I put
for
> latest development versions? Other commons subprojex look very different
> from validator and even each other?
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 27, 2004 1:01 PM
Subject: cvs commit: jakarta-struts project.xml
> germuska2004/08/27 10:01:36
>
> Modified:.project.xml
> Log:
> remove comment on c
germuska2004/08/27 10:01:36
Modified:.project.xml
Log:
remove comment on commons-validator dependency since the current version is now
served from iBiblio (yay!)
Revision ChangesPath
1.33 +0 -9 jakarta-struts/project.xml
Index: project.xml
==
husted 2004/08/25 04:49:06
Modified:.project.xml build.xml
Log:
Update build.xml and project.xml for 1.2.2.
Revision ChangesPath
1.32 +1 -1 jakarta-struts/project.xml
Index: project.xml
germuska2004/07/12 09:12:31
Modified:.project.xml
Log:
update Maven version to match tag; will move tag next
Revision ChangesPath
1.31 +1 -1 jakarta-struts/project.xml
Index: project.xml
husted 2004/06/23 17:34:56
Modified:.project.xml project.properties
Log:
Update to reflect availability of Validator 1.1.3 release (alpha)
Revision ChangesPath
1.29 +7 -6 jakarta-struts/project.xml
Index: project.xml
=
germuska2004/05/21 07:28:03
Modified:.project.xml
Log:
commons-validator dependency is 1.1.3-dev, not 1.1.2-dev.
Revision ChangesPath
1.28 +1 -1 jakarta-struts/project.xml
Index: project.xml
germuska2004/05/12 07:37:08
Modified:.project.xml
Log:
Change the "dependency" url for commons-validator to point to an explanation
of how to deal with the unreleased validator dependency.
Revision ChangesPath
1.27 +8 -0 jakarta-struts/project.xml