AW: Libraries and projects into SVN

Hi,

Von: Leonardo Laface de Almeida [mailto:leonardo_at_sweda.com.br]
>
> The system here is a bit complex and I will try to explain it.
>
> We have two main projects (P1 and P2). They are compiled in separated
> environments, generating *.exe different files, but they use the same
> source code allocated into a module (M1), that contains some
> functionalities like file system, file transfer, etc.
>
> We have also one library (L1) with 80% of source code equivalent of P1,
> and it is compiled separated from P1, generating a L1.dll file.
>
> The library L1 is used by three other application projects (A1, A2 and
> A3).

This looks like a classical use case for SVN externals. Put the common
code into its own project which is referenced via svn:externals into a
subdirectory of P1, P2 and L1.

> So, three main situations:
>
> 1) When source code from P1 changes module M1, the P2 must have access to
> it, and vice-versa.
> 2) When source code from P1 changes shared code from L1, the L1 source
> code
> must be actualized, and vice-versa.
> 3) When L1.dll changes, A1, A2 and A3 should automatically start to use
> the new L1 created.
>
> I'm still a bit lost here how to share the codes into SVN. I think I may
> create one repository to each one (P1, P2, M1, L1, A1, A2 and A3). The
> problem is doing all svn commands for each one.
>
> For example, If I will change L1, I must to check out P1 and M1 to compile
> it. Then, after changes, I must commit P1, M1 and L1, for source code and
> commit the L1.dll file for A1, A2 and A3. It's unlikelly doing this
> manually.

Svn externals or your build scripts, or even better a continuous integration
Tool can be used to take care of that.

> In other hand, I also think it's unlikelly to create only one repository
> for all these projects.

Why is that unlikely?

The Apache Software Foundation hosts nearly all of their 100+ projects
together in one big Subversion repository.

Each project has its subdirectory, and its own trunk/branches/tags structure
therein. It works fine.

> Finally, our system is a bit more complex than it, but the main structure
> is this.

HTH,

Best regards

Markus Schaber

-- 
___________________________
We software Automation.
3S-Smart Software Solutions GmbH
Markus Schaber | Developer
Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 | Fax +49-831-54031-50
Email: m.schaber@3s-software.com | Web: http://www.3s-software.com 
CoDeSys internet forum: http://forum.3s-software.com
Download CoDeSys sample projects: http://www.3s-software.com/index.shtml?sample_projects
Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915