Prasad,
I have put some thought into this myself and agree with you. It would be
too much of a hassle for users, I think, if they have to download
subversion and maven along with the sample app, and THEN compile it
before attempting to deploy it. Probably the best thing would be to have
'releases' or snapshots of the sample apps up on the wiki, along with
the source being in the subversion repo.
-Erik
Prasad Kashyap wrote:
While a part of me seems to agree with you that we should remove the
zip file from the samples' wiki pages, a greater part of me feels that
we may be forcing some our users to now get SVN.
A user who just downloads and installs from a binary server will have
no need for svn. But just to get to the samples, he now has to get
SVN.
Then he has to get maven to play with the samples. So we are making
him jump thro' many hoops just to see our prized samples.
Hmm..
Cheers
Prasad
On 10/29/07, Jarek Gawor <[EMAIL PROTECTED]> wrote:
On 10/29/07, Paul McMahan <[EMAIL PROTECTED]> wrote:
One other question -- should we try to have parity between what's in
samples/trunk and what's in the samples section of the wiki? Are
there barriers, technical or otherwise, that make this difficult?
http://cwiki.apache.org/GMOxSAMPLES/index.html
http://svn.apache.org/repos/asf/geronimo/samples/trunk/
Yes, definitely. That was the goal for 2.0 samples at least. The wiki
documentation should be up to date (expect the artifact version) and
all the code in wiki should be in the samples svn. If anything, I
would like to remove the attached sample .zip files from the wiki and
instead direct the users to checkout the sample code from svn.
Also, I think we should release samples at the same time (or close to)
when we release Geronimo.
Jarek
