Okay, i found out my build.xml, .classpath, and 1/2 the jars in my lib/
directory were somehow hosed.
1. I've put in a new build.xml with gabriel's changes and my/jody's
changes
2. I put in a build.properties file -- you'll have to edit that to put
your installation specific information in there
This took me a long time to track down and fix - please dont just
overwrite build stuff w/o telling anyone!!!
dave
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/
Okay, i found out my build.xml, .classpath, and 1/2 the jars in my lib/
directory were somehow hosed.
1. I've put in a new build.xml with gabriel's changes and my/jody's
changes
2. I put in a build.properties file -- you'll have to edit that to put
your installation specific information in there
I thinkt that we may not want an build.properties file in svn - this just
moves the location of people's personal changes to a different file. But
if they're still in svn, people will often accidentally commit theirs, and
when someone else does an update they'll have to deal with that. It
mostly depends on how people commit - I personally never commit
everything that's changed, I look at each file to make sure. So we can
just agree to never change the build.properties file. The other option is
to just have a build.properties.sample file in svn, with instrutions to
rename it to build.properties and configure it appropriately.
Chris
This took me a long time to track down and fix - please dont just
overwrite build stuff w/o telling anyone!!!
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
--
Or, option 3:
Put the file in svn, and then have it ignored using prop-set on the server side 
David
Quoting Chris Holmes <cholmes@anonymised.com>:
> Okay, i found out my build.xml, .classpath, and 1/2 the jars in my lib/
> directory were somehow hosed.
>
>
> 1. I've put in a new build.xml with gabriel's changes and my/jody's
> changes
> 2. I put in a build.properties file -- you'll have to edit that to put
> your installation specific information in there
I thinkt that we may not want an build.properties file in svn - this just
moves the location of people's personal changes to a different file. But
if they're still in svn, people will often accidentally commit theirs, and
when someone else does an update they'll have to deal with that. It
mostly depends on how people commit - I personally never commit
everything that's changed, I look at each file to make sure. So we can
just agree to never change the build.properties file. The other option is
to just have a build.properties.sample file in svn, with instrutions to
rename it to build.properties and configure it appropriately.
Chris
>
> This took me a long time to track down and fix - please dont just
> overwrite build stuff w/o telling anyone!!!
>
> 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
>
--
-------------------------------------------------------
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
okay, I put in a generic version.
dave
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/