It's not hard to add a pom.xml to a project that is not maven enabled. I did it for clojure and clojure-contrib in 2 minutes total. If it's a git project you can just include them in as a submodule (or ftree in hg or svn externals in svn) and setup up multi- module builds.
Clojure "Ties" would be probably pretty easy to resurrect. That's what I want. http://bitbucket.org/achimpassen/clojure-ties/overview/ It's broken right now pretty badly but I bet someone could fix it up again. On Apr 2, 11:56 am, Laurent PETIT <laurent.pe...@gmail.com> wrote: > Hello, > > 2009/4/2 Jason Sankey <ja...@zutubi.com> > > > > > > > Laurent PETIT wrote: > > > Hi, > > > > 2009/4/2 Jason Sankey <ja...@zutubi.com <mailto:ja...@zutubi.com>> > > > > Ivy [ ... ] also supports pluggable resolvers, so > > > you can host your Jars/dependency information in multiple ways. > > > > Does that mean one could write resolvers to automagically get libraries > > > from "source" repositories such as github, bitbucket, ... (as long as a > > > minimal standard convention for the repositories layout is followed) ? > > > > Clearly identified versions could be directly mapped to tagged branches, > > > and SNAPSHOT versions to the HEAD branch ? > > > > This could be really cool ! :-) > > > I certainly think this is possible. Are you talking about building from > > the source on demand, or having jars stored in the repositories? It > > sounds like the former, in which case I'm not sure if this would be an > > efficient way to do it. > > Honestly, I was talking about the former, thinking that once the library is > recompiled once it could be cached in a local repo for future uses. > > I thought about it because it seems to be the solution that demands the > least from the library developer: no need to subscribe to an external > repository hosting provider for each and every library he makes. But the > second solution is certainly and interesting one, given that some people > seem to already have the proper infrastructure for it! :-) > > > > > Instead, you can just have a build server that builds the projects on > > every change, and publishes the jars to a repository. Apart from the > > efficiency of building only once, the jars would only be published on a > > successful build/test. This is what I have set up now for clojure and > > clojure-contrib onhttp://pulse.zutubi.com/, where the jars go to an > > internal Ivy repository. I believe Howard Lewis Ship also has a build > > server that builds clojure only and publishes it to a Maven repository. > > > I'm happy to expand pulse.zutubi.com if people find it useful to other > > clojure projects, and work on the features of the internal repository. > > > Cheers, > > Jason > > > -- > > Pulse - Continuous Integration made easy. > > Does your project have a pulse? > > Try it free at:http://zutubi.com > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
