On 10/18/07, Borut Bolčina <[EMAIL PROTECTED]> wrote: > Hello, > > can you state pros and cons for your company's maven internal repository > layout. Why (for example) have "internal-snapshots" and "internal" repos.
It is best practice to separate releases from snapshots. In general other people are only interested in the released versions, they are not interested in snapshots unless they want to work on the bleeding edge. A side effect of including snapshots in your release repository is that a snapshot is always considered newer than a release and unless the pom specifies a specific version people will be using (potentially unstable) snapshot versions. See http://docs.codehaus.org/display/MAVENUSER/Using+Maven+in+a+corporate+environment which I wrote up with the reasons for why I laid out Maven, repositories etc in this way. > Which remote repos besides http://repo1.maven.org/maven2 and > http://people.apache.org/repo/m2-snapshot-repository? Any better ones? How > to keep company repo "hygienic"? Again see the above links. I firmly believe that you should not include the maven snapshot repositories in your build, unless you are a maven developer! If you include the maven snapshot repositories then as described above, you will always be using a snapshot version as they are newer than releases. I would really think about that before you choose this path. The alternative is to take a source copy of the plugin you want and to internally release it. This way you know what version revision you took, what patches were applied, and you can reproduce your build internally if you need to. If you are an open source project then this workaround won't help you.
