Martin Cooper wrote:
I honestly don't see that we could point at some other project outside the
ASF and say that we "endorse" the plugins produced by that project when what
we are really saying is that we don't consider those plugins to be
sufficiently worthy to live at the ASF.
I suppose that
On 8/19/07, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
>
> Martin Cooper wrote:
> > Perhaps. Perhaps not. But it's pretty much guaranteed that we would
> lower
> > the base of people who _could_ use them if they're not here. Some
> companies
> > (my current employer included) require approval for
Hi, Rene,
2007/8/17, Rene Gielen <[EMAIL PROTECTED]>:
> > You won't get NPE in this scenario. Ognl automatically create instance
> > for you. I believe you know about this feature.
> >
>
> Not when trying to read the property, only when applying values. The first
> invocation with null foo object
Don,
I want to propose independent projects/releases. The only problem is going
to be versioning, because all plug-ins are probably 2.0.x, right?
Paul
On 8/19/07, Don Brown <[EMAIL PROTECTED]> wrote:
>
> Makes sense to me. Would we bundle the second-tier plugins in our
> release or just the fi
On 8/19/07, Don Brown <[EMAIL PROTECTED]> wrote:
> Sorry, what I meant was what has Maven learned about managing plugins?
> As Martin pointed out, it can easily become scattered and confusing
> for users, but on the other hand, opening up plugins for outside
> contributions let's us focus on the
Makes sense to me. Would we bundle the second-tier plugins in our
release or just the first tier? Would second-tier plugins each get
their own release cycle, share one together, or be linked to the main
Struts 2 release cycle?
Don
On 8/20/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
> Hi all.
Hi all.
I think the Spring framework has a great model for this kind of problem.
They call it the "Spring portfolio" which is the Spring Framework (proper)
and then subprojects for very special criteria (security, web services,
etc.). We all know Spring is pretty good at integrating technologies,
Musachy, are you talking 10%-15% difference between the Ajax tags in
2.0.x and 2.1.x, or in versions of Dojo?
Frank
Musachy Barroso wrote:
There aren't many differences, lots of bug fixes and some new features
based on user request from the user list, I would say 10%-15%.
musachy
On 8/19/07,
Martin Cooper wrote:
Perhaps. Perhaps not. But it's pretty much guaranteed that we would lower
the base of people who _could_ use them if they're not here. Some companies
(my current employer included) require approval for each and every open
source component before it can be used within the comp
There aren't many differences, lots of bug fixes and some new features
based on user request from the user list, I would say 10%-15%.
musachy
On 8/19/07, Ian Roughley <[EMAIL PROTECTED]> wrote:
> My personal preference would be out of Struts - unless, the plugins
> within Struts2 can have indepen
On 8/19/07, Ted Husted <[EMAIL PROTECTED]> 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.
Pe
Sorry, what I meant was what has Maven learned about managing plugins?
As Martin pointed out, it can easily become scattered and confusing
for users, but on the other hand, opening up plugins for outside
contributions let's us focus on the core of Struts 2. How does Maven
ensure the support of po
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.
My concern is that some of the code in our distribution is not bei
On 8/19/07, Don Brown <[EMAIL PROTECTED]> wrote:
>
> Agreed, Spring should be a first-tier plugin. I'm fine with spinning
> off the others, but who would maintain them? If it will be the same
> people, then perhaps we should keep them in the repository.
Perhaps I'm missing something here, but h
On 8/19/07, Don Brown <[EMAIL PROTECTED]> wrote:
> Agreed, Spring should be a first-tier plugin. I'm fine with spinning
> off the others, but who would maintain them? If it will be the same
> people, then perhaps we should keep them in the repository.
>
> How does Maven handle this situation? W
+1 for keeping the Spring module at the Struts project.
-Original Message-
From: Tom Schneider [mailto:[EMAIL PROTECTED]
Sent: Sunday, August 19, 2007 10:18 AM
To: Struts Developers List
Subject: Re: [S2] [2.1.x] Bundled Plugins
I disagree with moving the Spring plugin outside of the cor
Agreed, Spring should be a first-tier plugin. I'm fine with spinning
off the others, but who would maintain them? If it will be the same
people, then perhaps we should keep them in the repository.
How does Maven handle this situation? Wendy?
Don
On 8/20/07, Tom Schneider <[EMAIL PROTECTED]> w
The underlying implementations may change, but that shouldn't affect
the tests in the Showcase. In fact, passing the tests in the showcase
would be a good proof that a different plugin is working.
If you have something to share, add it to
* https://issues.apache.org/struts/browse/WW-1912
and ho
Hi all,
I've started working on some Selenium tests. I started testing the
Ajax examples and I've been working through them in order. From all
the discussion it sounds like the Ajax tags are likely to change
often. Is it worth carrying on with the rest of the test suite? So far
I've written tests
My personal preference would be out of Struts - unless, the plugins
within Struts2 can have independent life cycles (which at the moment
doesn't seem to be the case). And, once again, this is biased on the
implementation of the ww2 tags where the dojo API was rapidly changing
:) If the dojo A
I disagree with moving the Spring plugin outside of the core set of
plugins. I think a lot of people use Spring and it would be a shame to
not have it as a core feature. Keep in mind that I think we run a huge
risk (IMO) of plugins being unmaintained if we set them free, however,
I'm more tha
On 8/18/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:
> do you mean to move the plugin out of Struts? Because Dojo is already
> on its own plugin in trunk.
My question was whether we wanted to keep Dojo as part of the project,
or move it GoogleCode, along with the YUI plugin. I think some of the
22 matches
Mail list logo
