Re: [Springframework-developer] adding eclipse files to cvs

[<jue...@we...>]

Hi Trevor, all,
=20
I don't mind Eclipse project files being added to the repository. I'm =
using IntelliJ IDEA, by the way - and I love it! Of course, Eclipse is =
fine, too ;-) Maybe I will add an IDEA project file to the repository =
too, if I find enough time to create a clean one.
=20
The current week is a laborious but final week for my company's current =
major project, for the time being. I hope I will be able to dedicate a =
significant part of the next few weeks to infrastructure development for =
the next major project, i.e. digging into Spring and Hibernate. Of =
course, I will use my spare time too, especially for further code review =
and documentation, and comparative research concerning Struts and =
WebWork.
=20
My main interest is in Spring's web functionality, validation, and the =
core infrastructure, so I will generally focus on those.
=20
Regards,
Juergen
=20
=20

	-----Urspr=FCngliche Nachricht-----
	Von: Trevor Cook [mailto:tc...@in...]=20
	Gesendet: Donnerstag, 13. Februar 2003 17:10
	An: Spring Developers (E-mail)
	Betreff: [Springframework-developer] adding eclipse files to cvs
=09
=09

	I hope I'm not being too forward or aggressive in making some =
recommendations for this project.  My experience so far has mainly been =
working solo or in small teams as lead developer, so my experience with =
open source (as a contributor) and large project management is nil.  If =
I'm out to lunch, just let me know.

	I think that the suggestion by "William G. Thompson, Jr." on the Wrox =
board about adding eclipse files is a good one.  It sounds like those so =
far involved (Rod, Yann, and me - not sure what Juergen is using) are =
using eclipse, so adding the few eclipse specific files (.project and =
.classpath) make sense to me.  I would also recommend standarizing on an =
eclipse variable for the one jar we don't distribute (j2ee) as being =
"J2EE_HOME".  Finally, we would need to specify the eclipse output =
folder.  I prefer "target" and eclipse defaults to "build", but I'll use =
whatever the team decides.  To get started though, the files would be as =
follows (subject to any changes recommended by the team):

	.project=20
	<?xml version=3D"1.0" encoding=3D"UTF-8"?>=20
	<projectDescription>=20
	        <name>springframework</name>=20
	        <comment></comment>=20
	        <projects>=20
	        </projects>=20
	        <buildSpec>=20
	                <buildCommand>=20
	                        <name>org.eclipse.jdt.core.javabuilder</name>=20
	                </buildCommand>=20
	        </buildSpec>=20
	        <natures>=20
	                <nature>org.eclipse.jdt.core.javanature</nature>=20
	        </natures>=20
	</projectDescription>=20

	.classpath=20
	<?xml version=3D"1.0" encoding=3D"UTF-8"?>=20
	<classpath>=20
	    <classpathentry kind=3D"src" path=3D"src"/>=20
	    <classpathentry kind=3D"src" path=3D"test"/>=20
	    <classpathentry kind=3D"con" =
path=3D"org.eclipse.jdt.launching.JRE_CONTAINER"/>=20
	    <classpathentry kind=3D"lib" path=3D"lib/clover/clover.jar"/>=20
	    <classpathentry kind=3D"lib" path=3D"lib/easymock/easymock.jar"/>=20
	    <classpathentry kind=3D"lib" path=3D"lib/junit/junit.jar"/>=20
	    <classpathentry kind=3D"lib" =
path=3D"lib/mockobjects/mockobjects-0.07-core.jar"/>=20
	    <classpathentry kind=3D"lib" =
path=3D"lib/velocity/velocity-1.3.jar"/>=20
	    <classpathentry kind=3D"lib" path=3D"lib/log4j-1.2.jar"/>=20
	    <classpathentry kind=3D"lib" =
path=3D"lib/mockobjects/mockobjects-0.07-j1.3-j2ee1.3.jar"/>=20
	    <classpathentry kind=3D"lib" =
path=3D"lib/mockobjects/mockobjects-0.07-jdk1.3.jar"/>=20
	    <classpathentry kind=3D"lib" =
path=3D"lib/velocity/velocity-dep-1.3.jar"/>=20
	    <classpathentry kind=3D"var" path=3D"J2EE_HOME/lib/j2ee.jar"/>=20
	    <classpathentry kind=3D"output" path=3D"target"/>=20
	</classpath>=20

	My other suggestion is partly a question which is adding .cvsignore to =
cvs.  I'm not sure if this is normal/good practice, or just something =
I've been doing.  If we did add it, as a start it would look like:

	junit-reports=20
	.classes=20
	.testclasses=20
	spring-core-0.8.jar=20
	spring-ejbimpl-0.8.jar=20
	spring-jdbc-0.8.jar=20
	spring-web-0.8.jar=20
	target=20

	My last suggestion is actually a response to an email from Rod, which =
I'll quote here to get it out to the team.=20

	>>I'm not sure about mo.whatever: maybe com.interface21.mockobjects=20
	>>would be better--I didn't think very hard about the naming.=20

	I think that "com.interface21.mockobjects" makes a lot more sense. I =
was just recommending mo.xxx to try to match the mo.ejb which already =
existed.  I'll use "com.interface21.mockobjects.jdbc" for the tests I'm =
refactoring.  When the other tests are refactored, we should probably =
move mo.ejb into an equivelent package, and possibly move servletapi as =
well (haven't looked closely enough at those test objects to comment).


	---
	Outgoing mail is certified Virus Free.
	Checked by AVG anti-virus system (http://www.grisoft.com).
	Version: 6.0.449 / Virus Database: 251 - Release Date: 1/27/03
	 =20