Hey everyone,
I've been using and evangelizing Maven 2 for a few years now. And yes,
it is really the greatest thing since sliced bread!
However, I've run into one thing makes life with Maven a little less
easy than it should be. Specifically, there are projects out there that
don't have anyone deploying project artifacts to a public Maven 2
repository (or at least they aren't advertising that fact, and I can't
seem to find some of them).
For example, right now I'd like to use a simple in-memory HTTP Server of
some sort for serving RSS. While there is a simple HTTPServer built into
Java 6 (
http://java.sun.com/javase/6/docs/jre/api/net/httpserver/spec/com/sun/net/httpserver/package-summary.html
), a good number of the projects described on
http://java-source.net/open-source/web-servers like Rupy, Simple, etc.
don't have artifacts deployed to http://repo1.maven.org/maven2/ . While
I could install/deploy the required jar(s) locally for my own projects,
I would like to use this in an open-source project without requiring
others to have to manually deploy the jar via installing it specifically
or via deployment to their m2 repo (if they have one setup).
Are there any of you out there that have open-source projects where you
couldn't find a dependency in a public Maven 2 repo, and if you, how did
you handle it?
I've run into issues with some of the Sun jars that have licensing
issues before, but I kind of consider that par for the course for Maven
2 projects. However, it doesn't seem "normal" to make a developer that
wants to build your project have to deploy some other libraries locally
just to build it when there are no licensing issues. So I'm just curious
how you guys usually handle these, if you don't mind me asking.
Thanks!
Gary
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
