You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Les Hazlewood <lh...@apache.org> on 2008/09/14 17:56:56 UTC
1.4-m3 JavaDoc?
I've downloaded 1.4-m3 and don't see it in the .zip. I also can't
find a link to it on the Wicket web site.
I'm afraid it is right in front of my eyes somewhere, but I'm hoping
someone can tell me where it is :)
Thanks,
Les
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: 1.4-m3 JavaDoc?
Posted by Stefan Lindner <li...@visionet.de>.
I built JavaDoc for M3 by myself. If anyone needs a jar file, please contact me.
Stefan
-----Ursprüngliche Nachricht-----
Von: Erik van Oosten [mailto:e.vanoosten@grons.nl]
Gesendet: Sonntag, 14. September 2008 21:02
An: users@wicket.apache.org
Betreff: Re: 1.4-m3 JavaDoc?
Here is the most up to date publicly available wicket javadoc that I
know of (1.4-m2):
http://www.ddpoker.com/javadoc/
Regards,
Erik.
Les Hazlewood wrote:
> This is not a fair statement. Great open source projects accommodate
> the user community when possible, and that includes posting online, at
> a very minimum level, JavaDoc of all things. That I have to download
> and install Maven, and then learn how to run specific targets for a
> build environment is certainly less than ideal when it comes to
> servicing a user community. Why can't I just visit a url that is
> linked to from the release announcement?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: 1.4-m3 JavaDoc?
Posted by Erik van Oosten <e....@grons.nl>.
Here is the most up to date publicly available wicket javadoc that I
know of (1.4-m2):
http://www.ddpoker.com/javadoc/
Regards,
Erik.
Les Hazlewood wrote:
> This is not a fair statement. Great open source projects accommodate
> the user community when possible, and that includes posting online, at
> a very minimum level, JavaDoc of all things. That I have to download
> and install Maven, and then learn how to run specific targets for a
> build environment is certainly less than ideal when it comes to
> servicing a user community. Why can't I just visit a url that is
> linked to from the release announcement?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: 1.4-m3 JavaDoc?
Posted by Les Hazlewood <lh...@apache.org>.
Thanks for your input James.
Lets just make it clear - I don't hate maven at all. I just don't
prefer it. I'm not a 'hater' by any means. I have no problem using
it on projects that are pretty clear cut in structure and don't
require any/much customization.
But let me rephrase what led to my confusion with an example:
In JSecurity, we use Ant + Ivy, and they do pretty much the same
thing. But when we make a JSecurity release, we view it as something
to be publicly used by end-users in projects. Even milestone or
release candidate releases are considered worth doing the normal
release procedure because people want consistency - it is convenient
for the community if all releases are done the same way - people know
where to go for docs, files, etc. Its just nice.
If it is not a publicly available release - that's fine - the
bleeding-edge users can just do an SVN update and build with ant+ivy
as described. No big deal because this is expected when using
bleeding edge software.
But if we made a JSecurity release and told people, "make sure Ant is
installed, then it will download Ivy for you, then download all the
dependencies, and then here are the files, etc, etc", our end-users
would probably complain because what an end-user (not a developer)
typically needs is not readily available.
I guess my point is - and the Wicket community could disagree with me,
and that's totally fine - is that, I, as an end user of a project,
shouldn't have to download and install build tools, then download
dependencies, and then build the software _just_ to use a .jar or read
some documentation. I expect releases to contain these things, or at
the very least a clear pointer to where they are hosted online so I
can access them easily ;)
Now this could just be an example of how the two projects' communities
and/or mentalities are different, and how we define a 'release', and
that's totally cool and I respect that. It is only my opinion (take
it or leave it) that if the Wicket team chooses to adopt this
philosophy, I for one (and probably other end-users) would be a little
happier, that's all ;)
Best regards,
Les
On Mon, Sep 15, 2008 at 7:52 AM, James Carman
<ja...@carmanconsulting.com> wrote:
> Gwyn,
>
> Let me start by saying I am *not* one of those Maven haters. I love
> Maven and I do have it installed and I use it on every project that I
> can. That being said, merely installing Maven isn't the whole story.
> Maven will download a *lot* of jars to your system, as you well know
> (and not just the ones needed for wicket, but everything required by
> whatever maven plugins are being used). When I tell folks to download
> and use maven to get one of my examples up and running, I think this
> is mainly the gripe from folks (aside from the usual "I hate maven
> because so and so hates maven" FUD). Some folks (a lot I'm guessing)
> are behind proxy servers, so that takes a few minutes to figure out
> how it works. With all the "haters" out there, that just gives them
> one more reason to throw their hands in the air and say "maven sucks."
> I guess what I'm trying to say is that we should think about
> including the javadocs and use maven-generated sites (no idea how the
> current site is generated). If you guys want help with that, I'm
> willing to lend a hand. We use maven to generate our projects' entire
> sites at Apache Commons and it works out great. The release plugin
> isn't really set up (out of the box at least) for the way Apache does
> business as far as releases go (create an RC and then release it). We
> have an "rc" profile that we use that helps mold it into what we want,
> though.
>
> On Mon, Sep 15, 2008 at 5:13 AM, Gwyn Evans <gw...@gmail.com> wrote:
>> On Sun, Sep 14, 2008 at 7:28 PM, Les Hazlewood <lh...@apache.org> wrote:
>>> That being said, I love Wicket so far, and enjoy the help received on
>>> this mailing list, and my comments are not meant to be antagonistic by
>>> any means. I would hope that this would lead to some target called
>>> 'release' or something (what we do in the JSecurity project), and then
>>> we upload the resulting .zip to a web server, unzip it, and bam -
>>> everything is publicly available.
>>> The next thing is that if anyone clicks our 'docs' url, they have a
>>> list of all docs for every release that they can click on. You'll
>>> find that this reduces the amount of time you spend answering peoples
>>> questions on the mailing list too ;)
>>
>> Hmm - the amount of time that's taken saying things such as: "For
>> milestone releases, run 'mvn javadoc:javadoc' in the src folder" is a
>> lot less than it would take to building & uploading the artifacts for
>> intermediate releases and is, in the general volume of traffic on the
>> user-list, inconsequental!
>>
>> Note that full releases *do* include apidoc & src jars, but we differ
>> in our interpretation of "very minimum level" - we view that as the
>> source! Having said that, we do supply compiled versions of the
>> source as a convenience to users such that they *don't* need to
>> install Maven, but do tend to expect that developers willing to work
>> with "early release" artifacts be prepared to generate their own
>> javadoc from the sources if they need it.
>>
>> If you do have Maven installed, it's trivial and frankly, these days,
>> there's no excuse not to - you don't have to use it for your own
>> projects, but it's used in enough places that it should be a tool that
>> you have to hand, in the same way that I still have a copy of Ant
>> around
>>
>> /Gwyn
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: 1.4-m3 JavaDoc?
Posted by James Carman <ja...@carmanconsulting.com>.
Gwyn,
Let me start by saying I am *not* one of those Maven haters. I love
Maven and I do have it installed and I use it on every project that I
can. That being said, merely installing Maven isn't the whole story.
Maven will download a *lot* of jars to your system, as you well know
(and not just the ones needed for wicket, but everything required by
whatever maven plugins are being used). When I tell folks to download
and use maven to get one of my examples up and running, I think this
is mainly the gripe from folks (aside from the usual "I hate maven
because so and so hates maven" FUD). Some folks (a lot I'm guessing)
are behind proxy servers, so that takes a few minutes to figure out
how it works. With all the "haters" out there, that just gives them
one more reason to throw their hands in the air and say "maven sucks."
I guess what I'm trying to say is that we should think about
including the javadocs and use maven-generated sites (no idea how the
current site is generated). If you guys want help with that, I'm
willing to lend a hand. We use maven to generate our projects' entire
sites at Apache Commons and it works out great. The release plugin
isn't really set up (out of the box at least) for the way Apache does
business as far as releases go (create an RC and then release it). We
have an "rc" profile that we use that helps mold it into what we want,
though.
On Mon, Sep 15, 2008 at 5:13 AM, Gwyn Evans <gw...@gmail.com> wrote:
> On Sun, Sep 14, 2008 at 7:28 PM, Les Hazlewood <lh...@apache.org> wrote:
>> That being said, I love Wicket so far, and enjoy the help received on
>> this mailing list, and my comments are not meant to be antagonistic by
>> any means. I would hope that this would lead to some target called
>> 'release' or something (what we do in the JSecurity project), and then
>> we upload the resulting .zip to a web server, unzip it, and bam -
>> everything is publicly available.
>> The next thing is that if anyone clicks our 'docs' url, they have a
>> list of all docs for every release that they can click on. You'll
>> find that this reduces the amount of time you spend answering peoples
>> questions on the mailing list too ;)
>
> Hmm - the amount of time that's taken saying things such as: "For
> milestone releases, run 'mvn javadoc:javadoc' in the src folder" is a
> lot less than it would take to building & uploading the artifacts for
> intermediate releases and is, in the general volume of traffic on the
> user-list, inconsequental!
>
> Note that full releases *do* include apidoc & src jars, but we differ
> in our interpretation of "very minimum level" - we view that as the
> source! Having said that, we do supply compiled versions of the
> source as a convenience to users such that they *don't* need to
> install Maven, but do tend to expect that developers willing to work
> with "early release" artifacts be prepared to generate their own
> javadoc from the sources if they need it.
>
> If you do have Maven installed, it's trivial and frankly, these days,
> there's no excuse not to - you don't have to use it for your own
> projects, but it's used in enough places that it should be a tool that
> you have to hand, in the same way that I still have a copy of Ant
> around
>
> /Gwyn
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: 1.4-m3 JavaDoc?
Posted by Gwyn Evans <gw...@gmail.com>.
On Sun, Sep 14, 2008 at 7:28 PM, Les Hazlewood <lh...@apache.org> wrote:
> That being said, I love Wicket so far, and enjoy the help received on
> this mailing list, and my comments are not meant to be antagonistic by
> any means. I would hope that this would lead to some target called
> 'release' or something (what we do in the JSecurity project), and then
> we upload the resulting .zip to a web server, unzip it, and bam -
> everything is publicly available.
> The next thing is that if anyone clicks our 'docs' url, they have a
> list of all docs for every release that they can click on. You'll
> find that this reduces the amount of time you spend answering peoples
> questions on the mailing list too ;)
Hmm - the amount of time that's taken saying things such as: "For
milestone releases, run 'mvn javadoc:javadoc' in the src folder" is a
lot less than it would take to building & uploading the artifacts for
intermediate releases and is, in the general volume of traffic on the
user-list, inconsequental!
Note that full releases *do* include apidoc & src jars, but we differ
in our interpretation of "very minimum level" - we view that as the
source! Having said that, we do supply compiled versions of the
source as a convenience to users such that they *don't* need to
install Maven, but do tend to expect that developers willing to work
with "early release" artifacts be prepared to generate their own
javadoc from the sources if they need it.
If you do have Maven installed, it's trivial and frankly, these days,
there's no excuse not to - you don't have to use it for your own
projects, but it's used in enough places that it should be a tool that
you have to hand, in the same way that I still have a copy of Ant
around
/Gwyn
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: 1.4-m3 JavaDoc?
Posted by Les Hazlewood <lh...@apache.org>.
On Sun, Sep 14, 2008 at 12:38 PM, Martijn Dashorst
<ma...@gmail.com> wrote:
> We just haven't gotten around to making the sites online for our
> releases [1]. The last sites generated online are for 1.3.2 iirc.
>
> Martijn
>
> [1] The maven site plugin was a bit flakey during our release
> building, so we rather invest time in fixing bugs, and improving
> wicket, than putting information on a website that you better include
> in your IDE's dependency management so you have it available without
> having to browse for it. [2]
>
> [2] I do agree that publishing the javadoc improves visibility and
> could be good promotional value (I think Wicket is one of the better
> JavaDoc'd projects out there)
>
> On Sun, Sep 14, 2008 at 6:26 PM, Les Hazlewood <le...@hazlewood.com> wrote:
>> I won't get into how I "should" use maven or not ;)
>
> For all its flaws, I think the Wicket project shows that Maven is not
> the disaster people claim it is. Yes it has its warts, but complaining
> about Maven is often unfounded, based on hear-say and quite frankly
> bullocks. I've been a user of maven since 2004 and have never looked
> back at ant.
Maven isn't a disaster - I just don't prefer it. And since you've
opened the floodgates ;), I've covered a few of my reasons here:
http://www.leshazlewood.com/?p=44
And my complaints at least - and I can't speak for anyone else - are
well founded due to real-world problems using Maven. The kind of
things that make me not like it are rarely seen in open source
projects such as Wicket, and usually has to do with specific build
requirements in corporations or maven customizations with plugins and
maven's 'secret sauce'. (See the comments of that post for a user
that has experienced exactly this).
>
> Using maven can get you a running Wicket project in a matter of
> seconds, *including* javadoc and sources for the Wicket project
> attached to your IDE, which is invaluable during development. Try that
> with your setup. If you'd use maven, this question wouldn't even have
> been asked.
This is not a fair statement. Great open source projects accommodate
the user community when possible, and that includes posting online, at
a very minimum level, JavaDoc of all things. That I have to download
and install Maven, and then learn how to run specific targets for a
build environment is certainly less than ideal when it comes to
servicing a user community. Why can't I just visit a url that is
linked to from the release announcement?
So, I could say the same thing in that "If you'd have posted the
JavaDocs, this question wouldn't have even been asked."
That being said, I love Wicket so far, and enjoy the help received on
this mailing list, and my comments are not meant to be antagonistic by
any means. I would hope that this would lead to some target called
'release' or something (what we do in the JSecurity project), and then
we upload the resulting .zip to a web server, unzip it, and bam -
everything is publicly available.
The next thing is that if anyone clicks our 'docs' url, they have a
list of all docs for every release that they can click on. You'll
find that this reduces the amount of time you spend answering peoples
questions on the mailing list too ;)
Just a suggestion :)
Best regards, and thanks for the clarification,
Les
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: 1.4-m3 JavaDoc?
Posted by Martijn Dashorst <ma...@gmail.com>.
We just haven't gotten around to making the sites online for our
releases [1]. The last sites generated online are for 1.3.2 iirc.
Martijn
[1] The maven site plugin was a bit flakey during our release
building, so we rather invest time in fixing bugs, and improving
wicket, than putting information on a website that you better include
in your IDE's dependency management so you have it available without
having to browse for it. [2]
[2] I do agree that publishing the javadoc improves visibility and
could be good promotional value (I think Wicket is one of the better
JavaDoc'd projects out there)
On Sun, Sep 14, 2008 at 6:26 PM, Les Hazlewood <le...@hazlewood.com> wrote:
> I won't get into how I "should" use maven or not ;)
For all its flaws, I think the Wicket project shows that Maven is not
the disaster people claim it is. Yes it has its warts, but complaining
about Maven is often unfounded, based on hear-say and quite frankly
bullocks. I've been a user of maven since 2004 and have never looked
back at ant.
Using maven can get you a running Wicket project in a matter of
seconds, *including* javadoc and sources for the Wicket project
attached to your IDE, which is invaluable during development. Try that
with your setup. If you'd use maven, this question wouldn't even have
been asked.
Martijn
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: 1.4-m3 JavaDoc?
Posted by Les Hazlewood <le...@hazlewood.com>.
I won't get into how I "should" use maven or not ;)
The Wicket team doesn't make the JavaDoc available online for
milestone releases? I would assume any publicly available release
should be viewable like any other - no?
Thanks,
Les
On Sun, Sep 14, 2008 at 12:17 PM, Martijn Dashorst
<ma...@gmail.com> wrote:
> cd src
> mvn javadoc:javadoc
>
> We don't include the javadoc because it doubles the download size. If
> you use maven (you should), mvn eclipse:eclipse (support for other
> ides varies) in your project will download the src and javadoc jars
> from maven. These will show up in your ide when hovering etc.
>
> Martijn
>
> On Sun, Sep 14, 2008 at 5:56 PM, Les Hazlewood <lh...@apache.org> wrote:
>> I've downloaded 1.4-m3 and don't see it in the .zip. I also can't
>> find a link to it on the Wicket web site.
>>
>> I'm afraid it is right in front of my eyes somewhere, but I'm hoping
>> someone can tell me where it is :)
>>
>> Thanks,
>>
>> Les
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.3.4 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: 1.4-m3 JavaDoc?
Posted by Martijn Dashorst <ma...@gmail.com>.
cd src
mvn javadoc:javadoc
We don't include the javadoc because it doubles the download size. If
you use maven (you should), mvn eclipse:eclipse (support for other
ides varies) in your project will download the src and javadoc jars
from maven. These will show up in your ide when hovering etc.
Martijn
On Sun, Sep 14, 2008 at 5:56 PM, Les Hazlewood <lh...@apache.org> wrote:
> I've downloaded 1.4-m3 and don't see it in the .zip. I also can't
> find a link to it on the Wicket web site.
>
> I'm afraid it is right in front of my eyes somewhere, but I'm hoping
> someone can tell me where it is :)
>
> Thanks,
>
> Les
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org