Background: In order for the Eclipse editor to function, it needs a .classpath file that defines as Build Path Libraries all the dependency JAR files that appear in any of the CAS 3 POM files. In order to know what to compile, it needs to define Build Path Source directories for all the POM project source directories.
It is easy for the project files to slip one dependency release back level as long as no methods defined by the new release are used. Thus the POM can download foobar-1.2.3.jar while the Eclipse .classpath can call out foobar.1.2.2.jar. Anyone who was using previous releases has the older jar in his maven repository, but someone starting from scratch discovers that Eclipse cannot find the library indicated by the Build Path. I don't have experience with m2eclipse, so I can't say if it will generate the right .classpath file from this particular set of POM files. I would not remove the Eclipse projects unless we were sure they can be automatically regenerated correctly. Problems should be detected if, as part of any release engineering, one deletes the entire .m2/repository and runs mvn to download it again (to make sure that dependencies are downloading and are not just being found because they are already in the repository). After that step, simply opening Eclipse will report a fatal problem if any of the dependencies in the Build Path are not found, and it is easy to update the Libraries to match the release level actually downloaded. However, to make the projects really useful one would ideally have different versions configured for different ways in which a J2EE application can be managed in Eclipse (Europa, Ganymede, MyEclipse). So maybe the various possible Eclipse project files really belong outside the CAS 3 project itself in some other contributed file location that could be synchronized with major releases and might try real hard to keep up with the trunk. (MyEclipse adds editors for HTML, XML, and other file formats and tends to complain when a few header/footer files in the "views" directory have starting but no ending or ending but no starting tags by design. A MyEclipse specific project would have MyEclipse specific configuration to exclude "views" from HTML/XML validation so these files don't generate an error message. I assume other environments have similar but different issues. Maybe someone wants to build a Netbeans project?) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Battaglia Sent: Monday, February 25, 2008 10:48 AM To: CAS Developers Mailing List Subject: [cas-dev] Eclipse project files in Subversion All, Our Eclipse project files are out of sync with the Maven POM (http://www.ja-sig.org/issues/browse/CAS-621). Anyone have any opinions on keeping/removing them and just letting a plugin such as m2eclipse manage the stuff locally? -Scott -- -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________ cas-dev mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas-dev
