Yes, confluence is great, but a bit of useless since the spam-incident.
I think the confluence is still full of with spammer users and
spamcontents. Also the registration doesn't work, but this is an another
issue. Nino, if I remember correctly, you can access confluence, right?
Could you do
I may be wrong, but wouldn't it make sense to delay creating a 1.4.x
branch until/unless someone actually wants to commit some code that
would be different for 1.4.x and 1.5-SNAPSHOT? Once we branch, we have
to start committing every bug fix to two different versions, right?
If we're lucky,
2010-03-23 11:24 keltezéssel, Boris Goldowsky írta:
I may be wrong, but wouldn't it make sense to delay creating a 1.4.x
branch until/unless someone actually wants to commit some code that
would be different for 1.4.x and 1.5-SNAPSHOT? Once we branch, we have
to start committing every bug fix
for
current wicket 1.4?
Stefan
-Ursprüngliche Nachricht-
Von: Major Péter [mailto:majorpe...@sch.bme.hu]
Gesendet: Dienstag, 23. März 2010 11:38
An: users@wicket.apache.org
Betreff: Re: Wicketstuff versioning
2010-03-23 11:24 keltezéssel, Boris Goldowsky írta:
I may be wrong, but wouldn't
Nachricht-
Von: Major Péter [mailto:majorpe...@sch.bme.hu]
Gesendet: Dienstag, 23. März 2010 11:38
An: users@wicket.apache.org
Betreff: Re: Wicketstuff versioning
2010-03-23 11:24 keltezéssel, Boris Goldowsky írta:
I may be wrong, but wouldn't it make sense to delay creating a 1.4.x
[mailto:majorpe...@sch.bme.hu]
Gesendet: Dienstag, 23. März 2010 11:38
An: users@wicket.apache.org
Betreff: Re: Wicketstuff versioning
2010-03-23 11:24 keltezéssel, Boris Goldowsky írta:
I may be wrong, but wouldn't it make sense to delay creating a 1.4.x
branch until/unless someone actually wants
An: users@wicket.apache.org
Betreff: Re: Wicketstuff versioning
2010-03-23 11:24 keltezéssel, Boris Goldowsky írta:
I may be wrong, but wouldn't it make sense to delay creating a 1.4.x
branch until/unless someone actually wants to commit some code that
would be different for 1.4.x and 1.5
and create a core wicketstuff release for
current wicket 1.4?
Stefan
-Ursprüngliche Nachricht-
Von: Major Péter [mailto:majorpe...@sch.bme.hu]
Gesendet: Dienstag, 23. März 2010 11:38
An: users@wicket.apache.org
Betreff: Re: Wicketstuff versioning
2010-03-23 11:24 keltezéssel, Boris
Nachricht-
Von: Major Péter [mailto:majorpe...@sch.bme.hu]
Gesendet: Dienstag, 23. März 2010 11:38
An: users@wicket.apache.org
Betreff: Re: Wicketstuff versioning
2010-03-23 11:24 keltezéssel, Boris Goldowsky írta:
I may be wrong, but wouldn't it make sense to delay creating a 1.4.x
branch
Péter [mailto:majorpe...@sch.bme.hu]
Gesendet: Dienstag, 23. März 2010 11:38
An: users@wicket.apache.org
Betreff: Re: Wicketstuff versioning
2010-03-23 11:24 keltezéssel, Boris Goldowsky írta:
I may be wrong, but wouldn't it make sense to delay creating a 1.4.x
branch until/unless someone
-Ursprüngliche Nachricht-
Von: Major Péter [mailto:majorpe...@sch.bme.hu]
Gesendet: Dienstag, 23. März 2010 11:38
An: users@wicket.apache.org
Betreff: Re: Wicketstuff versioning
2010-03-23 11:24 keltezéssel, Boris Goldowsky írta:
I may be wrong, but wouldn't it make sense to delay creating
Hi,
+1 on creating wicketstuff-core jira to coordinate release process.
Here it is: http://wicketstuff.org/jira/secure/Dashboard.jspa
+1 on creating a wicketstuff-core/wicketstuff-test module to share
testing code between core projects.
+1 on running integration tests to find run-time
Yepp, nice chat, but who wants to do the dirty work??
The first thing would be to create the 1.4.x branch, then release the
current state as wicketstuff 1.4.7, and then modify the settings of the
trunk to compile with wicket trunk.
Let's split these jobs up to people, then do it.
Also maybe we
I'll be happy to join in Boris.
2010/3/18 Boris Goldowsky bgoldow...@cast.org
Thank you for your thoughts Jeremy -- and your previous work on
WicketStuff. I am certainly unhappy to hear that it felt like torture
and that junk was being dumped on you rather than getting support from
the
[mailto:mcgreg...@e-card.bg]
Gesendet: Donnerstag, 18. März 2010 09:09
An: users@wicket.apache.org
Betreff: Re: Wicketstuff versioning
Here is how I understand wicketstuff hosting:
Someone makes something cool and decides to share it with the community.
Then this person asks in the mailing lists for commit
nino martinez wael wrote:
I'll be happy to join in Boris.
That would be awesome, thanks Nino.
I'm thinking the first thing would be to bump the wicket dependency to
v1.4.7 and do a maven release of the current state of wicketstuff-core
as version 1.4.7. Make sense? Is that something you
Hi,
count me in. I would like to help maintain wicketstuff-core too. ;)
When I came to build wicketstuff-core, sometimes I end up fixing
dependency issues and other stuff in others projects, but I don't commit
them, because I don't want to modify someone else's code without her/his
knowledge, and
2010/3/19 Major Péter majorpe...@sch.bme.hu
Hi,
count me in. I would like to help maintain wicketstuff-core too. ;)
When I came to build wicketstuff-core, sometimes I end up fixing
dependency issues and other stuff in others projects, but I don't commit
them, because I don't want to modify
Here is how I understand wicketstuff hosting:
Someone makes something cool and decides to share it with the community.
Then this person asks in the mailing lists for commit permissions. After
that this person jumps into something else and don't have time to
support the project. Later on I need
Exactly (I wrote something similar, but it apparently was declared spam:().
We could of course improve our structure as always, lifting the level a bit.
As I see it wicketstuff are as ops4j, which brings advantages and
disadvantages as well.
-regards Nino
2010/3/18 Martin Grigorov
Thank you for your thoughts Jeremy -- and your previous work on
WicketStuff. I am certainly unhappy to hear that it felt like torture
and that junk was being dumped on you rather than getting support from
the community.
I'd volunteer to put a bit of time into this, but I don't have time to
be
Really, it should match what's at trunk of Wicket, which should be
1.5-SNAPSHOT. There should be a branch for 1.4.x that is 1.4-SNAPSHOT.
But, nobody is really maintaining it any more, so it's a free-for-all.
That's always been the problem with WicketStuff.
--
Jeremy Thomerson
It sounds like whoever is responsible for wicketstuff needs to make a
clear choice here.
Is Wicketstuff going to be maintained as a place where lots of useful
add-ons will live? If so, it needs someone to take a slightly more
active role as curator; make sure the releases are done in
I always thought, that Jeremy was the maintainer of WicketStuff. Guess I
was wrong. :)
Sidenote:
Also, I really wanted to write docs for the javaee-inject project, but I
don't have confluence access, and the signup gives:
org.springframework.transaction.UnexpectedRollbackException: Transaction
Comments inline
--
Jeremy Thomerson
http://www.wickettraining.com
On Wed, Mar 17, 2010 at 2:25 PM, Boris Goldowsky bgoldow...@cast.orgwrote:
It sounds like whoever is responsible for wicketstuff needs to make a clear
choice here.
The community is responsible for WicketStuff. This
See other reply to Boris. Anyone can pick it up and become the maintainer
of WS. But it's going to take a group of people who set some rules about it
and then follow them. The problem with that is that then people *will*
whine because they always wanted WicketStuff to be a no-rules repo. I
26 matches
Mail list logo
