I think one of the problems is there are installation-dependent
information in the build.xml document. Is there some way we can split
it into two file - one with the build information and one with personal
settings.
That way we can just never update our "personal settings" and never
worry about seeing other people's stuff.
dave
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/
dblasby@anonymised.com wrote:
I think one of the problems is there are installation-dependent
information in the build.xml document. Is there some way we can split
it into two file - one with the build information and one with personal
settings.That way we can just never update our "personal settings" and never
worry about seeing other people's stuff.
That is the use of build.properties - good idea dave. Take the personal setting out into a build.properties file ...cholmes used to have the policy of making sure the "default" case contained no personal settings - and would compile against userConfig all ready for a release.
Jody
If my memory serves me correctly I used properties to store this info, so Dave
is this is a concern, please export the properties to a second properties.build
file and include a template only.
David
Quoting dblasby@anonymised.com:
I think one of the problems is there are installation-dependent
information in the build.xml document. Is there some way we can split
it into two file - one with the build information and one with personal
settings.That way we can just never update our "personal settings" and never
worry about seeing other people's stuff.dave
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
build.properties should be where your personal settings go. It might be
useful to have a build.properties.sample to get people started.
On Thu, 24 Feb 2005 dblasby@anonymised.com wrote:
I think one of the problems is there are installation-dependent
information in the build.xml document. Is there some way we can split
it into two file - one with the build information and one with personal
settings.That way we can just never update our "personal settings" and never
worry about seeing other people's stuff.dave
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--