On Oct 28, 2007, at 3:22 PM, Donald Woods wrote:
Any thoughts on setting up automated builds of Samples at least
once a week?
That would be helpful. Now that we have catalog support in car-maven-
plugin we could also automatically update the online plugins catalog
as well. This would
On 10/28/07, Donald Woods [EMAIL PROTECTED] wrote:
Also, maybe a samples project under the server testsuite dir that
verifies each sample can be installed and functions?
+1 to tests but I would rather put them somewhere with the samples.
Jarek
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?
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
Paul,
I can help you do this.
Cheers
Prasad
On 10/29/07, Paul McMahan [EMAIL PROTECTED] wrote:
On Oct 28, 2007, at 3:22 PM, Donald Woods wrote:
Any thoughts on setting up automated builds of Samples at least
once a week?
That would be helpful. Now that we have catalog support in
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
Binary files in wiki and source in svn? That works for me.
Jarek
On 10/29/07, Erik B. Craig [EMAIL PROTECTED] wrote:
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
When I mentioned parity between svn and the wiki I really meant to
stress the same stuff showing both locations, which I think Jarek's
suggestion would help achieve.Another idea would be to build and
deploy the samples using maven. Then we could point the wiki page at
the maven repo
Then why not make this a real release, with a bin and src zip/tar like
we do for the server?
-Donald
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
+1 to that.
If we released it, then we could point it to the published binaries.
Cheers
Prasad
On 10/29/07, Paul McMahan [EMAIL PROTECTED] wrote:
When I mentioned parity between svn and the wiki I really meant to
stress the same stuff showing both locations, which I think Jarek's
suggestion
+1 to removing all zips from the Wiki and releasing the samples with (or
very quickly) after the server.
-Donald
Jarek Gawor 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
Cool, thanks.
Any thoughts on setting up automated builds of Samples at least once a week?
Also, maybe a samples project under the server testsuite dir that
verifies each sample can be installed and functions?
-Donald
Jarek Gawor wrote:
This should be fixed now plus some other things
I believe there a couple samples still using
org.apache.geronimo.applications instead of the new
org.apache.geronimo.samples groupId
-Donald
Paul McMahan wrote:
Jarek helped on GERONIMO-2784 by moving the samples from server/trunk to
samples/trunk. Now I would like to deploy those
This should be fixed now plus some other things I've found (i.e. licenses).
Jarek
On 10/27/07, Donald Woods [EMAIL PROTECTED] wrote:
I believe there a couple samples still using
org.apache.geronimo.applications instead of the new
org.apache.geronimo.samples groupId
-Donald
Paul
Jarek helped on GERONIMO-2784 by moving the samples from server/trunk
to samples/trunk. Now I would like to deploy those samples to the
ASF snapshot repo so they can still be downloaded/installed from
Geronimo's plugin catalog.This notification starts a 3 day lazy
consensus timer for
I'm wanting to update the tooling build to be able to deploy snapshots
to the remote repo... Could someone point me to an example from the
geronimo tree where and how this goal is being configured?
Thanks
Sachin
Think i figured it out... however when its attempting to upload...
[echo]
Executing cd
/www/cvs.apache.org/repository/geronimo-devtools/poms; chmod g+w
org.apache.geronimo.devtools.eclipse.core-0.5.0-SNAPSHOT.pom; chgrp
maven
I think you need to set:
maven.repo.*.group=apcvs
(where * is the repo name you used)
- Brett
On 10/26/05, Sachin Patel [EMAIL PROTECTED] wrote:
Think i figured it out... however when its attempting to upload...
[echo]
Executing cd
Perfect. Thanks Brett!
Brett Porter wrote:
I think you need to set:
maven.repo.*.group=apcvs
(where * is the repo name you used)
- Brett
On 10/26/05, Sachin Patel [EMAIL PROTECTED] wrote:
Think i figured it out... however when its attempting to upload...
[echo]
Executing
19 matches
Mail list logo
