BLUE4A4E ha scritto:
I've seen that running the command "mvn eclipse:eclipse" Maven 2 generates ".classpath" and ".project" files for each module. I haven't understood if doing this operation and importing GeoTools sources into Eclipse, all dependencies described by pom.xml files are mantained: I can build from within Eclipse or I always have to call Maven?
All dependencies are mantained, and with Eclipse you can happily code and have it compile classes. But if by "build" you mean generating jars and putting them into the repository, I guess you have to do it with Maven. A good policy should be to code with the ide, but run a "maven clean install" before committing to make sure everything works as expected even on the command line (for example, in a project here we have tests that run fine in Eclipse but break in maven due to problems in the surefire classloader).
In the latter case I don't know if it is possible to call it from Eclipse as you can see at http://maven.apache.org/guides/mini/guide-ide-eclipse.html#Maven as an external tool <http://maven.apache.org/guides/mini/guide-ide-eclipse.html#Maven as an external tool> or with a tool like Maven 2.x Plug-in for Eclipse ( http://m2eclipse.codehaus.org/ ).
Hum... I don't know. I usually launch maven from the command line for the builds... Cheers Andrea ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
