Re: [ggc-development] Restructuring of SVN

[Nate B. <nat...@ga...>]

I have to agree with Andy on this one I fond it a hundred times easier
to get the app compiling when the .project files were checked into
SVN.  I think leaving it the old way will discourage other people from
joining.

I do agree with Reinhold that we should check all libs being used into
svn, I think there were only a few that were missing.



On Thu, Jul 3, 2008 at 4:10 AM, Andy Rozman <an...@tr...> wrote:
> Reinhold Rumberger wrote:
>>
>> Apart from using the same library naming structure as you, I would also have
>> to use the same default java version, classpath, etc. ...
>>
>> Because you added the .project and - even worse - the .classpath to the svn,
>> you are forcing me to do it your way, which unluckily doesn't work for me,
>> what with me not using your machine.
>> I've just spend a whole day just getting everything to work again, after the
>> whole thing flew apart with 1000+ errors.
>> Some problems I encountered along the way:
>>   - I named my projects differently, thus fucking the
>>     inter-project-dependencies.
>>   - I use the libs in ggc-support, and only those. I have the ggc-support
>>     project export them to the other projects, so they don't have to worry
>>     about carrying too much bloat.
>>   - I have other projects running and those mostly want the 1.6 JRE - which is
>>     my workspace default. Therefore I can't just use the default JRE.
>>
>> Should you ever try to do something similar again, it wouldn't hurt to consult
>> your teammates beforehand; even if only to avoid pissing them off. Especially
>> since you're using libs that aren't in the svn.
>> Please, never *ever* put .project and .classpath into svn when working in a
>> heterogeneous environment. That way, you're just making live hell for your
>> co-developers.
>>
>>
> Restructuring was made just so that any new user can come and take
> everything without much fuss. You can have normal
> working environment established in about 10 minutes or so. Since we are
> having several project which are bassically interdependent, we
> need to impose some limits.
>
> In worst case you will need to create separate workspace for GGC and
> your other projects. I know this is not best sollution, but it will have
> to do. On how to install everything please take a look at instructions
> in How_Can_I_Help.txt....
>
> You don't have to use my project files I you don't want. Use your own,
> but most users (if we have some new) will have problems with that.
>
> As I see you are working on several projects. Again simplest solution is
> to use several workspaces... This is also not my prefered way,
> but there is not much choice.
>
> I would have rather waited with restructuring for after project was
> released, but I needed to write documentatition and make it very easier
> for 1st time
> developers. As you know we had one new developer joining and he had
> several problems, and he said that most problems were gone after
> restruction
> with little action from his side.
>
> I am still having my hopes up that after first release, we will get a
> LOT of new developers and I wanted it to make using project as easy as
> possible...
> Which means that old cats like two (rumbi and me) of us will have to
> bend our ways a little.
>
> Sorry if you had problems, but it couldn't be avoided. I am also against
> putting project file under source control, but since we now have several
> projects and they are dependant on each other, we had to enforce some
> "rules".  First is naming of projects, and second that of libraries...
> First is
> done by us, and second must be done by users...   Since we are each on
> diferent OS and are using different java, I can't say just use 'java
> 1.5.x',
> I have to specify version (Eclipse does that) I have gone with default.
> Theoreticaly you can develop with 1.6, just be careful that when you put
> code
> in SVN that it's compilable on 1.5. You can do full recompile with ant
> and see if it works...
>
> Again I am sorry for problems you had, but it was required to do that...
>
> Take care,
> Andy
>
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> ggc-development mailing list
> ggc...@li...
> https://lists.sourceforge.net/lists/listinfo/ggc-development
>