Hey Ilia,
Great work !
Maybe the list should be mentioned on the official Wicket homepage or
even maintained there ? It's probably easier to update by just
submitting a pull request on GitHub though...
Cheers,
Tobias
Dear, Wicket users,
Exactly as you are, I love Wicket! It's great
Thank you! I was just looking for chartjs integration :-).
On Tue, Jul 3, 2018 at 10:32 AM, Martijn Dashorst <
martijn.dasho...@gmail.com> wrote:
> Great list! Thanks for maintaining it!
>
> Martijn
>
> On Tue, Jul 3, 2018 at 7:00 AM Илья Нарыжный wrote:
> >
> > Dear, Wicket users,
> >
> >
Great list! Thanks for maintaining it!
Martijn
On Tue, Jul 3, 2018 at 7:00 AM Илья Нарыжный wrote:
>
> Dear, Wicket users,
>
> Exactly as you are, I love Wicket! It's great framework and even modern JS
> frameworks as AngularJS, React and so on - pretty behind Wicket from
> architecture
Dear, Wicket users,
Exactly as you are, I love Wicket! It's great framework and even modern JS
frameworks as AngularJS, React and so on - pretty behind Wicket from
architecture perspective.
Most of us has his/her own set of wicket libs, own wicket-ecosystem.
Lets share our experience, lets share
).
EnD of off topic: Uff ;-)
Robert
- Originálna Správa -
Od: Jonathan Locke
Komu:
Poslaná: 06.09.2007 04:07
Predmet: Re: Wicket libraries
not only would the download be bigger, but there would be all kinds of
licensing headaches. some jar files might not even be legally distributed
HelloWorldApplication
/app/*
---
So please explain me why Tomcat is complaining at deployment time about
velocity just including it in the build path?
Regards
Robo.
- Originálna Správa -
Od: Gwyn Evans
Komu: Robo
Poslaná: 06.09.2007 10:34
Predmet: Re: Wicket libraries
On Thursday, September 6, 2007, 9:52:46 AM, Robo [EMAIL PROTECTED] wrote:
So after I put wicket-velocity jar in my build path, I`m getting
following errors. (I`m using nothing from it and the prove is
when I remove it it deploys OK.)
...
So please explain me why Tomcat is complaining at
Robo wrote:
Ok, seems removing \wicket-velocity-1.3.0-beta3.jar\ from build
path solved problem with velocity problem. But please explain me why
removing package from build path solves the problem if nowhere in my
Hello World code i call for any of the velocity packages. Is there
some
On 06 Sep 2007 11:44:56 +0200 (CEST), Robo [EMAIL PROTECTED] wrote:
Ok Thnaks for explanation.
And do not look for truth in jokes. Jokes are just jokes ;-)
But you are not using Velocity panel right? Why do you include that
jar in the first place? You can just include the core wicket jar.
-
Od: \Eelco Hillenius\
Komu:
Poslaná: 06.09.2007 18:09
Predmet: Re: Re: Wicket libraries stack trace
On 06 Sep 2007 11:44:56 +0200 (CEST), Robo wrote:
Ok Thnaks for explanation.
And do not look for truth in jokes. Jokes are just jokes ;-)
But you are not using Velocity panel
On 06 Sep 2007 17:23:13 +0200 (CEST), Robo [EMAIL PROTECTED] wrote:
And why not? Besides that Wicket is doing some initialization of not used
libraries is there any restriction of not including not neccesary libraries
in classpath? Most time I develop someting I have many libraries in my
Java jars are nto at all complex beast. They become tricky in situation where
you just put some of them inclasspath and they do what you normally do not
expect. Lib should be lib and when not called by developer they should do
nothing. Deliberatly breaking this rule makes the jars, beast
for help and good product. Demo app will be presented week after next
week so we`ll see hov wicket compares to other frameworks.
Robo
- Originálna Správa -
Od: \Eelco Hillenius\
Komu:
Poslaná: 06.09.2007 18:17
Predmet: Re: Re: Re: Wicket libraries stack trace
On 06 Sep 2007 17:23:13
On 06 Sep 2007 18:11:09 +0200 (CEST), Robo [EMAIL PROTECTED] wrote:
After small troubles I had with it I know it. But from my point of view it is
not correct to initiatie not used libraries just by including it in App
Server classpath. From my point of view lib is lib, and when nto called by
: Re: Re: Wicket libraries
Java jars are nto at all complex beast. They become tricky in situation
where you just put some of them inclasspath and they do what you normally
do not expect. Lib should be lib and when not called by developer they
should do nothing. Deliberatly breaking
: 06.09.2007 19:08
Predmet: Re: Re: Re: Re: Wicket libraries stack trace
On 06 Sep 2007 18:11:09 +0200 (CEST), Robo wrote:
After small troubles I had with it I know it. But from my point of view it
is not correct to initiatie not used libraries just by including it in App
Server classpath
You can use Ivy to resolve wicket dependencies and produce a report, if you
have trouble to generate a report with maven ATM. The report details may be
slightly different from what you get with m2, since Ivy is not 100%
compatible with m2, but it's better than nothing. If you're interested, I
can
-
Od: Al Maw
Komu:
Poslaná: 06.09.2007 17:44
Predmet: Re: Wicket libraries
Robo wrote:
Ok, seems removing \\\wicket-velocity-1.3.0-beta3.jar\\\ from build
path solved problem with velocity problem. But please explain me why
removing package from build path solves the problem
On 06 Sep 2007 18:24:44 +0200 (CEST), Robo [EMAIL PROTECTED] wrote:
Sorry Eelco but me and also quite a lot of other developers(I know, contrary
to others developers) consider same b.s. libraries which are \alive\ just
because they are in classpath. It is like talking when nobody asks you ...
On 06 Sep 2007 18:32:44 +0200 (CEST), Robo [EMAIL PROTECTED] wrote:
Yes I know Eelco. That is why there are so much troubles in Java programming
land. Misusing of basic concepts ... That is why one needs some sort of COC,
because there is lot`s of b.s. around ... J2EE 1.4 countained so much
for a Little bit
of sleep. :-))
Bye
Robo
- Originálna Správa -
Od: \Eelco Hillenius\
Komu:
Poslaná: 06.09.2007 19:54
Predmet: Re: Re: Re: Re: Re: Wicket libraries stack trace
On 06 Sep 2007 18:32:44 +0200 (CEST), Robo wrote:
Yes I know Eelco. That is why there are so much troubles
: 06.09.2007 19:36
Predmet: Re: Re: Wicket libraries
On 06 Sep 2007 17:35:26 +0200 (CEST), Robo wrote:
Stop it now please Al. You take oo personal aproach. Nobody forced you
in
responding.
heh, what you have to understand is that wicket is oss - so it IS
personal
Robo wrote:
Why there is no complete distribution of jar`s, needed to run Wicket aplication just
\out of the box\. it is a little bit boring to find out that I also need to
download slf4j and velocity. I uderstand that this info is writen on your page but I
would expect just download one tar
Hi,
You can use maven to build wicket-examples.war which will include all
necessary libs. I think mvn war:war should work.
I just use maven to download all the dependencies and to generate
eclipse project. Then I just open it with eclipse and run the Start class.
Piece a cake!
Robo wrote:
: Wicket libraries
Robo wrote:
Why there is no complete distribution of jar`s, needed to run Wicket
aplication just \\\out of the box\\\. it is a little bit boring to find
out that I also need to download slf4j and velocity. I uderstand that this
info is writen on your page but I would
Robo wrote:
Hello Al.
I worked on some big project where Maven was used(or misused) and form that tme
I refuse to solve Maven troubles so Skipping the Maven stuff as this is nto the
case:
I used to manage dependencies myself and I buil Hello WOrld Application from
scratch. Just Hello World.
On 9/5/07, Al Maw [EMAIL PROTECTED] wrote:
That said, maybe we should provide a separate ZIP with the dependencies.
I guess if you're using Ivy or Maven 2, you're not going to be
downloading the ZIP at all. There may be licensing issues with this,
though. What do people think? Martijn?
why dont we generate the maven stie somewhere? doesnt that have a list of
dependencies for each module?
-igor
On 9/5/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
On 9/5/07, Al Maw [EMAIL PROTECTED] wrote:
That said, maybe we should provide a separate ZIP with the dependencies.
I guess if
Remember the troubles I had with generating the site? Tim was working
on it, but it still is a long shot from being workable.
And yes, it has a list of dependencies, but I don't think they
generate a link to download each and every one of them :|
Martijn
On 9/5/07, Igor Vaynberg [EMAIL
we dont need links, just a list. and i thought the trouble was related to
skinning? if thats still the case can we just put a vanilla maven site on
wicket-stuff or somewhere?
-igor
On 9/5/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
Remember the troubles I had with generating the site? Tim
Skinning was not a problem, just generating a coherent site with just
one command:
cd wicket-1.x
mvn site:deploy
This just doesn't work (tm).
Martijn
On 9/5/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
we dont need links, just a list. and i thought the trouble was related to
skinning? if thats
ah, that blows :|
-igor
On 9/5/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
Skinning was not a problem, just generating a coherent site with just
one command:
cd wicket-1.x
mvn site:deploy
This just doesn't work (tm).
Martijn
On 9/5/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
we
On Wednesday, September 5, 2007, 1:23:42 PM, Robo [EMAIL PROTECTED] wrote:
I worked on some big project where Maven was used(or misused) and
form that tme I refuse to solve Maven troubles so Skipping
the Maven stuff as this is nto the case:
If your experience was with Maven 1, then I can
this message in context:
http://www.nabble.com/Wicket-libraries-tf4383758.html#a12514400
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
34 matches
Mail list logo
