-
1. Re: Adding maven projects to the JBoss repository
pgier Jul 16, 2008 12:02 PM (in response to jpav)No one needs to approve what you check in, if there ends up being a problem with it we can fix it or remove it. When you say that the dependencies don't exist in any other repositories where are these coming from? Are these commercial thirdparty jars? If they are, you probably shouldn't check them in unless you know that we have a right to redistribute them. If they are open source projects, then you may want to check something like this site:
http://www.mvnrepository.com/
That will tell you if they exist in the central repository and what groupId/artifactId they are using.
There is not much you can do about missing transitive dependencies. Again this is just an issue of where the jars are coming from. But if your main goal is to put Aperture in the repository and it has all the dependencies it needs, then I think that is ok.
Sorry there is no way to automate mavenization of the dependencies. But if the dependencies you're talking about are being pull from a maven repository, then they are already mavenized, at least to a certain extent. As far as getting a copy of the files for us, hopefully when I get the proxy server set up it can take care of storing a copy of downloaded dependencies for you. -
2. Re: Adding maven projects to the JBoss repository
jpav Jul 16, 2008 12:12 PM (in response to jpav)Thanks, Paul. They are not 3rd-party jars, and I was already checking in the central Maven repository. These come from maven repositories at Aduna and Semweb4j. I guess off I go...