On Wed, Sep 22, 2010 at 12:16 AM, Anders Hammar <[email protected]> wrote:
> > I don't use git, so I don't know. However, having independent release > cycles > will give you more flexibility at the cost of more complexity. I would > suggest try keeping it simple if possible. However, having a separate > release cycle for things that aren't related makes sense. > The "problem" with git here is more a matter of purity and maintainence, unlike subversion which tags/branches at a directory level, git tags/branches the entire repository, and you can't checkout but a sub-tree of a repository in a manner similar to svn. Ideally you want to have ONLY tags for module-a in module-a's repository - which leads to a "single artifact per repository" pattern, which with 61 sub modules is rather..... horrible ( and git submodules don't really help much here ). > > Also, under Maven 3 you won't get the -SNAPSHOT complaints until the > > current snapshot issues are sorted, > > Not sure what you mean... > > This reference is related to http://jira.codehaus.org/browse/MNG-3092 in which version range resolution removed -SNAPSHOTs from that resolution. I do see that the commit making this change has been reverted now until a better fix is worked out, so for now the problem is not really a problem anymore. > For those that have 1.1/1.2 differences, if you went the route of having > -two- artifacts for the various versions, you could declare the dependency > -and- the version of clojure. Or is the plan to support both versions from > the same artifact? > Not sure I understand. But basically, the end user controls the transitive > dependencies. Your artifacts can't do that. So if he wants to use version A > of Clojure, he can do that regardless of the version of your artifacts he's > using (it might not work though). Would it make sense to use an older > >From my understanding of the clojure-contrib library, there's currently two project trees for clojure 1.1.0 and 1.2.0 - which differ where there are incompatibles in clojure library versions. For these modules - the users choice is "the 1.1.0 version or the 1.2.0 version", rather than which version of clojure to include. Given Stuarts mentioned 61 sub modules, I'd hate to thinking of duplicating all 61 for 1.1.0 and 1.2.0.
