On Nov 11, 2009, at 2:37 PM, Jukka Zitting 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.
Yeah, but the deploy-file method works fine here. So, I would expect
sign-and-deploy to work too, but alas it doesn't since it does the
wrong setup. See http://old.nabble.com/SignAndDeploy-issue-tt26305689.html#a26305689
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.
Right, but it's almost guaranteed that these artifacts will change
with each release. Once Hadoop does their next release it will all be
moot, since then all artifacts will be available (watchmaker is now
published).
For now, I'm going to revert to just deploy and then upload the
signatures myself.
-Grant
