[Rails-devel] project layout

[Rainer M. <rai...@we...>]

> > > >Perhaps it is all worth a try.
> > > I have just checkout rails and use the default .project. Don'nt =
know=20
> > > if it comes with Rails or is the Eclipse default one. But class =
and
> > > java are in
> > > the same dir and that is quit confusing for me.
> >
> > I think that is a difference between Brett's and my setup:
> > I have created subfolders named src and bin for the sources and=20
> > classes, respectively, and I think Brett is using the Eclipse =
default.
> >
> This is true.  I don't change many of Eclipse's defaults.

So you checkout into src and move the files for the higher folder up?
OK - that will work for a while.


> > My main problem was how to get the resources and XMLs in the=20
> > classpath, but somehow I managed.
> >
> > I'm getting the feeling that you know a lot better how to set up =
such=20
> > a project than Brett (sorry if I'm wrong, Brett!) and certainly than =

> > me, and I'm absolutely interested to see a proper one....
> >
> No apology needed. This is true, this is my first real development
project.
>
> I know that there are many things that most software projects do that
we're not doing. I'd love to move toward a more=20
> standardized setup. However, I'd like to see all of the steps involved =
and
make better plans to do it in a way that=20
> doesn't disrupt our ability to still work on the code itself.
>
... (from other mail)
> Rainer - I think this is the core problem I'm having with many of =
these
suggestions.=20
> Instead of learning how we've been >>working, and doing it our way for =
a
while,=20
> you're suggesting a lot of large, drastic changes to accomodate your =
own
preferences.
>
> I think that we should focus more on reaching our existing goals. =20
> So far, I haven't received a patch for the first item you brought up =
(the
disclaimer)=20
> and now you're moving on to suggesting changing our RCS and moving all =
of
our files around=20
> and reworking large portions of our architecture.

Thanks - I'm working as 'software-project-leader' now for about 15 =
Years,
Writing code for about 30 Years, with UI as a main field for about 20 =
Years.
And thats maybe my problem. It's right. You start the project and have =
made
allmost all coding yet. I'm the new one in the project and should follow
you're project style. But if I see somethink, that I do not like, I will
tell you. I make offers, who you can make it better and tell you the
drawbacks. Thats all. I would not have bring up the discussion about =
project
layout if this project is under SubVersion or if I have knew that the
history is not verry valueable for you.=20
Doing thinks step by step is much better!=20
Every project layout change will hold the project at least for the =
hours,
you are doing it. As long as there are only a view people working on it,
that has no impact on the project.
As I said yesterday. I can give you a view on maven project layout on =
rails
or go on with the coding my fist changes on UI - starting sequence and
disclaimer. I like both thinks (both thinks will get me more familar =
with
your code) and you have the choice. So I will do coding tomorrow.
By the way: Everey time a get a new developer in my team, I have the =
same
problem as you have with me :-)

Rainer