David, you should be able to build your test project just by itself, as a consumer of GeoTools. You should not have to build GeoTools from source. As long as the GeoTools source jars have been downloaded once with -DdownloadSources and stored in your local repository, Maven eclipse:eclipse will notice the GeoTools source jars and attach them to your Eclipse project; you will then be able to step into GeoTools jars, place line breakpoints, and all the other features you would expect from the source debugger.
Consider using a release of GeoTools for the stability of your project, not a snapshot. Is this project meant to be added as a GeoTools module, or only be a consumer of GeoTools? That is, part of GeoTools or depending on GeoTools? At the moment, unless you have edited the poms to make your test project part of the GeoTools project, your project is not included in the build and Eclipse dependency references are resolved to your local repository. The little "M" means db2_test1 is still managed by Eclipse Maven. I would delete it from Eclipse (but not the files on disk; with the unchecked box this just removes the .project and .classpath) then re-create the project files with mvn eclipse:eclipse and re-import. If you do want to build all of GeoTools: Because the GeoTools build is failing for you, your local Maven repository is missing these artifacts. (1) Build everything to populate your local Maven repository, skipping tests to workaround your local failures: mvn -DskipTests -Dall clean install (2) Build Eclipse projects: mvn -DdownloadSources eclipse:clean eclipse:eclipse (3) Import projects into Eclipse. (4) Refresh all projects in Eclipse (I turn off autorefresh in Eclipse options to prevent Eclipse/Maven race conditions). Kind regards, Ben. On 07/12/16 09:53, David Adler wrote: > Ben, > My main reason for using Eclipse is to use the source debugger to trace > through > the GeoTools code at runtime. Is there a better way of doing this just using > Maven? > > Things have gone from bad to worse. My original test project based on the > GeoTools tutorial using Eclipse and the Maven plugin no longer works. All of > the > 17-SNAPSHOT files from my repository seem to have disappeared after running > the > command you suggested. Using the context menu Maven->update project doesn't do > anything useful. > > > In Eclipse, I used FIle->Import->Existing Projects into Workspace. This > created > >100 projects as shown below. > > > If I expand one of the projects, I see the following which has no individual > source files but seems to include the source as a jar file. > > > At this point I'm pretty confused and can't either run my test project or work > with the GeoTools source in Eclipse. At least before when I imported the Maven > project it all seemed to work although it had a bunch of pom.xml errors > reported. > > Regards, > David > > On 12/6/2016 2:34 PM, Ben Caradoc-Davies wrote: >> David, >> >> I always generate projects first and then import into Eclipse. I am using >> Neon.1 on Linux. To generate Eclipse projects (only), I recommend something >> like: >> >> mvn -DdownloadSources eclipse:clean eclipse:eclipse >> >> Eclipse project generation *must* be performed from the top-level directory >> so >> that projects have the correct in-workspace references and do not depend on >> GeoTools jars in your local Maven repository. >> >> I have never had success with the built-in Maven support in Eclipse. I find >> command-line Maven to be powerful and consistent. >> >> Kind regards, >> Ben. >> >> On 07/12/16 04:26, David Adler wrote: >>> Using Eclipse Neon, I imported the Maven project based on the current Git >>> clone. >>> There are over 100 errors, mostly relating to the pom.xml files. >>> >>> Is there a simple fix for this or should I be using a different process like >>> creating an Eclipse project first and then importing into it? >>> >>> >>> >>> -------------------------------------------------------------------------------- >>> Avast logo <https://www.avast.com/antivirus> >>> >>> This email has been checked for viruses by Avast antivirus software. >>> www.avast.com <https://www.avast.com/antivirus> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Developer Access Program for Intel Xeon Phi Processors >>> Access to Intel Xeon Phi processor-based developer platforms. >>> With one year of Intel Parallel Studio XE. >>> Training and support from Colfax. >>> Order your platform today.http://sdm.link/xeonphi >>> >>> >>> >>> _______________________________________________ >>> GeoTools-GT2-Users mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users >>> >> > > > > -------------------------------------------------------------------------------- > Avast logo <https://www.avast.com/antivirus> > > This email has been checked for viruses by Avast antivirus software. > www.avast.com <https://www.avast.com/antivirus> > > -- Ben Caradoc-Davies <[email protected]> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/xeonphi _______________________________________________ GeoTools-GT2-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
