interesting ..
Suddenly java gets passed by reference instead of value?
things like: (sounds dark magic to me ;) )
@Serializer
public pattern Range(int lo, int hi) {
lo = this.lo;
hi = this.hi;
}
On Wed, 12 Jun 2019 at 12:47, Martin Grigorov wrote:
> Current state:
Ehh serialisation is done in read and writeobject methods, all the stuff
should be created there (readObject)
The entry array is not meant to be serialized by itself.
At first sight it seem to be correct, the sizes are serialized and then an
int + object pair is done. And the read creates the tab
Ah we are taking here about the removal of the deprecated api not the code
for other browsers. That was 2.0 yes. Couldn't look it up that easy on
vacation..
But then I guess we need to stick to 1.8.x
On 3 Jul 2013 12:05, "Martijn Dashorst" wrote:
> On Wed, Jul 3, 2013
Why not just go to the latest 1.9.x?
I thought that was .10 but without all the removed api?
On 3 Jul 2013 11:13, "Martijn Dashorst" wrote:
> While I typically agree that using the latest stable versions of
> things is a good thing™, in this case the almighty gods that maintain
> jquery have deci
those files are needed, at least to get a consistent formatting behavior
across all developers.
I would say just commit those files. Thats the whole point of the .settings
dir in eclipse.. (else don't specify anything at the project level)
On 14 January 2013 13:27, Emond Papegaaij wrote:
> I jus
I am interested in your article..
How else to really do it then cherry picking.. but I guess h that also
depends where you do you're good first?
I always start at their lowest version I want to fix it and forward port
it, almost never do back ports
Op 10 sep. 2012 19:33 schreef "Carl-Eric Menzel"
+1
On 29 August 2012 15:41, Carl-Eric Menzel wrote:
> It's time to mop up the last remaining changes in 1.4.x so we can
> finally close that branch and concentrate on 1.5 and 6.0.
>
> Please check the following source release and then vote:
> - branch build/wicket-1.4.21
> - source tarball
>
>
> While my hatred for Maven runs deep, I have yet to find a solution
> that works better or is more appealing.
>
> Martijn
>
really?? runs deep? for martijn? i just can't believe that!
Explain to me then what Wicket it self really needs from the new API?
So what are we going to change?
On Apr 13, 2012 2:32 PM, "Emond Papegaaij"
wrote:
> Hi all,
>
> It was already mentioned by Martijn some time ago as a suggestion for the
> roadmap for Wicket 6, but it was never decided. The qu
i think it would be fine to have something like this, and enabled by default
but only to have an option to turn it off
On Sat, Apr 7, 2012 at 22:30, Igor Vaynberg wrote:
> -1 on adding it if its not enabled by default. its a trivial class
> thats only about 40-50 lines of real code. adding it i
fine by me, i am not sure why it does that, it seems to me that the script
that tests if the server is up and running is to aggressive or something.
Maybe point wicketstuff.org to wicket-library.com?
On Mon, Mar 26, 2012 at 10:51, Martijn Dashorst
wrote:
> All,
>
> We probably can (and should)
+1
On Mar 23, 2012 1:34 PM, "Martin Grigorov" wrote:
> This vote is to release wicket 6.0.0-beta1.
> This is the first release of 6.x branch and its purpose is to get more
> feedback from
> the community. There are no more planned changes in the API but if you
> find something
> that can be made
+1
On Mar 7, 2012 5:47 PM, "Igor Vaynberg" wrote:
> This vote is to release wicket 1.4.20
>
> Branch
>
> http://git-wip-us.apache.org/repos/asf/wicket/?p=wicket.git;a=shortlog;h=refs/heads/build/wicket-1.4.20
>
> Artifacts
> http://people.apache.org/~ivaynberg/wicket-1.4.20/dist/
>
> Maven repo
>
s inside a modal window..
On Thu, Feb 16, 2012 at 20:58, Igor Vaynberg wrote:
> thats why the javadoc says to put the modal window component inside a
> wicket form...
>
> -igor
>
> On Thu, Feb 16, 2012 at 11:55 AM, Johan Compagner
> wrote:
> > but the modal dialog iself
t panel
>div - wicket form inside the modal's content
>
> -igor
>
> On Thu, Feb 16, 2012 at 11:36 AM, Johan Compagner
> wrote:
> > ok for a form inside a modal dialog
> > you need to override:
> >
> >/**
> > * @see
not find any other form because
the modal dialog form is just in javascript/html, its not a wicket
component..
On Thu, Feb 16, 2012 at 20:22, Johan Compagner wrote:
> yes i just read that in a jira issue :)
> but in my example it doesn't ...
> will check it
>
>
>
> On
; see they are inside another form...
>
> -igor
>
> On Thu, Feb 16, 2012 at 11:16 AM, Johan Compagner
> wrote:
> > here:
> >
> >
> http://wicket.apache.org/apidocs/1.5/org/apache/wicket/extensions/ajax/markup/html/modal/ModalWindow.html
> >
> > we
Stick for now to Java 6
or does somebody really has good reason (api or feature that he wants to
use) to go to Java 7?
I think java 7 almost brought nothing, the all postponed the nice stuff to
Java 8 (which is postponed to next year i believe)
i do think that the eol of java 6 is quite fast, i d
is present i
> suppose. i am not sure if infra would like that or not...
>
> -igor
>
> On Fri, Feb 10, 2012 at 8:10 AM, Johan Compagner
> wrote:
> > can we somehow force that? Just like we did with svn that has that build
> in
> > case:xxx support (in the commit dial
can we somehow force that? Just like we did with svn that has that build in
case:xxx support (in the commit dialog?)
But i will place WICKET-XXX then in all my commits from now on
On Fri, Feb 10, 2012 at 17:08, Martin Grigorov wrote:
> On Fri, Feb 10, 2012 at 6:02 PM, Johan Compagner
>
,
> >>
> >> I asked the same question on dec 22 and Igor replied :
> >>
> >> infra is working on this afaik.
> >>
> >> -igor
> >>
> >>
> >> So I guess they haven't finished yet!
> >>
> >> Bertrand
Hi,
What "broke" now that we are over to git is the nice link between jira
issues and the source code
so this tab:
https://issues.apache.org/jira/browse/WICKET-1654?page=com.atlassian.jirafisheyeplugin:fisheye-issuepanel#issue-tabs
(or that subversion tab which ofcourse will not work anymore)
i
or use the let statement.. but support in all browsers could be a bit
tricky ;)
shouild be javascript 1.7 (thats FF 2.0 from 2006) but i don't think its in
EcmaScript yet (looks like EcmaScript 6 gets it) and most other browsers
follow that and do currently Edition 5.x or something
On Thu, Feb 9,
is something to tune in WebSphere. If it
> works then there is something in Wicket.
>
> On Mon, Feb 6, 2012 at 6:06 PM, Johan Compagner
> wrote:
> > Websphere,
> >
> > i am currently testing our product in a war deployment with the latest
> > wicket 1.4 code
>
Websphere,
i am currently testing our product in a war deployment with the latest
wicket 1.4 code
But i am still bumping against this with Websphere 8.0.2
was it really fixed? Do i need a setting somehow?
It is really weird for example
if this is the url
http://jcompagner-pc:9080/servoy/servoy-
i have a friend of mine that is also a long time eclipse users and he has
now a few months a job where they have to use Intellij
his qoute from a few days (after using it now for quite a while) ago: "btw,
intellij sucksnah, eclipse is way ahead"
so i guess thats a matter of taste..
The g
ally works fine for me:
> in 1.5.x:
> git commit -m "my commit"
> got to wicket 6:
> git fetch wicket-1.5 (fetches the commit i just did on wicket-1.5)
> git cherry-pick wicket-1.5/wicket-1.5.x
>
> Emond
>
>
> On Friday 06 January 2012 15:55:15 Johan Compagner
om/questions/5785549/able-to-push-to-all-git-remotes-with-the-one-command>
> .
>
> I too am new to git so I'd like to know if there are disadvantages to the
> second approach.
>
> Bertrand
>
>
>
> On 06/01/2012 9:11 AM, Johan Compagner wrote:
>
>> Ok,
1.6/trunk/master repo.
then everything is merged and i have in my 1.6/trunk repo all the changes
over the 3 branches and i push that to the remove wicket at onces
johan
On Fri, Jan 6, 2012 at 14:28, Renaud Bruyeron wrote:
> 2012/1/4 Johan Compagner :
> > What is then the nicest way?
>
#x27;m not sure if this is done using 'git checkout .' or 'git
> reset
> --hard HEAD' after changing autocrlf. Cloning again also fixes it :)
>
> Emond
>
> On Friday 06 January 2012 14:26:38 Johan Compagner wrote:
> > what is the best way to set that
what is the best way to set that ? or turn that off?
i tried this
http://stackoverflow.com/questions/1510798/trying-to-fix-line-endings-with-git-filter-branch-but-having-no-luck/1511273#1511273
but still many many outgoing changes.
On Fri, Jan 6, 2012 at 14:09, Emond Papegaaij wrote:
> core.aut
can push/fetch changes between your workspaces directly.
>
> Personally, I use this last approach, but that's mainly because I do not
> yet
> feel comfortable enough to play with git internals :)
>
> Emond
>
> On Wednesday 04 January 2012 16:25:32 Johan Compagner wrote:
>
ay with git internals :)
>
> Emond
>
> On Wednesday 04 January 2012 16:25:32 Johan Compagner wrote:
> > Currently i just have 3 workspaces for wicket (1.4,1,5 and trunk/master)
> >
> > But git works with a/one working directory...
> >
> > thats always one
uite a bit harder and way more steps (at least
it looks that way to me now) then what i would do with svn.. (using the
merge client shipped with subclipse)
On Wed, Jan 4, 2012 at 16:40, Martijn Dashorst
wrote:
> On Wed, Jan 4, 2012 at 4:25 PM, Johan Compagner
> wrote:
> > C
Currently i just have 3 workspaces for wicket (1.4,1,5 and trunk/master)
But git works with a/one working directory...
thats always one of those..
So is the only solution to have the remote git repo dumped three times on
my disk?
I don't find that very logical..
And no i don't want to constantl
Start coding! :-)
On Dec 30, 2011 4:26 PM, "Emond Papegaaij"
wrote:
> Thank you all for the confidence you have in my work! I'm really proud to
> be a
> member of the Wicket team and am looking forward to get some real work
> done.
> I've already pushed some patches for a few tickets, broke most
hmm i use EGit but some how i always get "not authorized" if i try to push
something
I am quite sure the username/password is correct, but will recheck it, i
use this url:
https://jcompag...@git-wip-us.apache.org/repos/asf/wicket.git
On Wed, Dec 21, 2011 at 19:26, Jeremy Thomerson
wrote:
> On
fine by me
i do monitor it now and then, problem if it doesn't run is mostly some
full disk problem that i then clean up
On Fri, Oct 14, 2011 at 06:08, Jeremy Thomerson
wrote:
> On Thu, Oct 13, 2011 at 11:53 PM, Michael O'Cleirigh
> wrote:
>>
>> Hello,
>>
>> Jenkins currently runs at wicketstuf
+1 code wise it runs fine for us. (was already on a snapshot with the
latest stuff)
On Wed, Oct 12, 2011 at 18:10, Igor Vaynberg wrote:
> This vote is to release wicket 1.4.19
>
> Branch
> http://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.19
>
> Artifacts
> http://people.apache.org/~iva
For us personally i don't care, <1> could be done, we are not on 1.5
yet and if we do the package rename is easy to fix.
But i agree with the rest that this is to big to do in such a late
stage, and maybe also after that stage.
Because for osgi the simppe fix is to make one big jar right? Thats
re
enabled dir listing
http://www.wicketstuff.org/maven/repository/
On Thu, Jul 21, 2011 at 09:21, Johan Compagner wrote:
> why is that suddenly disabled i ask my self, that always did work..
>
>
> On Thu, Jul 21, 2011 at 09:18, Martin Grigorov wrote:
>> 1.4-SNAPSHOT is still
why is that suddenly disabled i ask my self, that always did work..
On Thu, Jul 21, 2011 at 09:18, Martin Grigorov wrote:
> 1.4-SNAPSHOT is still there but I cannot make Tomcat see it.
> How can I configure Tomcat to list the contents of a folder in
> webapps/maven if maven/ has no WEB-INF/web.x
for a webapp the parallelism sits in the users all connecting at the
same time to the same server
not the divide up pure request of that server. I don't think you will
gain anything and only get loads of threading issues in the page..
On Tue, Jul 5, 2011 at 17:52, Andrea Del Bene wrote:
> My fa
the nice thing is that the diamond notation for generics is working
out of the box when you can target 1.7 your self in your app.
Thats can be quite a bit lot less typing of characters in wicket apps.
On Tue, Jul 5, 2011 at 14:57, Martin Grigorov wrote:
> I'm saying only that JDK7 based solution
>
> For Wicket 1.6 we can move to JDK6 but this will be discussed later.
> Usage of JDK7 for frameworks is not very close.
>
this is an understatement :)
wicket and java 7... my guess? more then 4 years...
But who knows if Oracle speeds it up (they say Java 8 next year..)
also the upgrades are a
+1 release
On Mon, Mar 28, 2011 at 10:10, Martin Grigorov wrote:
> On behalf of Igor Vaynberg:
>
> This vote is to release wicket 1.4.17. This is a bugfix release on the
> 1.4.x (stable) branch.
>
> Branch: http://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.17/
> Artifacts: http://people.
> Expected behavior:
> - request1: starts processing, locks pagemap
> - request2: comes in: tries to acquire lock
> - request2: waits for max N seconds (N being a small number, 1 or 2
> seconds) - request2: sets kill switch for request1
> - request1: first time in wicket managed code: throw
+1
On Mon, Feb 21, 2011 at 05:33, Igor Vaynberg wrote:
> This vote is to release wicket 1.4.16. This is a bugfix release on the
> 1.4.x (stable) branch.
>
> Branch: http://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.16/
> Artifacts: http://people.apache.org/~ivaynberg/wicket-1.4.16/dist
>
why not just introduce that interface and the impl in component?
So why also alter abstract behavior? Because that would mean that
suddenly almost all the behaviors that are used are suddenly also
IComponentConfigurationBehavior
And 99.9% of them don't do anything.
On Sat, Feb 19, 2011 at 04:17,
fine by me
On Tue, Feb 8, 2011 at 11:58, Martijn Dashorst
wrote:
> It appears that we can reduce the amount of spam JIRA sends to our
> commits list by telling it not to send notifications when the fix-in
> version is modified. I'd like that feature to be enabled...
>
> Martijn
>
> --
> Become a
+1
On Tue, Dec 7, 2010 at 20:55, Igor Vaynberg wrote:
> +1 to make it consistent, dont care which way its spelled.
>
> -igor
>
> On Tue, Dec 7, 2010 at 9:51 PM, Juergen Donnerstag
> wrote:
>> what shall we do with http://issues.apache.org/jira/browse/WICKET-715?
>> If we want to change it / make
gt; "dangerous" version to use:-( Does this merits rolling out a 1.4.15?
>
> Regards,
>
> Ernesto
>
>
> On Wed, Dec 1, 2010 at 2:26 PM, Johan Compagner
> wrote:
>> that really sounds ...
>
ok this test was then correct that it failed..
Ajax does have to push it to the client because it doesnt know if it
is there yet or not
that you only know because of the id
1.4.14. Could this be related?
>
> Regards,
>
> Ernesto
>
> On Wed, Dec 1, 2010 at 1:34 PM, Johan Compagner wrote:
>> This commits breaks all header contributions when the
>> ajaxrequesttarget has more then 1 component that it must render and
>> the component after t
This commits breaks all header contributions when the
ajaxrequesttarget has more then 1 component that it must render and
the component after the first one also wants to render something in
the head..
i committed a fix:
commit -m "fix form previous commit: 1031432..."
C:/workspace_wicket14/wicket
uch because 1.5 is out
> soonish. IListenerInterfaceTarget { canCallListenerInterface()} is not
> so bad.
>
> -igor
>
> On Wed, Nov 24, 2010 at 8:12 AM, Johan Compagner wrote:
>> yes that i did see in 1.5
>> but in 1.4 i guess the only thing
nabled();
> }
>
> It would solve the problem at the ticket. IMO the proposed interface is
> prolix because the behavior enabled/disabled state is enough information to
> decide to silent return or not an ajax call to it.
>
> On Wed, Nov 24, 2010 at 2:12 PM, Johan Compagner wrote:
that first one is a perfect name, except that the intent is that it
works just the opposite!
:)
On Wed, Nov 24, 2010 at 17:20, Martijn Dashorst
wrote:
> IWontDoAnythingWhenTheComponentIsDisabledBehavior
> IMASlackerBehavior
>
> Martijn
>
> On Wed, Nov 24, 2010 at 5:12 PM, Joha
:
> i added boolean canCallListenerInterface(Component component) to ibehavior
>
> -igor
>
> On Wed, Nov 24, 2010 at 12:54 AM, Johan Compagner
> wrote:
>> which method name?
>>
>> I currently only have a tagging interface that tags this behavior...
>>
>&
+1
On Wed, Nov 24, 2010 at 03:22, Igor Vaynberg wrote:
> the ibehavior interface has become somewhat cluttered and a lot of
> methods in it can have a nice default implementation that works for
> 99% of the usecases. there is no longer a point to having it as an
> interface. this vote is to
>
> -
gt; match?
>
> cheers,
> -igor
>
> On Tue, Nov 23, 2010 at 1:04 PM, Johan Compagner wrote:
>> that i find a big hack
>> then i need to have some none visible (in html not in java) label or
>> something.. thats horrible then i need to add all kinds of stuff.
>>
>
Nov 23, 2010 at 11:02 AM, Johan Compagner wrote:
>
>> i am currently using this patch for our wicket code so that we can move
>> on..
>>
>>
>> First check is that if it is an ajax request for that behavior then
>> just throw an abort exception..
>> Don
est()).isAjax())
+ {
+ throw new AbortException();
+ }
+ return;
+ }
+
+
// Invoke the interface method
behaviorListener.onRequest();
}
On Tue, Nov 23,
hi,
i suddenly bump big time into this issue that is fixed.
( https://issues.apache.org/jira/browse/WICKET-3098 )
I get that disabled behaviors can't be used to do respond, because
that behavior shouldnt be rendered in the first place.
But the fix also goes one step deeper... It also blocks if t
this is known issue from day 1 :)
it is a test that fails 2 times a year.. dont think anybody bothers about it :)
On Sun, Oct 31, 2010 at 14:02, Martin Grigorov wrote:
> Hi,
>
> Locally org.apache.wicket.util.time.TimeOfDayTest.test() fails today due to
> Daylight Time Savings change last night.
should be ok now.
On Sun, Oct 31, 2010 at 12:30, Sebastian wrote:
> hi,
>
> can someone please free some diskspace on the wicketstuff hudson server
> please.
>
> I receive "Error deploying artifact: Error creating temporary file for
> deployment: No space left on device" when trying to trigger a
+1
On Mon, Sep 13, 2010 at 05:45, Igor Vaynberg wrote:
> This vote is to release wicket 1.4.12. This release fixes a critical
> problem with 1.4.11 namely WICKET-3040.
>
> Branch: http://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.12/
> Artifacts:
> http://people.apache.org/~ivaynberg/wic
+1 release
On Sun, Sep 5, 2010 at 05:12, Igor Vaynberg wrote:
> This vote is to release wicket 1.4.11
>
> Branch: http://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.11/
> Artifacts:
> http://people.apache.org/~ivaynberg/wicket-1.4.11/dist
> Maven repo:
> http://people.apache.org/~ivaynber
when do you test this?
((WebRequestCycle)RequestCycle.get()).getWebRequest().getHttpServletRequest().getMethod(),
and why do you care if it is a get or post?
On Thu, Aug 19, 2010 at 22:15, ganesh.k...@gmail.com
wrote:
>
> New Document
>
>
>
>
>
>
> http://x.x.x.x/rootContext/su
cleaned it
On Tue, Aug 17, 2010 at 03:04, Michael O'Cleirigh
wrote:
> Hello,
>
> Hudson on wicketstuff.org is failing to build anything because of a lack of
> temporary space. I created a job to run nightly and attempt to clean up
> some space. Normally I have seen the local repository grow ve
i think this change was triggered by the commit for:
WICKET-1124: enhancement of nested form handling
its like that in the patch we got, i guess the patch is just applied this way.
On Thu, Aug 5, 2010 at 12:38, Florian Wunderlich wrote:
> It can be assumed that an enclosing Form in some way
done, trunk -> wicket
On Thu, Aug 12, 2010 at 17:14, Johan Compagner wrote:
> there is no such file with the extention .warplease ;)
>
> On Thu, Aug 12, 2010 at 17:12, Martin Grigorov wrote:
>> And the same for
>> http://hudson.zones.apache.org/hudson/job/Apache%2
can rename http://wicketstuff.org/wicket/ to
> http://wicketstuff.org/wicket15/ <http://wicketstuff.org/wicket/> ?
>
> On Thu, Aug 12, 2010 at 5:05 PM, Johan Compagner wrote:
>
>> ok if that is stable then thats fine
>> i updated the copywicket14.sh file:
>>
>> w
thats something else but i also fixed that one quickly
On Thu, Aug 12, 2010 at 16:57, Martin Grigorov wrote:
> Is this related to https://issues.apache.org/jira/browse/WICKET-2977 or this
> is something different ?
>
> On Thu, Aug 12, 2010 at 4:23 PM, wrote:
>
>> Author: jcompagner
>> Date: Thu
2, 2010 at 16:55, Martin Grigorov wrote:
> Here is a URL to latest build at Hudson:
> http://hudson.zones.apache.org/hudson/job/Apache%20Wicket%201.4.x/ws/wicket-1.4.x/wicket-examples/target/wicket-examples.war
> I think this is a stable URL so we can use it.
>
> On Thu, Aug 1
i think i can get _16 on it if i get it right.. But not sure if that
would fix your compile problem
On Thu, Aug 12, 2010 at 15:55, Johan Compagner wrote:
> at the moment "1.5.0_13-p7" does run there.
> And i dont know how to update that under freebsd.
>
>
> On T
at the moment "1.5.0_13-p7" does run there.
And i dont know how to update that under freebsd.
On Thu, Aug 12, 2010 at 14:53, Michael O'Cleirigh
wrote:
> Hello,
>
> With the version of java 5 currently installed on wicketstuff.org hudson
> gives build errors with one of the jwicket projects (rela
i see that teamcity is gone now, and we use hudson, but that doesnt
build wicket-examples
So the easy copy file that i have doesnt work anymore..
On Thu, Aug 12, 2010 at 15:09, Martin Grigorov wrote:
> Hi,
>
> I would like to ask wicketstuff.org maintainers to update the examples
> deployed at t
a very old java 5 version??
Java version: 1.5.0_06
thats old..
On Tue, Aug 10, 2010 at 18:56, Martin Grigorov wrote:
> I still don't understand why only Igor had these problems.
>
> On Tue, Aug 10, 2010 at 6:50 PM, Jeremy Thomerson > wrote:
>
>> Nevermind - just saw commits 983268 and 983292.
+1
On Sat, Aug 7, 2010 at 20:23, Igor Vaynberg wrote:
> This vote is to release wicket 1.4.10
>
> Branch: http://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.10/
> Artifacts:
> http://people.apache.org/~ivaynberg/wicket-1.4.10/dist
> Maven repo:
> http://people.apache.org/~ivaynberg/wicket
;
>> On Fri, Jul 23, 2010 at 1:50 AM, Martijn Dashorst
>> wrote:
>> > +1 for Johan's changes to make the surface area of the change smaller.
>> >
>> > I didn't find onInitialize and onConfigure in our code base as well.
>> >
>> > The
e test. But the described problem remains. I
> attached in the Jira another test case, in another package...
>
> On Fri, Jul 23, 2010 at 9:06 AM, Johan Compagner wrote:
>
>> yes if you use the package org.apache.wicket!!!
>> But that is something i definitely dont see as a prob
han, actually it is 2 overridable protected methods that can execute an
> rule already implemented by some custom component.
> I attached an test to via Jira site showing the possible problem.
>
> https://issues.apache.org/jira/browse/WICKET-2960
>
> On Fri, Jul 23, 2010 at 5:38 AM,
we (servoy) dont care much about those changes, they can be left in
(we dont use it and they also dont give us a problem (after my fix ;)
)
the only problem is by the way onInitialize and onConfigure()
Because initialize and also doInitialize() are package scope so they
are not a problem as far
Why do we want already tomcat 7, which is still in a first? beta?
Why not the latest stable 6? Is it really faster and better?
(I havent really looked into 7 yet will do asap)
- Original message -
> OK seems to be a tomcat 7 incompatibility of hudson...
>
> Martijn
>
> On Wed, Jul 21, 2
ng+Hudson#InstallingHudson-Unix%2FLinuxInstallation
>
> You *can* just do:
>
> java -jar hudson.war
>
> and it'll run. That's just a quick way to get it up and running to
> play around with it.
>
> On Wed, Jul 21, 2010 at 9:11 AM, Johan Compagner wrote:
>>
wrote:
> Security needs to be enabled and other stuff. Deploying as a war does
> have some drawbacks: restarting using the UI won't work,
> installing/updating plugins/new versions of hudson is enabled by
> default.
>
> Martijn
>
> On Wed, Jul 21, 2010 at 2:46 PM, Joha
hudson is just a war right?
so that can be dumped by anybody of the wicket devs to onto the tomcat
webapp dir.
What more does hudson need?
On Wed, Jul 21, 2010 at 11:14, Martijn Dashorst
wrote:
> My little bird told me that no build server is part of the new deal
> which is slated to be announc
+1 revert it, i dont see a big pro in having it anyway
On Sat, May 22, 2010 at 09:22, Jeremy Thomerson
wrote:
> As you may have noticed over the past couple of days (ha), there has been
> quite a bit of discussion over what seemed at the time like a very trivial
> change in WICKET-2846 [*]. The
or this problem, I'm very open to
> see it.
>
> Alex
>
>
> On 21 May 2010 00:21, Johan Compagner wrote:
>
>> But this is a very bad design you should use a thread pool for this and
>> not just start new threads when a button is pressed.
>>
>> So
which leaks?
give use a real wicket example where it leaks, which isnt the thread itself
thats the leak.
On Fri, May 21, 2010 at 12:49, Adriano dos Santos Fernandes <
adrian...@gmail.com> wrote:
> On 20/05/2010 19:14, Jeremy Thomerson wrote:
>
>> But it also don't break anything with the ITL, an
+1
(i dont care about the InheritableThreadLocal, if there are really problems
with it we could back it out in the next release)
On Wed, May 19, 2010 at 09:35, Jeremy Thomerson
wrote:
> This vote is to release wicket 1.4.9
>
> Branch: http://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.9
Exactly...
the InheritableThreadLocal is never a problem, its the thread itself not
what it possess
in the other thread this example is given:
final Application application = Application.get();
new Thread(new Runnable()
{
run() {application.xxx}
}).start();
if that thread doesnt die on a re
i still dont see your solution about the wicket thread class.
What should that one do??? give an example.
The best solution is to use a threadpool like a described above.
And yes that InheritableThreadLocal isnt needed then.
But using
final Application app = Application.get()
// start thread
i
If you where using threads in your application
Then i would do it this way:
Your WebApplication class has a method:
getExecutor() that returns a ThreadPoolExecutor
That threadpoolexecutor (that you extend) overrides 2 methods
protected void beforeExecute(Thread t, Runnable r) { }
that sets the
- Original message -
> On 19/05/2010 13:06, Alex Objelean wrote:
> This currently make web-classloader leaks. If you start using
> InheritableThreadLocal's with arbitrary objects, you're going to make
> even more leaks.
>
> Also note, there is something not good here. AFAIK, Wicket sets th
I checked today 2 little things in that i would like to have in the next
build
one of this is a small regression from: WICKET-1825
The other is a small fix for the patch that i did yesterday for modal
window.
On Mon, Apr 26, 2010 at 19:12, Igor Vaynberg wrote:
> this vote is to release wicket
Don't know about the tooling of git not in eclipse
i am monitoring it a bit, but as long as that is not the same as SVN (or
better cvs) i will not use it.
That sf.net outage is already there since pretty much day 1..
Then it works then it doesnt. very weird.
For example wicket-security-1.4 did wor
i cleaned out /var
will talk to seb to just kill those stupid mod_jk logs and httpd-access
i just deleted some log files and now on 22% is used...
On Mon, Apr 19, 2010 at 16:45, Martijn Dashorst
wrote:
> The volume says it's out of diskspace. The following usages are recorded:
>
> 0BTeamC
problem is that we need to roll those var logs better.
With those latest maven fixes for this unique version number problems did
fix most of the hd problems
only var is now an issue because of those logs that are just appending and
appending.
that will not solve even if we just host the examples be
1 - 100 of 577 matches
Mail list logo
