Thank you for your reply. I think we have combine geotools and geoserver successfully. We use eclpse:eclipse maven plugin and import every geoserver and geotools projects into a single eclipse workspace. But we have to change every geoserver's project dependency about geotools manully, from maven "SNAPSHOT" jars to specified geotools eclipse projects. If not, the modification to geotools's project will not take effect. We prefer eclipse because we need debug across two project sometime. If we want to import more projects like geoapi, shall we do the same thing again? Or if we have to use maven to compile everything?
Then there is another problem. When we compile geoserver using maven, dependent projects (mainly geotools) changes every day, and maven trys to download them each day we first try the compilation (if we use mvn -o option, maven report "Failed to resolve artifact" and the compilation cannot complete). Sometime our modification compile against them. And during our work, http://lists.refractions.net/m2/org/opengis/geoapi/2.2-SNAPSHOT/geoapi-2.2-SNAPSHOT.jar disappeared, We had to manully edit the pom.xml. We need a stable environment, we don't want the code update break our work every day. We need some advice on them. Thank you. On Dec 12, 2007 1:39 PM, Saul Farber <[EMAIL PROTECTED]> wrote: > A really important part of working with geotools/geoserver is to use > maven's "eclipse:eclipse" plugin/goal. > > So start with nothing in your eclipse workspace (delete all projects you > have in eclipse, but leave the svn checkout) > > Then do "mvn clean install" in the root geotools directory (optionally > add "-Dmaven.test.skip if you want to skip tests) > > Then do "mvn -Dmaven.test.skip eclipse:eclipse" > > Then go to eclipse->file->import and choose "import existing projects" > > Choose the root geotools directory and all geotools modules will wind up > with their own eclipse project. > > CLOSE ALL THE ECLIPSE PROJECTS (just "close" them, don't delete them). > > Then pick the module you're interested in, and open it. It will ask you > if you'd like to open dependent projects, and you should say "yes". > > Then go to the eclipse package manager "filters" setting (little "v" in > the upper right) and choose to "hide closed projects". > > Now you're looking at about 6-8 geotools projects that are easily > eclipse buildable (all dependencies on SNAPSHOTS and what-not are > handled by eclipse:eclipse) fairly small and well cross-referenced. > > > That's how I do it! > > --saul > > > > > On Wed, 2007-12-12 at 11:52 +0800, pi3orama wrote: > > Hello every one, we (some graduate students) have some problem: > > We are trying to do some work on geoserver and geotools. We have > > merged geoserver and geotools into a single eclipse workspace (nearly > > 100 projects), but then we find other dependence should be take care > > about, like geoapi and geowidget. Those projects are very activated > > and changing every day, we don't know the SNAPSHOT jar maven download > > match which svn version. > > > > Could any developer tell me how to manage so many projects and > > dependence? Is eclipse a good choice? > > Thany you. > > > > > ------------------------------------------------------------------------- > > SF.Net email is sponsored by: > > Check out the new SourceForge.net Marketplace. > > It's the best place to buy or sell services for > > just about anything Open Source. > > http://sourceforge.net/services/buy/index.php > > _______________________________________________ > > Geotools-devel mailing list > > Geotools-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/geotools-devel > > ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
