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
problem endemic
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, I
.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Concerned-Strutszien%3A-A-Manifesto-tp20053620p20159172.html
Sent from the Struts - Dev mailing list archive at Nabble.com
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 issues (was: Re: Concerned Strutszien: A Manifesto
.
--
View this message in context:
http://www.nabble.com/Concerned-Strutszien%3A-A-Manifesto-tp20053620p20102920.html
Sent from the Struts - Dev mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
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
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,
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 any
--- 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 some
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 examples to be in
--- 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 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 that
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
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
this message in context:
http://www.nabble.com/Concerned-Strutszien%3A-A-Manifesto-tp20053620p20102714.html
Sent from the Struts - Dev mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
independently tinkering with release process to try to
automate all assembly within a CI system so a formal release is an
administrative process only, but it's not much fun.
--
View this message in context:
http://www.nabble.com/Concerned-Strutszien%3A-A-Manifesto-tp20053620p20102920.html
this message in context:
http://www.nabble.com/Concerned-Strutszien%3A-A-Manifesto-tp20053620p20102714.html
Sent from the Struts - Dev mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
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 really
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*
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,
://www.nabble.com/-s2--Roadmap-%28was-Tag-it-and-Roll-it-%29-td5474867.html#a5474867
--
View this message in context:
http://www.nabble.com/Concerned-Strutszien%3A-A-Manifesto-tp20053620p20053620.html
Sent from the Struts - Dev mailing list archive at Nabble.com
* 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.
It
* 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?
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
24 matches
Mail list logo
