Rather than dump geoserver directly into the geotools svn archive, I wanted to do a test run into an independent repository, in case anything went awry.
http://svn.refractions.net/geoserver/
Once everything is confirmed good in this archive, I can dump it into the main geotools archive.
Currently I only have write access for cholmes and jgarnett. If there are non-geotools developers who are going to need access now (and in the future) I will need logins for them.
I'll also need a list of geoserver developers (as distinct from geotools developers) to set up ACL between the tools/server subdirectories when the time comes. Since everything is served by the same web server, every repository authenticates off the same file, so logins are easily shared between repositories.
Paul
So I think we're good to go on this. All developers I believe now have
the proper accounts. We will be working off of this archive for at
least a few weeks, and then will move over to the svn.geotools.org
domain when we are happy here. I didn't have time to update the docs
today, but will tomorrow or wednesday. But to check out the latest
version of GeoServer you can use the command:
svn co http://svn.refractions.net/geoserver/trunk/geoserver/
Assuming you have subversion.
Paul, when will we be able to get nightly builds going?
More soon.
best regards,
Chris
Quoting Paul Ramsey <pramsey@anonymised.com>:
Rather than dump geoserver directly into the geotools svn archive, I
wanted to do a test run into an independent repository, in case
anything went awry.
http://svn.refractions.net/geoserver/
Once everything is confirmed good in this archive, I can dump it into
the main geotools archive.
Currently I only have write access for cholmes and jgarnett. If there
are non-geotools developers who are going to need access now (and in
the future) I will need logins for them.
I'll also need a list of geoserver developers (as distinct from
geotools developers) to set up ACL between the tools/server
subdirectories when the time comes. Since everything is served by
the
same web server, every repository authenticates off the same file, so
logins are easily shared between repositories.
Paul
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on
ITManagersJournal
Use IT products in your business? Tell us what you think of them.
Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find
out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/
I need the magic incantation for building, and a list of what you want published nightly. Treat me like I have no brain, and this will go smoothly. 
cholmes@anonymised.com wrote:
Paul, when will we be able to get nightly builds going?
So the easiest would probably be for me to make an 'ant nightly' target
that copies all the files I want published into a directory specified
by a dir.nightly.release property? And have the script name the files
according to the date?
Chris
Quoting Paul Ramsey <pramsey@anonymised.com>:
I need the magic incantation for building, and a list of what you
want
published nightly. Treat me like I have no brain, and this will go
smoothly.
cholmes@anonymised.com wrote:
> Paul, when will we be able to get nightly builds going?
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/
On Tue, 2004-10-05 at 06:29, cholmes@anonymised.com wrote:
So the easiest would probably be for me to make an 'ant nightly' target
that copies all the files I want published into a directory specified
by a dir.nightly.release property? And have the script name the files
according to the date?
I would build the WAR nightly ... so you would also need a temp.dir
property.
Might not tag the builds daily though ... more along the tag weekly,
make a snapshot nightly? Just wondering what the lifetime of a nightly
build should be.
David
Chris
Quoting Paul Ramsey <pramsey@anonymised.com>:
> I need the magic incantation for building, and a list of what you
> want
> published nightly. Treat me like I have no brain, and this will go
> smoothly.
>
> cholmes@anonymised.com wrote:
>
> > Paul, when will we be able to get nightly builds going?
>
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
On Tue, 2004-10-05 at 06:29, cholmes@anonymised.com wrote:
> So the easiest would probably be for me to make an 'ant nightly'
target
> that copies all the files I want published into a directory
specified
> by a dir.nightly.release property? And have the script name the
files
> according to the date?
I would build the WAR nightly ... so you would also need a temp.dir
property.
Might not tag the builds daily though ... more along the tag weekly,
make a snapshot nightly? Just wondering what the lifetime of a nightly
build should be.
Let's start with just the war, and after I fix up the binary release to
work completely with ant we can start putting that up. Right now it
depends on the proper docs being generated, and puts the current
geoserver version in the file name. I think a date instead of the
version number makes sense here, as it won't exactly match the version
number. I don't think nightly builds need to have a long lifetime -
they are just for people to get the fixes that aren't yet in a release.
Ok, so the magic incantation for building the war is:
'ant release-war' from the root geoserver directory.
The file created is geoserver/release/geoserver.war
This is the only file (for now) that needs to go in the nightly build
archive. I'll let you know when I fix up geoserver-bin.zip for
nightlies. The release-war target ensures that it is built with the
default configuration.
thanks again,
Chris
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/