Jukka has a point that the dependencies don't need to be signed and deployed for each mahout release, but I've done it enough to know that running the dependency deploy by hand from the command-line can be painful. All of the sign-and-deploy stuff (for dependencies) could be moved to to another pom or module and remain unbound to the lifecycle Theoretically, the deps don't even need to be included underneath the main mahout module as long as any committer who changes them makes sure the updated versions are deployed properly.
Maybe that makes things easier to fix? Drew On Wed, Nov 11, 2009 at 2:37 PM, Jukka Zitting <[email protected]> wrote: > Hi, > > On Wed, Nov 11, 2009 at 8:50 PM, Grant Ingersoll <[email protected]> wrote: >> Not following. AFAICT, sign-and-deploy (we just used deploy-file before, >> but that doesn't sign) is specifically for this use case, AIUI . > > Like deploy-file, the sign-and-deploy goal is designed to be used > directly from the command line. Binding it to a normal build lifecycle > can end up overriding some of the default settings, like adding the > "maven/core" base path that you were seeing. > > Instead of running the sign-and-deploy goal within the Mahout release > build should not really be necessary, as you could just run it from > the command line to deploy the artifact. Note that this artifact only > needs to be uploaded once, not per each Mahout release. > > BR, > > Jukka Zitting >
