Bruno,
You can get snapshots from the maven snapshot repository at
http://wicketstuff.org/maven/repository.
Erik.
Bruno Borges schreef:
Martijn, isn't possible to release as an Early Access ? :)
[]'s!
--
Erik van Oosten
http://2007.rubyenrails.nl/
On 5/22/07, Johan Compagner [EMAIL PROTECTED] wrote:
But most api is now stable i think so if stable api was the deciding factor
if something is called beta or rc...
Mostly the open bugs in JIRA is the deciding factor in naming a
release. With 35 (give or take) open issues, I would not call a
really?
open up the eclipse bug database and do a open bug query when the are about
to release 3.3
i bet there are more then 35 issues then ;)
johan
On 5/22/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
On 5/22/07, Johan Compagner [EMAIL PROTECTED] wrote:
But most api is now stable i think
On 5/22/07, Johan Compagner [EMAIL PROTECTED] wrote:
i think releasing one extra beta is fine.
But most api is now stable i think so if stable api was the deciding factor
if something is called beta or rc...
From my point of view, a release candidate is a distribution you plan
to graduate to
What would be the correct naming that the api is stable?
API not stable: Alpha
API stable: Beta
Release 'stable' : RC
?
johan
On 5/22/07, Xavier Hanin [EMAIL PROTECTED] wrote:
On 5/22/07, Johan Compagner [EMAIL PROTECTED] wrote:
i think releasing one extra beta is fine.
But most api is
I'm not sure a beta always mean a stable API, but you can add in the
release notes of a beta that the API is frozen. Look at the eclipse
project, they only produce milestones, and starting at one of them in
the release plan they say the API is frozen.
So if your next distribution is API stable,
Hi
Im having a problem. Basically I want the gmap component to at a
feedback component if there are any attached to the page where the gmap
panel are placed.
the reason why I want this are because the gmap provides notification
via imodel, eg if the user clicks the map or moves around or
All,
In order to get a positive vote on our graduation we need to get a
good description and specify the scope of the Apache Wicket project.
Currently the draft contains the following snippet:
Apache Wicket Project, related to the creation and maintenance
of open-source software for component
(that includes *you*
too!) for improving this.
Apache Wicket is an Open-Source framework for creating highly dynamic,
component oriented webapplications with ease as well as seperation of
concerns in mind.
Every Wicket component contains the HTML Markup (in an nearly unmodified
HTML File),
On 5/22/07, Johan Compagner [EMAIL PROTECTED] wrote:
i think releasing one extra beta is fine.
But most api is now stable i think so if stable api was the deciding factor
if something is called beta or rc...
From my point of view, a release candidate is a distribution you plan
to graduate to
If there are no objections, I would like to build a distribution based
on thursday's code base, and vote on it during the weekend (giving us
some time to test it), and then submit the release to the IPMC on
monday.
With a bit of luck we can make the release available on thursday next
week (the
Hi Korbinian!
Thanks for chipping in! I appreciate your comment. Just one thing: it
is a bit on the long side :)
Can we trim this down into one or two sentences with enough adjectives
that define Wicket (and its current and future subprojects) with
enough leverage for future directions, but
Hi,
I think you have an obsolete link on the getting wicket page [1]. The
snapshot link for 1.3 leads to this page:
http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.3-incubating-SNAPSHOT/
while it should be this one I think:
I've updated the document, should take a while (about a hour or so) to
be picked up.
Thanks for the info!
Martijn
On 5/22/07, Xavier Hanin [EMAIL PROTECTED] wrote:
Hi,
I think you have an obsolete link on the getting wicket page [1]. The
snapshot link for 1.3 leads to this page:
Here's my swipe at it:
Apache Wicket is an Open-Source framework for easily creating dynamic,
component-oriented web applications.
On 5/22/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
Hi Korbinian!
Thanks for chipping in! I appreciate your comment. Just one thing: it
is a bit on the long
if you put robust and highly scalable in it, you get this:
http://tapestry.apache.org/ (first sentence) :P
-Ursprüngliche Nachricht-
Von: Nick Heudecker [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 22. Mai 2007 21:47
An: wicket-dev@incubator.apache.org
Betreff: Re: Need
I had about 5 different tries, but none short and elegant ... will think
about it tomorrow. If anyone finds a shorter or more elegant way to describe
it, I would be glad. The trouble is, that if you cut it too short then you
can just put *any* webframework into it and it still fits... (comes close
I honestly didn't even read the Tapestry site. Oh well...
On 5/22/07, Korbinian Bachl [EMAIL PROTECTED] wrote:
I had about 5 different tries, but none short and elegant ... will think
about it tomorrow. If anyone finds a shorter or more elegant way to
describe
it, I would be glad. The trouble
18 matches
Mail list logo
