Actually, I'm finding that it's not the jars that are a pain... here's what it takes from just plexus and maven to do a 'mvn clean'. I think there's got to be something wrong when you need 38 poms and 4 jars. What could maven legitimately want with the pom file for 5 different versions of plexus-utils?
bash-4.1$ find -name *.jar ./org/apache/maven/plugins/maven-clean-plugin/2.3/maven-clean-plugin-2.3 .jar ./org/apache/maven/shared/file-management/1.2.1/file-management-1.2.1.ja r ./org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.jar ./org/codehaus/plexus/plexus-utils/1.5.6/plexus-utils-1.5.6.jar bash-4.1$ find -name *.pom ./org/apache/apache/3/apache-3.pom ./org/apache/apache/4/apache-4.pom ./org/apache/maven/maven/2.0.2/maven-2.0.2.pom ./org/apache/maven/maven/2.0.6/maven-2.0.6.pom ./org/apache/maven/maven-artifact/2.0.2/maven-artifact-2.0.2.pom ./org/apache/maven/maven-artifact/2.0.6/maven-artifact-2.0.6.pom ./org/apache/maven/maven-artifact-manager/2.0.2/maven-artifact-manager-2 .0.2.pom ./org/apache/maven/maven-artifact-manager/2.0.6/maven-artifact-manager-2 .0.6.pom ./org/apache/maven/maven-model/2.0.6/maven-model-2.0.6.pom ./org/apache/maven/maven-parent/5/maven-parent-5.pom ./org/apache/maven/maven-parent/7/maven-parent-7.pom ./org/apache/maven/maven-parent/9/maven-parent-9.pom ./org/apache/maven/maven-plugin-api/2.0.6/maven-plugin-api-2.0.6.pom ./org/apache/maven/maven-plugin-registry/2.0.6/maven-plugin-registry-2.0 .6.pom ./org/apache/maven/maven-profile/2.0.6/maven-profile-2.0.6.pom ./org/apache/maven/maven-project/2.0.6/maven-project-2.0.6.pom ./org/apache/maven/maven-repository-metadata/2.0.2/maven-repository-meta data-2.0.2.pom ./org/apache/maven/maven-repository-metadata/2.0.6/maven-repository-meta data-2.0.6.pom ./org/apache/maven/maven-settings/2.0.6/maven-settings-2.0.6.pom ./org/apache/maven/plugins/maven-clean-plugin/2.3/maven-clean-plugin-2.3 .pom ./org/apache/maven/plugins/maven-plugins/12/maven-plugins-12.pom ./org/apache/maven/shared/file-management/1.2.1/file-management-1.2.1.po m ./org/apache/maven/shared/maven-shared-components/10/maven-shared-compon ents-10.pom ./org/apache/maven/shared/maven-shared-components/8/maven-shared-compone nts-8.pom ./org/apache/maven/shared/maven-shared-io/1.1/maven-shared-io-1.1.pom ./org/apache/maven/wagon/wagon/1.0-alpha-6/wagon-1.0-alpha-6.pom ./org/apache/maven/wagon/wagon-provider-api/1.0-alpha-6/wagon-provider-a pi-1.0-alpha-6.pom ./org/codehaus/plexus/plexus/1.0.11/plexus-1.0.11.pom ./org/codehaus/plexus/plexus/1.0.12/plexus-1.0.12.pom ./org/codehaus/plexus/plexus/1.0.4/plexus-1.0.4.pom ./org/codehaus/plexus/plexus-container-default/1.0-alpha-9/plexus-contai ner-default-1.0-alpha-9.pom ./org/codehaus/plexus/plexus-container-default/1.0-alpha-9-stable-1/plex us-container-default-1.0-alpha-9-stable-1.pom ./org/codehaus/plexus/plexus-containers/1.0.3/plexus-containers-1.0.3.po m ./org/codehaus/plexus/plexus-utils/1.0.4/plexus-utils-1.0.4.pom ./org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom ./org/codehaus/plexus/plexus-utils/1.4.1/plexus-utils-1.4.1.pom ./org/codehaus/plexus/plexus-utils/1.4.6/plexus-utils-1.4.6.pom ./org/codehaus/plexus/plexus-utils/1.5.6/plexus-utils-1.5.6.pom Now off to run-down junit and classworlds... Patrick Heck ||| Principal Software Engineer Aspen Technology, Inc. ||| +1 781-221-6483 ||| www.aspentech.com -----Original Message----- From: Gordon Cody [mailto:gc...@zafinlabs.com] Sent: Thursday, May 19, 2011 1:35 PM To: Maven Users List Subject: Re: Bootstraping a repository manager Hi Gus We seriously considered trying to implement the type of controls you talked about, but there are literally thousands of files you would have to manually install once you figure out what they all are. What we ended up doing was using the mirroOf feature in settings.xml and allow artifactory to download what it needed and keep it forever. We ran each of the standard mvn commands (and some others) that developers use, in order to populate our artifactory. Once we had all the necessary 3rd party bits & pieces we required, we configured artifactorys 'global offline' mode. Subsequently new jars or new versions of jars are only added manually after approval. Prior to working like this we got burned (once) when an artifact we required (a dependency of a dependency) was missing when we were trying to do a release. That was a bad day we will not ever repeat. -Gord --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org This e-mail and any attachments are intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified any dissemination, distribution or copying of this email, and any attachments thereto, is strictly prohibited. If you receive this email in error please immediately notify the sender and permanently delete the original copy and any copy of any e-mail, and any printout thereof. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
