Other than that you could file a JIRA against the maven-install-plugin to add a "skip" parameter
2009/9/24 Stephen Connolly <[email protected]>: > either: > > 1. never run as far as install... stop at verify > > or > > 2. run mvn dependency:purge-local-repository > > this is FAD > > 2009/9/24 Royan <[email protected]>: >> >> I've setup a repository manager and would like all of my projects to be >> deployed directly to the repository manager not maven local repository. >> >> Why? I have an environment where I start up my project (which runs on jetty. >> I do it by entering mvn clean install jetty:run from console. This makes >> maven upload all dependencies to its local repository. The problem comes >> when I deploy new snapshot to the repository manager. Because snapshot >> version does not change, when I do "mvn clean install jetty:run" maven finds >> the obsolete dependency in its local repository and continues with the >> startup instead of grabbing the new version from repository manager. >> >> By forbidding maven to upload dependencies to its local repository I'll make >> sure that no obsolete dependency is used to build the project >> -- >> View this message in context: >> http://www.nabble.com/How-to-prohibit-maven-to-copy-built-jars-into-local-repository--tp25572399p25572399.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
