Branch has been renamed, below commands to update your local copy:
git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a
sob., 30 lis 2024 o 00:31 Kusal Kithul-Godage
napisał(a):
>
> Sounds good
>
> On Fri, Nov 29, 2024 at 8:06 PM Lukasz Lenart
pon., 9 gru 2024 o 15:37 Orifhon Zunnunov napisał(a):
> Is there a target GA release date for Struts 7 ?
No, but except this issue [1] we are ready to prepare the first release
[1] https://issues.apache.org/jira/browse/INFRA-26325
Cheers
Lukasz
Hi folks,
Is there a target GA release date for Struts 7 ?
--
Best Regards
Orif
Sounds good
On Fri, Nov 29, 2024 at 8:06 PM Lukasz Lenart wrote:
>
> Struts 6.7.0 is out, I'm going to cut off a new release/struts-6-7-x
> branch, then merge Struts 7 PR into master. Any objections?
>
> pon., 18 lis 2024 o 08:12 Lukasz Lenart napisał(a):
> >
> > Thanks Kusal, you are right!
> >
Struts 6.7.0 is out, I'm going to cut off a new release/struts-6-7-x
branch, then merge Struts 7 PR into master. Any objections?
pon., 18 lis 2024 o 08:12 Lukasz Lenart napisał(a):
>
> Thanks Kusal, you are right!
>
> pon., 18 lis 2024 o 02:00 Kusal Kithul-Godage
> napisał(a):
> >
> > I'm concer
Thanks Kusal, you are right!
pon., 18 lis 2024 o 02:00 Kusal Kithul-Godage
napisał(a):
>
> I'm concerned it will do more harm than good. With the release of
> Struts 6.7 we have a decent upgrade path as most
> Actions/Interceptors/Results can now be made forwards compatible with
> 7.0. It leaves
I'm concerned it will do more harm than good. With the release of
Struts 6.7 we have a decent upgrade path as most
Actions/Interceptors/Results can now be made forwards compatible with
7.0. It leaves limited additional work when upgrading to 7.0. By
renaming the packages again we'd be breaking that
niedz., 17 lis 2024 o 12:00 Kusal Kithul-Godage
napisał(a):
>
> Curious what the use case for having both Struts 6 and 7 in the same
> WAR would be?
In some cases you must rewrite part of your actions and this might
help by running two versions of the framework in parallel. It's one of
the strate
Curious what the use case for having both Struts 6 and 7 in the same
WAR would be?
On Sun, Nov 17, 2024 at 8:30 PM Lukasz Lenart wrote:
>
> I'm going to prepare a test build of Struts 6.7 and I wonder if we
> shouldn't use "org.apache.struts7" as a base package name for Struts 7
> to allow two ve
I'm going to prepare a test build of Struts 6.7 and I wonder if we
shouldn't use "org.apache.struts7" as a base package name for Struts 7
to allow two versions of the framework to coexist in one war archive.
Does that make sense?
śr., 6 lis 2024 o 11:10 Kusal Kithul-Godage
napisał(a):
>
> Yep sou
Yep sounds good to me
On Wed, Nov 6, 2024 at 7:56 PM Lukasz Lenart wrote:
>
> Thanks, I think we are good to release Struts 6.7 as there is a lot of
> changes which should help in migration into Struts 7
>
> pon., 4 lis 2024 o 02:07 Kusal Kithul-Godage
> napisał(a):
> >
> > Actually, nevermind t
Thanks, I think we are good to release Struts 6.7 as there is a lot of
changes which should help in migration into Struts 7
pon., 4 lis 2024 o 02:07 Kusal Kithul-Godage
napisał(a):
>
> Actually, nevermind that last message, it's more complicated than I
> anticipated
>
> On Mon, Nov 4, 2024 at 11
Actually, nevermind that last message, it's more complicated than I anticipated
On Mon, Nov 4, 2024 at 11:35 AM Kusal Kithul-Godage
wrote:
>
> Also, I'm going to create 1 more deprecation PR for Struts 6.7 to
> provide a couple more replacement APIs.
>
> On Mon, Nov 4, 2024 at 12:48 AM Lukasz Len
Also, I'm going to create 1 more deprecation PR for Struts 6.7 to
provide a couple more replacement APIs.
On Mon, Nov 4, 2024 at 12:48 AM Lukasz Lenart wrote:
>
> I'm going to release a new milestone - M10, hopefully the last one.
> Also I want to create a dedicated branch "release/struts-6-7-x"
Sounds good. Hmm maybe merge [1] then recreate 'release/struts-7-0-x'
during the final 7.0 release? And then increment master to
7.1.0-SNAPSHOT
On Mon, Nov 4, 2024 at 12:48 AM Lukasz Lenart wrote:
>
> I'm going to release a new milestone - M10, hopefully the last one.
> Also I want to create a de
I'm going to release a new milestone - M10, hopefully the last one.
Also I want to create a dedicated branch "release/struts-6-7-x" and
use it to maintain Struts 6.
Not sure what to do with the master branch, merge [1] and use it to
support Struts 7? Or rather ignore (or remove) and use
"release/st
I upgrades struts-examples to use Struts 7 M9 and discovered issues
with @StrutsParameter
https://issues.apache.org/jira/browse/WW-5468
sob., 5 paź 2024 o 15:54 Lukasz Lenart napisał(a):
>
> pt., 27 wrz 2024 o 10:46 Johannes Geppert napisał(a):
> >
> > Thanks, Lukasz! Looking forward to seeing t
pt., 27 wrz 2024 o 10:46 Johannes Geppert napisał(a):
>
> Thanks, Lukasz! Looking forward to seeing the next release.
>
> Will this issue be part of the next release?
> https://issues.apache.org/jira/browse/WW-5452
Looking into it right now.
Another thing, I opt to deprecate the current Sitemesh
Thanks, Lukasz! Looking forward to seeing the next release.
Will this issue be part of the next release?
https://issues.apache.org/jira/browse/WW-5452
Johannes
#
web: https://www.jgeppert.com
Am Di., 24. Sept. 2024 um 08:11 Uhr schrieb Lukasz Len
This is the last PR [1] I want to merge into Struts 6.x (and probably
release 6.6.1), then I will reverse merge the master into Struts 7
branch, and apply this PR [2] with renaming packages and I think we
are good to go :)
[1] https://github.com/apache/struts/pull/1060
[2] https://github.com/apach
No objections here.
Thanks,
Burton
-- Original Message --
From "Lukasz Lenart"
To "Struts Developers List"
Date 9/2/2024 2:20:28 AM
Subject Struts 7 release plan
Hi,
I would like to release Struts 7 soon (there are a few outstanding
issues I would like to address first) and switch
21 matches
Mail list logo
