Re: Maven & Repository Layout

Hi,

the question you have to answer is simply:

Are those leaf components used by other parent projects except the one
you described here?

> There is another methodology to create a flat structure for all the
> system components and use the idea of svn:externals to link em all as
> described below.
>
> |--- REPO
> |---- comp1.sub.component1
> |---- comp2.sub2.component1
> |---- branches/
> |---- tags/
> |---- trunk/
> |---- pom.xml
> |---- src
> |---- project ()
You should simply create trunk, tags and branches folders for it, cause
it's part of your release process so you have to make tags for releases
and branches for different development lines...

put the following onto the "trunk".
> |---- pom.xml (Maven project descriptor)
> |---- component 1 (external link to REPO/comp2.sub2.component1/trunk)
>
> In this case the problem of the container componet POM file still exist :(
>
> Is there any recommendation or best practices for the above structure
> or Maven layout.

The other things is never use an external with "/trunk". You should use
"/tags/XXX" instead....

I would suggest to use a simpler layout...
|---Root
| !
| +--- Project
| +-- tags
| +-- branches
| +-- trunk
| +--- pom.xml
| +--- component1
| +--- pom.xml
| +--- component2
| +--- pom.xml
....will be much more simpler to use....

Kind regards
Karl Heinz Marbaise

-- 
SoftwareEntwicklung Beratung Schulung    Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise        ICQ#: 135949029
Hauptstrasse 177                         USt.IdNr: DE191347579
52146 Würselen                           http://www.soebes.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org