+1 on that. I just need to update the compressed javascripts which I
will do tomorrow.
By the way I forgot to bring this up, the compressed javascript
files(custom Dojo build) is not built using maven, currently I build
them on my machine and commit them, does anybody know how to automate
that?
Agreed, I'd like to see us pushing the 2.1 trunk more. If nothing
else, it will make a nice beta.
Don
On 8/22/07, Ted Husted <[EMAIL PROTECTED]> wrote:
> There's always more that we want to do, but is there anything so
> unstable in the HEAD that we couldn't go a head and release a 2.1.0
> build
Actually, plugins already have a robust, tested versioning and
dependency management system - Maven 2. Since Struts 2 plugins are
built-time resources, their version and what versions they require are
specified in the pom.xml and managed by Maven 2. If you want to use a
Struts 2 plugin that requi
There's always more that we want to do, but is there anything so
unstable in the HEAD that we couldn't go a head and release a 2.1.0
build?
-Ted.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
I think the tags are the main problem, specially after the Dojo refactoring.
musachy
On 8/21/07, Ted Husted <[EMAIL PROTECTED]> wrote:
> We never really branched the Struts 1 documentation. When a feature
> applied to a later release, we just said "Since Struts 1.2.9, "
> and kept on going.
>
We never really branched the Struts 1 documentation. When a feature
applied to a later release, we just said "Since Struts 1.2.9, "
and kept on going.
I'd suggest that we try and do the same with the Struts 2 docs. If a
section or a page only applies to Struts 2.1.0 (the head), we just say
"Si
Does anybody have anything about removing the validation code from the
workflow interceptor?
This could potentially break compatibility for users that are
exploiting this "feature" and do not have the validation interceptor
on their stack.
https://issues.apache.org/struts/browse/WW-2072
musachy
What's the status for this? Is it possible to "branch" the wiki, or do
we create new pages and "deprecate" the old ones?
Nils-H
On 8/2/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:
> I think it would be appropriate for 2.1 vs 2.0.x, +1 for it.
>
> musachy
>
> On 8/2/07, Don Brown <[EMAIL PROTECT
If someone is good enough to support a plugin, then they should also be good
enough to support Struts proper too.
In this line of thinking, it may good to outsource the lesser plugins into
GoogleCode (or whatever). If any plugins gain enough traction with outside
committers, perhaps then you do th
Oooh, good thinking! I mean on the minimum version check thing.
On Tue Aug 21 14:38 , 'Ted Husted' <[EMAIL PROTECTED]> sent:
>On 8/21/07, Ian Roughley [EMAIL PROTECTED]> wrote:
>> For the plugins kept in s2, the other change I would like to see is
>> independent life cycles. If the code has not
On 8/21/07, Ian Roughley <[EMAIL PROTECTED]> wrote:
> For the plugins kept in s2, the other change I would like to see is
> independent life cycles. If the code has not changed, I'm not sure why
> its version needs to be incremented (other than staying with the s2 core
> version). Would independe
Ted Husted wrote:
I'm not sure that anyone is maintaining them now. I'm not sure that
they all work.
My thinking is that if they are kept at another location where there
is a lower bar to entry, then perhaps we can attract someone to
maintain them.
Or, the other option is that no one picks
> Another way to boost plugin development would be to create an umbrella
> GoogleCode site to host plugins, rather than a separate site for each
> one, and offer membership to all the Struts committers, as well as any
> developer with a plugin to commit. If that group then wants to
> encourage peop
On 8/21/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
> What's the traction on having S2 plugin-only committers? I am referring to a
> previous email from Antonio. Just like people sign CLA to write
> documentation, I think our plugin development would have a major boost if we
> could have plugin-on
"Write access and being a committer are the same thing. So, no. :("
On 8/21/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
> I seem to have lost that email. What was Ted's reason?
>
> On 8/21/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:
> >
> > Yeah that's what I thought, per Ted's comments we ca
What's the status on this? Is your plugin usable with struts 2.0.9?
Just out of curiosity , what was JAXB being used for in the plugin?
On 6/8/07, Brian Pontarelli <[EMAIL PROTECTED]> wrote:
>
> I might not have moved the tests over yet. I am slowly getting enough
> time to start working on docume
I seem to have lost that email. What was Ted's reason?
On 8/21/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:
>
> Yeah that's what I thought, per Ted's comments we can't do that.
> Having independent releases for the plugins would be another boost.
>
> musachy
>
> On 8/21/07, Paul Benedict <[EMAIL
Yeah that's what I thought, per Ted's comments we can't do that.
Having independent releases for the plugins would be another boost.
musachy
On 8/21/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
> What's the traction on having S2 plugin-only committers? I am referring to a
> previous email from An
What's the traction on having S2 plugin-only committers? I am referring to a
previous email from Antonio. Just like people sign CLA to write
documentation, I think our plugin development would have a major boost if we
could have plugin-only committers too.
Paul
On 8/21/07, Nils-Helge Garli <[EMAI
I guess that's a question of definition, viewed in a historical
perspective ;) But I do intend to keep actively maintaining it, and a
few more people maintaining it would be very welcome!
Nils-H
On 8/21/07, James Holmes <[EMAIL PROTECTED]> wrote:
> +1 for keeping the Portlet plugin in the core St
+1 for keeping the Portlet plugin in the core Struts 2 distribution and
project. Nils-H is actively maintaining it and I am
interested in maintaining it as well.
James
On Tue Aug 21 1:43 , 'Nils-Helge Garli' <[EMAIL PROTECTED]> sent:
>I couldn't fint the portlet plugin mentioned on the list
Since it was refactored into a plugin, it has really undergone a face
lift, with a lot off issues resolved and stability improved. I can see
that there's a lot of documentation to be written. But other than
that, in your (as in everyone) opinion, what are the major areas where
it needs to be improv
On 8/20/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:
> I'm sold with Paul's idea, now a question, could it be possible for
> people to become committers to the plugins in this subproject without
> being an struts committer?
Write access and being a committer are the same thing. So, no. :(
> I h
Although it is a lot of work, I'd too like to see the portlet plugin
in the first-tier list.
Don
On 8/21/07, Nils-Helge Garli <[EMAIL PROTECTED]> wrote:
> I couldn't fint the portlet plugin mentioned on the list of plugins
> for the different tiers. Where does it fit in?
>
> As a plugin developer
24 matches
Mail list logo
