> The first thing I'd do is flip things around so that everything builds
> by default, and use profiles to *exclude* things if necessary. But
> since I'm pretty sure that would break Bamboo, I won't do it. I will
> make time to help if someone wants to drive this.
>
I think this much I could do
Did you get anywhere with this?
On Tue, Oct 21, 2008 at 10:16 PM, Jeromy Evans <
[EMAIL PROTECTED]> wrote:
> Wendy Smoak wrote:
>
>> On Tue, Oct 21, 2008 at 6:01 PM, Bob Tiernay <[EMAIL PROTECTED]>
>> wrote:
>>
>>
>>> I get the sense that CI + Maven is a like wrestling with a slinky. Is
>>> this
Thanks Frank! Your comments are appreciated and obviously well thought out.
> What is there in S2 to truly excite Web 2.0
>developers in S2 as compared to other frameworks?
Hmmm. From what I can tell you are describing Web 2.0 in terms of
client-heavy scripting language driven websites.
ippets.
# Additional examples can still be added/etc. by non-committers.
Dave
[1] I'll work on the snippet macro/etc. (if necessary) to support what I want
to do.
--- On Thu, 10/23/08, Philip Luppens wrote:
> From: Philip Luppens <[EMAIL PROTECTED]>
> Subject: Documentation iss
On Thu, Oct 23, 2008 at 1:03 AM, Dave Newton <[EMAIL PROTECTED]> wrote:
> --- On Wed, 10/22/08, Philip Luppens wrote:
>> Javadoc makes a very poor format for creating example code;
>
> Not in JavaDoc, as Java/JSP/FreeMarker/etc. and pulled in to the wiki via
> snippets. That way they're examples t
--- On Wed, 10/22/08, Philip Luppens wrote:
> Javadoc makes a very poor format for creating example code;
Not in JavaDoc, as Java/JSP/FreeMarker/etc. and pulled in to the wiki via
snippets. That way they're examples that actually work.
Dave
-
On Wed, Oct 22, 2008 at 8:45 PM, Dave Newton <[EMAIL PROTECTED]> wrote:
> --- On Wed, 10/22/08, Philip Luppens wrote:
>> - Documentation: no more (example) documentation in the
>> Javadocs so non-committers can make changes in the wiki.
>
> I'd augment this a bit
>
> I'd really like all the example
--- On Wed, 10/22/08, Philip Luppens wrote:
> - Documentation: no more (example) documentation in the
> Javadocs so non-committers can make changes in the wiki.
I'd augment this a bit
I'd really like all the examples to be in source control and have associated
tests, and I'm willing to spend som
> To be sure, there *are* some cool things in S2. What I for one don't
> see, and I've heard a similar feeling expressed by many as recently as
> at The Ajax Experience earlier this month, is a clear, coherent vision
> of how S2 lets me develop these so-called Web 2.0 applications better
> than a
> The release process here could be *much* simpler, but it's really hard
> to change someone else's process. :) It's going to take someone to
> volunteer to be release manager and refine the process and the build
> once or twice.
>
>
Whose process? Apache's? Either way, if it can be *much* simpler
Lots of the "pain" when doing a release comes from the administrative
side. Getting Jira issues in shape and tagged for the release, preparing
release notes and docs export, fixing site texts, managing the vote
process, doing announcements etc. In addition, there are some time
consuming and maybe m
On Wed, Oct 22, 2008 at 4:20 AM, dusty <[EMAIL PROTECTED]> wrote:
>
> So the more I think about it the more thoughts I have
>
> The major users like Atlassian and Google forked Webwork a while ago I think
> and they don't run their stuff off the Struts2 code base. Don has been
> awesome for St
dusty wrote:
So we get more aggressive with our releases. We definitely want to preserve
compatibility but if we have a good reason for breaking compatibility we let
people know and show them how to migrate. At the same time we get more
aggressive with marketing, by overhauling the website, gett
Wendy Smoak wrote:
On Tue, Oct 21, 2008 at 6:01 PM, Bob Tiernay <[EMAIL PROTECTED]> wrote:
I get the sense that CI + Maven is a like wrestling with a slinky. Is this
problem endemic to s2? What do other open source projects do to alleviate
this?
The release process here could be *much
On Tue, Oct 21, 2008 at 6:01 PM, Bob Tiernay <[EMAIL PROTECTED]> wrote:
> I get the sense that CI + Maven is a like wrestling with a slinky. Is this
> problem endemic to s2? What do other open source projects do to alleviate
> this?
The release process here could be *much* simpler, but it's reall
These are the steps:
http://struts.apache.org/2.x/docs/creating-and-signing-a-struts-21x-distribution.html
If they were easier, and there's got to be a way to make it easier, builds
would be coming out more often I am sure.
On Tue, Oct 21, 2008 at 9:50 PM, dusty <[EMAIL PROTECTED]> wrote:
>
>
>
So the more I think about it the more thoughts I have
The major users like Atlassian and Google forked Webwork a while ago I think
and they don't run their stuff off the Struts2 code base. Don has been
awesome for Struts2, but I don't know if there are any other commiters from
Atlassian or G
Jeromy Evans - Blue Sky Minds wrote:
>
> I share similar sentiment. Whenever I take a critical look as to whether
> to use struts2 I keep coming back to the conclusion that it's
> fundamentally sound as far as java frameworks go.
> I'd categorize the problem as not enough generals. Most of u
I get the sense that CI + Maven is a like wrestling with a slinky. Is this
problem endemic to s2? What do other open source projects do to alleviate
this?
My #1 issue is that it's *too difficult and time-consuming to create a
release* on the 2.1 trunk. If releases are difficult and dependent
dusty wrote:
How do we tackle all this? Do we have a meeting? Do we create a Chief who
can make decisions for better or for worse? Clearly decisions need to be
made. Do we start StrutsCon 2009 and lock everyone in a room until the
decisions are made? I started to also write apps in Rails an
* OGNL - Is is staying? Is it going? Can it be secure? Is it fast
enough?
I say drop it completely. No more evaluation in the JSPs or FTL files
at all and use MVEL for the parameters interceptor. FTL has a good
enough language and you have Java in JSPs if you need it. OGNL in
there is
* REST - Great way to organize web based applications
Nobody is working on this right?
I'm not working on it, but I have a few projects deployed using it, so i
would wonder if it needs
much in the way of work (if any at all).
Al.
--
>
>
> * OGNL - Is is staying? Is it going? Can it be secure? Is it fast enough?
>
Params interceptor was the biggest security problem and it has been patched.
It MVEL gets integrated then it will get interesting.
>
> * Convention - Buzz factor to me, but buzz none the less. I type pretty
> fast
Struts1 is arguably the most successful web framework, but it always felt
heavy. It's how I found WebWork, which I am convinced is the greatest web
framework. When WebWork made the move to Apache as Struts 2, I was excited
since it meant this great framework would continue on after the great wor
24 matches
Mail list logo
