The newest version of a smack jar in a maven repository is still 2.2.1 (http://repo1.maven.org/maven2/jivesoftware/smack/). So I always have to install the smack jars into my local repository to perform a maven build.
I wanted to open a wish issue on jira, but it seems that I cannot create issues after a new registration.
Any progress on this? I’d be happy to assist in making this happen.
Would it be possible to add a directory in svn to hold the repository info? That way the central maven repo can automatically sync without further user interaction
Someone with Jive would have to do that. Since I do not represent them in any way I wouldn’t be allowed to do this. From the Maven site: “Make sure you provide proof of owning the domain that matches the groupId (see groupId considerations above). Proof means either the server to sync from has a name under that domain, your name shows up in a prominent place in the domain, or you provide a link to a whois database where your name shows up as the domain owner.”
Would someone (maybe you) give me a quick rundown of what it takes to do this? What do you have to host on your own site? I’m not looking for a step by step description or a link to maven’s online docs, but rather a quick “yeah, all you have to do is set up an account with them, point them at your standard download url, and you’re done” or soemthing like that.
I think the simplest way is the create a repository and expose it via subversion. That way, the central maven repositiory can periodically run “svn update” to sync with your repository.
Where do the end users (developers) end up retrieving their copy of the .jar from? In other words, does the central repo cache a copy of the .jar so that the main provider’s site isn’t bombarded with requests? If it’s a simple matter of putting a .jar in an SVN repo, we can certainly do that. But if it means our repos will suddenly get exponentially more hits, we’ll start to run into problems. If it’s a trivial thing and not a maintenance nightmare, I’d see no reason why we couldn’t provide this directly. =)
The end users end up retrieving it from the central maven repository. The central maven repo periodically would sync with your repository to get the new jars, but that is the only entity that would be retrieving the jars from you.
Its not quite as simple as providing just sticking a jar into a svn repo somewhere, the directory structure needs to conform to the maven repository format. Really though, if you create the POM, running the maven “deploy” plugin will create the directory structure for you