You received this message because you are subscribed to the Google Groups "HORN Development" group.
To post to this group, send email to horn-dev...@googlegroups.com.
To unsubscribe from this group, send email to horn-developme...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/horn-development?hl=en.
>Should it not be the job of the OSS project in question to provide stable
Yes, if the user want a stable release then get it from the OSS
website, eg Castle has their releases published at
On Dec 17, 2:04 am, "G. Richard Bellamy" <rbell...@pteradigm.com>
> A set of descriptors pointing to the branch/tags (depending on repo
> type svn/git) perhaps?
> Sent from my mobile device. Please excuse any errors or omissions.
> On Dec 16, 2009, at 5:24 AM, Mauricio Scheffer <mauricioschef...@gmail.com
I have been taking a look at horn a bit, and I had a few ideas. Your
statement about it being good if .NET oss pulling libraries from a
central source is dead on. I think one of the ones that horn could
help facilitate that would be by providing a Maven repository from the
builds it creates.
First, I want to be clear that I am not suggesting projects would have
to use Maven to build their projects -- I don't think this is
reasonable for .NET projects. What I am suggesting is that horn could
build a Maven compatible repository of the binaries it builds. This
is a fairly simple process:
1. You would have to generate a simple XML document that contains the
elements listed on this page: http://maven.apache.org/guides/mini/guide-central-repository-upload.html.
A lot of this data is already in the .boo files in the horn
repository. It looks like the main thing you are missing right now is
version and license, but that simple to collect.
2. Generate a MD5 hash of the DLL and the pom.xml
3. Deploy the built artifacts to a repository, usually available via
HTTP, the following naming convention: /<groupId>/<artifactId>/
<version>/<artifactId>-<version>.<packaging> . Since you are building
from trunk, you would always append the -SNAPSHOT convention after the
Despite many people having a love/hate relationship with the Maven
build tool, the repository format has become the de facto standard for
sharing dependencies. Just to give an idea of some things that have
all standardized on the repository 1) Build tools - Maven, Apache Ivy,
Grails 2) Google Code (for Google releases), TeamCity (can act as an
Ivy repository) 3) Nexus and Artifactory (repository managers). There
is even early gem support for downloading dependencies in the Maven
What would this gain for .NET oss? Even though there are not any
native .NET tools that interface with Maven repository, I've built and
run Ivy with IKVM before and it works great. Since there is already a
community around the repository structure, it just seems to make
sense. Eventually, native .NET tools will source (task libraries for
I think what you are doing with horn is great and has a definite need,
but I think this can take the concept one step further. Like you
said, having a standard way for .NET oss to share libraries would
really be useful -- and help to drive adoption. If you there is some
interest, I would be willing to lend a hand.
On 20 Dec, 05:44, Paul Cowan <dag...@scotalt.net> wrote:
> >> Yes, if the user want a stable release then get it from the OSS website,
> eg Castle has their releases published at
> In an ideal world everybody would be referencing these castle dependencies
> but this is not always the case.
> A lot of projects will still be referencing and have castle binaries from
> the old trunk.
> I have had a nightmare with horn and all the different boo libraries that
> are doing the rounds in various bin folders.
> It would be really good if all .NET oss could pull libraries like boo from a
> central location and perhaps this could help ease the dependency nightmare
> we are all experiencing.
> Paul Cowan
> Cutting-Edge Solutions (Scotland)
> 2009/12/20 John Simons <johnsimons...@yahoo.com.au>
> > > > .
> > > > For more options, visit this group athttp://
> > groups.google.com/group/horn-development?hl=en
> > > > .
> > --
> > You received this message because you are subscribed to the Google Groups
> > "HORN Development" group.
> > To post to this group, send email to horn-dev...@googlegroups.com.
> > To unsubscribe from this group, send email to