You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Ted Husted <te...@gmail.com> on 2005/11/15 14:27:53 UTC
Re: 1.3.0 Release - Next Steps
I've been through Apps, and it's looking quite good now. There were
only very minor fixes to the pages, everything seems to be working
well.
Many thanks to Wendy and James and everyone who's been working on the
Maven builds. It's all come together very nicely. IMHO, the process is
more accessible, and it will be much easier for people to get involved
in the project, or get involved again after being away for a while.
As to remaining steps, I think all we need to do is
(1) Make a final pass on the documentation and configuration files, to
be sure all is current with the release plan.
(2) Rename struts-core as struts-action.
(3) Finalize what we are going to do with #36794 - the CG lib
DynaForm enhancements.
(4) Final updates the release notes as to recent changes.
(5) Set 1.3.0 tags for each subproject (ACTION_1_3_0, APPS_1_3_0,
EL_1_3_0, ...) .
(6) Assembly a ZIP archive of the respective JARs as the "Struts
Action Framework Library".
(7) Post for review
As to (3), one option is to move the code to the Extras subproject. We
might also want to consider if we want to move some other optional
classes there too. One candidate might be
[org.apache.struts.validator.ValidatorActionForm], which is the "path"
attribute version of ValidatorForm.
Release caveats are that we have two dependencies on non-GA code:
Commons Validator and Commons Resources. Commons Resources is being
used as part of the Extras subproject. All I did was build the dev
code from a nighly buid and post the JAR in the Apache repository. Is
anyone up for a Commons Resources release?
These caveats would keep a 1.3.0 release of Action Framework and
Extras from going GA, but I think we anticipate additional changes
anyway, so I don't see that they should keep us from rolling it.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 1.3.0 Release - Next Steps
Posted by Ted Husted <te...@gmail.com>.
On 12/6/05, Wendy Smoak <ws...@gmail.com> wrote:
> The release plan shows including struts-site.jar. There is no source
> code in 'site,' so that jar only contains a manifest. Ted, were you
> thinking of including the generated website in the release?
Yes, the citation to the JAR was just a copy glitch. The idea was to
include the website docs, if we can.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 1.3.0 Release - Next Steps
Posted by Ted Husted <te...@gmail.com>.
On 12/20/05, Wendy Smoak <ws...@gmail.com> wrote:
> The result of 'maven multiproject:site', zipped up, is 17.5 MB.
I still can't get that goal to run, so I've been building the ones I
work on individually.
--
E:\projects\Apache\struts\flow\src\java\org\apache\struts\flow\core\javascript\f
om\PageLocalScopeImpl.java:38: cannot find symbol
symbol : class Scriptable
location: class org.apache.struts.flow.core.javascript.fom.PageLocalScopeImpl
private Scriptable newObject() {
^
Note: E:\projects\Apache\struts\flow\src\java\org\apache\struts\flow\FlowAction.
java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
100 errors
BUILD FAILED
File...... C:\Documents and Settings\ted_2\.maven\cache\maven-multiproject-plugi
n-1.3.1\plugin.jelly
Element... maven:reactor
Line...... 103
Column.... 9
Unable to obtain goal [site] -- C:\Documents and Settings\ted_2\.maven\cache\mav
en-java-plugin-1.5\plugin.jelly:63:48: <ant:javac> Compile failed; see the compi
ler error output for details.
Total time: 4 minutes 51 seconds
Finished at: Tue Dec 20 09:16:35 EST 2005
E:\projects\Apache\struts\build>
I've tried it from my root of Struts current and /site, with the same result.
--
> What did you have in mind to include?
If each of the other subproject distributions include their own
website documentation, like Struts Scripting does, then all we really
need to do is to zip the top-level site docs for the actual site
subproject (as opposed to the multiproject "site" maven goal). If we
did want to include the rest of the site, we wouldn't need to drag
down the site archives. The links to those could be direct to the
website rather than relative.
I'm copying the live website to a local directory now. I'd like to do
a thorough review of what we do have online now and see if there is
any cruft we can remove. (Like some of the legacy JARs from when we
used to burst the WARs.)
But, overall, in terms of the 1.3.0 release, we're mainly waiting on
Message Resources, yes?
If that happens, and #37301 and #37730 are still open, I'd say we
should pull the new Enhanced DynaActionForm feature and roll it.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 1.3.0 Release - Next Steps
Posted by Wendy Smoak <ws...@gmail.com>.
On 12/12/05, Ted Husted <te...@gmail.com> wrote:
> If we think the problem is the tests, rather than the code, then I
> don't believe that the issue should affect whether we release.
That's what I think. I've had 1.3.0-dev in production since
mid-September and the app uses most of the Struts-EL HTML tags.
Either the code changed out from under the tests, or it's just a
Maven/Cactus misconfiguration.
earlier, Ted wrote:
> The idea was to include the website docs, if we can.
All of it? The result of 'maven multiproject:site', zipped up, is
17.5 MB. (That includes the old api docs and all of the Maven
reports, though.) For comparison, the struts-documentation.war is
around 5 MB.
I've made some progress on PDFs, but the PDF plugin is not
multiproject aware so it's one PDF per sub-project (and the relative
links don't work.)
What did you have in mind to include?
Thanks,
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 1.3.0 Release - Next Steps
Posted by Ted Husted <te...@gmail.com>.
If we think the problem is the tests, rather than the code, then I
don't believe that the issue should affect whether we release.
I might try to setup some webtests for the Taglib Exercises and
Cookbook, so that we still have automated tests for the tags.
I'm still twiddling with the MailReader tour page, but what's there is
OK. I think it's just a matter of resolving Commons Resources.
-Ted.
On 12/11/05, Wendy Smoak <ws...@gmail.com> wrote:
> On 12/6/05, Wendy Smoak <ws...@gmail.com> wrote:
>
> > The Cactus tests for EL are still a problem, but I haven't gotten
> > anywhere with them. I'm planning to try again this weekend.
>
> I looked at this again, and I still don't see anything wrong with the
> tags. Unfortunately I still haven't figured out why 'maven
> cactus:test' is failing, either.
>
> Maybe if some of you are bored in between sessions in San Diego, you
> can take a look. :)
>
> (I *think* I might have reclaimed my inbox from Bugzilla, I'm afraid
> to look again...)
>
> --
> Wendy
http://www.husted.com/poe/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 1.3.0 Release - Next Steps
Posted by Wendy Smoak <ws...@gmail.com>.
On 12/6/05, Wendy Smoak <ws...@gmail.com> wrote:
> The Cactus tests for EL are still a problem, but I haven't gotten
> anywhere with them. I'm planning to try again this weekend.
I looked at this again, and I still don't see anything wrong with the
tags. Unfortunately I still haven't figured out why 'maven
cactus:test' is failing, either.
Maybe if some of you are bored in between sessions in San Diego, you
can take a look. :)
(I *think* I might have reclaimed my inbox from Bugzilla, I'm afraid
to look again...)
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 1.3.0 Release - Next Steps
Posted by Wendy Smoak <ws...@gmail.com>.
Coming back around to the pending 1.3 release...
It looks like Commons Resources is coming along well, thanks to Niall,
Rahul and Christian.
Laurie, can we please have an update on Bug 37730 and the Enhanced
DynaActionForm addition in general? 37301 is also still open.
Thanks!
The Cactus tests for EL are still a problem, but I haven't gotten
anywhere with them. I'm planning to try again this weekend. As part
of that, I'd like to restructure EL so that the Maven build is less
complicated. (Right now the source code for both the jar and the
example app is in the same directory.)
The release plan shows including struts-site.jar. There is no source
code in 'site,' so that jar only contains a manifest. Ted, were you
thinking of including the generated website in the release?
Thanks,
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 1.3.0 Release - Next Steps
Posted by Wendy Smoak <ws...@gmail.com>.
On 11/15/05, Ted Husted <te...@gmail.com> wrote:
> I've been through Apps, and it's looking quite good now. There were
> only very minor fixes to the pages, everything seems to be working
> well.
I have a few changes (Validator Plugin config to use the copy of
validator-rules in the struts-core jar) but if they miss Apps 1.3.0
it's not a big deal.
Some time back I started making sure the license/notice files were in
every artifact and I don't think I made it through the entire project.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 1.3.0 Release - Next Steps
Posted by Martin Cooper <ma...@apache.org>.
On 11/15/05, Ted Husted <te...@gmail.com> wrote:
>
> Is it even useful to tag a SVN repository for a release?
Yes, I believe it is. That way, it's more explicit, you can see the tags
under struts/tags in the repo, and you don't have to dig up the repo
revision number. It's also cheap - nothing actually gets copied unless it's
changed.
--
Martin Cooper
If we document the revision as of the release, then we can always go
> back and branch on that revision later, or retrieve a snapshot of the
> repository as of the release.
>
> -Ted.
>
> On 11/15/05, James Mitchell <ja...@mac.com> wrote:
> > Let's not forget about the updates needed to support all of our uses
> > of svn:exterals. Whenever we branch or tag (it is really just a
> > copy), we'll need to fix any svn:externals to point to the tagged/
> > branched versions since this is not automatically done for us.
> >
> > I just updated this page:
> >
> > http://wiki.apache.org/struts/StrutsMaintenanceSvn
> >
> > ...scroll to the bottom section.
> >
> > --
> > James Mitchell
> > 678.910.8017
> >
> >
> >
> >
> > On Nov 15, 2005, at 8:27 AM, Ted Husted wrote:
> >
> > > I've been through Apps, and it's looking quite good now. There were
> > > only very minor fixes to the pages, everything seems to be working
> > > well.
> > >
> > > Many thanks to Wendy and James and everyone who's been working on the
> > > Maven builds. It's all come together very nicely. IMHO, the process is
> > > more accessible, and it will be much easier for people to get involved
> > > in the project, or get involved again after being away for a while.
> > >
> > > As to remaining steps, I think all we need to do is
> > >
> > > (1) Make a final pass on the documentation and configuration files, to
> > > be sure all is current with the release plan.
> > >
> > > (2) Rename struts-core as struts-action.
> > >
> > > (3) Finalize what we are going to do with #36794 - the CG lib
> > > DynaForm enhancements.
> > >
> > > (4) Final updates the release notes as to recent changes.
> > >
> > > (5) Set 1.3.0 tags for each subproject (ACTION_1_3_0, APPS_1_3_0,
> > > EL_1_3_0, ...) .
> > >
> > > (6) Assembly a ZIP archive of the respective JARs as the "Struts
> > > Action Framework Library".
> > >
> > > (7) Post for review
> > >
> > > As to (3), one option is to move the code to the Extras subproject. We
> > > might also want to consider if we want to move some other optional
> > > classes there too. One candidate might be
> > > [org.apache.struts.validator.ValidatorActionForm], which is the "path"
> > > attribute version of ValidatorForm.
> > >
> > > Release caveats are that we have two dependencies on non-GA code:
> > > Commons Validator and Commons Resources. Commons Resources is being
> > > used as part of the Extras subproject. All I did was build the dev
> > > code from a nighly buid and post the JAR in the Apache repository. Is
> > > anyone up for a Commons Resources release?
> > >
> > > These caveats would keep a 1.3.0 release of Action Framework and
> > > Extras from going GA, but I think we anticipate additional changes
> > > anyway, so I don't see that they should keep us from rolling it.
> > >
> > > -Ted.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: 1.3.0 Release - Next Steps
Posted by Ted Husted <te...@gmail.com>.
Is it even useful to tag a SVN repository for a release?
If we document the revision as of the release, then we can always go
back and branch on that revision later, or retrieve a snapshot of the
repository as of the release.
-Ted.
On 11/15/05, James Mitchell <ja...@mac.com> wrote:
> Let's not forget about the updates needed to support all of our uses
> of svn:exterals. Whenever we branch or tag (it is really just a
> copy), we'll need to fix any svn:externals to point to the tagged/
> branched versions since this is not automatically done for us.
>
> I just updated this page:
>
> http://wiki.apache.org/struts/StrutsMaintenanceSvn
>
> ...scroll to the bottom section.
>
> --
> James Mitchell
> 678.910.8017
>
>
>
>
> On Nov 15, 2005, at 8:27 AM, Ted Husted wrote:
>
> > I've been through Apps, and it's looking quite good now. There were
> > only very minor fixes to the pages, everything seems to be working
> > well.
> >
> > Many thanks to Wendy and James and everyone who's been working on the
> > Maven builds. It's all come together very nicely. IMHO, the process is
> > more accessible, and it will be much easier for people to get involved
> > in the project, or get involved again after being away for a while.
> >
> > As to remaining steps, I think all we need to do is
> >
> > (1) Make a final pass on the documentation and configuration files, to
> > be sure all is current with the release plan.
> >
> > (2) Rename struts-core as struts-action.
> >
> > (3) Finalize what we are going to do with #36794 - the CG lib
> > DynaForm enhancements.
> >
> > (4) Final updates the release notes as to recent changes.
> >
> > (5) Set 1.3.0 tags for each subproject (ACTION_1_3_0, APPS_1_3_0,
> > EL_1_3_0, ...) .
> >
> > (6) Assembly a ZIP archive of the respective JARs as the "Struts
> > Action Framework Library".
> >
> > (7) Post for review
> >
> > As to (3), one option is to move the code to the Extras subproject. We
> > might also want to consider if we want to move some other optional
> > classes there too. One candidate might be
> > [org.apache.struts.validator.ValidatorActionForm], which is the "path"
> > attribute version of ValidatorForm.
> >
> > Release caveats are that we have two dependencies on non-GA code:
> > Commons Validator and Commons Resources. Commons Resources is being
> > used as part of the Extras subproject. All I did was build the dev
> > code from a nighly buid and post the JAR in the Apache repository. Is
> > anyone up for a Commons Resources release?
> >
> > These caveats would keep a 1.3.0 release of Action Framework and
> > Extras from going GA, but I think we anticipate additional changes
> > anyway, so I don't see that they should keep us from rolling it.
> >
> > -Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 1.3.0 Release - Next Steps
Posted by Wendy Smoak <ws...@gmail.com>.
On 11/15/05, James Mitchell <ja...@mac.com> wrote:
> That would be a problem too because we would need a
> StrutsMaintenanceSvnCygwin, StrutsMainenanceSvnLinux.
You forgot Solaris. ;) I haven't found a problem using the
command-line instructions on Cygwin, so I doubt we'd need separate
instructions for each Unix-like type. Adding instructions for
TortoiseSVN should suffice *if* someone wants to write and maintain
them.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 1.3.0 Release - Next Steps
Posted by James Mitchell <ja...@mac.com>.
That would be a problem too because we would need a
StrutsMaintenanceSvnCygwin, StrutsMainenanceSvnLinux.
The notes I added are more of a guideline than a recipe.
--
James Mitchell
678.910.8017
Skpe: jmitchtx
On Nov 15, 2005, at 1:12 PM, Niall Pemberton wrote:
> The only problem with these notes (and some Ted added on that page)
> is that
> they're unix specific and don't mean alot to me. Maybe we need a
> could of
> generic sections for things like this and then some additional
> pages for
> different environments. I use TortoiseSVN in a windoze environment and
> achieving the same thing invloves "right clicking" on the tag/
> branch root
> directory, selecting properties from the context menu, selecting the
> "subversion" tab and then editing the "svn:externals" property.
>
> How about pages like "StrutsMaintenanceUnix" and
> "StrusMaintenanceTortoiseSVN" pages for specific examples?
>
> Niall
>
> ----- Original Message -----
> From: "James Mitchell" <ja...@mac.com>
> Sent: Tuesday, November 15, 2005 5:59 PM
>
>
>> Let's not forget about the updates needed to support all of our uses
>> of svn:exterals. Whenever we branch or tag (it is really just a
>> copy), we'll need to fix any svn:externals to point to the tagged/
>> branched versions since this is not automatically done for us.
>>
>> I just updated this page:
>>
>> http://wiki.apache.org/struts/StrutsMaintenanceSvn
>>
>> ...scroll to the bottom section.
>
>
>
> ---------------------------------------------------------------------
> 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: 1.3.0 Release - Next Steps
Posted by Wendy Smoak <ws...@gmail.com>.
On 11/15/05, Niall Pemberton <ni...@blueyonder.co.uk> wrote:
> The only problem with these notes (and some Ted added on that page) is that
> they're unix specific and don't mean alot to me.
Cygwin! I use TortoiseSVN, too, but sometimes it's easier to do
things at the command line.
I don't think anyone would object to adding instructions for how to do
things in other environments, though.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 1.3.0 Release - Next Steps
Posted by Niall Pemberton <ni...@blueyonder.co.uk>.
The only problem with these notes (and some Ted added on that page) is that
they're unix specific and don't mean alot to me. Maybe we need a could of
generic sections for things like this and then some additional pages for
different environments. I use TortoiseSVN in a windoze environment and
achieving the same thing invloves "right clicking" on the tag/branch root
directory, selecting properties from the context menu, selecting the
"subversion" tab and then editing the "svn:externals" property.
How about pages like "StrutsMaintenanceUnix" and
"StrusMaintenanceTortoiseSVN" pages for specific examples?
Niall
----- Original Message -----
From: "James Mitchell" <ja...@mac.com>
Sent: Tuesday, November 15, 2005 5:59 PM
> Let's not forget about the updates needed to support all of our uses
> of svn:exterals. Whenever we branch or tag (it is really just a
> copy), we'll need to fix any svn:externals to point to the tagged/
> branched versions since this is not automatically done for us.
>
> I just updated this page:
>
> http://wiki.apache.org/struts/StrutsMaintenanceSvn
>
> ...scroll to the bottom section.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 1.3.0 Release - Next Steps
Posted by James Mitchell <ja...@mac.com>.
Let's not forget about the updates needed to support all of our uses
of svn:exterals. Whenever we branch or tag (it is really just a
copy), we'll need to fix any svn:externals to point to the tagged/
branched versions since this is not automatically done for us.
I just updated this page:
http://wiki.apache.org/struts/StrutsMaintenanceSvn
...scroll to the bottom section.
--
James Mitchell
678.910.8017
On Nov 15, 2005, at 8:27 AM, Ted Husted wrote:
> I've been through Apps, and it's looking quite good now. There were
> only very minor fixes to the pages, everything seems to be working
> well.
>
> Many thanks to Wendy and James and everyone who's been working on the
> Maven builds. It's all come together very nicely. IMHO, the process is
> more accessible, and it will be much easier for people to get involved
> in the project, or get involved again after being away for a while.
>
> As to remaining steps, I think all we need to do is
>
> (1) Make a final pass on the documentation and configuration files, to
> be sure all is current with the release plan.
>
> (2) Rename struts-core as struts-action.
>
> (3) Finalize what we are going to do with #36794 - the CG lib
> DynaForm enhancements.
>
> (4) Final updates the release notes as to recent changes.
>
> (5) Set 1.3.0 tags for each subproject (ACTION_1_3_0, APPS_1_3_0,
> EL_1_3_0, ...) .
>
> (6) Assembly a ZIP archive of the respective JARs as the "Struts
> Action Framework Library".
>
> (7) Post for review
>
> As to (3), one option is to move the code to the Extras subproject. We
> might also want to consider if we want to move some other optional
> classes there too. One candidate might be
> [org.apache.struts.validator.ValidatorActionForm], which is the "path"
> attribute version of ValidatorForm.
>
> Release caveats are that we have two dependencies on non-GA code:
> Commons Validator and Commons Resources. Commons Resources is being
> used as part of the Extras subproject. All I did was build the dev
> code from a nighly buid and post the JAR in the Apache repository. Is
> anyone up for a Commons Resources release?
>
> These caveats would keep a 1.3.0 release of Action Framework and
> Extras from going GA, but I think we anticipate additional changes
> anyway, so I don't see that they should keep us from rolling it.
>
> -Ted.
>
> ---------------------------------------------------------------------
> 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: 1.3.0 Release - Next Steps
Posted by Niall Pemberton <ni...@blueyonder.co.uk>.
Thanks Ted :-)
From: "Ted Husted" <te...@gmail.com>
On 11/15/05, Niall Pemberton <ni...@blueyonder.co.uk> wrote:
> Validator 1.2.0 has only received 2 +1 votes so far - and so needs at
least
> one more before I can cut a release. Don Brown did alot of the Validator
> 1.2.0 work and I am expecting he will vote (hopefully +1), but hes away on
> vacation at the moment. Anyway until it gets another Jakarta PMC member /
> Commons Commiter to +1 it, its basically stuck in release candidate limbo.
Done.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 1.3.0 Release - Next Steps
Posted by Ted Husted <te...@gmail.com>.
On 11/15/05, Niall Pemberton <ni...@blueyonder.co.uk> wrote:
> Validator 1.2.0 has only received 2 +1 votes so far - and so needs at least
> one more before I can cut a release. Don Brown did alot of the Validator
> 1.2.0 work and I am expecting he will vote (hopefully +1), but hes away on
> vacation at the moment. Anyway until it gets another Jakarta PMC member /
> Commons Commiter to +1 it, its basically stuck in release candidate limbo.
Done.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 1.3.0 Release - Next Steps
Posted by Niall Pemberton <ni...@blueyonder.co.uk>.
----- Original Message -----
From: "Ted Husted" <te...@gmail.com>
Sent: Tuesday, November 15, 2005 1:27 PM
<snip>
Release caveats are that we have two dependencies on non-GA code:
Commons Validator and Commons Resources. Commons Resources is being
used as part of the Extras subproject. All I did was build the dev
code from a nighly buid and post the JAR in the Apache repository. Is
anyone up for a Commons Resources release?
These caveats would keep a 1.3.0 release of Action Framework and
Extras from going GA, but I think we anticipate additional changes
anyway, so I don't see that they should keep us from rolling it.
</snip>
Validator 1.2.0 has only received 2 +1 votes so far - and so needs at least
one more before I can cut a release. Don Brown did alot of the Validator
1.2.0 work and I am expecting he will vote (hopefully +1), but hes away on
vacation at the moment. Anyway until it gets another Jakarta PMC member /
Commons Commiter to +1 it, its basically stuck in release candidate limbo.
http://www.mail-archive.com/commons-dev%40jakarta.apache.org/msg69561.html
Niall
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org