Justin, > Other devs do this differently but i generally just keep separate > workspaces for geotools and geoserver. If you have the source jars in > your maven repo (which you can get by running mvn eclipse:eclipse with > -DdownloadSources or by compiling geotools locally) then eclipse will > pick them up and allow you to browse the sources as if they were in the > workspace. > > Now when making a change in geotools, to get it picked up you have to: > > 1. make it in your geotools workspace > 2. build the relevant module with maven > 3. refresh your geoserver eclipse workspace > > I have found that once you get used to this it is not too much overhead. > But again, this is just one way to do it.
I ended up doing almost the same - the only difference is that everything is in a single eclipse workspace. but, when I do mvn install in geotools, it takes a lot of time as it goes through all the unit tests. thus, turnaround is slow. Akos ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
