+1
On 1/18/07, Al Maw [EMAIL PROTECTED] wrote:
Igor Vaynberg wrote:
include https://issues.apache.org/jira/browse/WICKET-218 in 1.2.5
I've only seen this once before, but why not?
+1
It only gets restartet once a day. Thats usually it. It is not
available 100% that is true, but it is down only very few times. If
anyone wants to spend some time on investigating why it is done, I'm
more than happy to grant you access. Unfortunately I have only very
little time right now. It is
lets see how stable our server is. It runs much more apps so it should go
down earlier!
johan
On 1/19/07, Juergen Donnerstag [EMAIL PROTECTED] wrote:
It only gets restartet once a day. Thats usually it. It is not
available 100% that is true, but it is down only very few times. If
anyone
+1
-igor
On 1/18/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
include https://issues.apache.org/jira/browse/WICKET-218 in 1.2.5
-igor
yes i have the same questions as igor.
What do we move completely to Apache?
Is it so that when we have moved then only jira an confluence are still
there
for just Wicket-Stuff?
Everything else, so the auto building and auto deploying and serving of the
latest examples
are done then on the
On 1/18/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
...Problem is that to be able to do
that, you need to earn karma, and IMO you won't get karma until you
help administer stuff.
Are you aware of the Solaris zones?
See http://www.apache.org/dev/solaris-zones.html - I don't know much
about
It's already in trunk. I'm more thinking about backporting the wickettester
change from trunk to 1.3.
But perhaps I will raise a vote to backport 496616 to 1.2.5. But it easy for
users to fix it them selves, by doing what I do on there instance of
WicketTester.
WDYT?
Frank
On 1/19/07,
but when to execute that thing?
And what would be the big change? Instead of now RequestCycle.detach()
calling detach() on the RequestTargets
(that are the pages that are used in the current request) What would be
called now and when?
We first need to move the Session.touch(page) command to a
* Frank Bille:
It's already in trunk. I'm more thinking about backporting the
wickettester change from trunk to 1.3.
Oh yes you're right Frank, it was already in trunk, my bad.
It would be great to backport the whole WicketTester refactoring
to branch 1.x. I filed a patch for that:
can we get a zone if we are just incubating?
-igor
On 1/19/07, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
On 1/18/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
...Problem is that to be able to do
that, you need to earn karma, and IMO you won't get karma until you
help administer stuff.
Igor Vaynberg wrote:
can we get a zone if we are just incubating?
At this point, I personally would stick with either Sourceforge or Servoy.
The main issue being that zones aren't intended for use for public
websites, more for demos, tests, builds, etc, and you cannot map a
domain to a zone
Forgive me for asking a question that has been asked before but is there an
update on when Wicket 2.0 will be available?
I saw several responses in the summer and fall of last year saying that a
release would be in a few months but nothing more recent then that.
I'd like to recommend Wicket
Not really. Lots of stuff came in between. Imo the 2.0 is reasonably
stable and many of it's features got backported to 1.3, making both
1.3 and interesting enough alternative and giving the new features of
2.0 the change to get tested (there are at least a couple of
production systems written on
13 matches
Mail list logo
