I have a couple for questions that I'm hoping more out of desperation than anything else have easy positive answers: I'm just about ready to check-in a library called Aperture and all of its dependencies to the JBoss repository. Is there anyone that needs to see or approve how I do this or whether everything I have is accurate? I have a couple of concerns in particular: Many of these dependencies don't seem to exist in any other repository, so I have no source code, JavaDocs, or test code. I don't know how to ensure that the projects are complete in-and-of themselves, outside of their use by Aperture. In other words, individual jars used by Aperture may have other projects and jars they are dependent upon as a whole, but the Aperture distribution may not have included those merely because it doesn't use that functionality (just like our project is doing via explicit exclusions in our poms). Is there any good at least partially automated way to chase down all of these damn dependencies and get them mavenized? I just found another dependency that has its own host of dependencies that were automatically pulled down to my local repository that I now have to track down and migrate to my check-out location, including collecting source code, JavaDocs, test jars, updating the MD5 and SHA1 files....jeez, there's gotta be a better way! Somebody, please say, "Oh yeah, there's a much easier way..."! Thanks, John View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164769#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...