Re: [VOTE] Release Struts Annotations 1.0.2

[Antonio Petrelli]

+1 (non binding)
Downloaded and installed the source, the Struts 2.0.9-SNAPSHOT compiles
fine.
I am sorry if I delayed the vote for Strus 2.0.8 this way ;-)

Antonio

2007/6/7, Rainer Hermanns <[EMAIL PROTECTED]>:


Struts Annotations 1.0.2 has been tagged and is available for testing
in the following Maven repository:

  http://people.apache.org/builds/struts/struts-annotations-1.0.2/m2-
staging-repository/

To test this build, temporarily add a repository to pom.xml or
settings.xml. The the struts-annotations dependency version
number in the Struts2 on branch STRUTS_2_0_X has already been altered
to "1.0.2".


struts-annotations-102-staging
Struts Annotations 1.0.2 Staging Repository
http://people.apache.org/builds/struts/struts-annotations-1.0.2/
m2-staging-repository/


This is a build-time dependency for Struts 2, and there is no
distribution assembly,
though source and javadoc jars are available in the Maven repo.

Once you have had a chance to test this build, please vote on whether
to release it to the central Maven repository.

-Rainer

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

Re: [S2] Releasing a plugin

[Frank W. Zammetti]

Ok Don, good enough, thanks.  I just wasn't sure if there was any sort 
of actual procedure in place.  Look for it to be up in the next day or 
two (just have some final checks to do).  And I'll definitely announce it.


Take care,
Frank

Don Brown wrote:

Just copy what others have done: add a page with your plugin docs, probably
using the page template that's available.  It wouldn't hurt to announce it
in user@ either.

Don

On 6/8/07, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:


Hi everyone... I'm just about finished putting together my first plugin,
allowing for usage of the DataVision reporting package with S2 (was a
great learning experience, and I'm pushing some folks at work to move to
S2 sooner than later, and I know I'm going to need this for one
project).  My question is about releasing it... I know there is the
plugin registry, and I'd like to put it up there, but I'm not sure the
procedure involved.  Can anyone provide some guidance?  Or should I just
post it someone else and announce it on @user?

TIA,
Frank

--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
AIM/Yahoo: fzammetti
MSN: [EMAIL PROTECTED]
Author of "Practical Ajax Projects With Java Technology"
  (2006, Apress, ISBN 1-59059-695-1)
and "JavaScript, DOM Scripting and Ajax Projects"
  (2007, Apress, ISBN 1-59059-816-4)
Java Web Parts - http://javawebparts.sourceforge.net
  Supplying the wheel, so you don't have to reinvent it!

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







No virus found in this incoming message.
Checked by AVG Free Edition. 
Version: 7.5.472 / Virus Database: 269.8.11/838 - Release Date: 6/7/2007 2:21 PM


--
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
AIM/Yahoo: fzammetti
MSN: [EMAIL PROTECTED]
Author of "Practical Ajax Projects With Java Technology"
 (2006, Apress, ISBN 1-59059-695-1)
and "JavaScript, DOM Scripting and Ajax Projects"
 (2007, Apress, ISBN 1-59059-816-4)
Java Web Parts - http://javawebparts.sourceforge.net
 Supplying the wheel, so you don't have to reinvent it!

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

Re: [S2] Releasing a plugin

[Don Brown]

Just copy what others have done: add a page with your plugin docs, probably
using the page template that's available.  It wouldn't hurt to announce it
in user@ either.

Don

On 6/8/07, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:


Hi everyone... I'm just about finished putting together my first plugin,
allowing for usage of the DataVision reporting package with S2 (was a
great learning experience, and I'm pushing some folks at work to move to
S2 sooner than later, and I know I'm going to need this for one
project).  My question is about releasing it... I know there is the
plugin registry, and I'd like to put it up there, but I'm not sure the
procedure involved.  Can anyone provide some guidance?  Or should I just
post it someone else and announce it on @user?

TIA,
Frank

--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
AIM/Yahoo: fzammetti
MSN: [EMAIL PROTECTED]
Author of "Practical Ajax Projects With Java Technology"
  (2006, Apress, ISBN 1-59059-695-1)
and "JavaScript, DOM Scripting and Ajax Projects"
  (2007, Apress, ISBN 1-59059-816-4)
Java Web Parts - http://javawebparts.sourceforge.net
  Supplying the wheel, so you don't have to reinvent it!

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

[S2] Releasing a plugin

[Frank W. Zammetti]

Hi everyone... I'm just about finished putting together my first plugin, 
allowing for usage of the DataVision reporting package with S2 (was a 
great learning experience, and I'm pushing some folks at work to move to 
S2 sooner than later, and I know I'm going to need this for one 
project).  My question is about releasing it... I know there is the 
plugin registry, and I'd like to put it up there, but I'm not sure the 
procedure involved.  Can anyone provide some guidance?  Or should I just 
post it someone else and announce it on @user?


TIA,
Frank

--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
AIM/Yahoo: fzammetti
MSN: [EMAIL PROTECTED]
Author of "Practical Ajax Projects With Java Technology"
 (2006, Apress, ISBN 1-59059-695-1)
and "JavaScript, DOM Scripting and Ajax Projects"
 (2007, Apress, ISBN 1-59059-816-4)
Java Web Parts - http://javawebparts.sourceforge.net
 Supplying the wheel, so you don't have to reinvent it!

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

Re: [S2] Merge from 2_0_X to trunk

[Musachy Barroso]

what is new on xwork 2.1?

musachy

On 6/7/07, Ted Husted <[EMAIL PROTECTED]> wrote:


On 6/7/07, Rainer Hermanns <[EMAIL PROTECTED]> wrote:
> I would volunteer as release manager for the 2.1.0 release.

:) Wow! We didn't scare you away! :)

Of course, a RM still needs all the help he or she can get, and the
number of tickets posted against 2.1.0 could still use another
volunteer's kind attention.


> Prior to a S2 2.1.0 release lots of issues need to be addressed on
> the xwork side.
> Since I am the release manager for xwork as well, I can follow up
> with the S2
> release as soon as xwork 2.1 is out.

Would the plan then be to keep Struts 2.0.x aligned with XWork 2.0.x,
and Struts 2.1.x with the new XWork 2.1.x?

-Ted.

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





--
"Hey you! Would you help me to carry the stone?" Pink Floyd

Re: [S2] Merge from 2_0_X to trunk

[Ted Husted]

On 6/7/07, Rainer Hermanns <[EMAIL PROTECTED]> wrote:

I would volunteer as release manager for the 2.1.0 release.


:) Wow! We didn't scare you away! :)

Of course, a RM still needs all the help he or she can get, and the
number of tickets posted against 2.1.0 could still use another
volunteer's kind attention.



Prior to a S2 2.1.0 release lots of issues need to be addressed on
the xwork side.
Since I am the release manager for xwork as well, I can follow up
with the S2
release as soon as xwork 2.1 is out.


Would the plan then be to keep Struts 2.0.x aligned with XWork 2.0.x,
and Struts 2.1.x with the new XWork 2.1.x?

-Ted.

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

Re: New consolidated zero-config/codebehind/component plugin

[Musachy Barroso]

This is cool, and I think it would be perfect to bring it into core, +1 for
it. Is there any documentation around for the components? The tests for them
seem to be empty.

regards
musachy

On 6/6/07, Brian Pontarelli <[EMAIL PROTECTED]> wrote:


Ted Husted wrote:
> On 5/30/07, Ted Husted <[EMAIL PROTECTED]> wrote:
>> At this point, we have three Confluence spaces going
>
> ... and the S2 Documentation wiki (WW) is the only one that requires a
> CLA on file.
>
I put up the SmartURLs plugin on the plugin registry and I'm hoping to
get the documentation started soon. The latest working version is in
SubVersion over at google code (http://code.google.com/p/smarturls-s2)
and the JavaDoc is available over there as well. If anyone has comments,
feedback, bugs, enhancements, let me know. And if we still want to move
this sucker into core, I'm down with that.

-bp

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





--
"Hey you! Would you help me to carry the stone?" Pink Floyd

Re: [VOTE] Release Struts Annotations 1.0.2

[Musachy Barroso]

+1, I've always been using the latest one, compiled from trunk, and it seems
to work fine.

musachy

On 6/7/07, Rainer Hermanns <[EMAIL PROTECTED]> wrote:


Struts Annotations 1.0.2 has been tagged and is available for testing
in the following Maven repository:

  http://people.apache.org/builds/struts/struts-annotations-1.0.2/m2-
staging-repository/

To test this build, temporarily add a repository to pom.xml or
settings.xml. The the struts-annotations dependency version
number in the Struts2 on branch STRUTS_2_0_X has already been altered
to "1.0.2".


struts-annotations-102-staging
Struts Annotations 1.0.2 Staging Repository
http://people.apache.org/builds/struts/struts-annotations-1.0.2/
m2-staging-repository/


This is a build-time dependency for Struts 2, and there is no
distribution assembly,
though source and javadoc jars are available in the Maven repo.

Once you have had a chance to test this build, please vote on whether
to release it to the central Maven repository.

-Rainer

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





--
"Hey you! Would you help me to carry the stone?" Pink Floyd

Re: [S2] [VOTE] Struts 2.0.8 Quality

[Wendy Smoak]

On 6/7/07, Rainer Hermanns <[EMAIL PROTECTED]> wrote:


Wendy,
thanks for reminding me,... Just called the vote :)


No problem.  (And apologies for misspelling your name!)

--
Wendy

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

Re: [S2] Merge from 2_0_X to trunk

[Rainer Hermanns]

Ted,

I would volunteer as release manager for the 2.1.0 release.

Prior to a S2 2.1.0 release lots of issues need to be addressed on  
the xwork side.
Since I am the release manager for xwork as well, I can follow up  
with the S2

release as soon as xwork 2.1 is out.

-Rainer

Am 07.06.2007 um 18:06 schrieb Ted Husted:


First, someone needs to review the 72 open tickets for 2.1.0 and
decide which of those really need to go into 2.1.0, and which should
be slated for sometime in 2.1.x.  At this point, I don't even know if
we have a release manager for 2.1.0. It's not something that I would
be able to do myself anytime soon.

-Ted.

On 6/7/07, Al Sutton <[EMAIL PROTECTED]> wrote:
Given your comments on datetimepicker on the users list, and the  
overhead of
having two branches, I personally think it's probably time to  
focus solely
on 2.1 and put 2.0 into a maintainence mode whereby only critical  
bug fixes

go in.

-Original Message-
From: Musachy Barroso [mailto:[EMAIL PROTECTED]
Sent: 07 June 2007 14:01
To: Struts Developers List
Subject: Re: [S2] Merge from 2_0_X to trunk

Yes they should! As a matter of fact I wanted to ask, are we going  
to have a
2.0.9 release? I thought we were going to jump into 2.1 after  
2.0.8, given
that 2.1 is almost 2.0.8 + ajax refactoring, and the ajax part is  
done (few

bugs still open).

musachy

On 6/7/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
>
> Hi all!
> I noticed that, prior to the 2_0_8 tagging, some changes have been
> made to STRUTS_2_0_X and not ported to the trunk.
> Should they be merged to the trunk, or is there a reason for not  
doing it?

>
> Ciao
> Antonio
>
>  
-

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


--
"Hey you! Would you help me to carry the stone?" Pink Floyd


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





--
HTH, Ted 

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




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

Re: [S2] [VOTE] Struts 2.0.8 Quality

[Rainer Hermanns]

Wendy,
thanks for reminding me,... Just called the vote :)

Rainer
Am 07.06.2007 um 15:08 schrieb Wendy Smoak:


On 6/7/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:

2007/6/6, Rainer Hermanns <[EMAIL PROTECTED]>:
>  [X] Leave at test build

-1 (non binding, I am only a committer) to a release, because Struts
2.0.8 depends on Struts Annotations 1.0.2 that is not released.
In fact there isn't any release of Struts Annotations, how's that?


It's staged here, but should probably have a separate vote as it
wasn't mentioned in this one:

http://people.apache.org/builds/struts/struts-annotations-1.0.2/

(Ranier mentioned this when he closed
https://issues.apache.org/struts/browse/WW-1943.)

--
Wendy

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




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

Re: [S2] Merge from 2_0_X to trunk

[Rainer Hermanns]

Antonio,

my latest changes will be ported over to trunk either today or tomorrow.
These changes  were only important for the release assembly, but have  
no impact on functionality.


Rainer

Am 07.06.2007 um 12:55 schrieb Antonio Petrelli:


Hi all!
I noticed that, prior to the 2_0_8 tagging, some changes have been
made to STRUTS_2_0_X and not ported to the trunk.
Should they be merged to the trunk, or is there a reason for not  
doing it?


Ciao
Antonio

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




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

Re: [S2] [VOTE] Struts 2.0.8 Quality

[Rainer Hermanns]

Antonio,

as Musachy pointed out, the struts annotations are only a build time  
dependency.
Regarding the release, I just called a vote for Struts Annotations  
1.0.2.


Rainer

> [X] Leave at test build
>
> -1 (non binding, I am only a committer) to a release, because Struts
> 2.0.8 depends on Struts Annotations 1.0.2 that is not released.
> in fact there isn't any release of Struts Annotations, how's that?




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

[VOTE] Release Struts Annotations 1.0.2

[Rainer Hermanns]

Struts Annotations 1.0.2 has been tagged and is available for testing
in the following Maven repository:

 http://people.apache.org/builds/struts/struts-annotations-1.0.2/m2- 
staging-repository/


To test this build, temporarily add a repository to pom.xml or
settings.xml. The the struts-annotations dependency version
number in the Struts2 on branch STRUTS_2_0_X has already been altered  
to "1.0.2".



struts-annotations-102-staging
Struts Annotations 1.0.2 Staging Repository
http://people.apache.org/builds/struts/struts-annotations-1.0.2/ 
m2-staging-repository/



This is a build-time dependency for Struts 2, and there is no  
distribution assembly,

though source and javadoc jars are available in the Maven repo.

Once you have had a chance to test this build, please vote on whether
to release it to the central Maven repository.

-Rainer

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

Re: [S2] Merge from 2_0_X to trunk

[Musachy Barroso]

Release Manager wanted for 2.1, anyone? :)

musachy

On 6/7/07, Ted Husted <[EMAIL PROTECTED]> wrote:


First, someone needs to review the 72 open tickets for 2.1.0 and
decide which of those really need to go into 2.1.0, and which should
be slated for sometime in 2.1.x.  At this point, I don't even know if
we have a release manager for 2.1.0. It's not something that I would
be able to do myself anytime soon.

-Ted.

On 6/7/07, Al Sutton <[EMAIL PROTECTED]> wrote:
> Given your comments on datetimepicker on the users list, and the
overhead of
> having two branches, I personally think it's probably time to focus
solely
> on 2.1 and put 2.0 into a maintainence mode whereby only critical bug
fixes
> go in.
>
> -Original Message-
> From: Musachy Barroso [mailto:[EMAIL PROTECTED]
> Sent: 07 June 2007 14:01
> To: Struts Developers List
> Subject: Re: [S2] Merge from 2_0_X to trunk
>
> Yes they should! As a matter of fact I wanted to ask, are we going to
have a
> 2.0.9 release? I thought we were going to jump into 2.1 after 2.0.8,
given
> that 2.1 is almost 2.0.8 + ajax refactoring, and the ajax part is done
(few
> bugs still open).
>
> musachy
>
> On 6/7/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
> >
> > Hi all!
> > I noticed that, prior to the 2_0_8 tagging, some changes have been
> > made to STRUTS_2_0_X and not ported to the trunk.
> > Should they be merged to the trunk, or is there a reason for not doing
it?
> >
> > Ciao
> > Antonio
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED] For
> > additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> "Hey you! Would you help me to carry the stone?" Pink Floyd
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
HTH, Ted 

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





--
"Hey you! Would you help me to carry the stone?" Pink Floyd

Re: [S2] Merge from 2_0_X to trunk

[Ted Husted]

First, someone needs to review the 72 open tickets for 2.1.0 and
decide which of those really need to go into 2.1.0, and which should
be slated for sometime in 2.1.x.  At this point, I don't even know if
we have a release manager for 2.1.0. It's not something that I would
be able to do myself anytime soon.

-Ted.

On 6/7/07, Al Sutton <[EMAIL PROTECTED]> wrote:

Given your comments on datetimepicker on the users list, and the overhead of
having two branches, I personally think it's probably time to focus solely
on 2.1 and put 2.0 into a maintainence mode whereby only critical bug fixes
go in.

-Original Message-
From: Musachy Barroso [mailto:[EMAIL PROTECTED]
Sent: 07 June 2007 14:01
To: Struts Developers List
Subject: Re: [S2] Merge from 2_0_X to trunk

Yes they should! As a matter of fact I wanted to ask, are we going to have a
2.0.9 release? I thought we were going to jump into 2.1 after 2.0.8, given
that 2.1 is almost 2.0.8 + ajax refactoring, and the ajax part is done (few
bugs still open).

musachy

On 6/7/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
>
> Hi all!
> I noticed that, prior to the 2_0_8 tagging, some changes have been
> made to STRUTS_2_0_X and not ported to the trunk.
> Should they be merged to the trunk, or is there a reason for not doing it?
>
> Ciao
> Antonio
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED] For
> additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
"Hey you! Would you help me to carry the stone?" Pink Floyd


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





--
HTH, Ted 

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

Re: [S2] Merge from 2_0_X to trunk

[Ted Husted]

The key question is whether someone is ready to roll a 2.1.0 release.
Once that happens, it makes sense to put the prior minor release
series into "maintenance mode". But, until that happens, it makes
equal sense to keep pumping out 2.0.x releases with any likely
changes. We don't want to fall behind on the 2.0.x branch if the 2.1.0
branch is not ready-to-go.

-Ted.

On 6/7/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:

Yes they should! As a matter of fact I wanted to ask, are we going to have a
2.0.9 release? I thought we were going to jump into 2.1 after 2.0.8, given
that 2.1 is almost 2.0.8 + ajax refactoring, and the ajax part is done (few
bugs still open).

musachy

On 6/7/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
>
> Hi all!
> I noticed that, prior to the 2_0_8 tagging, some changes have been
> made to STRUTS_2_0_X and not ported to the trunk.
> Should they be merged to the trunk, or is there a reason for not doing it?
>
> Ciao
> Antonio
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
"Hey you! Would you help me to carry the stone?" Pink Floyd




--
HTH, Ted 

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

RE: [S2] Merge from 2_0_X to trunk

[Al Sutton]

Given your comments on datetimepicker on the users list, and the overhead of
having two branches, I personally think it's probably time to focus solely
on 2.1 and put 2.0 into a maintainence mode whereby only critical bug fixes
go in.

-Original Message-
From: Musachy Barroso [mailto:[EMAIL PROTECTED] 
Sent: 07 June 2007 14:01
To: Struts Developers List
Subject: Re: [S2] Merge from 2_0_X to trunk

Yes they should! As a matter of fact I wanted to ask, are we going to have a
2.0.9 release? I thought we were going to jump into 2.1 after 2.0.8, given
that 2.1 is almost 2.0.8 + ajax refactoring, and the ajax part is done (few
bugs still open).

musachy

On 6/7/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
>
> Hi all!
> I noticed that, prior to the 2_0_8 tagging, some changes have been 
> made to STRUTS_2_0_X and not ported to the trunk.
> Should they be merged to the trunk, or is there a reason for not doing it?
>
> Ciao
> Antonio
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
"Hey you! Would you help me to carry the stone?" Pink Floyd


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

Re: [S2] [VOTE] Struts 2.0.8 Quality

[Wendy Smoak]

On 6/7/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:

2007/6/6, Rainer Hermanns <[EMAIL PROTECTED]>:
>  [X] Leave at test build

-1 (non binding, I am only a committer) to a release, because Struts
2.0.8 depends on Struts Annotations 1.0.2 that is not released.
In fact there isn't any release of Struts Annotations, how's that?


It's staged here, but should probably have a separate vote as it
wasn't mentioned in this one:

http://people.apache.org/builds/struts/struts-annotations-1.0.2/

(Ranier mentioned this when he closed
https://issues.apache.org/struts/browse/WW-1943.)

--
Wendy

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

Re: [S2] Merge from 2_0_X to trunk

[Musachy Barroso]

Yes they should! As a matter of fact I wanted to ask, are we going to have a
2.0.9 release? I thought we were going to jump into 2.1 after 2.0.8, given
that 2.1 is almost 2.0.8 + ajax refactoring, and the ajax part is done (few
bugs still open).

musachy

On 6/7/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:


Hi all!
I noticed that, prior to the 2_0_8 tagging, some changes have been
made to STRUTS_2_0_X and not ported to the trunk.
Should they be merged to the trunk, or is there a reason for not doing it?

Ciao
Antonio

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





--
"Hey you! Would you help me to carry the stone?" Pink Floyd

Re: [S2] [VOTE] Struts 2.0.8 Quality

[Musachy Barroso]

Struts annotations is a build time dependency. This was discussed before but
I can't remember the final outcome. In any case, we could just release S2
annotations (hasn't changed in some time).

musachy

On 6/7/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:


2007/6/6, Rainer Hermanns <[EMAIL PROTECTED]>:
>  [X] Leave at test build

-1 (non binding, I am only a committer) to a release, because Struts
2.0.8 depends on Struts Annotations 1.0.2 that is not released.
In fact there isn't any release of Struts Annotations, how's that?

Antonio

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





--
"Hey you! Would you help me to carry the stone?" Pink Floyd

Re: Possible problem with 2.0.8

[Antonio Petrelli]

2007/6/7, Al Sutton <[EMAIL PROTECTED]>:


Struts 2.0.8 doesn't include tiles-jsp-2.0.3 which means that none of the
tiles jsp tags are available.

If the -core & -api jars are included the -jsp jar go in as well to avoid
users being left in a situation where they run the risk of installing all
the jars from whatever newest version of tiles is available (which may not
be compatible with 2.0.8), or they have to hunt down the 2.0.3 tiles
distribution which has already dissapeared from the front page of
tiles.apache.org (and I couldn't find it on the download pages either :().




In fact the tiles-jsp jar is not included as a dependency in the assembly
module, while tiles-core and tiles-api are included as transitive
dependencies (from the struts2-tiles plugin).
the tiles-jsp jar must be included explicitly.

About Tiles previous releases, thanks for the notification, I will add a
JIRA issue for Tiles :-)

Antonio

Possible problem with 2.0.8

[Al Sutton]

Struts 2.0.8 doesn't include tiles-jsp-2.0.3 which means that none of the
tiles jsp tags are available. 
 
If the -core & -api jars are included the -jsp jar go in as well to avoid
users being left in a situation where they run the risk of installing all
the jars from whatever newest version of tiles is available (which may not
be compatible with 2.0.8), or they have to hunt down the 2.0.3 tiles
distribution which has already dissapeared from the front page of
tiles.apache.org (and I couldn't find it on the download pages either :().

[S2] Merge from 2_0_X to trunk

[Antonio Petrelli]

Hi all!
I noticed that, prior to the 2_0_8 tagging, some changes have been
made to STRUTS_2_0_X and not ported to the trunk.
Should they be merged to the trunk, or is there a reason for not doing it?

Ciao
Antonio

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

Re: [S2] [VOTE] Struts 2.0.8 Quality

[Antonio Petrelli]

2007/6/6, Rainer Hermanns <[EMAIL PROTECTED]>:

 [X] Leave at test build


-1 (non binding, I am only a committer) to a release, because Struts
2.0.8 depends on Struts Annotations 1.0.2 that is not released.
In fact there isn't any release of Struts Annotations, how's that?

Antonio

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

RE: [S2] 2.0.8 library versions

[Al Sutton]

Whats the preference, a patch per library, or one patch to bind them? :) 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ted
Husted
Sent: 07 June 2007 00:50
To: Struts Developers List
Subject: Re: [S2] 2.0.8 library versions

Update the Maven configuration to reference the new releases, build the
framework locally, and try it with your own application. If it passes,
submit to JIRA a patch to the Maven configuration. For extra credit,
play-test the example applications as well. :)

 * http://struts.apache.org/2.x/docs/building-with-maven.html

HTH, Ted.

On 6/6/07, Al Sutton <[EMAIL PROTECTED]> wrote:
> There are a few "old" libraries in the 2.0.8 release, should there be 
> an effort to upgrade them?, and if so whats the best way of doing it?
>
> The libraries in question are;
>
> antlr (2.7.2 shipped, 2.7.7 latest in 2.7 branch, theres also a v3 
> branch) commons-beanutils (1.6 shipped, 1.7.0 is the latest) 
> commons-logging (1.0.4 shipped, 1.1 is the latest) commons-validator 
> (1.3.0 shipped, 1.3.1 is the latest) freemarker (2.3.8 shipped, 2.3.10 
> is the latest)
>
> and of course there is now tiles 2.0.4 :)
>
> Al.

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



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