You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Don Brown <mr...@twdata.org> on 2006/03/24 02:54:07 UTC
Action 2 has begun!
The WebWork team has successfully completed WebWork 2.2.2, which was
immediately imported into the WebWork 2 Incubator podling. Here is the
current status:
- The code is at https://svn.apache.org/repos/asf/incubator/webwork2
- All but Toby have Apache accounts and karma (Toby has sent in his CLA
so we are awaiting its confirmation)
- A Struts JIRA instance is in the process of being created. It will
initially be populated with existing WebWork tickets, however in time,
the existing Struts Bugzilla tickets will be migrated as well.
- You can follow the current Incubator status at
http://incubator.apache.org/projects/webwork2
- New Action 2 modules (legacy and apps) will be developed in the
sandbox under 'action2'
- The WebWork 2 documentation and site will remain up and active until
we can identify an Apache resource (hopefully a new Confluence instance)
for migration
At this point, I encourage everyone to jump in and start transforming
WebWork 2 to Action 2. From a code perspective, we'll need to
accomplish the following tasks:
- Move the package and project identifiers to Action 2
(org.apache.struts.action2)
- Identify dependencies that use incompatible licenses and either:
1. Convince the project to dual license or switch to a BSD-compatible
2. Replace the dependency with one that has a more favorable license
3. Write out the dependency
- Continue to develop the code
If you are a Struts committer and do not have karma, let me know and
I'll add you to the proposal and request webwork karma for you. If you
are a WebWork committer who is not on the proposal, I'm looking into the
process of how to add more external developers. In the meantime, I
suggest you either feed the patch through an existing committer, or file
a bug ticket once our JIRA gets stood up.
Congratulations to the WebWork team for a successful release and here's
to a successful migration and Action 2 project!
Don
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Action 2 has begun!
Posted by Greg Reddin <gr...@apache.org>.
Congratulations! Great job, guys!
Greg
On Mar 23, 2006, at 7:54 PM, Don Brown wrote:
> The WebWork team has successfully completed WebWork 2.2.2, which
> was immediately imported into the WebWork 2 Incubator podling.
> Here is the current status:
> - The code is at https://svn.apache.org/repos/asf/incubator/webwork2
> - All but Toby have Apache accounts and karma (Toby has sent in his
> CLA so we are awaiting its confirmation)
> - A Struts JIRA instance is in the process of being created. It
> will initially be populated with existing WebWork tickets, however
> in time, the existing Struts Bugzilla tickets will be migrated as
> well.
> - You can follow the current Incubator status at http://
> incubator.apache.org/projects/webwork2
> - New Action 2 modules (legacy and apps) will be developed in the
> sandbox under 'action2'
> - The WebWork 2 documentation and site will remain up and active
> until we can identify an Apache resource (hopefully a new
> Confluence instance) for migration
>
> At this point, I encourage everyone to jump in and start
> transforming WebWork 2 to Action 2. From a code perspective, we'll
> need to accomplish the following tasks:
> - Move the package and project identifiers to Action 2
> (org.apache.struts.action2)
> - Identify dependencies that use incompatible licenses and either:
> 1. Convince the project to dual license or switch to a BSD-
> compatible
> 2. Replace the dependency with one that has a more favorable license
> 3. Write out the dependency
> - Continue to develop the code
>
> If you are a Struts committer and do not have karma, let me know
> and I'll add you to the proposal and request webwork karma for
> you. If you are a WebWork committer who is not on the proposal,
> I'm looking into the process of how to add more external
> developers. In the meantime, I suggest you either feed the patch
> through an existing committer, or file a bug ticket once our JIRA
> gets stood up.
>
> Congratulations to the WebWork team for a successful release and
> here's to a successful migration and Action 2 project!
>
> Don
>
> ---------------------------------------------------------------------
> 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: Action 2 has begun!
Posted by Don Brown <mr...@twdata.org>.
My plan is to bundle Action 1 with Action 2 for distribution, and in
fact, the Action 2 build will depend on Action 1 already for the
migration library. The Action 2 classes are in a different package,
which should help them run side by side. I'm hoping to take it further
than make it possible to share messages and things like validation
configuration files between the two. We'll see how that pans out, however.
To clarify, Action 2 will not _merge_ with Action1 so they will remain
their own branch, build, etc., so I'm talking about the Action 2
distribution file including Action 1 jars.
Don
Paul Benedict wrote:
>>> The Action 1 migration is probably the
>>> most important part of Action 2, at least in the beginning. We need to
>>> make it easy and obvious for developers to move.
>>>
>
> Don, is Action2 going to include ALL the classes from Struts
> 1.3 (same package name) so that I can run action2 and action1
> in one framework? Or is the plan to tell developers to run two frameworks
> in one application?
>
> Paul
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> ---------------------------------------------------------------------
> 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: Action 2 has begun!
Posted by Paul Benedict <pa...@yahoo.com>.
>> The Action 1 migration is probably the
>> most important part of Action 2, at least in the beginning. We need to
>> make it easy and obvious for developers to move.
Don, is Action2 going to include ALL the classes from Struts
1.3 (same package name) so that I can run action2 and action1
in one framework? Or is the plan to tell developers to run two frameworks
in one application?
Paul
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Action 2 has begun!
Posted by Don Brown <mr...@twdata.org>.
Paul Benedict wrote:
> I am very excited about this. I have two questions:
>
> 1. What is the plan for the large amount of bugzilla tickets
> that are against the 1.x branch? Since Comitters are a Limited
> Resource, it will be impossible to complete them all and maintain
> the 1.x branch, if 1.x is still going to be enhanced.
>
Can't speak for other committers, but I'll be spending most/all of my
time getting Action 2 up and running. I still have Action 1 apps that I
won't be able to migrate, so I'm sure I'll help out there every now and
then. Of course, it is my goal that Action 2 is so great, people forget
all improving about Action 1... ;)
> 2. What can non-commiters do to help?
>
Same things committers do, only you'll have to funnel patches through
another committer and/or tickets. The WebWork 2 JIRA has a ton of
tickets soon to be migrated, giving more sources of inspiration.
Probably the most useful thing now is to help identify how we can best
assist Action 1 developers looking to migrate both their knowledge and
code to Action 2. For example, tutorials, conversion tools,
commons-validator support, etc. The Action 1 migration is probably the
most important part of Action 2, at least in the beginning. We need to
make it easy and obvious for developers to move.
Don
> Paul
>
> --- Don Brown <mr...@twdata.org> wrote:
>
>
>> The WebWork team has successfully completed WebWork 2.2.2, which was
>> immediately imported into the WebWork 2 Incubator podling. Here is the
>> current status:
>> - The code is at https://svn.apache.org/repos/asf/incubator/webwork2
>> - All but Toby have Apache accounts and karma (Toby has sent in his CLA
>> so we are awaiting its confirmation)
>> - A Struts JIRA instance is in the process of being created. It will
>> initially be populated with existing WebWork tickets, however in time,
>> the existing Struts Bugzilla tickets will be migrated as well.
>> - You can follow the current Incubator status at
>> http://incubator.apache.org/projects/webwork2
>> - New Action 2 modules (legacy and apps) will be developed in the
>> sandbox under 'action2'
>> - The WebWork 2 documentation and site will remain up and active until
>> we can identify an Apache resource (hopefully a new Confluence instance)
>> for migration
>>
>> At this point, I encourage everyone to jump in and start transforming
>> WebWork 2 to Action 2. From a code perspective, we'll need to
>> accomplish the following tasks:
>> - Move the package and project identifiers to Action 2
>> (org.apache.struts.action2)
>> - Identify dependencies that use incompatible licenses and either:
>> 1. Convince the project to dual license or switch to a BSD-compatible
>> 2. Replace the dependency with one that has a more favorable license
>> 3. Write out the dependency
>> - Continue to develop the code
>>
>> If you are a Struts committer and do not have karma, let me know and
>> I'll add you to the proposal and request webwork karma for you. If you
>> are a WebWork committer who is not on the proposal, I'm looking into the
>> process of how to add more external developers. In the meantime, I
>> suggest you either feed the patch through an existing committer, or file
>> a bug ticket once our JIRA gets stood up.
>>
>> Congratulations to the WebWork team for a successful release and here's
>> to a successful migration and Action 2 project!
>>
>> Don
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> ---------------------------------------------------------------------
> 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: Action 2 has begun!
Posted by Paul Benedict <pa...@yahoo.com>.
I am very excited about this. I have two questions:
1. What is the plan for the large amount of bugzilla tickets
that are against the 1.x branch? Since Comitters are a Limited
Resource, it will be impossible to complete them all and maintain
the 1.x branch, if 1.x is still going to be enhanced.
2. What can non-commiters do to help?
Paul
--- Don Brown <mr...@twdata.org> wrote:
> The WebWork team has successfully completed WebWork 2.2.2, which was
> immediately imported into the WebWork 2 Incubator podling. Here is the
> current status:
> - The code is at https://svn.apache.org/repos/asf/incubator/webwork2
> - All but Toby have Apache accounts and karma (Toby has sent in his CLA
> so we are awaiting its confirmation)
> - A Struts JIRA instance is in the process of being created. It will
> initially be populated with existing WebWork tickets, however in time,
> the existing Struts Bugzilla tickets will be migrated as well.
> - You can follow the current Incubator status at
> http://incubator.apache.org/projects/webwork2
> - New Action 2 modules (legacy and apps) will be developed in the
> sandbox under 'action2'
> - The WebWork 2 documentation and site will remain up and active until
> we can identify an Apache resource (hopefully a new Confluence instance)
> for migration
>
> At this point, I encourage everyone to jump in and start transforming
> WebWork 2 to Action 2. From a code perspective, we'll need to
> accomplish the following tasks:
> - Move the package and project identifiers to Action 2
> (org.apache.struts.action2)
> - Identify dependencies that use incompatible licenses and either:
> 1. Convince the project to dual license or switch to a BSD-compatible
> 2. Replace the dependency with one that has a more favorable license
> 3. Write out the dependency
> - Continue to develop the code
>
> If you are a Struts committer and do not have karma, let me know and
> I'll add you to the proposal and request webwork karma for you. If you
> are a WebWork committer who is not on the proposal, I'm looking into the
> process of how to add more external developers. In the meantime, I
> suggest you either feed the patch through an existing committer, or file
> a bug ticket once our JIRA gets stood up.
>
> Congratulations to the WebWork team for a successful release and here's
> to a successful migration and Action 2 project!
>
> Don
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org