snarf

i've completed the repackaging task that i began last week.
cosmo and
scooby both are now distributed as webapps, and we now have
a new
project called "snarf" that provides an integrated
bundle:

<http://wiki.osafoundation.org/bin/view/Projects/Sna
rfHome>

now that cosmo and scooby are webapp-only, developers on
those
projects need to set up a runtime environment. snarf works
well for
that:

<http://wiki.osafoundation.org/bin/view/P
rojects/SnarfDevelopmentHome>

should somebody need to hack on snarf itself, here are the
build instructions:

<http://wiki.osafoundation.org/bin/view
/Projects/SnarfBuildInstructions>

bear, i suggest setting up a new tinderbox for snarf that
simply runs
'maven:dist' (there are no build or test steps) and copies
the
generated tarball to the downloads server. when that's
running, let me
know so i can update the docs. there shouldn't be any
changes to the
cosmo and scooby tinderboxes as far as copying their
tarballs.

note that the cosmo and scooby war files are dependencies of
snarf. in
order for the snarf tarball to pick up changes committed to
scooby or
cosmo, those projects' developers need to remember to run
'maven
war:deploy' to copy the wars up to the osaf maven
repository. or i
guess tinderbox could do that too.

also note that cosmo, scooby and snarf are all using the
maven
-SNAPSHOT versioning practice now to indicate continuous or
interim
snapshots that are taken in between formal releases. a
formal snarf
release will be versioned like 'snarf-0.3-0.1' to indicate
that it
includes the 0.3 release of cosmo and the 0.1 release of
scooby. until
there are both formal scooby and cosmo releases, the snarf
version
will be 'snarf-0.3-0.1-SNAPSHOT'.
_______________________________________________
Cosmo mailing list
Cosmoosafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo

On Jan 30, 2006, at 8:31 PM, Brian Moseley wrote:

> i've completed the repackaging task that i began last
week. cosmo and
> scooby both are now distributed as webapps, and we now
have a new
> project called "snarf" that provides an
integrated bundle:

very cool - this will make things cleaner I think in the
distribution 
side of the house

> bear, i suggest setting up a new tinderbox for snarf
that simply runs
> 'maven:dist' (there are no build or test steps) and
copies the
> generated tarball to the downloads server. when that's
running, let me
> know so i can update the docs. there shouldn't be any
changes to the
> cosmo and scooby tinderboxes as far as copying their
tarballs.

I'll do that tomorrow.

> note that the cosmo and scooby war files are
dependencies of snarf. in
> order for the snarf tarball to pick up changes
committed to scooby or
> cosmo, those projects' developers need to remember to
run 'maven
> war:deploy' to copy the wars up to the osaf maven
repository. or i
> guess tinderbox could do that too.
>
> also note that cosmo, scooby and snarf are all using
the maven
> -SNAPSHOT versioning practice now to indicate
continuous or interim
> snapshots that are taken in between formal releases. a
formal snarf
> release will be versioned like 'snarf-0.3-0.1' to
indicate that it
> includes the 0.3 release of cosmo and the 0.1 release
of scooby. until
> there are both formal scooby and cosmo releases, the
snarf version
> will be 'snarf-0.3-0.1-SNAPSHOT'.

What I would like to do is now get rid of the continuous
tarball 
generation that the tinderboxes are doing and replace it by
using the 
maven SNAPSHOT deploy.  What we are doing with the
tinderboxes is 
exactly the same as the maven setup - might as well use it.

What that will mean for IT is that the auto-install scripts
will need 
to either run maven or I'll have to adjust the symlinks and
url's to 
point to the maven repository (which is easy since they are
all on the 
same box).

This will also remove the need for each team to have to
remember to use 
war:deploy on a regular basis.

I'll experiment with this tomorrow and  let you guys know
when it's all 
setup.

---
Bear

Build and Release Engineer
Open Source Applications Foundation (OSAF)
bearosafoundation.org
http://www.osafoundation
.org

bearcode-bear.com
http://code-bear.com

PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822
40B3 CD29


_______________________________________________
Cosmo mailing list
Cosmoosafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo

I think that having a package of Cosmo and Scooby together
is a good  
thing.

I'm not as clear on why this is a separate project.  Are you
really  
going to have a separate subversion, mailing list, irc,
landing pages  
and so forth, just for packaging?

Ted


On Jan 30, 2006, at 5:31 PM, Brian Moseley wrote:

> i've completed the repackaging task that i began last
week. cosmo and
> scooby both are now distributed as webapps, and we now
have a new
> project called "snarf" that provides an
integrated bundle:
>
> <http://wiki.osafoundation.org/bin/view/Projects/Sna
rfHome>
>
> now that cosmo and scooby are webapp-only, developers
on those
> projects need to set up a runtime environment. snarf
works well for
> that:
>
> <http://wiki.osafoundation.org/bin/view/P
rojects/SnarfDevelopmentHome>
>
> should somebody need to hack on snarf itself, here are
the build  
> instructions:
>
> <http
://wiki.osafoundation.org/bin/view/Projects/ 
> SnarfBuildInstructions>
>
> bear, i suggest setting up a new tinderbox for snarf
that simply runs
> 'maven:dist' (there are no build or test steps) and
copies the
> generated tarball to the downloads server. when that's
running, let me
> know so i can update the docs. there shouldn't be any
changes to the
> cosmo and scooby tinderboxes as far as copying their
tarballs.
>
> note that the cosmo and scooby war files are
dependencies of snarf. in
> order for the snarf tarball to pick up changes
committed to scooby or
> cosmo, those projects' developers need to remember to
run 'maven
> war:deploy' to copy the wars up to the osaf maven
repository. or i
> guess tinderbox could do that too.
>
> also note that cosmo, scooby and snarf are all using
the maven
> -SNAPSHOT versioning practice now to indicate
continuous or interim
> snapshots that are taken in between formal releases. a
formal snarf
> release will be versioned like 'snarf-0.3-0.1' to
indicate that it
> includes the 0.3 release of cosmo and the 0.1 release
of scooby. until
> there are both formal scooby and cosmo releases, the
snarf version
> will be 'snarf-0.3-0.1-SNAPSHOT'.
> _______________________________________________
> Cosmo mailing list
> Cosmoosafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo

----
Ted Leung                 Open Source Applications
Foundation (OSAF)
PGP Fingerprint: 1003 7870 251F FA71 A59A  CEE3 BEBA 2B87
F5FC 4B42


_______________________________________________
Cosmo mailing list
Cosmoosafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo