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

[Rod J. <rod...@in...>]

Juergen,

> My main interest is in Spring's web functionality, validation, and the
core infrastructure, so I will generally focus on those.

I would be happy for you to take the lead in the web area, as I don't
anticipate that I'll be looking that much at that area in the near future,
as I'm currently involved mostly in financial middleware. Of course I will
be happy to contribute my ideas and discuss yours.

I think the basic MVC design is very flexible--much more so than Struts--and
very sound.

The validation mechanism, however, needs attention. I think it might aim to
do too much.

The whole issue of how Spring MVC integrates with custom tags etc. is
another interesting point. Personally I think that Struts is too
JSP-centric. I'm not a big fan of JSP. However, the fact is that the main
strength and selling point of Struts is its integration with custom tags.

The Spring philosophy of "don't reinvent the wheel" means that integration
with JSTL is a priority. However, this still leaves some areas unfilled.

Regards,
Rod
----- Original Message -----
From: "jürgen höller [werk3AT]" <jue...@we...>
To: "Spring Developers (E-mail)"
<spr...@li...>
Sent: Thursday, February 13, 2003 5:33 PM
Subject: Re: [Springframework-developer] adding eclipse files to cvs


Hi Trevor, all,

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.

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.

My main interest is in Spring's web functionality, validation, and the core
infrastructure, so I will generally focus on those.

Regards,
Juergen



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



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
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
        <name>springframework</name>
        <comment></comment>
        <projects>
        </projects>
        <buildSpec>
                <buildCommand>
                        <name>org.eclipse.jdt.core.javabuilder</name>
                </buildCommand>
        </buildSpec>
        <natures>
                <nature>org.eclipse.jdt.core.javanature</nature>
        </natures>
</projectDescription>

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

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
.classes
.testclasses
spring-core-0.8.jar
spring-ejbimpl-0.8.jar
spring-jdbc-0.8.jar
spring-web-0.8.jar
target

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

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

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